Training new Browser Staff

(see also: Getting Started for Browser QA Engineers and Getting Started for Browser Dev Engineers)

Logistics

• get a computer
• get a login
• get permission from Browser Project Manager to cluster-Admins to have your default group set to genecats, your secondary group set to protein
• get a redmine account http://redmine.soe.ucsc.edu (Register)
• email for UCSC and SOE
• subscribe/add to mail lists (and for QA, these additional mail lists)
• key card
• add your contact information to your .plan file
• copy .tcshrc and .bashrc from one of us (both are needed to run scripts)
• copy .hg.conf and .hg.conf.beta from someone, so you can run hgsql and scripts that use it.
• set up shell ssh authentication among dev, beta and your terminal
• check out a copy of the kent source tree daily script: File:DailyGITUpdate.txt and: Make_your_own_virtual_space
• take this [quiz] to get git commit access
• set up nightly cron to update kent source tree
• build your own sandbox
• get genomewiki access (Hiram/Vanessa)

Tools

• vi (vimtutorial) VI_quick_start -- or other editor
• mysql
• git -- see [Working_with_Git] and [Getting_Started_With_Git]

Browser

• Open Helix tutorials
• ASHG hands-on tutorial

Data

• Jorge's data flow PowerPoint presentation [Browsermap.pdf]

Training person-to-person (in rough chronological order)

1. machine layout
2. data flow
3. using git: day to day commands, and git reports/pair review process
4. make docs
5. pushQ
6. redmine
7. trackDb.ra and trackDb table
8. (for Q/A only) QAing a "normal" track (using the New_track_checklist)
   1. joinerCheck
9. static docs
10. makefiles
11. /usr/local/apache vs. the git tree
12. hgcentral