operator-framework
Contributors Document Needs an Update
The existing CONTRIBUTING.md document has a few gaps that should be addressed in order to provide new users in the community with a better onboarding experience. Specifically, I would like to see:
- Better guidelines surrounding how this project pulls in new work.
- How this project uses discussions to collect feedback.
- How this project assigns labels to issues.
- Define maintainers commitment to addressing issues / discussions as they pop up.
- Whether or not we submit PRs to the operator-framework/enhancements repository (Historically, we've used EPs to submit net new ideas and have used GH Issues/Discussions to drive feature development that implement EPs).
It should be mentioned that there is an ongoing effort to improve existing the contributor experience within the operator-framework portfolio of projects. Please feel encouraged to comment on the linked ticket to help improve the operator-framework governance model!
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.