DM Technical Control Team

from: LSST Data Management

Table of Contents

  1. Membership
  2. Charter
  3. Initiating a Software Policy/Procedure/Design Change
  4. Meeting Schedule
  5. Proposals for Future Review
  6. Action Items
  7. Past Meetings
  8. Reviewed Proposals
  9. TCT Relevant Links

Membership

  • Robyn Allsman - Chair
  • Tim Axelrod
  • Roc Cutri / Lee Armus
  • Gregory Dubois-Felsmann
  • Robert Lupton
  • Ray Plante

Charter

The DM Technical Control Team (TCT), formerly known as the DM Configuration Control Board (CCB), weighs in on key topics for the development of LSST Data Management software, including major design issues, the tools to be used, and standards and policies.

The following mandate established the TCT:

  • The board is chaired by the DM System QA and Test Lead.
  • Members include DM System Scientist and Lead Institution Project Scientists.
  • The board determines when specification and deliverables are of sufficient maturity and quality to be baselined (placed under configuration controlled status) or released.
  • The board reviews and approves proposed changes to baselined items.
  • The board meets at least monthly and more often during periods prior to major reviews and data challenge integrations or when development requests approval to change baseline.

For further clarification, refer to pre- and post-baseline duties.

Initiating a Software Policy/Procedure/Design Change

Prepare a wiki document describing the proposed change. Invite on-line comments to be entered within the wiki document by inserting the [[[AddComment]]] macro.

Advertise your request for timely comments on the new proposal to the LSST-data mail group with a complete URL in the message. Also, update this TCT page by including the wiki pointer to your proposal under the section heading "Proposals for Future Review". Allow an adequate comment period (a week or so) prior to the TCT meeting at which you want the topic discussed.

Be prepared to discuss the pros and cons of your proposal at the next TCT telecon.

Meeting Schedule

  • Next meeting: Wednesday, 2 December 2009, 9 AM PST

Proposals for Future Review

  • [wiki:PointerToProposal], Author, Date
  • TBD: TCTPythonCodingStandardsChanges, Robyn Allsman
  • TBD: TCTPackageProposal - a reprise, Robert Lupton et al.
  • TBD: List of supported OS for hosting DM Software Stack, Ray Plante
  • TBD: Policy statement on acceptance criteria for 3rd Party software packages, Ray Plante
  • TBD: Policy statement on use of radians for internal quantities (when appropriate).
  • TBD: Initial Criteria To Consider when Contemplating Java-based Implementation, Ray Plante
  • Possibly coming soon: proposal for naming for factory functions
  • Possibly coming soon: proposal for having "scons install" automatically create a version number
  • Possibly coming soon: Policy Statement on Random Number Generation

Action Items

Past Meetings

2008 2009
15 January
4 February
27 March
2 April 1 April
7 May 6 May
4 June
25 June 8 July
4 August
3 September 18 September
1 October 7 October
5 November 4 November

Reviewed Proposals