Difference between revisions of "New Member Orientation"
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
* Noyes basement | * Noyes basement | ||
* Green Zone | * Green Zone | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Keys === | === Keys === | ||
| Line 33: | Line 27: | ||
* CS/physics lounge - CAA6 | * CS/physics lounge - CAA6 | ||
* Dennis back entrance - CAX | * Dennis back entrance - CAX | ||
| + | |||
| + | == Computers == | ||
| + | get someone to make username, passwd | ||
| + | * ACL's | ||
| + | * proto (going away) | ||
| + | * new-proto (will eventually become proto) | ||
== Projects== | == Projects== | ||
Revision as of 11:25, 15 May 2015
Read what you need or want; you can always come back.
Contents
Overview
- read the About Us page
- there's generally a pool of projects available
- you can pick what project you work on
- we perform maintenance as well as implement new projects
Workspaces
- Dennis roof
- Noyes basement
- Green Zone
Keys
- go [here]
- fill it out and include applicable locations
- Dennis back entrance, CAX
- Dennis roof, CAB 6
- 2nd floor lab, CAA3
- Noyse basement, CAB 13
- public Safety should email you when your keys are ready
Key Codes
- Dennis Roof - CAB6
- Noyse Lab - CAB13
- ENI lab - CAA3
- CS/physics lounge - CAA6
- Dennis back entrance - CAX
Computers
get someone to make username, passwd
- ACL's
- proto (going away)
- new-proto (will eventually become proto)
Projects
Check HIP for up-to-date project listings.
Communication
Group
- we use a listserv, hip@cs.earlham.edu
- notify the group about significant progress via listserv or in meetings
- questions can be asked via listserv
- google drive is used frequently
Meetings
- Friday in the Green Zone for lunch (12-1pm)
- general discussion about current and future projects
- bring-your-own-lunch style
- Sunday on the roof (1-3pm)
- working together in the same space
Documentation
Documentation is an important part of HIP because different people from different semesters will need to know about the work you did. It's also more efficient to point the curious here rather than to explain something multiple times.
- document projects
- inline code documentation helps readability
- wiki articles are fast and helpful
- document changes to keep information relatively accurate
- document your work, process, or experience
- your experience is invaluable to someone who is in a similar situation
Wiki Basics
- how to use
- you need an account to be created by an admin; ask Charlie or Ivan
- if a page doesn't exist, search for it and the wiki will let you create that page
- make sure to click "Save Page" after you're finished editing
- how to learn
- edit pages to look at their syntax
- use Wiki Syntax
- how to style
- having too many headers can be overkill
- lists are the simplest way to organize content
- trim things down
