Training new Browser Staff

From Genecats
Revision as of 23:51, 12 January 2012 by Katrina (talk | contribs)
Jump to navigationJump to search

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

Logistics

  • get a computer
  • get a login
  • get a redmine account
  • email for UCSC and SOE
  • subscribe/add to mail lists (QA)
  • 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
  • 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

Browser

  • Open Helix tutorials
  • ASHG hands-on tutorial

Data

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