Reword project management to adapt to existing SIGs #2832
Conversation
| * Non-trivial being: introducing new conventions, forming a new SIG around a subject, topic or technology, and stabilization efforts. | ||
| * A new SIG being formed, focusing on a set of initial set of deliverables before stabilizing. | ||
| * An existing SIG taking on new work which will affect the OpenTelemetry project as a whole, and will need review from the broader community. | ||
| * An existing SIG working on a major roadmap item, which focuses their efforts for a specified length of time. |
There was a problem hiding this comment.
I'm not sure these require approval from GC/TC? E.g.
There was a problem hiding this comment.
Yeah, I think right now we have a mix of projects like those, which are happening without being listed in the community repo, and others that are listed (e.g. Collector v1).
I think if a project is being proposed as part of an existing SIG, it shouldn't need approval from GC/TC. However, I think it should be listed in the community repo and have the same structure (i.e. problem to solve, goals, deliverables, GH project, etc). A standard approval from 2 repo approvers, like any other PR here, would suffice in those cases IMO.
Co-authored-by: Trask Stalnaker <[email protected]>
|
|
||
| Special care should be put into defining the scope of a given project, especially when it requires a new SIG. A project is not synonymous to a SIG charter, so limiting the scope to an initial set of deliverables can avoid projects that never finish. | ||
|
|
||
| A project may also be created to signal a significant effort, or milestone, from one or more existing SIGs. As documented in the [project proposal](#project-proposal) section below, a project from an existing SIG requires significantly less logistics to get started, providing a way for SIGs to publicize their current milestones. |
There was a problem hiding this comment.
From @jsuereth during last GC/TC meeting: although sponsorship/liaison can be inherited for projects in these cases (i.e. existing SIGs creating a new project) there's a risk SIGs take on more than TC sponsors (or delegates) can agree to support. We should add guidance here for those cases.
|
At the last GC meeting (Thu 16 July) we decided that the best way to allow existing SIGs to make important milestones or roadmap items more visible to the community is to reduce process, while having some type of common structure. This will most likely involve creating GH projects (i.e. boards) and for those to be picked up and presented in a common roadmap as OpenTelemetry Roadmap I will update this PR to reflect that discussion. |
|
I'm going to close this one due to recent changes in how we collate roadmap items and how it relates to projects and SIGs. I'll open a PR soon that will include a small subset of the changes here. |
2 participants
This change adapts wording in the project management doc, and the project template, to streamline the creation of projects as a way to communicate roadmap items for existing SIGs, inheriting sponsorship and staffing requirements from the existing SIG. It also aligns with recent changes to TC sponsorship requirements and clarifies the relationship between SIGs and projects.