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

Update contributing guidelines and add maintainer guidelines #56

Merged
merged 1 commit into from
May 4, 2016

Conversation

caniszczyk
Copy link
Contributor

Each project in the OCI should have similar contributing guidelines
and maintainer guidelines.

Signed-off-by: Chris Aniszczyk caniszczyk@gmail.com

Each project in the OCI should have similar contributing guidelines
and maintainer guidelines.

Signed-off-by: Chris Aniszczyk <caniszczyk@gmail.com>

We are always thrilled to receive pull requests, and do our best to
process them as fast as possible. Not sure if that typo is worth a pull
request? Do it! We will appreciate it.
Copy link
Contributor

Choose a reason for hiding this comment

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

My initial CONTRIBUTING.md submission in #43 assumed this project was following the runtime-spec's [“one sentence per line”][1] convention. Is this new content copy/pasted from somewhere else? Should it be updated here (or upstream?) to match that convention?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The goal is for all OCI projects to share the same files, we have created a repo here:
https://github.com/opencontainers/project-template

Copy link
Contributor

Choose a reason for hiding this comment

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

On Tue, May 03, 2016 at 11:59:17AM -0700, Chris Aniszczyk wrote:

The goal is for all OCI projects to share the same files, we have created a repo here:
https://github.com/opencontainers/project-template

Sounds like a reasonable starting point, but this CONTRIBUTING.md is
currently too specific to apply to this repo (e.g. references to a
test suite we don't have). Are downstream modifications like removing
test references or the leader-issue requirement allowed? Does the
upstream project-template follow runtime-spec's “one sentence per
line”? Should I be discussing this in
opencontainers/project-template#1?

@crosbymichael
Copy link
Member

@mrunalp can you restart the build? we got a weird error

a pull request removing them.



Copy link
Contributor

Choose a reason for hiding this comment

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

One trailing newline is probably enough ;).

@mrunalp
Copy link
Contributor

mrunalp commented May 3, 2016

I have hit restart.

@crosbymichael
Copy link
Member

@wking there files should be general in scope so that all OCI projects can share the same structure and files for how the projects are run. Alot of your comments are on specific points regarding how they related to this project but should be general applicable for everything.

@wking
Copy link
Contributor

wking commented May 3, 2016

On Tue, May 03, 2016 at 01:44:10PM -0700, Michael Crosby wrote:

there files should be general in scope…

I agree that it's nice to share generic docs. But I don't think it
makes sense to share overly-specific docs. That means doing one or both of:

  • Genericize the template so it does apply to all OCI projects,
  • Allow downstream edits to customize the generic template to match
    the local project.

Both of those changes sound useful to me, but I'm not sure what sounds
best to the project-template maintainers.

@crosbymichael
Copy link
Member

I think it would be better to just move this conversation to the repo from my comment here:

opencontainers/runtime-spec#420 (comment)

We can work out the kinks and get this in shape so that it can apply to all of OCI's repos.

@mrunalp
Copy link
Contributor

mrunalp commented May 4, 2016

@crosbymichael Sounds good. The build failure seems related to travis not populating the commit range so we can merge this now.

@mrunalp
Copy link
Contributor

mrunalp commented May 4, 2016

LGTM

@mrunalp mrunalp merged commit 30dfd9a into master May 4, 2016
@crosbymichael
Copy link
Member

@mrunalp i was more meaning that we can close this for now but we can made the changes and have another pr to update this. both work fine

@mrunalp
Copy link
Contributor

mrunalp commented May 4, 2016

@crosbymichael I misread your comment and have merged this but we can fix this depending on what we decide. Leaving it in for now.

@crosbymichael
Copy link
Member

works for me, thanks ;)

@mrunalp
Copy link
Contributor

mrunalp commented May 4, 2016

Cool :)

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.

4 participants