distribution: Drop "Related GitHub Issues" section #39
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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]>
|
However these are handled, they need to be called out. This is fine in its current form. |
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. |
|
We'll leave it in, I'm fine leaving in more useful information. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.