-
Notifications
You must be signed in to change notification settings - Fork 683
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
Suggest nominations based on commit history #5855
Suggest nominations based on commit history #5855
Conversation
Initial version of the code owners file with no owners filled in. This just breaks the code down into different areas that might want owners.
To allow some components to be unowned, remove the default owner.
* Add writers to CODEOWNERS
This reverts commit e5b9330.
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.
+1
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.
The nominations for persistence don't seem quite right: @kirklund @dschneider-pivotal @jchen21
For example, I've never studied or touched the persistence code. I think the best candidate reviewers for persistence code should be @upthewaterspout and @gesterzhou.
After the self-nomination process we still had a few gaps. I've reviewed past commit history to suggest a couple names for each remaining area.
As per dev list discussion, review period for this PR will be extended to 3pm Friday Jan 8. At that time, anyone that has not explicitly consented to their nomination (by approving this PR) will be removed (and if this leaves any code areas with fewer than 2 owners, the remaining owner will be cleared as well).