Training new Browser Staff: Difference between revisions

From genomewiki
Jump to navigationJump to search
No edit summary
(Replacing page with 'This page is no longer maintained.')
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
(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 Engineers])
This page is no longer maintained.
[[Category:Browser QA]]
 
== Logistics ==
* get a computer
* get a login
* 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
* 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) tutorial: http://www.soe.ucsc.edu/research/compbio/cvsdoc/cvs-tutorial/cvs_tutorial_toc.html
 
== Browser ==
* Open Helix tutorials
* ASHG hands-on tutorial
 
== Data ==
* Jorge's data flow PowerPoint presentation [[Image:Browsermap.pdf]]
 
== Training person-to-person (in rough chronological order) ==
# machine layout
# data flow
# using cvs: day to day commands, and cvs reports/pair review process
# trackDb.ra and trackDb table
# make docs
# pushQ
# (for Q/A only) QAing a "normal" track (using the [[New_track_checklist]] perhaps)
##joinerCheck
# static docs
# makefiles
# /usr/local/apache vs. the cvs tree
# hgcentral

Latest revision as of 19:25, 10 March 2011

This page is no longer maintained.