Difference between revisions of "Team:Michigan Software/Attributions"

(Prototype team page)
 
Line 2: Line 2:
 
<html>
 
<html>
  
−
<h2> Attributions</h2>
+
<h1> Attributions</h1>
  
−
<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>
+
<h2> Student Attributions </h2>
−
 
+
<ul>
−
 
+
<li>Joshua Abramson: Organized team and Protocat Back-end</li>
−
<div class="highlightBox">
+
<li>Hy Doan: Protocat Back-end and Test Coverage</li>
−
 
+
<li>Graham Domnick: Outreach</li>
−
<h4> Can we base our project on a previous one? </h4>
+
<li>Max Gittleman: Protocat Back-end</li>
−
<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>
+
<li>Zach Gittleman: Protocat Front-end and API</li>
−
</div>
+
<li>Ali Hammoud: Treasurer</li>
−
 
+
<li>Ali Turfah: Wiki and Graphic design</li>
−
 
+
<li>Mary Weber: Poster and Presentation</li>
−
 
+
<li>Katherine Williams: Protocat user page</li>
−
<h4> Why is this page needed? </h4>
+
<li>Campbell Yore: Contacting labs</li>
−
<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>
+
</ul>
−
<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>
+
−
 
+
−
 
+
−
<h5> What should this page have?</h5>
+
  
 +
<h2>Adviser Attribution</h2>
 +
<ul>
 +
<li>Dr. Marcus Ammerlaan: General Project Adviser</li>
 +
<li>Dr. Cavalcoli: Project and Fundraising Adviser</li>
 +
<li>Dr. Chris Gates: Programming Consultant </li>
 +
<li>Dr. Santiago Schnell: Contact for department funding </li>
 +
</ul>
 
<ul>
 
<ul>
 
<li>General Support</li>
 
<li>General Support</li>
Line 34: Line 36:
 
<li>Human Practices support</li>
 
<li>Human Practices support</li>
 
<li> Thanks and acknowledgements for all other people involved in helping make a successful iGEM team</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>
 
</ul>
  
 
</div>
 
</div>
 
</html>
 
</html>

Revision as of 22:12, 17 September 2015


Michigan Software 2015

Attributions

Student Attributions

  • Joshua Abramson: Organized team and Protocat Back-end
  • Hy Doan: Protocat Back-end and Test Coverage
  • Graham Domnick: Outreach
  • Max Gittleman: Protocat Back-end
  • Zach Gittleman: Protocat Front-end and API
  • Ali Hammoud: Treasurer
  • Ali Turfah: Wiki and Graphic design
  • Mary Weber: Poster and Presentation
  • Katherine Williams: Protocat user page
  • Campbell Yore: Contacting labs

Adviser Attribution

  • Dr. Marcus Ammerlaan: General Project Adviser
  • Dr. Cavalcoli: Project and Fundraising Adviser
  • Dr. Chris Gates: Programming Consultant
  • Dr. Santiago Schnell: Contact for department funding
  • General Support
  • Project support and advice
  • Fundraising help and advice
  • Lab support
  • Difficult technique support
  • Project advisor support
  • Wiki support
  • Presentation coaching
  • Human Practices support
  • Thanks and acknowledgements for all other people involved in helping make a successful iGEM team