Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Critical
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Story Points:1.1
-
Epic Link:
-
Sprint:Fall 4 : 30 Sep to 11 Oct, Summer 1: 8 Jun - 19 Jun, Summer 2: 22 Jun - 3 Jul, Summer 3: 6 Jul - 17 Jul
Description
Many open source projects have a stated "code of conduct" describing proper behavior for contributors.
For example, a code of conduct can explain whether or not it is OK to reveal another contributor's email address or other personal details.
To get a sense of why this type of thing is important, read this recent article that touches on on-line communities and how people within them interact:
https://www.newyorker.com/magazine/2019/09/30/four-years-in-startups
We do not have a written and publicly shared code of conduct for the IGB project. However, we also would like for external developers to contribute! To make this easier, we should provide a "code of conduct" so that developers will come to know good ways to interact with other IGB contributors as well as with developers working on related sister projects.
For this task, please provide links to codes of conduct (5 to 10?) used by open source projects.
Read them and and then make note of any commonalities among them. Also make note of aspects you feel we should consider when developing a code of conduct for the various IGB-related projects.
Places to start:
Look for codes of conduct from awardees of Chan Zukerberg Initiative Essential Open Source Softare grants
Code of Conduct
Guide to Contributions
Jbrowse
Apollo
Bioconductor project
R project
Galaxy
BioPerl
BioPython
BioJava
BioConda - good one to do
- Galaxy project code of conduct
- Codes of conduct for projects that include large numbers of contributors (Linux maybe?)
When you have finished above, review the codes of conduct and pull out ideas and themes you think in your best judgement we should emulate for the IGB project.
Attachments
Activity
Thank you so much - this is great!
Quick request: Please transfer ownership of the doc to aloraine@uncc.edu.
I'll then put into the same folder with your "papers citing IGB" doc and also make sure you will still be able to edit it.
[~aloraine]
I accidentally transferred the ownership to the current added email of: Ann.Loraine@uncc.edu instead of aloraine@uncc.edu
Please let me know if this will cause any issues
Thank you
Moving this ticket back to needs first level review
I think we should use this one - https://www.contributor-covenant.org
The guidelines seem clear and easy to understand, and many projects are already using it. Many developers are probably already familiar with this, and so it will be easier for them to join our project if we use the same code of conduct their other projects are using.
For the next steps, could you make a branch that contains a new "md" file with the CoC from their site - https://www.contributor-covenant.org/version/2/0/code_of_conduct/code_of_conduct.md ? For the contact email, please use igbhelper@gmail.com
Once that is done, we can get some feedback from people on the team.
cc: Jay Chamma
I added the CoC to an "md" file and added it to a new branch
branch link: https://bitbucket.org/Gchamma/integrated-genome-browser/branch/IGBF-2029
Moving this ticket to "needs first level review"
Please see comments on the branch. Please review the comments, make changes as you see fit, rebase onto the main (master) branch, and submit a pull request.
Revised the Code of Conduct file as requested, rebased onto master and submitted a pull request
Pull request link:
https://bitbucket.org/lorainelab/integrated-genome-browser/pull-requests/805/create-a-new-md-file-containing-igb-code/diff
Steps to test this:
1. Update your repository with the remote master branch
2. Check the CodeOfConduct.md file inside the integrated-genome-browser folder
Please see the following Google document
https://docs.google.com/document/d/1jTZXcRGKKfSYN4acZXvAS_0bh8VM-lLOnSzooAQGChU/edit?usp=sharing
[~aloraine] I sent you an invitation to allow you to edit the document if needed
The document is ready for first level review