Difference between revisions of "Developer documentation"

From WormBaseWiki
Jump to navigationJump to search
Line 5: Line 5:
 
*[[Conference call agendas and minutes]]
 
*[[Conference call agendas and minutes]]
 
*[[Project meeting agendas and minutes]]
 
*[[Project meeting agendas and minutes]]
 +
*[[Doodle Polls for conference call scheduling]]
 
*[[Linking To WormBase|Linking To WormBase]]  
 
*[[Linking To WormBase|Linking To WormBase]]  
 
*[[Suggested pre-release data checks|Suggested pre-release data checks]]  
 
*[[Suggested pre-release data checks|Suggested pre-release data checks]]  

Revision as of 10:26, 16 June 2010

This page contains information pertinent to employees of WormBase.

Project Management

Web Site Documentation

Rearchitecture Design Stages

  1. Requirements analysis / Design Specifications
  2. Architecture Outline
  3. Prototyping
  4. Formal Development via established conventions
    1. Formal development strategy - An overview of the development process at WormBase
    2. Developer notes - Best practices, conventions, etc
    3. Coding standards
  5. Testing
  6. Deployment

Coding standards

Software platform

Hardware platform

--

Administration

Routine Administration Tasks

Load balancing and Failover

Monitoring and Crises Management

Frozen Releases

Frozen Releases as Virtual Machines

Updates

Developer Tools

All Hands Meeting Agendas and Notes

Source Code Repositories

We use the distributed source code management system Mercurial. Projects are hosted on BitBucket.

How-To create, check out, and manage our repositories

Deprecated Documentation

The good word gone bad. Cruft. Lint. Maybe useful but probably not.