You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the August 7th US meeting, we discussed this. I'd like to propose we adopt the project management method we use in the Spec repo, and are proposing to also use in the Contributor Experience SIG. If it works for us, it would be great if we could standardize something like this across the SIGs that do this kind of work. 😺
Project management proposal
New issues come in as no status.
New issues are triaged at the beginning of every meeting.
If the issue is in scope for the project, and it seems reasonable that we might be able to accomplish it sometime this year, it is moved to accepted.
Non-accepted issues are closed.
Community members thumbs up to indicate interest.
Community members assign themselves to issues if they are willing/available to actually do work.
We choose which issues we actively work on from the list of most thumbed up issues that have a sufficient number of assignees.
These issues are moved to in progress.
We limit ourselves to four issues at a time, in order to concentrate our efforts and complete these issues as fast as possible.
Once we have finished work on an issue, it is moved to completed.
If for some reason it turns out that we cannot complete an issue, we stop working on it and it is either moved back to accepted or it is closed.
A roadmap for the project needs to be laid out and prioritized in the project board, https://github.com/orgs/open-telemetry/projects/105
The text was updated successfully, but these errors were encountered: