reference my krbroot, with ATHENA_USER and screen support

[wiki.git] / join.mdwn

diff --git a/join.mdwn b/join.mdwn
index e52a7ac3ac95cfeb05fe970fe26a59e2b292570e..d13c1c8463c89c0996f6817d627dc9709b05db38 100644 (file)
--- a/join.mdwn
+++ b/join.mdwn
@@ -16,17 +16,17 @@ topics technical and otherwise.
 
 Prospective members are encouraged to **hang out around the SIPB office** during
 meetings (they're Mondays at 7:30PM) and at other times (check the door icon on
-[sipb.mit.edu](http://sipb.mit.edu/) to see if the office is open).
+[sipb.mit.edu](http://sipb.mit.edu/) to see if the office is open). (Coming to at least four meetings is required to be membered, though usually this happens before prospectives are otherwise ready to be membered.)
 
 You can also participate in SIPB activities like hackathons,
 [cluedumps](http://cluedumps.mit.edu/), and [IAP
-classes](http://sipb.mit.edu/iap). Our [[calendar]] contains the many of our
+classes](http://sipb.mit.edu/iap). Our [[calendar]] contains many of our
 events.
 
 ### "Furthering the Goals of SIPB"
 
-"Furthering the Goals of SIPB", or FTGOSing, usually means working on some SIPB
-[[projects]].
+"Furthering the Goals of SIPB", or FTGOSing, usually means **working on some SIPB
+[[projects]]**.
 
 Our technical [[projects]] can generally absorb arbitrary amounts of attention. If
 you are already familiar with the relevant skills, you may be able to find the
@@ -47,9 +47,9 @@ 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.
 
-#### One route
+### A possible route
 
-One possible way to get involved is:
+There are many possible ways to get involved in SIPB, but one route is:
 
 1. Take a look at the [[Projects]] page, and identify a project that looks
 interesting.
@@ -65,9 +65,11 @@ ticket is best to start with and how to implement it.
 5. Code your thing, and talk to somebody involved in the project to get it
 committed.
 
-You probably can't do all of that on your own. Feel free to talk to people
-around SIPB about each of those steps, and somebody will probably be happy to
-help you through them.
+If you follow something like this process and get some contributions into some
+SIPB project, you're probably doing fine at FTGOS. You probably can't do all of
+that on your own, though. That's fine, since you also need to get socially
+integrated. Feel free to talk to people around SIPB about each of those steps,
+and somebody will probably be happy to help you through them.
 
 ## The office
 
@@ -79,7 +81,7 @@ evening.  We strive to make it a fun and comfortable place to work on
 projects, homework, or anything else by providing an array of amenities:
 
 * Nice chairs, big monitors, many computers, table space for laptops
-* Music: ours (CDs or [LAMP](https://lamp.mit.edu/)) or yours (via a certain ["printer"](http://sipb.mit.edu/sipbmp3/))
+* Music: ours (CDs or [LAMP](https://lamp.mit.edu/)) or yours (via a certain ["printer"](http://sipb.mit.edu/doc/using-sipbmp3/))
 * Tons of equipment and supplies from video adapters to an oscilloscope to Band-Aids
 * A diverse technical library, including popular textbooks
 * Soda and snacks for late-night sessions, cheaper and closer than Verde's