-
Notifications
You must be signed in to change notification settings - Fork 580
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
Add a standard CONTRIBUTING.md template #384
base: master
Are you sure you want to change the base?
Conversation
/cc @ematejska @theadactyl I don't have write access here. Can you |
## CODEOWNERS | ||
Describe how codeownership and maintainership in the repo: | ||
* How to be a Codeowner | ||
* How to be a Maintainer |
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 would like to suggest we consider adding this as a separate file (CALL_FOR_MAINTAINERS.md?) due to the importance of the role.
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.
Good, we could put here just a like to an external markdown.
I don't know if we could open a new thread later about standardizing a little bit the CALL_FOR_MAINTAINERS
process/roles.
E.g. Debian has historically a quite regulated Maintainer process. This is just to make a reference example but it is too complex for us.
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.
/cc I think that also @mihaimaruseac could be interested in the Codeowner/Maintainer status and process.
/cc @lamberta for a review |
@bhack Is this ready for review or still a draft? |
I don't know how to collect early feedback. |
Will review.
…On Thu, Dec 9, 2021 at 8:57 AM bhack ***@***.***> wrote:
I don't know how to colllect early feedback.
What do you think @theadactyl <https://github.com/theadactyl> @yarri-oss
<https://github.com/yarri-oss>?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#384 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABREJVJ3PW353KNKHWCFTR3UQDNY7ANCNFSM43K4DG7A>
.
|
@theadactyl Can you review? |
Just a reminder for the reviewers. We need to figure out also how to handle topics mentioned in #223 I suppose we could add a general point in this template if we could define some general rules on how to handle duplicated/conflicting contributions. |
This is a Draft CONTRIBUTING.md template.
It is part of an effort to standardize some early access info for Github community health files across the TensorFlow ecosystem repositories.