-
Notifications
You must be signed in to change notification settings - Fork 6.8k
header updates to clarify use of CODEOWNERS #9426
Conversation
Proposal to clarify the use of CODEOWNERS for Apache MXNet contributors and comitters.
Looks good to me. Please update the development process on Apache MXNet wiki once this file is merged. |
# https://help.github.com/articles/about-codeowners/ and | ||
# https://github.com/blog/2392-introducing-code-owners | ||
# | ||
# The first owner listed for a package is considered the maintainer for a package. |
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.
One "maintainer"? I strongly oppose this. Who would even decide who that is? This sounds like a recipe for conflict within the community.
# as additional owners to get notified about changes in a specific package. | ||
# | ||
# By default the package maintainer should merge PR after appropriate review. | ||
# A PR which received 2 +1 (or LGTM) comments can be merged by any committer. |
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 still maintain that any committer can merge something if they feel they've given it a good review -- this encourages people to learn new parts of the code and allows the project to scale.
The rule as stated above would mean that only a few people would be "allowed" to merge code at all, which sounds more like an internal corporate style and does not promote community, IMHO.
# | ||
# By default the package maintainer should merge PR after appropriate review. | ||
# A PR which received 2 +1 (or LGTM) comments can be merged by any committer. | ||
# In the future we might consider adopting required reviews |
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.
Who is "we"?
This was not agreed upon in dev and should be reverted |
This reverts commit 63394de.
This reverts commit 63394de. This PR was merged in error
* header updates to clarify use of CODEOWNERS Proposal to clarify the use of CODEOWNERS for Apache MXNet contributors and comitters. * fixed typo
…pache#9442) This reverts commit 63394de.
* header updates to clarify use of CODEOWNERS Proposal to clarify the use of CODEOWNERS for Apache MXNet contributors and comitters. * fixed typo
…pache#9442) This reverts commit 63394de.
* header updates to clarify use of CODEOWNERS Proposal to clarify the use of CODEOWNERS for Apache MXNet contributors and comitters. * fixed typo
…pache#9442) This reverts commit 63394de.
* header updates to clarify use of CODEOWNERS Proposal to clarify the use of CODEOWNERS for Apache MXNet contributors and comitters. * fixed typo
…pache#9442) This reverts commit 63394de.
* header updates to clarify use of CODEOWNERS Proposal to clarify the use of CODEOWNERS for Apache MXNet contributors and comitters. * fixed typo
…pache#9442) This reverts commit 63394de.
Description
Proposal to clarify the use of CODEOWNERS for Apache MXNet contributors and comitters.
Checklist
Essentials
make lint
)Changes
Comments
Change is not complete and needs to be finalized. Discussion ongoing at https://lists.apache.org/thread.html/6d83f8a93d9a1cd152e869caa1e570e570677886dd5c65fc28298322@%3Cdev.mxnet.apache.org%3E
Do not merge until discussion converged.