Difference between revisions of "Competition/Rules of Conduct/Responsible Conduct"

m (Protected "Competition/Rules of Conduct/Responsible Conduct" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) [cascading])
 
(2 intermediate revisions by 2 users not shown)
Line 3: Line 3:
  
 
<div class="column full_size">
 
<div class="column full_size">
−
<h1>Responsible Conduct Committee</h1>
+
    <h1>Responsible Conduct Committee</h1>
−
<p> <span class="on_page"></span>
+
    <p> <span class="on_page"></span>
−
<b> On this page</b> you will find:
+
    <b> On this page</b> you will find:
−
<a href="#mission">Committee Mission</a>,
+
    <a href="#mission">Committee Mission</a>,
−
<a href="#examples">Examples</a>,
+
    <a href="#examples">Examples</a>,
−
<a href="#members">Committee Members</a>, and
+
    <a href="#members">Committee Members</a>, and
−
<a href="#contacting">Contacting the RCC Committee</a>
+
    <a href="#contacting">Contacting the RCC Committee</a>
−
.</p>
+
    .</p>
  
−
<div class="clear extra_space" id="mission"></div>
+
    <div class="clear extra_space" id="mission"></div>
  
−
<h3>Committee Mission</h3>
+
    <h3>Committee Mission</h3>
−
<p> The iGEM Responsible Conduct Committee is an external panel of experts who deal with all issues related to conduct in the competition. Our RCC members collectively have over 20 years of experience in the iGEM competition and are well versed in conduct and behavior related issues. </p>
+
    <p> The iGEM Responsible Conduct Committee is an external panel of experts who deal with all issues related to conduct in the competition. Our RCC members collectively have over 20 years of experience in the iGEM competition and are well versed in conduct and behavior related issues. </p>
  
−
<p>The role of the Responsible Conduct Committee is to ensure a high standard of conduct on the part of all iGEM participants and to address issues of inappropriate behavior in iGEM. The committee is led by Director of Judging, Peter Carr.</p>
+
    <p>The role of the Responsible Conduct Committee is to ensure a high standard of conduct on the part of all iGEM participants and to address issues of inappropriate behavior in iGEM. The committee is led by Director of Judging, Peter Carr.</p>
 
</div>
 
</div>
  
 
<div class="column half_size">
 
<div class="column half_size">
−
        <h3>Conduct Policy</h3>
+
    <h3>Conduct Policy</h3>
−
<p>Members of the iGEM Community, including iGEMers, judges and other members of our community, are expected to uphold the values of iGEM:</p>
+
    <p>Members of the iGEM Community, including iGEMers, judges and other members of our community, are expected to uphold the <a href="https://igem.org/Values">values</a> of iGEM:</p>
−
<ul>
+
    <ul>
−
<li>Integrity</li>
+
        <li>Integrity</li>
−
<li>Good sportsmanship</li>
+
        <li>Good sportsmanship</li>
−
<li>Respect</li>
+
        <li>Respect</li>
−
<li>Honesty</li>
+
        <li>Honesty</li>
−
<li>Celebration</li>
+
        <li>Celebration</li>
−
<li>Cooperation</li>
+
        <li>Cooperation</li>
−
<li>Effort</li>
+
        <li>Effort</li>
−
<li>Excellence</li>
+
        <li>Excellence</li>
−
</ul>
+
    </ul>
 
</div>
 
</div>
  
  
 
<div class="column half_size">
 
<div class="column half_size">
−
<img src= "https://2016.igem.org/wiki/images/0/08/IGEM_Responsible_Conduct_1.png">
+
    <img src= "https://2016.igem.org/wiki/images/0/08/IGEM_Responsible_Conduct_1.png">
 
</div>
 
</div>
  
  
 
<!------------------------------------------------------------------------------------------------------------------------->
 
<!------------------------------------------------------------------------------------------------------------------------->
−
 
  
  
Line 50: Line 49:
  
 
<div class="column full_size">
 
<div class="column full_size">
 +
    <h2>What kinds of inappropriate behavior are we referring to, and what kinds of consequences?</h2>
 +
    <p>
 +
        The Responsible Conduct Committee (RCC) is tasked with making sure that iGEMers, judges and members of our community are upholding the highest values of iGEM. Below, you'll find some examples of situations that the RCC would be tasked with investigating. Please note that these are purely hypothetical situations that have no bearing on past events in iGEM.
 +
    </p>
  
