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.

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

ReadMe: Link to shared Code of Conduct in TOB repo #375

Merged
merged 1 commit into from
Apr 20, 2016
Merged

ReadMe: Link to shared Code of Conduct in TOB repo #375

merged 1 commit into from
Apr 20, 2016

Conversation

RobDolinMS
Copy link
Collaborator

Signed-off-by: Rob Dolin RobDolin@microsoft.com

Signed-off-by: Rob Dolin <RobDolin@microsoft.com>
@@ -57,7 +57,7 @@ The specification and code is licensed under the Apache 2.0 license found in the

## Code of Conduct

Participation in the OpenContainers community is governed by [OpenContainer's Code of Conduct](code-of-conduct.md).
Participation in the OpenContainers community is governed by [OpenContainer's Code of Conduct](https://github.com/opencontainers/tob/blob/master/code-of-conduct.md).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then shall we still keep the code-of-conduct.md in rutime-spec and keep it syncing with the tob one?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same question I was going to ask on the image-spec PR

On Thu, Apr 7, 2016, 21:39 Qiang Huang notifications@github.com wrote:

In README.md
#375 (comment)
:

@@ -57,7 +57,7 @@ The specification and code is licensed under the Apache 2.0 license found in the

Code of Conduct

-Participation in the OpenContainers community is governed by OpenContainer's Code of Conduct.
+Participation in the OpenContainers community is governed by OpenContainer's Code of Conduct.

Then shall we still keep the code-of-conduct.md in rutime-spec and keep
it syncing with the tob one?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/opencontainers/runtime-spec/pull/375/files/b05cbff7a7a57147a626ab2665a42f35c0e6ee09#r58970830

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vbatts Did you discuss this in 2016-04-20 call?
I guess we should keep it since we need it in PDF?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hqhq yes, sorry. The file does not strictly need to be in the repo. Though any changes to the document in the tob repo, ought to be mirrored to the file in this repo.
While I like the idea of not needing to duplicate the work across repos, during the call I decided to leave this file in the repo for ease and simplicity of making the PDF/HTML docs

@philips
Copy link
Contributor

philips commented Apr 20, 2016

LGTM

1 similar comment
@vbatts
Copy link
Member

vbatts commented Apr 20, 2016

LGTM

@vbatts
Copy link
Member

vbatts commented Apr 20, 2016

(discussed on the 2016-04-20 call)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants