Training new Browser Staff

Some ideas about how to train new QA Engineers...

(see also: Getting Started)

Logistics

• get a computer
• get a login
• email for UCSC and SOE
• 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 ssh authentication among dev, beta and your linux box
• check out a copy of the kent source tree
• set up nightly cron to update kent source tree
• build your own sandbox

Tools

• vi (vimtutorial) -- or other editor
• mysql
• CVS (or git, if we git it) tutorial: http://www.soe.ucsc.edu/research/compbio/cvsdoc/cvs-tutorial/cvs_tutorial_toc.html

Browser

• Open Helix tutorials
• ASHG hands-on tutorial

Data

• Jorge's data flow PowerPoint presentation File:Browsermap.pdf

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

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