Requests for Comment/Improvements for notification of global discussions

This Request for Comment is intended to make it so that notification of any global discussions is spread more effectively. After all, as Miraheze's landing page says to be "community-centric", it would be great to have many wiki communities that use Miraheze participate in these discussions, if they choose to. For clarity, global discussions are defined here as discussions that potentially affect any or all of wikis and/or users of Miraheze. Recent Requests for Comment have gotten a central notice and/or an announcement in the Discord server, but I believe that other global discussions, as listed below, should also get a chance, along with some adjustments detailed in the proposals below. K599 (talk) 20:46, 16 August 2021 (UTC)

Global discussions include:
 * Global Requests for Comment
 * Global proposals on community noticeboard
 * Requests for Stewardship (including nomination and revocation)
 * Requests for Global Sysop (including nomination and revocation)
 * Requests for Community Director (including nomination and revocation)

The proposals should apply for all future and ongoing global discussions. In addition, note that the intent of these proposals is to become policy. __NEWSECTIONLINK__

Proposal 1: Central notices
A central notice should be made for each global discussion, lasting for as long as the discussion is open for people to participate.

Support

 * 1) Central notices are a straightforward way of notifying everyone. Having them last for as long as the discussion is open helps to lower the possibility of people missing the discussion even when it’s still open for participation. K599 (talk) 20:48, 16 August 2021 (UTC)
 * 2)  Oh yes, absolutely. To be fair though, it makes it difficult for other users (new and old) to navigate through the requests for whatever permission, as long as they have met the criteria for such requirement. I'm definitely casting a strong support vote on this one. DarkMatterMan4500 (talk) (contribs) 22:39, 18 August 2021 (UTC)
 * 3) Central notices would increase the likelihood of user engagement throughout Miraheze's communities in global discussions. &#32;  Miraheze Logo.svg centrist16 | P mail.svg | Discord color D.svg  &#32; 21:20, 19 August 2021 (UTC)

Oppose

 * 1) A CentralNotice for all types of requests would be nice but may annoy users and in turn cause them to turn them off completely and then cause them to miss important global notices.  Agent Isai  Talk to me! 20:56, 16 August 2021 (UTC)

Comments

 * Just copying from Discord: In the README for the CentralNotice extension, there's a config called $wgCentralNoticeCampaignTypes, which should allow for users to opt out of specific campaign types in their preferences. That way, users can choose to not see, for example, RfS if they aren't interested. K599 (talk) 21:28, 16 August 2021 (UTC)
 * This could be a good idea for more granular sitenotices, certainly better than the "one size fits all" approach we currently do. Allowing communities to opt into specific categories such as say, elections or RfCs (we'd have to define these), would be an improvement over all or nothing. -- Void  Whispers 22:09, 16 August 2021 (UTC)
 * If Fandom had notified people about major changes like domain name and UI then I probably would never have moved to Miraheze so I think that if there was a major one like a domain name change then this would be a good option. ~ El Komodos Drago (talk to me) 21:43, 16 August 2021 (UTC)
 * would it be possible to do this with an alert/notification instead? ~ El Komodos Drago (talk to me) 21:43, 16 August 2021 (UTC)
 * I very, very much prefer exploring this, if it is viable for our current workforce of course. I would rather not try to bend global notices into doing the job. --Raidarr (talk) 13:15, 19 August 2021 (UTC)
 * If this is successful, will it take effect immediately? DarkMatterMan4500 (talk) (contribs) 22:46, 18 August 2021 (UTC)

Proposal 2: Translation of central notices
All central notices should be made translatable. For each central notice, there should be a link to the page where they can be translated, saying "Translate this notice!".

An example of such a central notice is this fundraising notice from early 2020.

Support

 * 1) Translations are important for allowing non-English speakers to understand what's going on. K599 (talk) 20:48, 16 August 2021 (UTC)
 * 2) Translations would be awesome for global notices.  Agent Isai  Talk to me! 20:56, 16 August 2021 (UTC)
 * 3) as a multilingual wiki farm, providing notices in multiple languages should be very important to us. ~ El Komodos Drago (talk to me) 16:38, 19 August 2021 (UTC)
 * 4) Multilingual accessibility lies at the core of this community. &#32;  Miraheze Logo.svg centrist16 | P mail.svg | Discord color D.svg  &#32; 21:20, 19 August 2021 (UTC)

Oppose

 * 1)  Not going to lie, but shouldn't this have been filled automatically a long time ago? DarkMatterMan4500 (talk) (contribs) 22:41, 18 August 2021 (UTC)

