Add a standard CONTRIBUTING.md template

[bhack]

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.

[bhack]

/cc @ematejska@theadactyl I don't have write access here. Can you convert to draft? Thanks

[yarri-oss]

I would like to suggest we consider adding this as a separate file (CALL_FOR_MAINTAINERS.md?) due to the importance of the role.

[bhack]

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.

[bhack]

/cc I think that also @mihaimaruseac could be interested in the Codeowner/Maintainer status and process.

[bhack]

/cc @lamberta for a review

[ematejska]

@bhack Is this ready for review or still a draft?

[bhack]

I don't know how to collect early feedback.
What do you think @theadactyl@yarri-oss?

[theadactyl]

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> .

[ematejska]

@theadactyl Can you review?

[bhack]

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.