This user left Wikipedia. Sumone10154 has not edited Wikipedia since February 21, 2019. As a result, any requests made here may not receive a response. If you are seeking assistance, you may need to approach someone else.
Hello, I am contacting you because you tagged Segs4Vets for speedy deletion. I researched the wikipedia guidelines and researched the organization online and collected all the information to make the article. I researched and found that wikipedia also has articles about other Veteran organizations such as Wounded Warrior Project, AMVETS and Disabled American Veterans. Can you please be specific on what violations that I made, because I have looked over my work and I have not seen it as of yet. Thank you very much Sumone. DavidMinhPham (talk) 21:48, 10 April 2012 (UTC)[reply]
Hello Sumone10154. I am just letting you know that I declined the speedy deletion of Segs4Vets, a page you tagged for speedy deletion, because of the following concern: Article claims coverage in reliable sources. Thank you. — Malik ShabazzTalk/Stalk04:44, 11 April 2012 (UTC)[reply]
Well, if you ever have any questions about it, I'll be happy to answer them for you. I make regular use of its list maker for tasks inside and outside of AWB, so I'm quite familiar with that and its filter. I've used AWB for many thousands of edits, including edits using Regex (regular expressions). I'm now exploring AWB's most tricky features — the ones with no instructions in the manual, like passing arguments and content to external programs and scripts — and will soon have even more tricks to teach. So keep me in mind. Until you need me, have fun. See ya around. The Transhumanist20:53, 23 April 2012 (UTC)[reply]
P.S.: (Assuming you use Firefox), be sure to check out WP:LINKY (no registration needed). -TT
I was trying to figure out one-by-on how AWB's technical features worked (tools menu, etc.), and used its I/O feature to check the results (the AWB manual provides no help at all on the advanced features). I must have somehow hit the save button instead of the skip button. Thank you for fixing it. The Transhumanist20:16, 23 April 2012 (UTC)[reply]
*Why did you revert my edits, WP:SURNAMEclearly states After the initial mention of any name, the person should be referred to by surname only, without an honorific prefix such as "Mr", "Mrs", "Miss", or "Ms". I am reverting the changes back, the least you could've done was make a proper edit summary explaining why you wished to revert the changes. Gsingh (talk) 17:30, 1 May 2012 (UTC)[reply]
Sorry, I realized that you reverted to my revision, in which I had forgot to fix some errors. Please accept my apologies. And great work in reverting vandalism! Gsingh (talk) 17:58, 1 May 2012 (UTC)[reply]
Dear Sumone, I wonder why Gsingh etc do not use the same standards of WP:SURNAME when it comes to Sikh Gurus. Afterall , they are also Gurus only for their disciples and they were perceived as enemies by others. Can you help address these double standards on the part of these users , or maybe some users are not entitled to neutrality.And look at the flaming nostrils in response to your innocuous revert above!!ThanksRealnews7 (talk) 00:28, 3 May 2012 (UTC)
Best regards[reply]
Speedy deletion nomination of St. Paul Athletic Club ice hockey players[edit]
You got my blessing for a speedy deletion of this article. It was intended to be a category, however mistake due to a slow computer speed (on my part) messed me up. Thanks. --Pennsylvania Penguin (talk) 18:26, 2 May 2012 (UTC)[reply]
Hello Sumone10154! I saw you tagged Shakhipur Upazila for WP:CSD#A1CSD#A1. Though you applied the correct criteria but when this criteria is applicable on an article it is suggested to give author some time (preferably 10 minutes) to improve the article. The same is applicable for CSD#A3. Happy editing! --SMSTalk20:39, 2 May 2012 (UTC)[reply]
Convexrook here. I just edited the Stroke page for an assignment. Is it possible for you to let me know where I went wrong and what I could do to make the addition worthwhile. I am not sure what I need to do and I would love to make a worthwhile contribution.
Thank you very much in advance.
Sorry, I didn't see the section on Outcome Measure that you added, so I'll add that back. I think you accidentally put four tildes (~~~~) at the top of the page and that's what I intended to revert. –sumone10154(talk • contribs)01:48, 4 May 2012 (UTC)[reply]
Sorry, no that wasn't vandalism. That was an edit to add context after a discussion on the Talk page of the article with numerous ppl. I won't hold it against you that you failed to notice the difference. ChaseRocker (talk) 01:53, 4 May 2012 (UTC)[reply]
Thank you for pointing that out, Sumone10154! I'm trying my best on to make articles... in fact... this article was from the japanese version of wikipedia. I actually translated the article from the japanese Wikipedia to this one. Search up "COOL&CREATE" on the japanese version!
I see you have already expressed your support for the WMF Travel Guide! I'm just checking to see if you are also aware of the proposal to move the English travel wiki over to WikiVoyage on an interim basis until the big move to WMF happens (or possibly permanently in the event that WMF declines to host a travel wiki). It turns out that, due to the spambot issues and lack of patrolling, edits to Wikitravel are no longer being backed up (I myself only found out recently). I figured I'd let you know since you've made some recent edits to Wikitravel, including new articles. Eco84 | Talk18:29, 18 August 2012 (UTC)[reply]
About the interest of starting a Romanian version of the travel guide, I don't know, there haven't been a single active user (including myself :) for years, this version hasn't grown so I think at least for now, I'm looking forward to seeing anyone interested and having the necessary amount of time to kickstart it again. --Vlad|->09:04, 22 August 2012 (UTC)[reply]
Here's your quick overview of what has been happening around Wikidata over the last week.
Development
Tpt wrote an awesome SpecialPage (Special:EntitiesWithoutLabel) that lists all items without a label in a given language (merged; will be in next deployment)
Tpt changed the page to create new items to allow you to enter links as well
Created patch for review for next deployment on wikidata.org
Hi. Thanks for patrolling recent changes, but you need to be careful about reverting large deletions. Usually they are vandalism, but sometimes the author has blanked his own work, e.g. because it has been tagged for deletion and he realises it is inappropriate. In that case, it is confusing for him if the blanking is reverted and he is accused of vandalism for the blanking; the thing to do is tag it {{db-g7}}. The article Ojapali just now was slightly different; it had been tagged as copyvio, and the author had replaced the long copyvio text with a one-line stub, but once again would be confused to find his copyvio restored. The thing to do is, have a look at the history before deciding to revert a large deletion. Regards, JohnCD (talk) 22:56, 17 November 2012 (UTC)[reply]
Hello, I'm Sumone10154. I noticed that you recently removed some content from Matt Ramsey without explaining why. In the future, it would be helpful to others if you described your changes to Wikipedia with an edit summary. If this was a mistake, don't worry, the removed content has been restored. If you think I made a mistake, or if you have any questions, you can leave me a message on my talk page. Thanks, –sumone10154(talk) 18:17, 17 November 2012 (UTC)
The edit I made (removing a redirect of a US state representative to a pornography actor)
1. was summarized in the "edit summary":
Removed redirect to Peter North (pornography actor)
...which you obviously didn't read, and
2. is undoing obvious vandalism. Matt Ramsey is not Peter North. What more explanation do I need to put into an edit summary? Is it not enough to state that I removed a redirect from one person to another person entirely? I might understand if the name was an alias; in this case, however, it's clearly not. This page really should be reported, it's apparently been redirected to the porn actor for three years, and repeatedly corrected and then revandalized. — Preceding unsigned comment added by Klugerama (talk • contribs) 21:04, 18 November 2012 (UTC)[reply]
Sorry about that, I was unfamiliar with those two people, and assumed the redirect was correct. Next time, you can tag an incorrect redirect for deletion, instead of blanking the page. –sumone10154(talk)03:11, 19 November 2012 (UTC)[reply]
Does not grant you any special status above other editors.
You should probably also read WP:PROTECT, since this user privilege deals largely with page protection. As the requirements for this privilege are still in a state of flux, I would encourage you to keep up to date on the WP:REVIEWER page. Feel free to ask me if you have any questions! Happy editing! Reaper Eternal (talk) 13:23, 19 November 2012 (UTC)[reply]
Hi Sumone10154. While I did just delete the page Association of Dive Program Administrators which you had tagged for speedy deletion, I wanted to let you know that you should not have taggged the page so quickly. You marked the page for speedy deletion only 2 minutes after it was created. For all we know, the creator could have been in the middle of improving the article, but after seeing teh speedy deletion tag, got discouraged and left. As a general rule, you need to wait no less than 15 minutes since the last edit; truth be told, though, for A7 taggings, it's much much better to wait several hours. There's no rush to get A7 material off immediately; a few hours for the person to possibly (in a small number of cases) improve the article is a much better, more friendly approach. Qwyrxian (talk) 04:08, 30 November 2012 (UTC)[reply]
Here's your quick overview of what has been happening around Wikidata over the last week.
Development
Deployed new code on wikidata.org with a lot of bug fixes and a new Special:EntitiesWithoutLabel (all changes here)
http://test2.wikipedia.org now uses Wikidata (click “edit links” at the bottom of the page), and we are working to enable the synchronization of changes to test2 and display links from the repository
Added wbsetqualifier API module
Added wbremovequalifiers API module
New JavaScript wb.Api now used for labels, descriptions, aliases and sitelinks
Improved Selenium tests and PHPUnit tests
Selenium tests now independent from ULS
Selenium tests for statements UI
Existing statements can be edited now
Filtering anons and Wikidata in RecentChanges on client now works correctly
Added extra checks on client RecentChange save point to avoid duplicate entries
Started an experimental branch with API methods for claims
Link to Commons Media displayed for Snak values of related data type
Improved styling of statements in JavaScript mode
Improvements in templating engine
Started working on adding Statements to existing section of Statements
http://test2.wikipedia.org now uses http://wikidata.org for getting language links and wikidata.org edits affecting the existing articles on test2 show up in RecentChanges (if they are not hidden)
Statements (think of “population: 2.000.000” and similar things) are taking shape in the interface. They are still pretty buggy though at this point.
It is now possible to link to images on Wikimedia Commons in a statement (think of “image: sundown_at_the_beach.png” for example)
No longer possible to create new items and set labels when database is set to read-only
Added more tests to the GeoCoordinate parser
Make use of EditEntity in removeclaims API
Removed many singletons to reduce global state
Made SpecialSetLabel work with non-item entities
Improved settings system
Improved options of ValueFormatters
Improved options of ValueParsers
Moved label+description uniqueness check out of transaction to avoid deadlocks and changed it to only be enforced for edits changing any violating values
Fixed serialization of SiteArray
~=[,,_,,]:3
Had to fix reporting of aliases in wbsearchentities again
Implemented integration of baserevids for statements UI API calls for editconflict detection for statements/claims/snaks
Universal Language Selector fallback fix for Selenium tests
Report URL to entity in wbsearchentites API module
Moved the demo system to a larger server
Fixed several bugs in Statements user interface, most notably, adding Statements to existing sections and layout fixes
Added wikibase API module on the client to provide information about the associated repo (e.g. url, script path, article path)
A bunch of messages for autocomments were fixed (they are automatically added as an edit summary for edits on items and co in Wikidata - for example: “Changed [en] description: Finnish rock band”)
Disambiguation link notification for December 17[edit]
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Full course dinner, you added a link pointing to the disambiguation page Punch (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ • Join us at the DPL WikiProject.
Here's your quick overview of what has been happening around Wikidata over the last week. It's rather short this time because pretty much everyone enjoys some well-deserved vacation.
Development
Some of us unwrapped gifts (-:
Started working on supporting different kinds of Snaks in the user interface
Fixing support for PostgreSQL in core, which was broken with introduction of the sites stuff
Code reviewing of changes in MediaWiki core
Adding watchlist filter in client for Wikidata changes
We have an intern for a week, Marius aka User:Hoo man. He’ll be working on the wizard for linking a new Wikipedia article to an existing item or creating a new item for it if none exists yet. (the first two stories here)
Refactored sites code to improve design
Changed item datatype to use entityid as datavalue rather than string
Added lots of new Selenium tests
Changed AbuseFilter so Wikibase can hook into it
Implemented new change dispatcher script
~=[,,_,,]:3
Working on combining successive changes to avoid watchlist clutter
Claims error handling (i.e. they now show error messages when needed)
Implemented initial version of Solr-based search for Wikidata in extension WikibaseSolr
Started investigating use of Lua/Scribunto for the Wikibase client
Deployment of first parts of phase 2 on wikidata.org are planned for February 4 and deployment on English Wikipedia for February 11. See this blog post for details and more dates.
Open Tasks for You
Test statements on the [demo system before the roll-out to wikidata.org on February 4
Support for enhanced recent changes format in client
There are automatic comments for statement edits as well in the history now
Special page for unconnected pages, that is pages on the client that are not connected to items on the repository
Added permission checks for statements, so a user that can not edit will not be able to edit or that only a group can be allowed to do some changes like creating statements
d:User:PinkAmpersand is looking for someone to write a script that once someone has been made an autopatroller, retroactively patrols all of their prior edits
Note: changed day of next German office hour to March 8
Other Noteworthy Stuff
We have a time scheduled when Wikidata will be read-only for a database migration. The window for that is Feb 20 19:00 to Feb 21 2:00 UTC.
New features and bugfixes on Wikidata are planned to be deployed on Monday (Feb 18). This should among other things include:
Showing useful diffs for edits of claims (they’re currently empty)
Automatic comments for editing of claims (there are currently none)
Ability to add items to claims by their ID
Better handling of deleted properties
More results in the entity selector (that’s the thing that lets you select properties, items and so on) so you can add everything and not just the first few matches that are shown
We’re still working on the issue that sometimes editing of certain parts of items or properties isn’t possible. If you’re running into it try to reload the page and/or change the URL to the www. version or the non-www. version respectively.
Deployment on all other Wikipedias is currently planned for March 6 (a note to the Village Pumps of all affected projects will follow soon)
Lots of discussions about certain properties and how they should be used. Current state is at d:Wikidata:List of properties and new ones are being discussed at [d:Wikidata:Property proposal]]
Rollout of phase 1 (language links) on all remaining Wikipedias is still planned for March 6
Next update on wikidata.org is also planned for March 6. This will have bugfixes and if all goes well string as a new available data type.
Proposal was made to the Hungarian, Hebrew and Italian Wikipedias to be the first batch to use phase 2 of Wikidata (infoboxes). Scheduled timeframe for this is end of March
Here's your quick overview of what has been happening around Wikidata over the last week.
Development
More work on widget to add language links on the Wikipedias directly without having to go to Wikidata
Bug fixes for Wikipedias, including:
don't show edit link when noexternallanglinks magic word suppresses Wikidata links (bugzilla:45037)
use Q## links instead of linking to Special:ItemByTitle for “edit links” link (bugzilla:44536)
preference for showing Wikidata edits by default in watchlist (bugzilla:44973)
Catching up on writing tests for untested functionality
More work on the Lua support for accessing data from the repository (wikidata.org) on the Wikipedias
Updated Wikidata’s Vagrant development machine
Created initial QueryStore interface
Created initial setup code for the SQL QueryStore
Discussed and created initial schema for the SQL QueryStore
Simplified code for client settings, including which namespaces can have Wikidata links. The default is now all namespaces, without needing to explicitly specify them in the settings
Improved code for sorting interwiki links in the clients, with step towards allowing the communities to specify custom sort orders per Wikipedia
Improved handling of deleted properties
Further work on replacement for current search box
More work on improving error reporting and edit summaries in the API
Tim and Aaron killed the mystery bug that caused corrupt login tokens (bugzilla:41586)
Asked the Italian, Hebrew and Hungarian Wikipedias if they want to be the first to use phase 2 (will ask a few more to join the first batch later today)
Is a specific bug report really important to you? If you have an account on bugs.wikimedia.org you can easily add yourself to the CC list of the bug and then receive updates about its status via email
Here's your quick overview of what has been happening around Wikidata over the last week.
Development
Design improvements to the SetClaim API module
More work on implementing the simple inclusion syntax that will be 1 way to access Wikidata data on Wikipedia
More work on Lua (the second way to access Wikidata data on Wikipedia)
Added parser page property to hold entity id in client. This fixes:
bugzilla:45037 - don’t show edit link if noexternallanglinks has suppressed all Wikidata links
bugzilla:44536 - have the edit link go directly to the Q### pages, instead of Special:ItemByTitle which shall make the link be more reliable and work for all namespaces
Selenium tests for deleted-property-handling
Selenium tests for multiline references
Selenium tests for add-sitelinks-from-client
Selenium tests for Entity-Selector-as-Searchbox
Selenium tests for language-table
Implemented in-process caching for entities
Lua support to access the repo data and implement getEntity (so you can use stuff like entity = mw.wikibase.getEntity("Q1459") in Lua modules)
rebuildTermSearchKey is now ready for production (this still needs to be run but once done it will make search case-insensitive)
Improved error reports from the API
Ground work for better edit summaries from the API
Added a table of content to item pages
Added debug functionality to be able to investigate why it takes longer than it should for Wikidata changes to show up on recent changes and watchlists on Wikipedia
Finished implementation of References-UI
Implemented GUID generator in JavaScript
Worked on fixing a bug related to deleted properties where the UI would display wrong information
Minor fixes/additions to the JS datamodel implementation
If you add a Babel box to your user page Wikidata will show you items and descriptions in other languages you speak as well without you having to switch the language
Want to know which items use a certain property? Try the “what links here” link on a property page
Thanks for uploading File:Sporcle.PNG. The media description page currently specifies that it is non-free and may only be used on Wikipedia under a claim of fair use. However, it is currently orphaned, meaning that it is not used in any articles on Wikipedia. If the media was previously in an article, please go to the article and see why it was removed. You may add it back if you think that will be useful. However, please note that media for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
If you have uploaded other unlicensed media, please check whether they're used in any articles or not. You can find a list of 'file' pages you have edited by clicking on the "my contributions" link (it is located at the very top of any Wikipedia page when you are logged in), and then selecting "File" from the dropdown box. Note that all non-free media not used in any articles will be deleted after seven days, as described on criteria for speedy deletion. Thank you. Hazard-Bot (talk) 04:51, 30 March 2013 (UTC)[reply]
Hello, Sumone10154. You have new messages at Wikipedia:Help desk. You can remove this notice at any time by removing the {{Interwiki talkback}} or {{Itb}} template.
Copyright checks when performing AfC reviews[edit]
Hello Sumone10154. This message is part of a mass mailing to people who appear active in reviewing articles for creation submissions. First of all, thank you for taking part in this important work! I'm sorry this message is a form letter – it really was the only way I could think of to covey the issue economically. Of course, this also means that I have not looked to see whether the matter is applicable to you in particular.
The issue is in rather large numbers of copyright violations ("copyvios") making their way through AfC reviews without being detected (even when easy to check, and even when hallmarks of copyvios in the text that should have invited a check, were glaring). A second issue is the correct method of dealing with them when discovered.
If you don't do so already, I'd like to ask for your to help with this problem by taking on the practice of performing a copyvio check as the first step in any AfC review. The most basic method is to simply copy a unique but small portion of text from the draft body and run it through a search engine in quotation marks. Trying this from two different paragraphs is recommended. (If you have any question about whether the text was copied from the draft, rather than the other way around (a "backwards copyvio"), the Wayback Machine is very useful for sussing that out.)
If you do find a copyright violation, please do not decline the draft on that basis. Copyright violations need to be dealt with immediately as they may harm those whose content is being used and expose Wikipedia to potential legal liability. If the draft is substantially a copyvio, and there's no non-infringing version to revert to, please mark the page for speedy deletion right away using {{db-g12|url=URL of source}}. If there is an assertion of permission, please replace the draft article's content with {{subst:copyvio|url=URL of source}}.
Some of the more obvious indicia of a copyvio are use of the first person ("we/our/us..."), phrases like "this site", or apparent artifacts of content written for somewhere else ("top", "go to top", "next page", "click here", use of smartquotes, etc.); inappropriate tone of voice, such as an overly informal tone or a very slanted marketing voice with weasel words; including intellectual property symbols (™,®); and blocks of text being added all at once in a finished form with no misspellings or other errors.
Thanks for uploading File:Sporcle.PNG. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
Hello, Sumone10154. Voting in the 2016 Arbitration Committee elections is open from Monday, 00:00, 21 November through Sunday, 23:59, 4 December to all unblocked users who have registered an account before Wednesday, 00:00, 28 October 2016 and have made at least 150 mainspace edits before Sunday, 00:00, 1 November 2016.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Hello, Sumone10154. Voting in the 2017 Arbitration Committee elections is now open until 23.59 on Sunday, 10 December. All users who registered an account before Saturday, 28 October 2017, made at least 150 mainspace edits before Wednesday, 1 November 2017 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Your access to AWB may be temporarily removed[edit]
Hello Sumone10154! This message is to inform you that due to editing inactivity, your access to AutoWikiBrowser may be temporarily removed. If you do not resume editing within the next week, your username will be removed from the CheckPage. This is purely for routine maintenance and is not indicative of wrongdoing on your part. You may regain access at any time by simply requesting it at WP:PERM/AWB. Thank you! — MusikBot IItalk20:27, 9 January 2018 (UTC)[reply]
Your newsletter page is full tot he point where newsletters have stopped being delivered. You need to remove some of the content on that page if you wish for newsletters to return. — billinghurstsDrewth11:44, 25 April 2019 (UTC)[reply]
Hello, and welcome to Wikipedia. Although everyone is welcome to contribute to Wikipedia, at least one of your recent edits, such as the one you made to A picture is worth a thousand words, did not appear to be constructive and has been reverted or removed. Please use your sandbox for any test edits you would like to make, and read the welcome page to learn more about contributing constructively to this encyclopedia. Allens (talk | contribs) 19:03, 30 April 2012 (UTC)[reply]
Thanks for uploading File:Sporcle.PNG. The media description page currently specifies that it is non-free and may only be used on Wikipedia under a claim of fair use. However, it is currently orphaned, meaning that it is not used in any articles on Wikipedia. If the media was previously in an article, please go to the article and see why it was removed. You may add it back if you think that will be useful. However, please note that media for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).
