Line 325: | Line 325: | ||
<th>Thursday <br> November 09</th> | <th>Thursday <br> November 09</th> | ||
<td></td> | <td></td> | ||
− | <td><label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="yes"> Yes</label><br /> | + | <td><label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="yes"> Yes</label><br /><br> |
<label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="no"> No</label> | <label><input type="radio" name="Availability Thu Oct 27, Evening" data-form-field="available_thu_eve" value="no"> No</label> | ||
</td> | </td> | ||
Line 333: | Line 333: | ||
<tr> | <tr> | ||
<th>Friday <br> November 10</th> | <th>Friday <br> November 10</th> | ||
− | <td><label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="yes"> Yes</label><br /> | + | <td><label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="yes"> Yes</label><br /><br> |
<label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="no"> No</label> | <label><input type="radio" name="Availability Fri Oct 28, Morning" data-form-field="available_fri_morn" value="no"> No</label> | ||
</td> | </td> | ||
− | <td><label><input type="radio" name="Availability Fri Oct 28, Evening" data-form-field="available_fri_eve" value="yes"> Yes</label><br /> | + | <td><label><input type="radio" name="Availability Fri Oct 28, Evening" data-form-field="available_fri_eve" value="yes"> Yes</label><br /><br> |
<label><input type="radio" name="Availability Fri Oct 28, Evening" data-form-field="available_fri_eve" value="no"> No</label> | <label><input type="radio" name="Availability Fri Oct 28, Evening" data-form-field="available_fri_eve" value="no"> No</label> | ||
</td> | </td> | ||
Line 348: | Line 348: | ||
<th>Saturday <br> November 11</th> | <th>Saturday <br> November 11</th> | ||
− | <td><label><input type="radio" name="Availability Sat Oct 29, Morning" data-form-field="available_sat_morn" value="yes"> Yes</label><br /> | + | <td><label><input type="radio" name="Availability Sat Oct 29, Morning" data-form-field="available_sat_morn" value="yes"> Yes</label><br /><br> |
<label><input type="radio" name="Availability Sat Oct 29, Morning" data-form-field="available_sat_morn" value="no"> No</label> | <label><input type="radio" name="Availability Sat Oct 29, Morning" data-form-field="available_sat_morn" value="no"> No</label> | ||
</td> | </td> | ||
Line 359: | Line 359: | ||
<tr> | <tr> | ||
<th>Sunday <br> November 12</th> | <th>Sunday <br> November 12</th> | ||
− | <td><label><input type="radio" name="Availability Sun Oct 30, Morning" data-form-field="available_sun_morn" value="yes"> Yes</label><br /> | + | <td><label><input type="radio" name="Availability Sun Oct 30, Morning" data-form-field="available_sun_morn" value="yes"> Yes</label><br /><br> |
<label><input type="radio" name="Availability Sun Oct 30, Morning" data-form-field="available_sun_morn" value="no"> No</label> | <label><input type="radio" name="Availability Sun Oct 30, Morning" data-form-field="available_sun_morn" value="no"> No</label> | ||
</td> | </td> | ||
Line 369: | Line 369: | ||
<tr> | <tr> | ||
<th>Monday <br> November 13</th> | <th>Monday <br> November 13</th> | ||
− | <td><label><input type="radio" name="Availability Mon Oct 31, Morning" data-form-field="available_mon_morn" value="yes"> Yes</label><br /> | + | <td><label><input type="radio" name="Availability Mon Oct 31, Morning" data-form-field="available_mon_morn" value="yes"> Yes</label><br /><br> |
<label><input type="radio" name="Availability Mon Oct 31, Morning" data-form-field="available_mon_morn" value="no"> No</label> | <label><input type="radio" name="Availability Mon Oct 31, Morning" data-form-field="available_mon_morn" value="no"> No</label> | ||
</td> | </td> |
Revision as of 18:24, 24 March 2017
NOTE: This page is under development
Apply to be a Judge
Judging in iGEM is a lot of fun, but it does require a strong commitment. iGEM teams work incredibly hard on their projects over the summer, so we need judges who are also committed to work hard to evaluate them. If you can spend time learning about the judging process during the summer, evaluating team wikis the week before the Jamboree, and attending the Jamboree in September, we would love to have you on board!
We need judges who understand iGEM, and judges who are willing to learn about iGEM. We will provide educational resources to help judges learn how to evaluate teams, and we will help you get up to speed if you are selected.
Lastly, I'm afraid that if you are a student on a 2017 iGEM team, you can't apply to be a judge this year. But you can apply when you graduate and become an iGEM alum!
Please email kim [AT] igem [DOT] org if you have questions!
We're looking for:
- iGEM instructors and advisors
- People who have judged iGEM in the past
- People in the synthetic biology industry
- Synthetic biology researchers who are new to iGEM
- iGEM alumni who want to stay involved
If you have colleagues who you think should apply, please feel free to direct them to this form.
NEW: Instructor judges will receive a 50% discount on their Jamboree attendance fee!
Judge Application Form
This form has been submitted.
You can unsubmit the form if you wish to make further edits.
-- Please choose a team
Admin view (orange) is only visible to super users. (Hide admin view)
Go to Admin Mode / Go to Team Example / Go to Username:
Thank you!
Thank you for filling out this form. We look forward to picking a strong judging team for 2017!
Finished?
Need to make changes?