Adding a Code of Conduct to MacPorts

[Michael Dickens]

I'll second that having a CoC isn't a bad idea. I like the shorter version < https://www.contributor-covenant.org/version/1/4/code-of-conduct.html >, which leaves room for our project to implement various parts as we see fit (the PostgreSQL CoC is, in my opinion, a little too specific in some ways such as timelines for complaints). Even if we don't have a formal MacPorts conference, we are a significant online presence for OSX users and, though (to the best of my knowledge) we haven't had significant issues yet that would require a CoC, it seems inevitable that something will happen & having the CoC in place allows for at least the basics (policies and/or procedures) for handling the situation. My US$0.02 ... - MLD

On Tue, Sep 18, 2018, at 11:44 AM, Ryan Schmidt wrote:
> 
> 
> On Sep 18, 2018, at 09:55, Jackson Isaac wrote:
> 
> > Lately, I have seen open source projects have started adopting Code of
> > Conduct. [1], [2]
> > 
> > I think it is a great step to keep the open source community healthy
> > and welcoming to everyone.
> > 
> > I would like to know what other developers think about this. Also, who
> > would be the decision makers (PortMgrs?)
> > 
> > Reference:
> > [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/code-of-conduct.rst
> > [2] https://lwn.net/Articles/765332/
> > 
> > Kind Regards,
> > Jackson Isaac
> 
> Hopefully we've already been a welcoming community so far, but having a 
> code of conduct document doesn't seem like a bad idea.
>