Preamble: While the developer experience working group is organizing itself, we need a means of making decisions. As the group grows, these mechanisms may be adjusted.
As the Developer experience git repository is the public facing aspect of the group, merge's should happen during or immediately after group meetings and reflect agreements made there.
Currently the meeting recurrs every week on Tuesday at 16:00 UTC - if there are 4 or more developer-participants at that group and the chair, and there is 60% or greater approval among attendees that a proposal or pull request status should be adjusted, then the status can be updated on git. However in general the group will seek to work from consensus.
Proposals can have the following statuses
- Discussion - Identifies an issue which may have no clear solution - but can be identified as an area of research for the working group. (these can take the form of github issues with labels for priority)
- Draft - Seeks to solve a Discussion issue with a concrete proposal which is technologically feasible (if applicable). This may be a place where developers wishlist features of a proposed solution.
- Accepted - the proposal describes a sound solution to a statistically significant problem
- Seeking Sponsorship/Action - The working group is actively soliciting sponsors or other actors to provide the solution described.