Training new Browser Staff

From genomewiki
Revision as of 19:13, 12 February 2010 by Pauline (talk | contribs)
Jump to navigationJump to search

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)

  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)
  • joinerCheck
  1. static docs
  2. makefiles
  3. /usr/local/apache vs. the cvs tree
  4. hgcentral