I'm +1 on creating a CODE_OF_CONDUCT.md (or whatever the standard name for the file is) and putting in a link to Apache's CoC. I'm, as I mentioned, -1 on creating one unique to us or adopting a non-Apache CoC.
Creating CODE_OF_CONDUCT.md (or appropriate) and adding it to the bottom of our CONTRIBUTING.md (or appropriate) file will increase discoverability and prevent future people from thinking we don't have one. :) Apache's CoC is really well written, I think, and it's been vetted by Apache Legal, which is a major plus. On Wed, Oct 18, 2017 at 9:13 AM, Timilsina, Ashish <[email protected]> wrote: > Hi all, > > As we are discussing various things at the TC Summit here in Atlanta, Jan > mentioned that our project needs a Code of Conduct which is extremely > important as our community grows. > I used the following > (https://www.contributor-covenant.org/version/1/4/code-of-conduct.html) for > our project and created a PR however, based on the feedback I got from > @rob05c<https://github.com/rob05c> and > @alficles<https://github.com/alficles>, it seems like our project is already > covered by the Apache foundation > (https://www.apache.org/foundation/policies/conduct.html). So, instead of > creating a new one like I did, we can just add the apache link in the > “contribution.md” file. > I want to get everyone’s opinion on this before I create another PR to modify > our contribution page. > Let me know if you have any questions. > > Sincerely, > Ashish Timilsina > Product Development Specialist | Comcast Technology Solutions > 1899 Wynkoop St, Suite 550 | Denver, CO 80202 > M | 303-913-3379 > [email protected]
