Developer documentation

From WormBaseWiki
Jump to navigationJump to search

This page contains information pertinent to employees of WormBase.

Project Management

Web Site Documentation

Development Milestones

July 14 - July 30th

  • Coronate Czars
  • Coding standards and best practices for CSS, Javascript, API in place
  • Release new pages to production powered by the new architecture (classic view only)

July 30th - August 31st

  • http://wiki.wormbase.org/index.php/AceOjbect_Redesign_Page
  • Finish API development of critical classes
  • Finish migration of prominent CGI-based pages to new architecture and release into production (classic view only)
  • Solidify look-and-feel of new site: site map, browsing paths, design patterns, navigation

September 1st

  • Begin beta testing of new site to invited parties

October 1st - November 1st

  • Begin public beta testing of new site
  • Launch UI and general surveys.

November 1st - December 1st

  • Address survey issues
  • Test, test, test

December 1st

  • Go Live with new site

Division of Labor

Duties, current as of July 2010.

Configuration Czar

View and application configuration

  • Keep configuration files neat, orderly, and documented
  • Create new configuration for hard-coded variables and UI elements when needed.
  • Evangelize configuration standards and formatting to dev group

CSS Czar

Responsible for the maintenance of CSS files

  • Develop CSS best practices for the dev group
  • Keep CSS files tidy and organized function
  • Help enforce standard CSS markup in templates

Javascript Czar

Template Czar

Define and document shared elements, keep template directory organized, enforce standards


Major UI features

    • Searches Czar
    • External URLs

Controller

WormBase::API Czar

document shared API methods; enforce coding standards

Testing Czar

  • Develop and document test requirements for the dev group
  • Ensure adequate test coverage and performance
  • Develop global View and API tests


Profiling Czar

Coding standards and Best Practices

Software platform

Configuration

WormBase::API

View

  • Template Overview -- a quick tutorial on the templating system
  • Common template elements -- how to include common elements like references and species in a page
  • Things to document: evidence handling, linking entities, external URLs, searches

Model

Controller

Hardware platform

--

Administration

Routine Administration Tasks

Updates

Load balancing and Failover

Monitoring and Crises Management

Frozen Releases

Developer Tools


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. Probably not.

Frozen Releases as Virtual Machines