After the first review of the Technical Collaboration Guideline (T144625) is completed, the TCG needs to be piloted and tested with a new product (as noted in the timeline T138339#2528413 ). The subject and participants of the pilot are to be determined soon.
Description
Related Objects
- Mentioned In
- T170953: Build out TCG use-case documentation
T163441: Technical Collaboration quarterly check in for April - June 2017
T144625: First review of the Technical Collaboration Guidance by Foundation Product teams and most active technical volunteers
T150658: Technical Collaboration quarterly check in for January – March 2017 - Mentioned Here
- T138339: Create a systematic approach to community engagement for product development teams
T144625: First review of the Technical Collaboration Guidance by Foundation Product teams and most active technical volunteers
Event Timeline
Can we please list somewhere the teams/projects that already went through TCG, even if just partually? I believe at least one project Chris worked on did?, and Hovercards is probably going to follow. Lessons learned are also useful. TY
As of right now, there has not been a product that has gone through the TCG in any real way - me sitting down with the PM and CL and working out plans and strategies based on the recommendations. It has been used as a reference work, but not in a formal way. Such a pilot would be a formal application. That being said, the TCG largely documents the work of CLs in communicating with communities so all things considered, all products the CLs work on go through the TCG in a sense :)
I will have some documentation on applications and lessons learned in the near future.
As of right now, there has not been a product that has gone through the TCG in any real way - me sitting down with the PM and CL and working out plans and strategies based on the recommendations. It has been used as a reference work, but not in a formal way.
I will note that this has been intentional, not using the TCG formally yet, as we want to make sure we have stakeholder buy-in from product before it is used as an actual thing of guidance provided by the TC team to product and the communities as a whole.
Just a detail...
After the first review of the Technical Collaboration Guideline
It doesn't need to be after. The TCG draft is already in a state where it could be used by an earlier adopter.
Reviewed the previous ORES work in relation to the TCG, reviewed the TCG itself, and set up a plan for proposing and developing an ORES auditing tool: https://www.mediawiki.org/wiki/Meta-ORES
Resolving this task, will open new tasks for the project as needed.