Point other OCI projects to this common org data

[vbatts]

• image-spec https://github.com/opencontainers/image-spec#weekly-call
• runtime-spec https://github.com/opencontainers/runtime-spec#meetings
• runc https://github.com/opencontainers/runc/#security
• runtime-tools https://github.com/opencontainers/runtime-tools
• image-tools https://github.com/opencontainers/image-tools
• go-digest https://github.com/opencontainers/go-digest#reporting-security-issues
• selinux https://github.com/opencontainers/selinux
• tob https://github.com/opencontainers/tob/blob/master/code-of-conduct.md
• project-template https://github.com/opencontainers/project-template

[vsoch]

I'll update the code of conduct links for the following (copied so I have write). I can't tell if the links to specific sections are relevant (for example, runtime-spec link to "Meetings" doesn't seem salient to data in org) so I'll assume we are talking about the code of conduct.

• image-spec https://github.com/opencontainers/image-spec#weekly-call
• runtime-spec https://github.com/opencontainers/runtime-spec#meetings
• distribution-spec updating link to code of conduct in org repository distribution-spec#57
• runc https://github.com/opencontainers/runc/#security
• runtime-tools https://github.com/opencontainers/runtime-tools
• image-tools https://github.com/opencontainers/image-tools
• go-digest https://github.com/opencontainers/go-digest#reporting-security-issues
• selinux https://github.com/opencontainers/selinux
• tob https://github.com/opencontainers/tob/blob/master/code-of-conduct.md
• project-template https://github.com/opencontainers/project-template

[vbatts]

On 26/02/19 10:27 -0800, Vanessasaurus wrote: I'll update the code of conduct links for the following (copied so I have write). I can't tell if the links to specific sections are relevant (for example, runtime-spec link to "Meetings" doesn't seem salient to data in org) so I'll assume we are talking about the code of conduct. * [x] image-spec https://github.com/opencontainers/image-spec#weekly-call * [x] runtime-spec https://github.com/opencontainers/runtime-spec#meetings * [x] opencontainers/distribution-spec#57 * [ ] runc https://github.com/opencontainers/runc/#security * [ ] runtime-tools https://github.com/opencontainers/runtime-tools * [ ] image-tools https://github.com/opencontainers/image-tools * [ ] go-digest https://github.com/opencontainers/go-digest#reporting-security-issues * [ ] selinux https://github.com/opencontainers/selinux * [ ] tob https://github.com/opencontainers/tob/blob/master/code-of-conduct.md * [ ] project-template https://github.com/opencontainers/project-template

Meetings is since all projects use the same URL and currently the same schedule. (and worse, some of the meeting times listed on the various projects aren't all consistent)

[vsoch]

Let me know if there are consistent chunks that I should write for specific sections (e.g., meetings). Since the repo here has security and code of conduct, I'll look across all the repos above for those things (and point to here)!

[vbatts]

Basically, when we first started, we only had a "specs" repo which became "runtime-spec". It was canonical for the org, and then copy-pasta happened. Part of this /org is to clean that up and unify it.

…

On Tue, Feb 26, 2019, 13:35 Vanessasaurus ***@***.***> wrote: Let me know if there are consistent chunks that I should write for specific sections (e.g., meetings). Since the repo here has security and code of conduct, I'll look across all the repos above for those things (and point to here)! — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEF6fNehMdhSnPSsLeLIicdQka5Ijcrks5vRX5kgaJpZM4a4An0> .

[vsoch]

Understood - in that case updating with links for all roads to point to Rome (org) should do the trick.

[vsoch]

@vbatts I don't have the full history / background to update the templates perfectly, but above I've gone through and created consistent links to shared security and code of conduct docs here! Note that both paths won't exist until the PR is merged.

[vbatts]

this is for the most part done.