Talk:Global sysops/2013
Latest comment: 10 years ago by Whatamidoing (WMF) in topic Major VisualEditor Rollout coming on Monday
 | Please do not post any new comments on this page. This is a discussion archive first created in 2013, although the comments contained were likely posted before and after this date. See current discussion. |
Inactivity
Just removed the sentence about inactivity which was added in October 2011 as there was clearly no consensus for this change despite this. Trijnsteltalk 22:57, 16 November 2012 (UTC)
- Oh, okey, I've been taking care of monitoring inactivity and had missed that. I will poke you to confirm it and then act upon it. Snowolf How can I help? 10:08, 8 January 2013 (UTC)
- It should be noted that the discussion resulting in "no consensus" was open for far less time and had less input than the one which caused the addition in the first place... whatever. Not my definition of "clearly no consensus" when a month-long discussion fails to garner opposition, and then a two-day long "vote" somehow proves it wrong. Ajraddatz (Talk) 12:23, 8 January 2013 (UTC)
- There are currently two global sysops that would be removed under the current wording of the policy. I am seriously confused as to what I'm supposed to do... Snowolf How can I help? 10:05, 9 January 2013 (UTC)
- I'd just remove them. The added line was never voted on at large anyway, and while I disapprove of the way it is brushed off as having no consensus, a large discussion would probably reveal that. If there are inactive global sysops, they might as well be removed. Ajraddatz (Talk) 11:59, 9 January 2013 (UTC)
- There are currently two global sysops that would be removed under the current wording of the policy. I am seriously confused as to what I'm supposed to do... Snowolf How can I help? 10:05, 9 January 2013 (UTC)
- It should be noted that the discussion resulting in "no consensus" was open for far less time and had less input than the one which caused the addition in the first place... whatever. Not my definition of "clearly no consensus" when a month-long discussion fails to garner opposition, and then a two-day long "vote" somehow proves it wrong. Ajraddatz (Talk) 12:23, 8 January 2013 (UTC)
Requesting unprotection from ko.wikt
Hello, global sysops. Korean Wiktionary agreed to unprotect semi-protected articles and down-protect full protected articles to semi protected which are in specific namespaces (위키낱말사전:, 위키낱말사전토론:, 도움말:). List of the articles can be seen at [1], [2] and [3]. You can find local discussions at ko:wikt:위키낱말사전:자유게시판#보호 문서 해제. Thanks!--관인생략 (talk) 14:03, 2 October 2013 (UTC)
- Hello! I (or another GS/steward) will do this, but next time please make miscellaneous requests on SRM. PiRSquared17 (talk) 14:13, 2 October 2013 (UTC)
- Done. Please note that the cascading protection from wikt:ko:위키낱말사전:편집창 had to be removed as well, as they cannot be applied to autoconfirmed. Regards, Vogone talk 16:25, 2 October 2013 (UTC)
Major VisualEditor Rollout coming on Monday
Just a note to let the global sysops know about a major upcoming rollout to many of our smaller wikis. This page has a full list. For more details, see Whatamidoing's post to the Small Wiki Monitoring team. Regards, PEarley (WMF) (talk) 23:31, 26 November 2013 (UTC)
- Why would global sysops be concerned? Will there probably be an increase in misguided/test/vandalistic edits? PiRSquared17 (talk) 23:33, 26 November 2013 (UTC)
- Just a courtesy note. We don't expect high usage on these wikis. I just thought global sysops should know about the rollout, since they work on these projects occasionally. PEarley (WMF) (talk) 00:17, 27 November 2013 (UTC)
- Will there be a possibilty to disable the VE globally? This tool is rather obstructing my countervandalism work on small wikis than improving it while tagging pages due to the extension's slowness if I accidentally click on the VE button instead on the button which is for the source text. At least this is my experience from the few wikis to which the VE is already deployed. Vogone talk 17:18, 28 November 2013 (UTC)
- As far as I know, Vogone, no. You'd have to do it manually through prefs on each wiki. I will inquire though. PEarley (WMF) (talk) 22:03, 28 November 2013 (UTC)
- Vogone, since you have global JS, you can just use JS to disable VE. I sometimes just use ctrl-e, which gives the normal (old) editing window. You're not the first to ask this. Until global preferences are a reality, the only way to do that is with Pathoschild's/Quentin's script, or my global script (which hopefully will not be needed, because I hope the WMF implements global prefs soon) PiRSquared17 (talk) 22:36, 28 November 2013 (UTC)
- PiRSquared, I think we all wish for global prefs. Right now, with every new wiki I reach, I have to manually reset the settings for the watchlist, or I'll miss things if I'm away from that wiki for more than three days. (Really? Three days? Who thought that would be the ideal setting for most users?)
- Anyway, sysops do actually need to know about this because VisualEditor occasionally has unexpected problems, especially when you hit an odd combination of browser/language/font character. (The wonderful thing about language standards is that there are so many to choose from...) So if you see "vandalism" that trashes every "ෆ" in an article, but also contains something reasonable, and the person is using VisualEditor, then I think it's important for you to spend a second considering whether that is actually the user's fault, rather than a bug in VisualEditor or Parsoid that should be blamed on the devs rather than on the user who accidentally, and probably unknowingly, triggered the bug.
- Vandalism has not changed at Wikipedias where VisualEditor is available. Some good-faith problems decrease (mismatched brackets), and some good-faith problems increase (e.g., putting a ref tag inside your citation, which displays as intended in VisualEditor, but not on the saved page), although each Wikipedia has its own pattern.
- In case of a total emergency-level, trashing-every-page disaster (like we saw a month ago with a Parsoid update), please hit IRC or e-mail James Forrester directly, any time of night or day. They don't want it up if it's causing problems for a specific language. Whatamidoing (WMF) (talk) 18:23, 29 November 2013 (UTC)
- Vogone, since you have global JS, you can just use JS to disable VE. I sometimes just use ctrl-e, which gives the normal (old) editing window. You're not the first to ask this. Until global preferences are a reality, the only way to do that is with Pathoschild's/Quentin's script, or my global script (which hopefully will not be needed, because I hope the WMF implements global prefs soon) PiRSquared17 (talk) 22:36, 28 November 2013 (UTC)
- As far as I know, Vogone, no. You'd have to do it manually through prefs on each wiki. I will inquire though. PEarley (WMF) (talk) 22:03, 28 November 2013 (UTC)
- Will there be a possibilty to disable the VE globally? This tool is rather obstructing my countervandalism work on small wikis than improving it while tagging pages due to the extension's slowness if I accidentally click on the VE button instead on the button which is for the source text. At least this is my experience from the few wikis to which the VE is already deployed. Vogone talk 17:18, 28 November 2013 (UTC)
- Just a courtesy note. We don't expect high usage on these wikis. I just thought global sysops should know about the rollout, since they work on these projects occasionally. PEarley (WMF) (talk) 00:17, 27 November 2013 (UTC)