−
<h2>What kinds of inappropriate behavior are we referring to, and what kinds of consequences?</h2>
+
    <div class="clear extra_space"></div>
−
<p>This committee is tasked with making sure that iGEMers, judges and members of our community are upholding the highest values of iGEM. Below, you'll find some examples of situations where the responsible conduct committee would be tasked with investigating. Please note that these are purely hypothetical situations that have no bearing on past events in iGEM. </p>
+
  
−
<div class="clear extra_space"></div>
+
    <div class="highlight gray">
 +
        <h3> Example 1: Biased Judging</h3>
 +
        <p>A judge that has a conflict of interest (such as also advising an iGEM team) tries to use their position as judge to convince other judges their team deserves an award. (iGEM judging policy clearly forbids this.) If this happens once, and seems to be an honest mistake, that judge is simply instructed by other judges, and the RCC does not get called into action. If a judge repeatedly and deliberately continues to violate the conflict of interest policy, the RCC can be asked to make a decision. In an extreme case, that judge could be barred from future iGEM judging and a letter sent to his or her organization explaining why this decision was made.</p>
 +
    </div>
  
−
<div class="highlight gray">
+
    <div class="clear extra_space"></div>
−
<h3> Example 1 </h3>
+
−
<p>A judge that has a conflict of interest (such as also advising an iGEM team) tries to use their position as judge to convince other judges their team deserves an award. (iGEM judging policy clearly forbids this.) If this happens once, and seems to be an honest mistake, that judge is simply instructed by other judges, and the RCC does not get called into action. If a judge repeatedly and deliberately continues to violate the conflict of interest policy, the RCC can be asked to make a decision. In an extreme case, that judge could be barred from future iGEM judging and a letter sent to his or her organization explaining why this decision was made.</p>
+
−
</div>
+
  
−
<div class="clear extra_space"></div>
+
    <div class="highlight gray">
 +
        <h3> Example 2: Dishonest Attribution</h3>
 +
        <p>A team takes credit for the work of others. If it is simply a matter of poor attribution (for example, the team forgets to include literature references on their wiki) this is a simple judging issue and not a matter for the RCC. The team will simply get a poor score from the judges on attribution. But if a team takes the results of another team or research group and seeks to pass that work off as their own, it is a more serious matter, and the RCC could be asked to make a decision. This should not be confused with two teams that simply happen to be working on similar projects. Possible consequences could include being disqualified from receiving awards (if before the Jamboree) or even taking away an award (if a decision can only be made after the Jamboree). iGEM takes honesty and attribution very seriously.</p>
 +
    </div>
  
−
<div class="highlight gray">
+
    <div class="clear extra_space"></div>
−
<h3> Example 2 </h3>
+
−
<p>A team takes credit for the work of others. If it is simply a matter of poor attribution (for example, the team forgets to include literature references on their wiki) this is a simple judging issue and not a matter for the RCC. The team will simply get a poor score from the judges on attribution. But if a team takes the results of another team or research group and seeks to pass that work off as their own, it is a more serious matter, and the RCC could be asked to make a decision. This should not be confused with two teams that simply happen to be working on similar projects. Possible consequences could include being disqualified from receiving awards (if before the Jamboree) or even taking away an award (if a decision can only be made after the Jamboree). iGEM takes honesty and attribution very seriously.</p>
+
−
</div>
+
−
+
−
<div class="clear extra_space"></div>
+
  
−
<div class="highlight gray">
+
    <div class="highlight gray">
−
<h3>Example 3</h3>
+
        <h3>Example 3: Harrassment</h3>
−
<p>Some members of a team are unhappy with the judging results and decide to take that frustration out on the judges. They send e-mails to the judges insulting and threatening them. [NOTE: this has never happened] This would definitely be a matter for the RCC. Consequences could include a team being stripped of awards and individuals not allowed any future involvement in iGEM. While this action has not been taken in iGEM, an institution could be banned from participating in future competitions. In the most extreme cases, matters would be referred to the appropriate legal authorities.</p>
+
        <p>Some members of a team are unhappy with the judging results and decide to take that frustration out on the judges. They send e-mails to the judges insulting and threatening them. [NOTE: this has never happened] This would definitely be a matter for the RCC. Consequences could include a team being stripped of awards and individuals not allowed any future involvement in iGEM. While this action has not been taken in iGEM, an institution could be banned from participating in future competitions. In the most extreme cases, matters would be referred to the appropriate legal authorities.</p>
