Training new Browser Staff: Difference between revisions
From genomewiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
* copy .tcshrc or .bashrc from one of us | * copy .tcshrc or .bashrc from one of us | ||
* check out a copy of the kent source tree | * check out a copy of the kent source tree | ||
* set up nightly cron to update kent source tree | |||
* build your own sandbox | * build your own sandbox | ||
| Line 16: | Line 17: | ||
* vi (vimtutorial) -- or other editor | * vi (vimtutorial) -- or other editor | ||
* mysql | * mysql | ||
* CVS (or git, if we | * CVS (or git, if we git it) | ||
== Browser == | == Browser == | ||
| Line 28: | Line 29: | ||
# machine layout | # machine layout | ||
# data flow | # data flow | ||
# using cvs: day to day commands, and cvs reports/pair review process | |||
# trackDb.ra and trackDb table | # trackDb.ra and trackDb table | ||
# make docs | # make docs | ||
Revision as of 19:13, 12 February 2010
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
- copy .tcshrc or .bashrc from one of us
- 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)
Browser
- Open Helix tutorials
- ASHG hands on tutorial
Data
- Jorge's data flow PowerPoint presentation
Training person-to-person (in rough chronological order)
- machine layout
- data flow
- using cvs: day to day commands, and cvs reports/pair review process
- trackDb.ra and trackDb table
- make docs
- pushQ
- QAing a "normal" track (using the checklist, perhaps)
- joinerCheck
- static docs
- makefiles
- /usr/local/apache vs. the cvs tree
- hgcentral
