Adoption of Contributor Code of Conduct
95 views
Skip to first unread message
Brian Granger
Sep 9, 2015, 9:25:31 PM9/9/15
to Project Jupyter
Hi all,
Gina Helfrich (working for NumFOCUS) has brought up the question of
NumFOCUS projects adopting a Contributor Code of Conduct. I am in
favor of this but wanted to get feedback from the community.
If there is support for this or variations of this, I will open PR on
the governance repo.
Here is the text from Gina:
### From Gina Helfrich
I recently came across this website: http://contributor-covenant.org/
It seems like a fairly compelling idea to me -- low cost, potentially
high reward in diversifying contributors.
What do you all think about potentially having a Contributor Code of
Conduct for NumFOCUS projects? Here is the one suggested by that
website:
"Contributor Code of Conduct
As contributors and maintainers of this project, and in the interest
of fostering an open and welcoming community, we pledge to respect all
people who contribute through reporting issues, posting feature
requests, updating documentation, submitting pull requests or patches,
and other activities.
We are committed to making participation in this project a
harassment-free experience for everyone, regardless of level of
experience, gender, gender identity and expression, sexual
orientation, disability, personal appearance, body size, race,
ethnicity, age, religion, or nationality.
Examples of unacceptable behavior by participants include:
* The use of sexualized language or imagery
* Personal attacks
* Trolling or insulting/derogatory comments
* Public or private harassment
* Publishing other's private information, such as physical or
electronic addresses,
without explicit permission
* Other unethical or unprofessional conduct.
Project maintainers have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions
that are not
aligned to this Code of Conduct. By adopting this Code of Conduct,
project maintainers commit themselves to fairly and consistently
applying these principles to every aspect of managing this project.
Project maintainers who do not follow or enforce the Code of Conduct
may be permanently removed from the project team.
This code of conduct applies both within project spaces and in public
spaces when an individual is representing the project or its
community.
Instances of abusive, harassing, or otherwise unacceptable behavior
may be reported by opening an issue or contacting one or more of the
project maintainers.
This Code of Conduct is adapted from the Contributor Covenant
(http://contributor-covenant.org), version 1.2.0, available at
http://contributor-covenant.org/version/1/2/0/"
--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgra...@calpoly.edu and elli...@gmail.com
Gina Helfrich (working for NumFOCUS) has brought up the question of
NumFOCUS projects adopting a Contributor Code of Conduct. I am in
favor of this but wanted to get feedback from the community.
If there is support for this or variations of this, I will open PR on
the governance repo.
Here is the text from Gina:
### From Gina Helfrich
I recently came across this website: http://contributor-covenant.org/
It seems like a fairly compelling idea to me -- low cost, potentially
high reward in diversifying contributors.
What do you all think about potentially having a Contributor Code of
Conduct for NumFOCUS projects? Here is the one suggested by that
website:
"Contributor Code of Conduct
As contributors and maintainers of this project, and in the interest
of fostering an open and welcoming community, we pledge to respect all
people who contribute through reporting issues, posting feature
requests, updating documentation, submitting pull requests or patches,
and other activities.
We are committed to making participation in this project a
harassment-free experience for everyone, regardless of level of
experience, gender, gender identity and expression, sexual
orientation, disability, personal appearance, body size, race,
ethnicity, age, religion, or nationality.
Examples of unacceptable behavior by participants include:
* The use of sexualized language or imagery
* Personal attacks
* Trolling or insulting/derogatory comments
* Public or private harassment
* Publishing other's private information, such as physical or
electronic addresses,
without explicit permission
* Other unethical or unprofessional conduct.
Project maintainers have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions
that are not
aligned to this Code of Conduct. By adopting this Code of Conduct,
project maintainers commit themselves to fairly and consistently
applying these principles to every aspect of managing this project.
Project maintainers who do not follow or enforce the Code of Conduct
may be permanently removed from the project team.
This code of conduct applies both within project spaces and in public
spaces when an individual is representing the project or its
community.
Instances of abusive, harassing, or otherwise unacceptable behavior
may be reported by opening an issue or contacting one or more of the
project maintainers.
This Code of Conduct is adapted from the Contributor Covenant
(http://contributor-covenant.org), version 1.2.0, available at
http://contributor-covenant.org/version/1/2/0/"
--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgra...@calpoly.edu and elli...@gmail.com
Chris Colbert
Sep 9, 2015, 9:41:34 PM9/9/15
to jup...@googlegroups.com
+1 from me generally. -1 on using issues to report misbehavior. I think that's bettered reported and handled directly. Particularly when the issue may have privacy concerns.
--
You received this message because you are subscribed to the Google Groups "Project Jupyter" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jupyter+u...@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAH4pYpSt194w5k%3DO1yZYfonPE_oC1mBgpdk6_cVOV8OcqQyAww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Safia Abdalla
Sep 9, 2015, 9:43:12 PM9/9/15
to jup...@googlegroups.com
Brian,
I think this is an awesome idea! I know Coraline, the woman who wrote up the Contributor Covenant, and trust the work that she has put into the document. Any adaptation that we take from it will work well for Jupyter.
Consider this my impassioned endorsement.
Brian Granger
Sep 9, 2015, 9:50:10 PM9/9/15
to Project Jupyter
Chris, good point.
In the past, when these issues have arisen, we often take them up
privately. Other times, when they are mild, we try to reply in the
same context in which they occur so the community can see in place how
we handle these things. Not sure how to "formalize" that practice best
and still have a clear process.
The other issue with using issues for this is that with our many, many
repos, it is a little difficult to keep track of all the issues that
show up in the corners of the repos.
> https://groups.google.com/d/msgid/jupyter/CAPc_zRXkYv97071HTvDkW74dMyTJsFit7XMb%2BYBFFZHhznTr-A%40mail.gmail.com.
In the past, when these issues have arisen, we often take them up
privately. Other times, when they are mild, we try to reply in the
same context in which they occur so the community can see in place how
we handle these things. Not sure how to "formalize" that practice best
and still have a clear process.
The other issue with using issues for this is that with our many, many
repos, it is a little difficult to keep track of all the issues that
show up in the corners of the repos.
Jessica B. Hamrick
Sep 9, 2015, 9:51:44 PM9/9/15
to jup...@googlegroups.com
+1 from me for adopting this as well.
--
Cheers,
Jess
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAJ2PXeOGA9X%3D5a-YCjVmU%3D_esOS70QkiHnHsR2H%2BwjETufPK%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
Cheers,
Jess
Kyle Kelley
Sep 9, 2015, 11:26:14 PM9/9/15
to jup...@googlegroups.com
+1 for adoption
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CALUXcBwbkHG5ZnjP0XDrJqGMU2_B_gxMmBCh-YAmex6QQwOgxw%40mail.gmail.com.
MinRK
Sep 10, 2015, 6:53:38 AM9/10/15
to jup...@googlegroups.com
Same as Chris - +1 in general, but Issues probably aren't the place for reporting misconduct. The mailing list is probably the right place if it should be done publicly, or private contact to the steering council or a member if discretion is desired.
-MinRK
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CA%2BtbMaV6h_93s3AdmUJXifzttGNff_gc97cPgAyrEM_1EsU4yg%40mail.gmail.com.
Damián Avila
Sep 10, 2015, 9:18:23 AM9/10/15
to jup...@googlegroups.com
+1 as well for the adoption... also in agreement with Min's and Chris's comments...
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAHNn8BX9UbEBKWhjEfUoLSfhDxSLoYg-dHZ2gnmbqQnF%2B9g%2BRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
Damián Avila
Brian Granger
Sep 10, 2015, 10:49:10 AM9/10/15
to Project Jupyter
Sounds like there is consensus on this, I will create a PR on the
governance repo that adds this.
> https://groups.google.com/d/msgid/jupyter/CAH%2BmRR10N_fzzPNGarSC4VSdq_OUdP-4oOh8YEhFeON%3DC7GRJg%40mail.gmail.com.
governance repo that adds this.
MinRK
Sep 10, 2015, 2:58:30 PM9/10/15
to jup...@googlegroups.com
Great, thanks Brian!
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAH4pYpR8eRGe1_jXKYH_sJbZ9L9VeHRemwcrGt9HJFf8E-n6hA%40mail.gmail.com.
Fernando Perez
Sep 10, 2015, 8:57:39 PM9/10/15
to jup...@googlegroups.com
Hi all,
sorry for the silence, I've been traveling and with a grueling meeting schedule, this is my first breather...
Thanks Brian for pushing on this, we should have done it long ago!
I'm +1 on the idea, but I would also prefer that we have a designated set of contacts for reporting these issues rather than github.
One option is to have a single ab...@jupyter.org address, but it's always possible that the reporter may be concerned that the issue they are reporting may involve someone with access to that address.
An alternative would be to officially list a group in charge of handling these reports, staffed by say three volunteers. By default we could suggest that reports be sent to all three to increase reporting response speeds, but that gives the option to the reporter of omitting someone if they feel uncomfortable with one of them for any reason (such as that person being the source of conflict, for example).
Thoughts?
f
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAHNn8BUC2-nLtPyBAPCDLxzue8w1WRfYs%2B%3D%3DaS%3D4QhSCAcMNPw%40mail.gmail.com.
Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail
Damián Avila
Sep 11, 2015, 8:41:06 AM9/11/15
to jup...@googlegroups.com
>An alternative would be to officially list a group in charge of handling these reports, staffed by say three volunteers. By default we could suggest that reports be sent to all three to increase reporting response speeds, but that gives the option to the reporter of omitting someone if they feel uncomfortable with one of them for any reason (such as that person being the source of conflict, for example).
I tend to agree with this option.
To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAHAreOqHM6yowpwfsTaLrNCrSm5_OawybX-ZwnKDcggSBH1p-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
Damián Avila
Carol Willing
Sep 11, 2015, 9:40:15 AM9/11/15
to Project Jupyter
+1 on Code of Conduct.
Django's Code of Conduct Reporting is one of the best in open source and very similar to Fernando's suggestion. https://www.djangoproject.com/conduct/reporting/
Agree that GitHub is the wrong avenue for reports.
Reply all
Reply to author
Forward
0 new messages