From b434b7d1d7662ed8e509bd9ac9c767d4c480be6a Mon Sep 17 00:00:00 2001 From: Bastian Greshake Date: Fri, 5 Feb 2016 14:50:42 +0100 Subject: [PATCH 1/2] added first CoC draft --- app/views/news/index.html.erb | 8 ++- code_of_conduct.md | 91 +++++++++++++++++++++++++++++++++++ 2 files changed, 97 insertions(+), 2 deletions(-) create mode 100644 code_of_conduct.md diff --git a/app/views/news/index.html.erb b/app/views/news/index.html.erb index 010893a..eb1e3af 100644 --- a/app/views/news/index.html.erb +++ b/app/views/news/index.html.erb @@ -40,9 +40,13 @@ }).render().setUser('opensnporg').start(); +
2016-02-05: Adopting a Code of Conduct
+

+ We strive to keep openSNP a friendly community, amongst our developers as well as the community on openSNP.org. So far this hasn't been a problem and we don't expect it to become one. Thanks for being model open science citizens to everyone in the openSNP universe. In order to show our commitment to diversity, inclusion and creating safe spaces we are adopting a Code of Conduct, inspired by the team of Slidewinder.io. +

2015-09-23: openSNP is now on Patreon

- As our database has grown so much (over 2100 data sets already!), we will need to upgrade our server to keep track with the amount of data to process. To support us in renting more computing power you can help us with a small monthly contribution on Patreon. You can learn more about this on our blog! + As our database has grown so much (over 2100 data sets already!), we will need to upgrade our server to keep track with the amount of data to process. To support us in renting more computing power you can help us with a small monthly contribution on Patreon. You can learn more about this on our blog!

#thedress, ethics for participant-lead research, research hack days

@@ -56,7 +60,7 @@

API: JSON methods

- The promised support for the Distributed Annotation System will take some time. But in the meantime you can access openSNP using some simple JSON-methods. Examples can be found for SNPs, users and phenotypes. To learn more about how to use those methods you may want to read the FAQ or this blogpost we've written about this. + The promised support for the Distributed Annotation System will take some time. But in the meantime you can access openSNP using some simple JSON-methods. Examples can be found for SNPs, users and phenotypes. To learn more about how to use those methods you may want to read the FAQ or this blogpost we've written about this.

SSL-Support

diff --git a/code_of_conduct.md b/code_of_conduct.md new file mode 100644 index 0000000..1170f66 --- /dev/null +++ b/code_of_conduct.md @@ -0,0 +1,91 @@ +# Code of Conduct + +## 1. Purpose + +A primary goal of openSNP is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof). + +This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior. + +We invite all those who participate in openSNP to help us create safe and positive experiences for everyone. + +## 2. Open [Source/Culture/Tech] Citizenship + +A supplemental goal of this Code of Conduct is to increase open [source/culture/tech] citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community. + +Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society. + +If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know. + +## 3. Expected Behavior + +The following behaviors are expected and requested of all community members: + +- Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community. +- Exercise consideration and respect in your speech and actions. +Attempt collaboration before conflict. +- Refrain from demeaning, discriminatory, or harassing behavior and speech. +- Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential. +- Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations. + + +## 4. Unacceptable Behavior + +The following behaviors are considered harassment and are unacceptable within our community: + +- Violence, threats of violence or violent language directed against another person. +- Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language. +- Posting or displaying sexually explicit or violent material. +- Posting or threatening to post other people’s personally identifying information ("doxing"). +- Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability. +- Inappropriate photography or recording. +- Inappropriate physical contact. You should have someone’s consent before touching them. +- Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances. +- Deliberate intimidation, stalking or following (online or in person). +- Advocating for, or encouraging, any of the above behavior. +- Sustained disruption of community events, including talks and presentations. + +## 5. Consequences of Unacceptable Behavior + +Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated. + +Anyone asked to stop unacceptable behavior is expected to comply immediately. + +If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event). + +## 6. Reporting Guidelines + +If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible by emailing info@opensnp.org. + +Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress. + +## 7. Addressing Grievances + +If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the openSNP team with a concise description of your grievance. + +## 8. Scope + +We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues–online and in-person–as well as in all one-on-one communications pertaining to community business. + +This code of conduct and its related procedures also applies to unacceptable behavior occuring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members. + +## 9. Contact info + +**To report or discuss a suspected violation of this code of conduct by a community member, you may contact any of the team directly and in confidence**: + +- Bastian Greshake +- Philipp Bayer +- Helge Rausch + +## 10. License and attribution + +This Code of Conduct is distributed under a Creative Commons Attribution-ShareAlike license. + +We shamelessly copied and adapted it from [Slidewinder](http://www.slidewinder.io) + +It is derived from the Citizen Code of Conduct at http://citizencodeofconduct.org/. + +Portions of text dervied from the Django Code of Conduct and the Geek Feminism Anti-Harassment Policy. + +Revision 2.1. Posted 4 February 2015. + +Revision 2.0, adopted by the Stumptown Syndicate board on 10 January 2013. Posted 17 March 2013. From 697ef3469eea47eac494791143d87703ed9afc10 Mon Sep 17 00:00:00 2001 From: Bastian Greshake Date: Fri, 5 Feb 2016 16:21:35 +0100 Subject: [PATCH 2/2] added kay as external person --- code_of_conduct.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/code_of_conduct.md b/code_of_conduct.md index 1170f66..d9afed3 100644 --- a/code_of_conduct.md +++ b/code_of_conduct.md @@ -76,6 +76,13 @@ This code of conduct and its related procedures also applies to unacceptable beh - Philipp Bayer - Helge Rausch +**To report or discuss a suspected violation of this code of conduct by a member of the core team, you may contact any of these people in confidence**: + +- Kay Thaney, Director @ Mozilla Science Lab + - email: kay@mozillascience.org + - twitter: [@kaythaney](http://twitter.com/kaythaney) + - gitter: https://gitter.im/kaythaney + ## 10. License and attribution This Code of Conduct is distributed under a Creative Commons Attribution-ShareAlike license.