Training new Browser Staff: Difference between revisions

From Genecats
Jump to navigationJump to search
(New page: (see also: [http://genecats.cse.ucsc.edu/qa/newQaHire.html Getting Started for Browser QA Engineers] and [http://genecats.cse.ucsc.edu/eng/index.html Getting Started for Browser Dev Engin...)
 
(→‎Tools: hard linked to genome wiki)
Line 20: Line 20:
* vi (vimtutorial) -- or other editor
* vi (vimtutorial) -- or other editor
* mysql
* mysql
* git -- see [[Working_with_Git]] and [[Getting_Started_With_Git]]
* git -- see [[http://genomewiki.ucsc.edu/index.php/Working_with_Git Working_with_Git]] and [[http://genomewiki.ucsc.edu/index.php/Getting_Started_With_Git Getting_Started_With_Git]]


== Browser ==
== Browser ==

Revision as of 21:25, 9 March 2011

(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
  • 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 linux box
  • check out a copy of the kent source tree
  • get git commit access
  • set up nightly cron to update kent source tree
  • build your own sandbox

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
Retrieved from "https://genomewiki.ucsc.edu/genecats/index.php?title=Training_new_Browser_Staff&oldid=60"