@Trizek-WMF - I figured this task was still a little too open-ended. Let's consider it complete when we finish the main two topics that need discussion:

• Article creation hypothesis discussion
• Community configuration hypothesis discussion

I changed the acceptance criteria to reflect how the work is done.

Thanks! The summary from the Article creation hypothesis discussion is here.

Community configuration hypothesis discussion

The initial deadline for initial feedback was end of July 2023. We reached users who recently edited the Configuration page.

• Editing is not done that often by volunteers, so we have a low response rate. Hence we extended the deadline for feedback.
• According to one user, it seems that the default config we provide is enough.

The usual roles and processes to monitor and edit the configuration are preferred:

• All configuration pages can be read by anyone
• (interface-)admins can edit because they have enough knowledge
• They can apply requests made after a discussion
• History of requests and changes keep track of changes

This configuration page might impact a lot of users, and is to be handled with care.

• Several ways to prevent issues were suggested:
  • the creation of a new role, for trusted admins who know what they do
  • The creation of a reviewing process to validate a change made by one admin
• A clear and centralized history page is needed to spot any changes made on the different configurations.

No clear feedback regarding the current design

Prediction of edits: from 0 to 100/year (10 on average); one pragmatic user said “more”.

@KStoller-WMF, up to you to close this task.