The TCG needs a text cleanup and a navigation/design facelift before being "1.0".
|Resolved||Keegan||T138339 Create a systematic approach to community engagement for product development teams|
|Declined||Elitre||T144625 First review of the Technical Collaboration Guidance by Foundation Product teams and most active technical volunteers|
|Resolved||Elitre||T176462 Goal: Best practices of collaboration between product development teams and communities agreed and ready for adoption|
|Duplicate||Keegan||T176274 Improve and finalize TCG based on P&T and community feedback|
|Duplicate||Keegan||T176275 Cleanup Technical Collaboration Guidance text|
|Declined||Keegan||T176276 Technical Collaboration Guidance design|
- Mentioned In
- T184080: Technical Collaboration quarterly check in for January - March 2018
T175000: Technical Collaboration quarterly check in for October - December 2017
T176462: Goal: Best practices of collaboration between product development teams and communities agreed and ready for adoption
- Mentioned Here
- T176276: Technical Collaboration Guidance design
The two subtasks refer to improvements on the existing pages. However, it is worth to review the current index, the structure of the TCG itself. I have the impression that it has grown organically and that it has room for improvement. I am not sure new readers landing to the TCG main page will quickly understand the scope of the TCG and will find the right page for the information they are looking for. Has there been any feedback in this direction?
T176276: Technical Collaboration Guidance design is largely about this question, not just specific pages (though that is part of it). Feedback in this direction has begun, in written form with the CL review of the TCG and in-person conversations, and is extending to the product teams this coming quarter as working groups form between the teams to review the TCG.
There will be several design options available. A simple example of one I drew up is here: https://docs.google.com/a/wikimedia.org/drawings/d/1u3Ovglnb1U-5b-wg362HZuU6X8rd8WYvJrTVa-KSYio/edit?usp=sharing
Hopefully I'll have more professional input on what we end up going with.