−
</div>
+
    </div>
−
+
 
 +
    <div class="clear extra_space"></div>
 +
 
 +
    <div class="highlight gray">
 +
        <h3>Example 4: Stereotyping and Over-Promising</h3>
 +
        <p>A team’s promotional video includes scenes where they pretend to experience a diabetic attack. A reviewer flags the exaggerated, almost-comical way the team acted out the diabetes symptoms, and a scene which shows someone falling into a coma, while a voiceover announces that this never could have happened if they’d used the team’s engineered microbiome solution. The RCC reaches out to make sure that the team intended for the video to be respectful, and has engaged responsibly with any diabetic people contacted during their project. As long as the discussion does not reveal other issues, the only change would be the addition of a content warning to the beginning of the video.</p>
 +
    </div>
 +
 
 +
    <div class="clear extra_space"></div>
 +
 
 +
    <div class="highlight gray">
 +
        <h3>Example 5: Tasting Prototypes</h3>
 +
        <p>A team produces biodegradable food colouring from engineered bacteria. They extract the dye, then make sure that it tastes okay by spreading it on some toast and having a bite. If the toast was eaten in the lab, this is a <a href="https://2021.igem.org/Safety/Working_Safely">Lab Safety issue</a>, and if the dye was brought outside the lab without permission from the Safety and Security Committee, this violates the <a href="https://2021.igem.org/Safety/Do_not_Release">Do Not Release</a> policy. Regardless, the fact that someone took a bite is a straightforward violation of the <a href="https://2020.igem.org/Safety/Policies#human">No Human Experimentation</a> policy. Consequences for violating these Safety policies would be ultimately determined by the Safety and Security Committee, who would likely recommend full or partial disqualification of the project. The RCC might also get involved, as such violations also raise questions about whether the team is upholding iGEM’s values.</p>
 +
    </div>
 
</div>
 
</div>
  
 
<!------------------------------------------------------------------------------------------------------------------------->
 
<!------------------------------------------------------------------------------------------------------------------------->
  
−
<div class="clear extra_space"></div>
+
    <div class="clear extra_space"></div>
−
<div class="line_divider"></div>
+
    <div class="line_divider"></div>
−
<div class="clear extra_space" id="members"></div>
+
    <div class="clear extra_space" id="members"></div>
−
+
 
  
 
<div class="column full_size">
 
<div class="column full_size">
  
−
<h2>Committee Members</h2>
+
    <h2>Committee Members</h2>
−
<div class="clear extra_space"></div>
+
    <div class="clear extra_space"></div>
−
<img src="https://static.igem.org/mediawiki/2021/9/97/Competition_rcc_committee.jpg">
+
    <img src="https://static.igem.org/mediawiki/2021/9/97/Competition_rcc_committee.jpg">
−
<p class="image_caption"> Members of the Responsible Conduct Committee Committee at the 2019 Giant Jamboree</p>
+
    <p class="image_caption"> Members of the Responsible Conduct Committee Committee at the 2019 Giant Jamboree</p>
−
<div class="clear extra_space"></div>
+
    <div class="clear extra_space"></div>
  
  
−
<ul>
+
    <ul>
−
<li>Committee Chair: Peter Carr</li>
+
        <li>Committee Chair: Chris French</li>
−
<li>Committee HQ Liaison: Traci Haddock-Angelli</li>
+
        <li>Committee Co-Chair: Karmella Haynes</li>
−
<li>Committee HQ Liaison: Piers Millet</li>
+
        <li>Committee HQ Liaison: Traci Haddock-Angelli</li>
−
</ul>
+
        <li>Committee HQ Liaison: Piers Millet</li>
 +
    </ul>
  
  
−
<p> Voting Committee Members:</p>
+
    <p> Voting Committee Members:</p>
−
<ul>
+
    <ul>
−
<li>Chris French</li>
+
        <li>Peter Carr</li>
