Change Details

The MVP release of Community Configuration 2.0 will only be editable by Admins, but in the future there might be certain configuration changes that should be editable by other user groups or attached to a certain user right. Project info: https://www.mediawiki.org/wiki/Community_configuration ####User story & summary: As a Steward, I want to enable 'emergency CAPTCHAs' for anonymous IP edits {T303433} As a Event Coordinator, I want to adjust community configuration for the newcomer homepage's [[ https://www.mediawiki.org/wiki/Growth/Community_Updates | Community Updates module ]]. ####Background & research: This task is important because communities need the ability to customize features for their wikis, but not all configuration settings need to be tied to adminship. ####Questions: - Are edit rights limited by Community Configuration page, section within the page, or individual Configuration variable? - How can we ensure it's clear who has edit access to certain Community Configuration forms (or sections of the form)? ####Designs: TBD ####Acceptance Criteria: TBD

The MVP release of Community Configuration 2.0 will only be editable by Admins, but in the future there might be certain configuration changes that should be editable by other user groups or attached to a certain user right. Project info: https://www.mediawiki.org/wiki/Community_configuration ####User story & summary: As a Steward, I want to enable 'emergency CAPTCHAs' for anonymous IP edits {T303433} As a Event Coordinator, I want to adjust community configuration for the newcomer homepage's [[ https://www.mediawiki.org/wiki/Growth/Community_Updates | Community Updates module ]]. ####Background & research: This task is important because communities need the ability to customize features for their wikis, but not all configuration settings need to be tied to adminship. In {T360919}, we're ensuring non-administrators see all providers at Special:CommunityConfiguration as disabled. This does not necessarily have to be always the case – for example, aspects related to how AbuseFilter operates could be delegated to abuse filter maintainers, who necessarily do not need to be administrators. It would also be potentially useful to let mentors determine how mentorship work like themselves, without having to escalate to an administrator. Within this task, we should ensure client extensions can specify a lower permission for providers, giving access to non-admins as well. This task does not include support for providers that even admins are unable to edit (this is not practical, as the configuration is stored in NS_MEDIAWIKI, which is directly editable by any administrator). We also need to ensure it is clear from visiting Special:CommunityConfiguration, which providers you are able to modify, and which providers are available as read-only only. ####Questions: - Are edit rights limited by Community Configuration page, section within the page, or individual Configuration variable? - How can we ensure it's clear who has edit access to certain Community Configuration forms (or sections of the form)? ####Designs: TBD ####Acceptance Criteria: TBD

The MVP release of Community Configuration 2.0 will only be editable by Admins, but in the future there might be certain configuration changes that should be editable by other user groups or attached to a certain user right. Project info: https://www.mediawiki.org/wiki/Community_configuration ####User story & summary: As a Steward, I want to enable 'emergency CAPTCHAs' for anonymous IP edits {T303433} As a Event Coordinator, I want to adjust community configuration for the newcomer homepage's [[ https://www.mediawiki.org/wiki/Growth/Community_Updates | Community Updates module ]]. ####Background & research: This task is important because communities need the ability to customize features for their wikis, but not all configuration settings need to be tied to adminship. In {T360919}, we're ensuring non-administrators see all providers at Special:CommunityConfiguration as disabled. This does not necessarily have to be always the case – for example, aspects related to how AbuseFilter operates could be delegated to abuse filter maintainers, who necessarily do not need to be administrators. It would also be potentially useful to let mentors determine how mentorship work like themselves, without having to escalate to an administrator. Within this task, we should ensure client extensions can specify a lower permission for providers, giving access to non-admins as well. This task does not include support for providers that even admins are unable to edit (this is not practical, as the configuration is stored in NS_MEDIAWIKI, which is directly editable by any administrator). We also need to ensure it is clear from visiting Special:CommunityConfiguration, which providers you are able to modify, and which providers are available as read-only only. ####Questions: - Are edit rights limited by Community Configuration page, section within the page, or individual Configuration variable? - How can we ensure it's clear who has edit access to certain Community Configuration forms (or sections of the form)? ####Designs: TBD ####Acceptance Criteria: TBD