Difference between revisions of "Community"

Line 24: Line 24:
 
<div class="threeColumns">
 
<div class="threeColumns">
  
<h3>Communicate Directly with iGEM HQ</h3>
+
<h3>Communicate with iGEM HQ</h3>
 
<p>We love hearing from iGEM teams and instructors!
 
<p>We love hearing from iGEM teams and instructors!
  

Revision as of 15:30, 15 January 2016

This page is under active development and is in draft form. Nothing posted here is finalized.

Communication in iGEM

Communicate with iGEM HQ

We love hearing from iGEM teams and instructors!

Please email us at:

hq (at) igem (dot) org!

You can also email individual members of the iGEM Staff (email details can be found here).

You can also call us at:

+1-617-500-3106

Please note: Our normal business hours are Monday-Friday 9am-5pm EST.


Our Address:
One Kendall Square
Suite B6104
Cambridge, MA 02139
USA

Connect with the iGEM Community

One of the most common requests we receive from teams is the ability to easily contact other teams, which usually means people requesting email addresses. This is a challenging request for us since we respect the privacy of our registered iGEM account users and thus don't give our personal information, including email addresses.

We wanted to find another way to provide a means of easy communication between teams and the rest of the iGEM community since social media clearly wasn't enough.

We will have a new forum for iGEM 2016!

We hope this forum will allow teams to easily and openly communicate with one another and the rest of the iGEM community.

More information will be provided in the coming weeks!

iGEM Forum

Be Social

Connect with iGEM HQ, Staff, and Teams on Twitter! And remember to keep an eye on (and contribute to) #iGEM2016 to see the latest updates about iGEM!

You can also follow iGEM HQ on Facebook! We post all major announcements on both Twitter and Facebook, as well as on the 2016 Homepage.

Stay connected with us for the latest news about iGEM 2016!



Do you know of another social media App or website that iGEM should be using? Please let us know! @iGEM or by email hq AT igem DOT org