summaryrefslogtreecommitdiff
path: root/NewMembers.mdwn
authorSarah Bailey <saharabeara@gmail.com>2006-01-10 07:47:37 (GMT)
committer Sarah Bailey <saharabeara@gmail.com>2006-01-10 07:47:37 (GMT)
commit6504aeaafc445c2e748731884e8525f532104576 (patch) (side-by-side diff)
treecd5372ff2210f205e8cd35594f473c94760a3b82 /NewMembers.mdwn
parent94a7a65c6d30546be4fec9721c46e7c890de7e7b (diff)
downloadwiki-6504aeaafc445c2e748731884e8525f532104576.zip
wiki-6504aeaafc445c2e748731884e8525f532104576.tar.gz
NewMembers
Diffstat (limited to 'NewMembers.mdwn') (more/less context) (ignore whitespace changes)
-rw-r--r--NewMembers.mdwn18
1 files changed, 18 insertions, 0 deletions
diff --git a/NewMembers.mdwn b/NewMembers.mdwn
index 886fbe0..23f46fd 100644
--- a/NewMembers.mdwn
+++ b/NewMembers.mdwn
@@ -84,3 +84,21 @@ That said, if you have a reason for monitoring the lists - such as you're workin
</table>
2. Get yourself registered to use our wiki, a web-collaboration tool which lets us edit the PSAS site on the fly with nothing but a browser. Do this by coming to one of our meetings, and see our [[wiki editing help|MoinFormattingHelp]] to get started.
+
+----
+
+Advice from a not-so-new newbie:
+
+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:
+
+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.
+
+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