Training new Browser Staff: Difference between revisions

From Genecats
Jump to navigationJump to search
(→‎Logistics: bolding .tcshrc line.)
Line 14: Line 14:
* key card
* key card
* add your contact information to your [[.plan]] file
* add your contact information to your [[.plan]] file
* copy .tcshrc and [[Sample .bashrc | .bashrc]] from one of us (both are needed to run scripts)
* copy '''.tcshrc''' and [[Sample .bashrc | .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.
* copy .hg.conf and .hg.conf.beta from someone, so you can run hgsql and scripts that use it.
* set up [[ssh_authentication_setup | shell ssh authentication]] among dev, beta and your terminal
* set up [[ssh_authentication_setup | shell ssh authentication]] among dev, beta and your terminal

Revision as of 19:26, 7 October 2015

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

Logistics

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