Add contributor guidelines and CoC

[camillescott]

No description provided.

[jarrodmillman]

It seems like it would be good to adopt existing contributor guidelines and CoC from upstream projects. To that end...

Here is the contributing overview for networkx:
https://github.com/networkx/networkx/blob/master/CONTRIBUTING.rst

It is almost identical to (with the head removed):
https://github.com/scikit-image/scikit-image/blob/master/CONTRIBUTING.txt

Both projects (as well as many others) also use:
https://github.com/matthew-brett/gitwash

I could make a PR if this seems like a reasonable start.

I don't have much experience with this, but here is the scipy CoC:
https://github.com/scipy/scipy/tree/master/doc/source/dev/conduct
https://github.com/scipy/scipy/blob/master/.github/CODE_OF_CONDUCT.md
If that seems reasonable, I could also make a PR for the CoC as well.

For both PRs I would do basic editing so that things are specific to grave and not the project I copy them from. I would submit them as separate PRs as they may have different lifetimes as a PR being reviewed even though they are related.

Thoughts?

[NelleV]

Sounds good to me!

…

On Fri, Mar 30, 2018, 3:40 PM Jarrod Millman ***@***.***> wrote: It seems like it would be good to adopt existing contributor guidelines and CoC from upstream projects. To that end... Here is the contributing overview for networkx: https://github.com/networkx/networkx/blob/master/CONTRIBUTING.rst It is almost identical to (with the head removed): https://github.com/scikit-image/scikit-image/blob/master/CONTRIBUTING.txt Both (as well as many others) project also use: https://github.com/matthew-brett/gitwash I could make a PR if this seems like a reasonable start. I don't have much experience with this, but here is the scipy CoC: https://github.com/scipy/scipy/tree/master/doc/source/dev/conduct https://github.com/scipy/scipy/blob/master/.github/CODE_OF_CONDUCT.md If that seems reasonable, I could also make a PR for the CoC as well. For both PRs I would do basic editing so that things are specific to grave and not the project I copy them from. I would submit them as separate PRs as they may have different lifetimes as a PR being reviewed even though they are related. Thoughts? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AALR3lDY_DI8Bpks50jfAxDeFVlCYvN6ks5tjrRNgaJpZM4TCFBy> .

[camillescott]

That sounds great Jarrod! It looks like scipy is using the standard Ada Initiative CoC, or something close to it, which was the direction I was thinking. We just need to find ourselves an outside contact point for complaints against core developers. @halexand is currently in our lab but starting a tenure track position at WHOI this fall; she's super cool and easy to talk with, and has volunteered to take on the contact position. Thoughts? On Fri, Mar 30, 2018, 5:27 PM Nelle Varoquaux <[email protected]> wrote:

…

Sounds good to me! On Fri, Mar 30, 2018, 3:40 PM Jarrod Millman ***@***.***> wrote: > It seems like it would be good to adopt existing contributor guidelines > and CoC from upstream projects. To that end... > > Here is the contributing overview for networkx: > https://github.com/networkx/networkx/blob/master/CONTRIBUTING.rst > > It is almost identical to (with the head removed): > https://github.com/scikit-image/scikit-image/blob/master/CONTRIBUTING.txt > > Both (as well as many others) project also use: > https://github.com/matthew-brett/gitwash > > I could make a PR if this seems like a reasonable start. > > I don't have much experience with this, but here is the scipy CoC: > https://github.com/scipy/scipy/tree/master/doc/source/dev/conduct > https://github.com/scipy/scipy/blob/master/.github/CODE_OF_CONDUCT.md > If that seems reasonable, I could also make a PR for the CoC as well. > > For both PRs I would do basic editing so that things are specific to grave > and not the project I copy them from. I would submit them as separate PRs > as they may have different lifetimes as a PR being reviewed even though > they are related. > > Thoughts? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#9 (comment)>, or mute > the thread > < https://github.com/notifications/unsubscribe-auth/AALR3lDY_DI8Bpks50jfAxDeFVlCYvN6ks5tjrRNgaJpZM4TCFBy > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACwxrSEGQhE4DydkdYJ9W2VmAfUcZeZ7ks5tjsV9gaJpZM4TCFBy> .

[jarrodmillman]

Harriet looks like a great choice and even better she is willing to do it! I'll create a PR later today.