Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Define Spec API best practices #273

Closed
vishh opened this issue Dec 17, 2015 · 1 comment · Fixed by #287
Closed

Define Spec API best practices #273

vishh opened this issue Dec 17, 2015 · 1 comment · Fixed by #287

Comments

@vishh
Copy link
Contributor

vishh commented Dec 17, 2015

To make contributions easier, as we come up with best practices for the Spec, we should document them.
For example, we decide to use pointers for all fields that need to provide a "do not touch" option.
@wking
Copy link
Contributor

wking commented Dec 17, 2015

+1 from me 1 :).

 Subject: Recording style and policy in opencontainers/specs
 Date: Wed, 9 Sep 2015 11:09:29 -0700
 Message-ID: <[email protected]>

@wking wking mentioned this issue Dec 22, 2015
Closed
wking added a commit to wking/nmbug-oci that referenced this issue Dec 29, 2015
@wking
Recording style and policy in opencontainers/specs
61a0fb6 
Tag this thread for documenting existing decisions to avoid rehashing
settled issues in the absence of new arguments.  See also [1].

[1]: opencontainers/runtime-spec#273
@wking wking mentioned this issue Dec 30, 2015
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

style: Collect established conventions in a discoverable location wking/opencontainer-runtime-spec
2 participants
@wking @vishh