Training new Browser Staff
From Genecats
(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 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)
- machine layout
- data flow
- using git: day to day commands, and git reports/pair review process
- make docs
- pushQ
- redmine
- trackDb.ra and trackDb table
- (for Q/A only) QAing a "normal" track (using the New_track_checklist)
- joinerCheck
- static docs
- makefiles
- /usr/local/apache vs. the git tree
- hgcentral
