Follow the specification update proposal process to propose updates to the specification
If you, as an individual non-Margo member, own the contribution, you MUST SIGN the Individual Contributor License Agreement (CLA) at the point of submitting a PR. This signed CLA will be required before your contribution can be merged into the project repository. As an individual contributor, you are acting on your own behalf and not on your employer.
Step 1: The Contributor selects either Category 1 or Category 2 based on the type of submission proposal.
Category 1 (Cat 1): Minor Bug Report Issue or pull request submission to suggest a simple editorial change
Category 2 (Cat 2): Specification Enhancement Request detailing a proposed function.
Cat 1 - Step 2: Submit PR
Cat 2 - Step 2: Submit Enhancement Request
ALL Non-member PR submissions must sign the Contributor License Agreement.
- Cat 1:
- PR approved by TWG members and merged into the appropriate release branch
- Cat 2:
- Enhancement requests accepted and added to the roadmap
- (Optional) Specification update proposal (SUP) document submitted and approved by the TWG technical leads
Decision gate 3 is a PR to merge the initial proposal into the /proposals folder. The focus is on making sure what the SUP owner plans to propose is clear and aligns with the roadmap. Technical details are not expected at this point.
Phase 3: Technical Design (P3)
Phase 3 is when SUP groups work on the technical design. The SUP owner may create a draft PR to merge the SUP into the /submitted folder to help get feedback from the community.
Phase 4 is a PR to merge the full proposal to the /submitted folder. During this phase, community members can post comments on the PR. Once comments have been addressed, the SUP will be voted on by the TWG Leads.
| Owner | Description | Stage | LINK |
|---|---|---|---|
| @arne-broering | Application package as OCI | P4 | Approved |
| @julienduquesnay-se | Device gateway | P3 | |
| @ajcraig | Standardizing REST API | P4 | Approved |
| @matlec | Desired state as Manifest API | P4 | Approved |