Skip to content

Governance Process

Tricia Farris edited this page Oct 24, 2019 · 1 revision

Submission Review Process

Stakeholders, Stakeholder groups, and the CEDS Team may work together or individually to create use cases for proposal. When a use case and code are submitted through GitHub Issues, the submitter will receive an email confirming receipt and next steps.

The CEDS Team will verify that the use case is complete and understood. Next, they will ensure that the proposed change conforms to CEDS conventions, assess the impact of the change, and review existing education standards for related elements and option sets. When the use case has been provisionally accepted, we invite the submitter to work with the CEDS team to review design options, code, data model, and any data definition changes/additions, and complete development of code changes as needed.

Next the use case and code are reviewed by the community. Use cases will be open for public review for a minimum of two weeks. The impacts of the proposed changes will be assessed and addressed through scheduled working sessions open to the community. Please note that lack of participation or response by the community is seen as consent and the change will be implemented.

If approved during these sessions by the community, the changes will be pre-released and available for immediate use and formally added into the model in the next version release.

Clone this wiki locally