Comments

 * This is more of a process change than a community change. I personally have been trying to make sure all central notices get translated, but there isn't really a good system in place to do so yet. For specific implementation, I think we need a translation group of common messages (such as the translate this notice like that would go in every notice), as well as a common setup for all future notices that is easy to implement with the new notice. -- Void  Whispers 22:15, 16 August 2021 (UTC)

Proposal 3: Social media
A post on each of Miraheze's social media accounts should be made for each global discussion. To be clear, Miraheze has a Twitter account and a Facebook account.

Support

 * 1) Good for notifying people using social media. K599 (talk) 20:48, 16 August 2021 (UTC)

Oppose

 * 1) This would be overtly tedious to do and host.  Agent Isai  Talk to me! 20:56, 16 August 2021 (UTC)
 * What do you mean by "host"? I also don't see how this would be "tedious". K599 (talk) 21:00, 16 August 2021 (UTC)
 * If SRE needs to post an important notice, like this one, then by needing community input, the tweet would be delayed. Or what about a simple tweet like this one? Requiring a discussion would be a waste of time and a tedious task for those setting up the vote. Additionally, I'm sure there'd be very low turn out for this. Agent Isai  Talk to me! 21:03, 16 August 2021 (UTC)
 * This proposal does not mean to make it so that a discussion is needed to make a tweet, it means that when a global discussion is started, a tweet is made to let people know. The tweets you listed are not related to this proposal, and it is not being suggested that any community discussion is needed for those kinds of tweets to be made, or any tweets really. K599 (talk) 21:10, 16 August 2021 (UTC)
 * Ah, I see. Thanks for clearing that up! I think it would be useful only if the discussion reaches only a certain threshold (e.g. an RfS reaches 5 supports) to prevent every single request from cluttering up Miraheze's social media feed. For example, if a new user requests Stewardship, it obviously would fail per WP:SNOW so to prevent every single request from receiving a notice posted on social media, I would suggest a minimum threshold for a notice to be pushed out. Agent Isai  Talk to me! 21:15, 16 August 2021 (UTC)
 * This seems sensible. ~ El Komodos Drago (talk to me) 21:44, 16 August 2021 (UTC)
 * Might be worth having such a requirement in place for other forms of notifications as well. -- Void  Whispers 22:16, 16 August 2021 (UTC)

Comments

 * Hmm, this might be tricky to implement, as (in theory), community appointed roles (Stewards and the like) don't have access to the social media accounts. Instead access is limited to technical volunteers. It might be worth discussing opening up additional access, or creating some process by which the community can "stage" messages for social media that a technical volunteer could then post. Thoughts? -- Void  Whispers 22:19, 16 August 2021 (UTC)
 * I think having volunteers who could be able to post notices on social media for this would be good. Agent Isai  Talk to me! 22:43, 16 August 2021 (UTC)
 * Yeah, some sort of "social media manager" role could be a good idea. K599 (talk) 22:55, 16 August 2021 (UTC)
 * how is this phrasing for a new proposal: "A post on each of Miraheze's social media accounts should be made for Requests for Stewardship, Requests for Global Sysop, and Requests for Community Director (all including nomination and revocation) when such requests reach half the number of required support votes (i.e. the support ratio of the minimum number of comments, so 80% of 20 = 16 for Stewards) and Global Requests for Comment and Global proposals on community noticeboard when they reach 3 votes in favour. To be clear, Miraheze has a Twitter account and a Facebook account." ~ El Komodos Drago (talk to me) 16:34, 19 August 2021 (UTC)

Proposal 4: Discord
A message in the #announcements channel of the Discord server should be made for each global discussion.

Support

 * 1) Good for notifying people in the Discord server. K599 (talk) 20:48, 16 August 2021 (UTC)
 * 2)  Agent Isai  Talk to me! 20:56, 16 August 2021 (UTC)
 * 3)  Definitely. Honestly, this should have been done automatically to begin with. DarkMatterMan4500 (talk) (contribs) 22:43, 18 August 2021 (UTC)
 * 4)  due to the frequency of other announcements and because by discords nature all recipients are interested in Miraheze this seems like a no brainer even without any minimum bar for support. ~ El Komodos Drago (talk to me) 13:54, 19 August 2021 (UTC)
 * 5)  A common sense addition that's a quick and convenient way to reach Discord users. &#32;  Miraheze Logo.svg centrist16 | P mail.svg | Discord color D.svg  &#32; 21:20, 19 August 2021 (UTC)