From: Edward Z. Yang Date: Sat, 1 Sep 2012 19:01:39 +0000 (-0400) Subject: (no commit message) X-Git-Url: https://sipb.mit.edu/gitweb.cgi/wiki.git/commitdiff_plain/8120de8201f10c8ac7f184a7a67a06f7624bd3cb?ds=sidebyside --- diff --git a/learn.mdwn b/learn.mdwn new file mode 100644 index 0000000..6d70058 --- /dev/null +++ b/learn.mdwn @@ -0,0 +1,44 @@ +How does one "get involved with a SIPB project"? I’ve had countless prospective SIPB members ask me this question, but I have never really had a good answer for them. It’s a complicated, ill-defined process that even recent new members have difficulty describing. Even worse, no two people ever have the same experience, and what worked for one person may not work for another. + +This essay is an attempt to describe this process. Not as a series of step-by-step instructions, because such a recipe doesn’t exist, but as a philosophy, an identification of a mindset that will get you asking the right questions, talking to the right people, and working on the right problems. We’ll take the huge task “Get involved with a SIPB project”, and continually divide it into smaller, more well-defined problems, until we are left with tasks that you can tackle head-on. + +Let’s get started. + +Level 0: Joining a project +-------------------------- + +Level 1: Getting in touch +------------------------- + +Level 1: Fixing bugs +-------------------- + +Level 1: Helping users +---------------------- + +Level 1: Writing new software +----------------------------- + +Level 1: System administration +------------------------------ + +Level 2: Identifying problems +----------------------------- + +Level 2: Understanding problems +------------------------------- + +Level 2: Getting code +--------------------- + +Level 2: Navigating code +------------------------ + +Level 2: Modifying code +----------------------- + +Level 2: Running code +--------------------- + +Level 2: Submitting code +------------------------