Difference between revisions of "Team:Sherbrooke/Attributions"

m
m
Line 4: Line 4:
 
<h2> Attributions</h2>
 
<h2> Attributions</h2>
  
<p> Each team must clearly attribute work done by the student team members on this page. The team must distinguish work done by the students from work done by others, including the host labs, advisors, instructors, and individuals not on the team roster. </p>
 
 
 
<div class="highlightBox">
 
 
<h4> Can we base our project on a previous one? </h4>
 
<p>Yes! You can have a project based on a previous team, or based on someone else's idea, <b>as long as you state this fact very clearly and give credit for the original project.</b> </p>
 
</div>
 
 
 
 
<h4> Why is this page needed? </h4>
 
<p>The Attribution requirement helps the judges know what you did yourselves and what you had help with. We don't mind if you get help with difficult or complex techniques, but you must report what work your team did and what work was done by others.</p>
 
 
<p>
 
<p>
For example, you might choose to work with an animal model during your project. Working with animals requires getting a license and applying far in advance to conduct certain experiments in many countries. This is difficult to achieve during the course of a summer, but much easier if you can work with a postdoc or PI who has the right licenses.</p>
+
Being a team does not mean we do everything together. Actually, doing that would not be really optimal. Being a team for us is more that everyone contributes in their own way, with their own skills and ideas to the project. In our case, our project was big, it has a lot of different modules, each with their own challenges: some electrical, some mechanical, some software and even some human oriented. With that in mind, this page is intended to attributes, for every student team member, the work they have achieved to make this project a reality.
 
+
</p>
 
+
<h5> What should this page have?</h5>
+
 
+
<ul>
+
<li>General Support</li>
+
<li>Project support and advice</li>
+
<li>Fundraising help and advice</li>
+
<li>Lab support</li>
+
<li>Difficult technique support</li>
+
<li>Project advisor support</li>
+
<li>Wiki support</li>
+
<li>Presentation coaching</li>
+
<li>Human Practices support</li>
+
<li> Thanks and acknowledgements for all other people involved in helping make a successful iGEM team</li>
+
</ul>
+
  
  
<h4>Inspiration</h4>
 
<p>Take a look at what other teams have done:</p>
 
<ul>
 
<li><a href="https://2011.igem.org/Team:Imperial_College_London/Team">2011 Imperial College London</a> (scroll to the bottom)</li>
 
<li><a href="https://2014.igem.org/Team:Exeter/Attributions">2014 Exeter </a></li>
 
<li><a href="https://2014.igem.org/Team:Melbourne/Attributions">2014 Melbourne </a></li>
 
<li><a href="https://2014.igem.org/Team:Valencia_Biocampus/Attributions">2014 Valencia Biocampus</a></li>
 
</ul>
 
  
 
         </div></div> <!--Closing tag for div id="mainContainer" and div id="contentContainer". Opening tag are in the template-->
 
         </div></div> <!--Closing tag for div id="mainContainer" and div id="contentContainer". Opening tag are in the template-->
 
</html>
 
</html>

Revision as of 01:36, 13 August 2015

Attributions

Being a team does not mean we do everything together. Actually, doing that would not be really optimal. Being a team for us is more that everyone contributes in their own way, with their own skills and ideas to the project. In our case, our project was big, it has a lot of different modules, each with their own challenges: some electrical, some mechanical, some software and even some human oriented. With that in mind, this page is intended to attributes, for every student team member, the work they have achieved to make this project a reality.