−
<li>Genya Dana</li>
+
        <li>Genya Dana</li>
−
<li>Karmella Haynes</li>
+
        <li>Karmella Haynes</li>
−
<li>King Chow</li>
+
        <li>King Chow</li>
−
<li>Roman Jerala</li>
+
        <li>Christopher Workman</li>
−
</ul>
+
    </ul>
  
−
<p>Emeritus Committee Members:</p>
+
    <p>Emeritus Committee Members:</p>
−
<ul>
+
    <ul>
−
<li>Martha Eborall</li>
+
        <li>Martha Eborall</li>
−
<li>Terry Johnson</li>
+
        <li>Terry Johnson</li>
−
</ul>
+
        <li>Roman Jerala</li>
 +
    </ul>
  
  
Line 122: Line 137:
  
  
−
<div class="clear extra_space"></div>
+
    <div class="clear extra_space"></div>
−
<div class="line_divider"></div>
+
    <div class="line_divider"></div>
−
<div class="clear extra_space" id="contacting"></div>
+
    <div class="clear extra_space" id="contacting"></div>
−
+
 
−
<div class="column full_size">
+
    <div class="column full_size">
−
<h2>Contacting the RCC Committee</h2>
+
        <h2>Contacting the RCC Committee</h2>
−
<p>If you suspect someone involved in iGEM is in breach of the values of iGEM and behaving in a manner not in line with the high standards of iGEM, you can contact the committee to open a case. However, you should only contact the committee in a case where breach of iGEM values and behavior are the core issues. </p>
+
        <p>If you suspect someone involved in iGEM is in breach of the values of iGEM and behaving in a manner not in line with the high standards of iGEM, you can contact the committee to open a case. However, you should only contact the committee in a case where breach of iGEM values and behavior are the core issues. </p>
−
+
 
−
+
 
−
<h3>Responsible Conduct Committee</h3>
+
        <h3>Responsible Conduct Committee</h3>
−
<p>To contact the Responsible Conduct Committee, please email <i>rcc [AT] igem [DOT] org</i>.<p>
+
        <p>To contact the Responsible Conduct Committee, please email <i>rcc [AT] igem [DOT] org</i>.<p>
 +
 
 +
        <h3>Judging</h3>
 +
        <p>For issues related to judging, please contact the Judging Program Committee (<i>judging [AT] igem [DOT] org</i>). </p>
 +
 
 +
        <h3>Lab Safety</h3>
 +
        <p>For lab safety or project safety issues, please contact the iGEM Safety Committee (<i>safety [AT] igem [DOT] org</i>).</p>
  
−
<h3>Judging</h3>
 
−
<p>For issues related to judging, please contact the Judging Program Committee (<i>judging [AT] igem [DOT] org</i>). </p>
 
−
 
−
<h3>Lab Safety</h3>
 
−
<p>For lab safety or project safety issues, please contact the iGEM Safety Committee (<i>safety [AT] igem [DOT] org</i>).</p>
 
  
 +
        <div class="clear extra_space"></div>
  
−
<div class="clear extra_space"></div>
+
        <div class="highlight post gray">
−
+
            <div class="details">
−
<div class="highlight post_item gray">
+
                <div class="title why">Questions?</div>
−
    <div class="details">
+
            </div>
−
    <span class="icon why"></span>
+
            <div class="column full_size">
−
<div class="title">Questions?</div>
+
            <p>If you are not sure which committee to contact, you may email Traci Haddock-Angelli, the iGEM Director of the Competition, directly for advice at <i>traci [AT] igem [DOT] org</i> or send an email to iGEM Headquarters at <i> hq [AT] igem [DOT] org</i>.</p>
−
</div>
+
            </div>
−
   
+
        </div>
−
    <p>If you are not sure which committee to contact, you may email Traci Haddock-Angelli, the iGEM Director of the Competition, directly for advice at <i>traci [AT] igem [DOT] org</i> or send an email to iGEM Headquarters at <i> hq [AT] igem [DOT] org</i>.</p>
+
−
   
+
−
</div>
+
  
−
</div>
+
    </div>
  
  

Latest revision as of 13:01, 13 November 2021

