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
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | IGBF-1531 [ 17617 ] |
| Rank | Ranked higher |
| Assignee | Ann Loraine [ aloraine ] |
| Assignee | Ann Loraine [ aloraine ] |
| Story Points | 2 | 0.5 |
| Sprint | Fall 4 : 30 Sep to 11 Oct [ 75 ] | Fall 4 : 30 Sep to 11 Oct, Fall 5 : 14 Oct to 25 Oct [ 75, 76 ] |
| Rank | Ranked higher |
| Workflow | Fall 2019 Workflow Update [ 20786 ] | Revised Fall 2019 Workflow Update [ 21128 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | To-Do [ 10305 ] |
| Sprint | Fall 4 : 30 Sep to 11 Oct, Fall 5 : 14 Oct to 25 Oct [ 75, 76 ] | Fall 4 : 30 Sep to 11 Oct [ 75 ] |
| Sprint | Fall 4 : 30 Sep to 11 Oct [ 75 ] | Fall 4 : 30 Sep to 11 Oct, Summer 1: 8 Jun - 19 Jun [ 75, 96 ] |
| Labels | Beginner Intern |
| 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: * Galaxy project code of conduct * Codes of conduct for projects that include large numbers of contributors (Linux maybe?) When you have finished above, |
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: * 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. |
| Story Points | 0.5 | 1 |
| Story Points | 1 | 2 |
| Rank | Ranked higher |
| Sprint | Fall 4 : 30 Sep to 11 Oct, Summer 1: 8 Jun - 19 Jun [ 75, 96 ] | Fall 4 : 30 Sep to 11 Oct, Summer 1: 8 Jun - 19 Jun, Summer 2: 22 Jun - 3 July [ 75, 96, 97 ] |
| Rank | Ranked higher |
| Assignee | Jay Chamma [ gchamma ] |
| 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: * 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. |
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. |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Story Points | 2 | 1 |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Story Points | 1 | 1.2 |
| Assignee | Jay Chamma [ gchamma ] |
| Story Points | 1.2 | 1.1 |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Jay Chamma [ gchamma ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Jay Chamma [ gchamma ] | Ann Loraine [ aloraine ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Assignee | Ann Loraine [ aloraine ] | Jay Chamma [ gchamma ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Assignee | Jay Chamma [ gchamma ] |
| Assignee | Jay Chamma [ gchamma ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | To-Do [ 10305 ] |
| Status | To-Do [ 10305 ] | In Progress [ 3 ] |
| Status | In Progress [ 3 ] | Needs 1st Level Review [ 10005 ] |
| Status | Needs 1st Level Review [ 10005 ] | First Level Review in Progress [ 10301 ] |
| Status | First Level Review in Progress [ 10301 ] | Ready for Pull Request [ 10304 ] |
| Status | Ready for Pull Request [ 10304 ] | Pull Request Submitted [ 10101 ] |
| Assignee | Jay Chamma [ gchamma ] |
| Status | Pull Request Submitted [ 10101 ] | Reviewing Pull Request [ 10303 ] |
| Status | Reviewing Pull Request [ 10303 ] | Merged Needs Testing [ 10002 ] |
| Assignee | Jay Chamma [ gchamma ] |
| Sprint | Fall 4 : 30 Sep to 11 Oct, Summer 1: 8 Jun - 19 Jun, Summer 2: 22 Jun - 3 Jul [ 75, 96, 97 ] | Fall 4 : 30 Sep to 11 Oct, Summer 1: 8 Jun - 19 Jun, Summer 2: 22 Jun - 3 Jul, Summer 3: 3 Jul - 14 Jul [ 75, 96, 97, 98 ] |
| Rank | Ranked higher |
| Assignee | Jay Chamma [ gchamma ] |
| Assignee | Jay Chamma [ gchamma ] |
| Assignee | Jay Chamma [ gchamma ] |
| Status | Merged Needs Testing [ 10002 ] | Post-merge Testing In Progress [ 10003 ] |
| Resolution | Done [ 10000 ] | |
| Status | Post-merge Testing In Progress [ 10003 ] | Closed [ 6 ] |
| Assignee | Jay Chamma [ gchamma ] |