Warn against setting people up on zephyr.

[wiki.git] / join.mdwn

diff --git a/join.mdwn b/join.mdwn
index 09504476f2a36dc93d7f97faaeef872896a41f63..5180e16f70531316ea909bac696b98cc1d5e1efc 100644 (file)
--- a/join.mdwn
+++ b/join.mdwn
@@ -16,9 +16,9 @@ our weekly meetings regularly (they're Mondays at 7:30 PM), participate in SIPB
 hackathons, [cluedumps](http://cluedumps.mit.edu/), and [IAP classes](http://sipb.mit.edu/iap),
 and either create a new [[SIPB
 project|projects]] or help with some existing [[SIPB projects|projects]].  This process
-generally takes about a term of active participation.
+generally takes about a term of active participation.  Our [[calendar]] contains the full schedule of our events.
 
-To get involved in SIPB projects, you can hack on an existing
+To get involved in SIPB projects, you can contribute to an existing
 project—begin by talking to the people currently working on
 it—or start a new one.  The best way to start
 a SIPB project is to pick some computing-related problem that is
@@ -28,6 +28,8 @@ reporting on your progress to the SIPB.  The most successful SIPB
 projects have often been things that the people involved really wanted
 to do, and found resources or collaborators to do them through SIPB.
 
+You don't have to be a coding ace to become a SIPB member!  There are plenty of ways for nontechnical people to get involved: you can write documentation, help organize events, work on publicity or advocacy, or contribute design skills.  If you want to contribute to SIPB by coding but don't think you're a good enough programmer, there are many SIPB members willing to work with you to help you get better, and for many people working on a project and learning as you go along is a great way to build your programming skills.
+
 
 ## The office