CALENDAR
Meetups & Events
Opening Weekend Festival ⇗
TEAMS
Certificates ⇗
Judging Feedback ⇗
iGEM 2021 Survey ⇗
Team Grants
Impact Grant
Safety & Security Grant
Team Information
Team List ⇗
Team Wikis ⇗
Team Parts ⇗
Community
Collaborations
Mentorship
iGEM Global Slack
Ambassadors
Ambassador / Team Calls
News Archive
Quick Links
Create an Account ⇗
Join a Team ⇗
COMPETITION
Register A Team
Team Fee
Handbook
Consent Forms
Commercial Teams
2021 Requirements
Team Requirements
Rules of Conduct
Responsible Conduct
Deliverables
Safety Forms
Promotion Video
Team Wiki
Team Poster
Team Presentation
Judging Form
Project Attribution
Part Pages
Project Description
Title and Abstract
Track Selection
Team Roster
Other Information
About Tracks
Diagnostics
Energy
Environment
Food and Nutrition
Foundational Advance
Hardware
High School
Information Processing
Manufacturing
New Application
Open
Software
Therapeutics
Two-Phase Projects
Distribution Kit
GIANT JAMBOREE ⇗
Team Registration
Judging Sessions
Team Information
Volunteer
JUDGING
For Teams
Introduction
Medals
Awards
Pages for Awards
Rubric
Judging Form ⇗
Other Information
Committees
For Judges
Resources
Application
Judging Handbook
SAFETY
Online Events
Workshops
Requirements
Working Safely
Rules
Policies
Coronavirus
Do Not Release
Roles
Committee
Tools
Risk Groups
White List
Risk Assessment Tool
Environmental Samples
Exemplary Projects
Forms
Safety Form
Check In Form
Animal Use Form
HUMAN PRACTICES
Introduction
FAQ
Resources
Examples
History
Committee
ENGINEERING
Introduction
Design
Build
Test
Learn
Exemplary Projects
Committee
StackExchange
Online Events
Webinars
DIVERSITY
Introduction
Gender Diversity
Committee
Recommendations
Examples
Black Lives Matter
VIDEOS
Video Universe ⇗
Production
Wiki
Examples
RESOURCES
General
Navigating iGEM
Tips for Teams
Start a Team
Funding
FAQ
SDGs
Wet and Dry Lab
Cloning Help
Transformations
Digests & Ligations
Parts Registry ⇗
Software Tools
Documentation
Telling your Story
Wiki Editing Help
HTML CSS Javascript
Template Documentation

Responsible Conduct Committee

On this page you will find: Committee Mission, Examples, Committee Members, and Contacting the RCC Committee .

Committee Mission

The iGEM Responsible Conduct Committee is an external panel of experts who deal with all issues related to conduct in the competition. Our RCC members collectively have over 20 years of experience in the iGEM competition and are well versed in conduct and behavior related issues.

The role of the Responsible Conduct Committee is to ensure a high standard of conduct on the part of all iGEM participants and to address issues of inappropriate behavior in iGEM. The committee is led by Director of Judging, Peter Carr.

Conduct Policy

Members of the iGEM Community, including iGEMers, judges and other members of our community, are expected to uphold the values of iGEM:

  • Integrity
  • Good sportsmanship
  • Respect
  • Honesty
  • Celebration
  • Cooperation
  • Effort
  • Excellence

What kinds of inappropriate behavior are we referring to, and what kinds of consequences?

The Responsible Conduct Committee (RCC) is tasked with making sure that iGEMers, judges and members of our community are upholding the highest values of iGEM. Below, you'll find some examples of situations that the RCC would be tasked with investigating. Please note that these are purely hypothetical situations that have no bearing on past events in iGEM.

Example 1: Biased Judging

A judge that has a conflict of interest (such as also advising an iGEM team) tries to use their position as judge to convince other judges their team deserves an award. (iGEM judging policy clearly forbids this.) If this happens once, and seems to be an honest mistake, that judge is simply instructed by other judges, and the RCC does not get called into action. If a judge repeatedly and deliberately continues to violate the conflict of interest policy, the RCC can be asked to make a decision. In an extreme case, that judge could be barred from future iGEM judging and a letter sent to his or her organization explaining why this decision was made.

Example 2: Dishonest Attribution

