Version 4 (modified by robyn, 10 years ago) (diff)


DM Technical Control Team

from: LSST Data Management


  • Robyn Allsman - Chair
  • Tim Axelrod
  • Roc Cutri / Schuyler Van Dyk
  • Gregory Dubois-Felsmann
  • Robert Lupton
  • Ray Plante


The DM Technical Control Team (TCT), formerly known as the DM Configuration Control Board (CCB), reviews and approves changes to all baselines in the LSST Data Management System, including proposed changes to the DM functional requirements' (FRS), reference design, or Data Challenge design baselines, 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.

The Technical Control Team and the System Architecture Team work in synchrony. The SAT (and the various DM team members as delegated) is responsible for creating, establishing, updating, analyzing, proposing the reference and DC designs and changes to them, whether they might affect the FRS, the reference design, or the DC design. The TCT makes sure these changes don't get into the baseline without proper change control. The TCT must involve PM before approving an FRS change, as this might affect the project schedule or cost envelope. Restated more simply, the FRS is baselined, and the Reference Design are baselined, and so should each DC design be baselined. The SAT defines them, the TCT controls baselining and acceptance of changes to the baseline for all 3.

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, ??14 April 2010, 9 AM PST ??

Proposals for Future Review

  • [wiki:DM/Policy/PointerToProposal], Author, Date <- Note 'DM/Policy' prefix in name.
  • TBD: Use of 'mercurial' as an SVN Repository Clone for non-LSST Developers
  • TBD: Moving to later GCC release (4.4+) (for performance in diffim & others), Robert Lupton
  • 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: Initial Criteria To Consider when Contemplating Java-based Implementation, Ray Plante

Action Items

Past Meetings

Notes from past meetings are available at DM/TCT/meetings.

Reviewed Proposals