Change Details

####User story & summary: As a Wikipedia admin, I want to easily update [[ https://www.mediawiki.org/wiki/Growth/Community_configuration | community configuration ]], so that I can customize features to work well for my wiki. ####Background: This task is important because Special:EditGrowthConfig has increased in complexity we can't continue to scale this feature without design improvements. Short-term this project supports the Editing and Moderator Tools team projects (Edit check and Revert prediction bot), and long-term this work will help evolve how WMF product and technology teams develop and deploy features. Prioritizing work on Community configuration acknowledges that each community has unique needs, and invested community members should be empowered to configure features to meet those needs. This approach removes the barrier for non-technical moderators to customize settings for their communities and fosters a more inclusive and collaborative product development process, thus enabling WMF to better serve the Wikimedia movement. ####Needed research & open questions: - Ideally community configuration is a well-known tool for admins that can be adjusted as needed, but doesn't require frequent changes. You can view [[ https://martin-urbanec.toolforge.org/growth-reports/community_configuration_usage/ | Community configuration usage here ]]. Do admins know about Community configuration? Do they feel empowered to make changes or feel blocked currently? Do they have any feedback about needed Community configuration improvements? - How can configuration options be organized in a way that will scale well overtime? For example, both the Apps and Web have "Suggested edits": would those be organized together, or separated since they are different platforms? How can we resist [[ https://en.wikipedia.org/wiki/Conway%27s_law | Conway's law ]] and ensure the organization matches user needs rather than the organizational structure they are designed in? - User access levels: Community configuration should be visible by all, but only editable by a trusted subset of experienced Wikimedians. Are all configuration options only editable by Admins? Do Bureaucrats and Stewards have access to make changes? Do some configuration options have different user access levels? ####Design: TBD ####Acceptance Criteria: Collaborate closely with communities, @Urbanecm_WMF, and WMF teams interested in Community configuration (Moderator Tools & Editing), to develop design improvements for Community configuration that will allow this feature to scale and evolve to meet community needs. Given I access Special:EditGrowthConfig When want to review or adjust the configuration, Then I can easily access the section I care to adjust.

####User story & summary: As a Wikimedianpedia admin, I want to easily update [[ https://www.mediawiki.org/wiki/Growth/Community_configuration | community configuration ]], so that I can customize the feature sets to work well for my wiki. ####Background & research: This task is important because Special:EditGrowthConfig has increased in complexity we can't continue to scale this feature without design improvements. Short-term this project supports the Editing and Moderator Tools team projects (Edit check and Revert prediction bot), and long-term this work will help evolve how WMF product and technology teams develop and deploy features. Prioritizing work on Community configuration acknowledges that each community has unique needs, and invested community members should be empowered to configure features to meet those needs. This approach removes the barrier for non-technical moderators to customize settings for their communities and fosters a more inclusive and collaborative product development process, thus enabling WMF to better serve the Wikimedia movement. ####Needed research & open questions: - Ideally community configuration is a well-known tool for admins that can be adjusted as needed, but doesn't require frequent changes. You can view [[ https://martin-urbanec.toolforge.org/growth-reports/community_configuration_usage/ | Community configuration usage here ]]. Do admins know about Community configuration? Do they feel empowered to make changes or feel blocked currently? Do they have any feedback about needed Community configuration improvements? - How can configuration options be organized in a way that will scale well overtime? For example, both the Apps and Web have "Suggested edits": would those be organized together, or separated since they are different platforms? How can we resist [[ https://en.wikipedia.org/wiki/Conway%27s_law | Conway's law ]] and ensure the organization matches user needs rather than the organizational structure they are designed in? - User access levels: Community configuration should be visible by all, but only editable by a trusted subset of experienced Wikimedians. Are all configuration options only editable by Admins? Do Bureaucrats and Stewards have access to make changes? Do some configuration options have different user access levels? ####Design: [[ |Figma designs]]TBD ####Acceptance Criteria: Collaborate closely with communities, @Urbanecm_WMF, and WMF teams interested in Community configuration (Moderator Tools & Editing), to develop design improvements for Community configuration that will allow this feature to scale and evolve to meet community needs. Given I access Special:EditGrowthConfig When want to review or adjust the configuration, Then I can easily access the section I care to adjust.