A team takes credit for the work of others. If it is simply a matter of poor attribution (for example, the team forgets to include literature references on their wiki) this is a simple judging issue and not a matter for the RCC. The team will simply get a poor score from the judges on attribution. But if a team takes the results of another team or research group and seeks to pass that work off as their own, it is a more serious matter, and the RCC could be asked to make a decision. This should not be confused with two teams that simply happen to be working on similar projects. Possible consequences could include being disqualified from receiving awards (if before the Jamboree) or even taking away an award (if a decision can only be made after the Jamboree). iGEM takes honesty and attribution very seriously.

Example 3: Harrassment

Some members of a team are unhappy with the judging results and decide to take that frustration out on the judges. They send e-mails to the judges insulting and threatening them. [NOTE: this has never happened] This would definitely be a matter for the RCC. Consequences could include a team being stripped of awards and individuals not allowed any future involvement in iGEM. While this action has not been taken in iGEM, an institution could be banned from participating in future competitions. In the most extreme cases, matters would be referred to the appropriate legal authorities.

Example 4: Stereotyping and Over-Promising

A team’s promotional video includes scenes where they pretend to experience a diabetic attack. A reviewer flags the exaggerated, almost-comical way the team acted out the diabetes symptoms, and a scene which shows someone falling into a coma, while a voiceover announces that this never could have happened if they’d used the team’s engineered microbiome solution. The RCC reaches out to make sure that the team intended for the video to be respectful, and has engaged responsibly with any diabetic people contacted during their project. As long as the discussion does not reveal other issues, the only change would be the addition of a content warning to the beginning of the video.

Example 5: Tasting Prototypes

A team produces biodegradable food colouring from engineered bacteria. They extract the dye, then make sure that it tastes okay by spreading it on some toast and having a bite. If the toast was eaten in the lab, this is a Lab Safety issue, and if the dye was brought outside the lab without permission from the Safety and Security Committee, this violates the Do Not Release policy. Regardless, the fact that someone took a bite is a straightforward violation of the No Human Experimentation policy. Consequences for violating these Safety policies would be ultimately determined by the Safety and Security Committee, who would likely recommend full or partial disqualification of the project. The RCC might also get involved, as such violations also raise questions about whether the team is upholding iGEM’s values.

Committee Members

Members of the Responsible Conduct Committee Committee at the 2019 Giant Jamboree

  • Committee Chair: Chris French
  • Committee Co-Chair: Karmella Haynes
  • Committee HQ Liaison: Traci Haddock-Angelli
  • Committee HQ Liaison: Piers Millet

Voting Committee Members:

  • Peter Carr
  • Genya Dana
  • Karmella Haynes
  • King Chow
  • Christopher Workman

Emeritus Committee Members:

  • Martha Eborall
  • Terry Johnson
  • Roman Jerala

Contacting the RCC Committee

If you suspect someone involved in iGEM is in breach of the values of iGEM and behaving in a manner not in line with the high standards of iGEM, you can contact the committee to open a case. However, you should only contact the committee in a case where breach of iGEM values and behavior are the core issues.

Responsible Conduct Committee

To contact the Responsible Conduct Committee, please email rcc [AT] igem [DOT] org.

Judging

For issues related to judging, please contact the Judging Program Committee (judging [AT] igem [DOT] org).

Lab Safety

For lab safety or project safety issues, please contact the iGEM Safety Committee (safety [AT] igem [DOT] org).

Questions?

If you are not sure which committee to contact, you may email Traci Haddock-Angelli, the iGEM Director of the Competition, directly for advice at traci [AT] igem [DOT] org or send an email to iGEM Headquarters at hq [AT] igem [DOT] org.

iGEM Foundation

The International Genetically Engineered Machine (iGEM) Foundation is an independent, non-profit organization dedicated to the advancement of synthetic biology, education and competition, and the development of an open community and collaboration. Visit us at igem.org

Contact


hq AT igem DOT org


45 Prospect Street
Cambridge, MA 02139


Due to COVID-19, iGEM staff are working remotely and cannot receive phone calls.
Please contact us by email.

Quicklinks

Main Page
Competition Requirements
News
Calendar
Events
Sponsor Offers
Collaborations
Resources Hub
Sitemap

Keep in touch!




Join Slack:

Stay up to date with our newsletter:

SUBSCRIBE