This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Category:Standards Governance Board Precepts"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
*'''Precept: Any artifact which must have its own ballot level must be balloted with the scope of content clearly designated.''' | *'''Precept: Any artifact which must have its own ballot level must be balloted with the scope of content clearly designated.''' | ||
| − | + | *'''Precept: In order to submit a ballot, the submitter must have a documented understanding of the roles and responsibilities of managing and reconciling a ballot. Effective date: TBD''' | |
| − | + | *'''Precept: Ballot management tooling must by default support best practices and rules''' | |
| − | + | *'''Precept: A ballot package must clearly identify the Individual Ballots within the package which will be progressed or not as a standard.''' | |
| − | + | *'''Precept: For each family, methodology determines what the quality critera are, and the management groups establish a plan to ensure the criteria are applied.''' | |
Revision as of 20:36, 5 June 2017
This page documents a Standards Governance Board Precepts
- Precept: Posting of Minutes As A Precondition of Balloting or Publishing Specifications
- WGs must post minutes documenting committee decisions to initiate standards development projects and decisions to ballot, reconcile and publish specifications.
- The SGB recommends to the TSC that the way the precept is measured is through recording the WG's decision in published minutes and the addition of a link pointing to published minutes in the PSS and the publication request. The NIB may use a check box to assert that the WG decision has been minuted and those minutes have or will be published.
- Precept: Separation of Concerns
- WGs should be organized where practical to separate the work items with respect to concerns.
- An artifact’s scope should be determined to support separation of concerns.
- Where separation of concerns have been implemented in a product family, an individual should not be a cochair of more than one of the appropriate governance, management, or methodology groups. Exceptions can be granted on a case-by-case basis by the TSC.
- Precept: Standards related GOM materials should be backed up by formal precepts.
- Given that there has been substantial work in the development of the materials in the GOM, we'll accept the GOM as the set of rules that we operate under; SGB will formally document the precepts to support those rules as the need arises.
- Precept: Any artifact which must have its own ballot level must be balloted with the scope of content clearly designated.
- Precept: In order to submit a ballot, the submitter must have a documented understanding of the roles and responsibilities of managing and reconciling a ballot. Effective date: TBD
- Precept: Ballot management tooling must by default support best practices and rules
- Precept: A ballot package must clearly identify the Individual Ballots within the package which will be progressed or not as a standard.
- Precept: For each family, methodology determines what the quality critera are, and the management groups establish a plan to ensure the criteria are applied.
This category currently contains no pages or media.
