Hey all,
The following was what I wrote in my notes today as a definition of the TWG mandate:
Technical Working Group Mandate:- The role of the TWG is as the 'conflict resolution body for technical conflict' (similar to how the Community working group is the conflict resolution body for 'people' conflict).
- The TWG also has a responsibility as the community 'curator' of technical policy, accountable for ensuring that community technical policies are documented, published, and maintained current.
- The community perspective seems to be that we are responsible for 'authoring' policy; or driving the conversation and facilitating the process of gaining community consensus on all policy proposals (more specifically, all of the coding standards issues which were moved to our queue).
- I don't feel that the working group is well positioned to actually take on this perceived role, as attempting to keep abreast of every potential technical policy proposal being made or debated within the community would quickly bury us ... and my view is that we are not looking to 'replace' the existing community consensus-driven approach, only augment it in order to guide the community when that existing process breaks down.