Requests for Comment/Central notice changes

These are a couple of proposals related to central notices, previously from Requests for Comment/Improvements for notification of global discussions where they happened to have failed due to insufficient consensus. Hopefully a more clear consensus can be found in this discussion. __NEWSECTIONLINK__

Proposal 1: Central notice duration
Central notices for discussions should last while the discussion is open for people to participate. As in, the central notice would only be removed after the discussion is resolved.

Support

 * 1) Having notices last while the discussion is still open helps to lower the possibility of people missing the discussion even when it’s still open for participation. K599 (talk) 18:50, 19 November 2021 (UTC)

Oppose

 * 1) Vague proposal, doesn't define anything.  Agent Isai  Talk to me! 16:04, 22 November 2021 (UTC)

Comments

 * This proposal is rather vague, what is the definition of 'discussion' in this context? Agent Isai  Talk to me! 20:28, 19 November 2021 (UTC)
 * I would think that the definition of a discussion would be obvious, but I guess since it's been asked, a discussion is a sort of gathering of people, open to any user in this case, where they discuss a sort of change, generally to the workings of a system, or to elect an individual to a position.
 * Or we could just say, from the campaign types being proposed below, Requests for Comment, Requests for Stewardship, Requests for Global Sysop, and Requests for Community Director. You could also just say any sort of proposal in general to summarize the above. K599 (talk) 22:15, 19 November 2021 (UTC)

Proposal 2: Make campaign types for central notices
A campaign type can be set for central notice campaigns, allowing users to opt out of specific campaign types in their preferences, specifically in the "Banners" section. Here is a proposal for what campaign types Miraheze should use:
 * Fundraising
 * Surveys
 * Maintenance
 * Requests for Comment
 * Requests for Stewardship
 * Requests for Community Director

To make it clear how to use preferences to opt-out of campaign types, some text instructing people how to do so should be added to central notices.

In technical terms, campaign types are configured with $wgCentralNoticeCampaignTypes in LocalSettings.php.

Support

 * 1) Campaign types would be a good way for individual users to have better control over what kinds of central notices they would see. K599 (talk) 18:50, 19 November 2021 (UTC)

Comments

 * On another note, this can presumably work with ManageWiki to apply for a whole wiki. To sysadmins, this would presumably be done by using a custom variable to set $wgDefaultUserOptions['centralnotice-display-campaign-type-whatever'] = 0. K599 (talk) 18:50, 19 November 2021 (UTC)
 * I feel like this is out of scope in part for an RfC. If anything, the suggestion should be moved to Phabricator or first discussed on #miraheze-sre on IRC/Discord for a technical discussion. Agent Isai  Talk to me! 20:31, 19 November 2021 (UTC)
 * My thinking is that the list of campaign types to be used should have the consensus of the communities. K599 (talk) 22:18, 19 November 2021 (UTC)

Include RfGS as a campaign type
Include Requests for Global Sysop in the list of campaign types.

Support

 * 1) This is a global role that is granted major abilities, such as globally locking users. I think that should at least be considered. K599 (talk) 18:50, 19 November 2021 (UTC)

Oppose

 * 1) Partially in part per my above point that this might be better suited for discussion first on #miraheze-sre but even if that weren't the case, I feel like both Global Sysops and Steward requests should be included in one category as both have powerful effects globally.  Agent Isai  Talk to me! 20:39, 19 November 2021 (UTC)
 * Well, whether those requests should be partitioned or not would be one particular thing that I think can be discussed in this RfC. K599 (talk) 22:21, 19 November 2021 (UTC)