- Mentioned In
- T132643: Agreement on when and how communities provide feedback.
T121260: Q4 Goal: Internal work on product design and development principles and process
T124022: Goal: Clarify community engagement in WMF product development process
- Mentioned Here
- T124022: Goal: Clarify community engagement in WMF product development process
T125815: Consolidate the Communities subpage of the product development process
From what I understand, the /Communities page will transclude information from each of the five steps that is relevant to community role and participation with each particular step; in other words, the page should be a nutshell for community members to know what is expected of them in each step of product development.
This task documents what CLs do in conjunction with product teams to inform both teams and communities about participation and expectations at each level, as well as documenting the communications around the information and then what we do with the community feedback we collect.
To me, there is a distinct difference in purpose between the two pages.
I still think that it is better to use the subpages for stages, transcluding by audiences. At least at the beginning. This is the way to assure that people interested in Understand can read all about it in one page, and people interested in Communities can also read everything in one page. Having two axes is already complex enough, adding more information in third pages might be a recipe for confusion / duplication.
So from https://www.mediawiki.org/wiki/User:Keegan_(WMF)/PDP/CL_checklist, I would put the Understand portion under https://www.mediawiki.org/wiki/WMF_product_development_process/Understand#Communities, and the same with the rest of sections. Then transclude.
If later on this is not enough, we can always play with transcluded / non-transcluded content. But in any case, all about Communities should be found at https://www.mediawiki.org/wiki/WMF_product_development_process/Communties
Does this make sense?
Yes, you are right. Keeping the pages editable by audiences makes more sense, since audiences will have clearer maintainers, whereas stages probably won't.
Summarizing: this checklist should go to /Communities, and then each section could be transcluded in its related stage page.
OK, this is very good. I am not sure about closing the task already. Does https://www.mediawiki.org/wiki/WMF_product_development_process/Communities have the buy-in from Product, or even Technical Collaboration? How should we call for community review? You could also consider this task as completing the first proposal (which you did), and then use T124022 as ultimate check for a reviewed version.