summaryrefslogtreecommitdiff
path: root/NewMembers.mdwn
authorAndrew Greenberg <andrew@psas.pdx.edu>2006-09-13 15:35:57 (GMT)
committer Andrew Greenberg <andrew@psas.pdx.edu>2006-09-13 15:35:57 (GMT)
commit859c0bc5a2e204decfab9e2bc4d38e4dae7c8174 (patch) (side-by-side diff)
tree67000396f4eb56eec6dd81551b6bf90a7e55142c /NewMembers.mdwn
parent986fc5cc34b11254082710fe7caa5179b94ed213 (diff)
downloadwiki-859c0bc5a2e204decfab9e2bc4d38e4dae7c8174.zip
wiki-859c0bc5a2e204decfab9e2bc4d38e4dae7c8174.tar.gz
NewMembers
Diffstat (limited to 'NewMembers.mdwn') (more/less context) (ignore whitespace changes)
-rw-r--r--NewMembers.mdwn8
1 files changed, 3 insertions, 5 deletions
diff --git a/NewMembers.mdwn b/NewMembers.mdwn
index 9122d26..3c64aff 100644
--- a/NewMembers.mdwn
+++ b/NewMembers.mdwn
@@ -10,7 +10,7 @@ For those who want to monitor our general progress and big events via email, ple
## <a name="I&#39;d like to monitor some aspect"></a><a name="I&#39;d like to monitor some aspect "></a> I'd like to monitor some aspect of PSAS (avionics, propulsion, software, etc)
-Our mailing lists are really meant for our active volunteers. If you're not going to be active, and you'd just like to monitor what we're doing, then we'd like to encouarge you to join `psas-announce` and read the various list archives, rather than join a specific team's mailing list. We try and keep the lists very focused and on topic, and a lot of non-active people on the lists has historically gotten in the way of that.
+Our mailing lists are really meant for our active volunteers. If you're not going to be active, and you'd just like to monitor what we're doing, then we'd like to encouarge you to join [psas-announce](http://lists.psas.pdx.edu/mailman/listinfo/psas-announce) and read the various list archives, rather than join a specific team's mailing list. We try and keep the lists very focused and on topic, and a lot of non-active people on the lists has historically gotten in the way of that.
That said, if you have a reason for monitoring the lists - such as you're working on a similar project or have something to contribute - then please feel free to [[join a team's list|MailingLists]]. You may be asked why you'd like to join; please don't feel offended, we honestly just want to know. Note that you'll automatically be added to `psas-all` when you register for a team list, so don't bother to join psas-general unless all you want is the all-group emails.
@@ -24,16 +24,14 @@ That said, if you have a reason for monitoring the lists - such as you're workin
## <a name="Further Adivce"></a> Further Adivce
-People often come to PSAS with no idea what they want to do, only knowing that they think the group is really cool. Here's my general advice for how to integrate yourself into the group:
+People often come to PSAS with no idea what they want to do, only knowing that they think the group is really cool. Here's Sarah's general advice for how to integrate yourself into the group:
1. When you come to meetings, ask lots of questions. Members are always willing to answer questions (multiple times if necessary). Don't be afraid to interrupt with a question! We're a loud group, so sometimes you may have to talk over us.
-2. Read the PSAS wiki. Try to get a general overview of the systems (avionics, communications, software, etc.). Once you've done that, focus on whatever interests you. If you get confused by something on the wiki, send email to the mailing list (either the general list or a specific team mailing list). We're not perfect, and often pages are outdated or incorrect. If you don't get a response, ask the question again at a meeting.
+2. Read the PSAS wiki. Try to get a general overview of the systems (avionics, communications, airframe, software, etc.). Once you've done that, focus on whatever interests you. If you get confused by something on the wiki, send email to the mailing list (either the general list or a specific team mailing list). We're not perfect, and often pages are outdated or incorrect. If you don't get a response, ask the question again at a meeting.
3. Ask if there's a good intro project. You may want to update documentation or clean up code to get yourself familiar with the project you really want to work on.
4. Go looking for a project. No one in the group is going to force you to work on something, and they'd rather you pick something you're passionate about and start on it.
PSAS is not for the shy, and no one is going to hold your hand because there's just too many people who come into the group, start a project, and then drift away and never finish it. It takes a while to really get comfortable with the group (and their odd sense of humor), but once you do, they're a great resource, and a really nice group of people.
-
-[[SarahBailey]]