The WMF is working through documenting how software is made. This includes steps for volunteer engagement and collaboration, principles for development and documentation, etc.
I'll work with an interested product team to put these documented steps into practice for a product.
More to be determined as this quarter's work moves forward.
Maybe it is a matter of wording? We could pilot a new Product plan through the Technical-Collaboration-Guidance draft recommendations we have. Theory and practice combined.
Alright, I think it is better to close this task. Community-Relations-Support are increasingly taking into account the Technical Collaboration Guideline draft recommendations and ongoing discussions when supporting Product teams. This is happening as part of other tasks, instead of becoming a task in itself.
More than a specific pilot for a single project, what we are doing is checking against our recommendations every time that special support is needed, or every time we start a new activity.