-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define new project management workflow #1584
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've reviewed the files at the root directory, not the individual projects.
@jpkrohling I rewrote the intro and Project proposal sections to be clearer about what counts as a project. Please have a look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like codifying this more explicitly. We plan to leverage it more and more in semconv.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
What is the process for existing projects/workgroups that did not follow this process? For example we have Agent Management Workgroup that made great progress and has a lot of current momentum. I assume this proposal does not mean existing de-facto projects have to necessarily meet all the new requirements and have to pass a review before we accept them. We probably need to grandfather existing de-facto projects. |
@tigrannajaryan I propose that all existing projects fill out a project document and get added to the project board. I agree that there should not be an approval process - we have already agreed to do the work and have started the working group. But we need to surface all of these commitments so that we can track how thin our resources are spread. Groups which currently do not have any deadlines would be encouraged to define them for any work which will require public review. The client and messaging groups found this helpful - having a six week goal led to an increased cadence in project work, and helped resolve debate. It will also help with getting a more coherent public review. If the deadlines prove to be unrealistic, they can be always be updated. |
@tedsuo it would be useful to have this written in project-management.md so that the expectations from existing projects are clear. |
This pull request updates our current project management workflow, based on the proposal in #1534.