Skip to content

Conversation

@wking
Copy link
Contributor

@wking wking commented Jan 26, 2018

These were added based on @stevvooe's recommendation. But the new distribution-API maintainers can port those pull-requests over after the project is formed. Or the docker/distribution maintainers can land them before the new project is formed. Either way, there's no need to involve the TOB at this level of detail.

These were added based on Stephen's recommendation [1].  But the new
distribution-API maintainers can port those pull-requests over after
the project is formed.  Or the docker/distribution maintainers can
land them before the new project is formed.  Either way, there's no
need to involve the TOB at this level of detail.

[1]: opencontainers#35 (comment)

Signed-off-by: W. Trevor King <[email protected]>
@stevvooe
Copy link
Contributor

However these are handled, they need to be called out. This is fine in its current form.

@wking
Copy link
Contributor Author

wking commented Feb 1, 2018

However these are handled, they need to be called out.

I still don't see why the TOB needs to care about them. What changes if they aren't listed in the proposal? If nothing changes, why include them? I'd rather have the TOB focus on the things it controls, like project scoping, the initial maintainer set, and seed content.

@caniszczyk
Copy link
Contributor

We'll leave it in, I'm fine leaving in more useful information.

@caniszczyk caniszczyk closed this Feb 7, 2018
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.

3 participants