WHAT IS A PMC?

A project management committee (PMC) reports directly to the Board of Directors the i2b2 tranSMART Foundation.  It is responsible for one of the Platforms of the Foundation.  The PMC is responsible for top level project management and coordination as well as planning and managing the releases of its Foundation platform.  Most new capabilities or upgrades are contributed by organizations outside of the Foundation.

The PMC is made up of representatives of the key contributing groups and other stakeholders in the Platform.  Membership is generally open, but up to the discretion of each PMC and its chair.

The PMC also supports and manages the code governance set by the Executive management and Board of the Foundation.

i2b2 tranSMART Foundation PMC Mission Statement

To enable the effective sharing, integration, standardization, and analysis of heterogeneous data from collaborative translational research using and of the i2b2 tranSMART Foundation platforms.

What are the Roles of the PMC

The primary role is oversight of the software product or platform it is charged with responsibility for

• Meeting the feature and quality goals of each Platform Release
• Stay on budget (to the extent there that Foundation managed resources are being used)
• Maintain acceptable quality
• Comply with the coding standards and cod governance guidelines set forth by the Foundation
• Meets all legal, ethical, moral codes of the Foundation.

Secondly the role of the PMC is

• To further the long term development and health of the community as a whole
• To ensure that balanced and wide scale peer review and collaboration does happen

Responsibilities to the PMC and the Foundation

Foundation Responsibility

• All necessary technical support to allow contributors to successfully integrate their code into code repositories
• Integration of contributor-supplied tests into the proper stages of the development, continuous integration, and release processes
• Independent execution of functional tests, and certification of correct results, as part of the release process
• Testing against all supported database backends
• Integration of installation and upgrade procedures into supported installation and upgrade mechanisms

Contributors Responsibility

• Provide a complete description of the feature or enhancement
• Development code, merged in to the Community Branch for the intended release
• Carefully and completely detail the Database changes
• Perform an Impact analysis
• Execute and provide Unit and functional tests and test data
• Define Installation prerequisites and documentation
• Documentation
• Future requirements:
  • Ongoing defect review and repair (pre-release & post release)
  • Appropriate contribution of code to the Foundation (copyright; licensing; DCO)