Training new Browser Staff: Difference between revisions

From Genecats
Jump to navigationJump to search
(→‎Logistics: adding links to other wiki pages.)
(adding mailing list section)
Line 17: Line 17:
* set up nightly cron to update kent source tree
* set up nightly cron to update kent source tree
* [[Make_your_own_virtual_space | build your own sandbox]]
* [[Make_your_own_virtual_space | build your own sandbox]]
==Mailing Lists that QA'ers should be on==
* Sign yourself up for the genecats mailing list: https://lists.soe.ucsc.edu/mailman/listinfo/genecats
* Sign yourself up for the genome mailing (USCS genome browser discussion) list: https://lists.soe.ucsc.edu/mailman/listinfo/genome
* Sign yourself up for the genome mailing (USCS genome browser mirror discussion) https://lists.soe.ucsc.edu/mailman/listinfo/genome-mirror
* Sign yourself up for the genome mailing (USCS genome browser announcments) https://lists.soe.ucsc.edu/mailman/listinfo/genome-announce
* Sign yourself up for the School of Engineering (SoE) Staff mailing list: https://lists.soe.ucsc.edu/mailman/listinfo/staff
* Ask Donna and Bob to add your email address to the following alias lists:
**browser-qa
**browser-staff
**push-request
**genome-www?


== Tools ==
== Tools ==

Revision as of 17:34, 28 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

Mailing Lists that QA'ers should be on

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