-
Notifications
You must be signed in to change notification settings - Fork 541
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 associated projects #328
Update associated projects #328
Conversation
|
||
## Testing | ||
|
||
* [opencontainers/ocitools](https://github.com/opencontainers/ocitools) - A config generator and runtime testing framework. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not clear on intended scoping for this project, but there's an in-flight PR for bundle validation as well (opencontainers/runtime-tools#20) that hasn't been closed as “out of scope”. So probably list bundle testing as well, unless we want to file a follow-up PR adding it if/when the ocitools PR lands.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree, 'testing&tools' is a better description here.
I think @mrunalp agreed ocitools should cover three areas currently.(I cannot find the related conversation in issue/PR)
- generate
- bundle validate
- runtime validate
@liangchenye Yes, those are the initial tools and we could always add more tooling as the project evolves. |
@hqhq Can you update the PR? |
While we're touching these references, maybe drop in a reference to |
Where do we draw the line of what is added to this list? I don't see it as a scale-able thing to have in the repo. Are we just going to link to anything and everything? |
@crosbymichael Maybe we could just provide a pointer to opencontainer/ocitools (Since it will be supported and updated to keep up with the spec) and keep the rest in a wiki? |
Ya, it would probably be better to just have the official repositories here if anything at all. If you think about it, if we add just any repo what uses or consumes the spec it will be a never ending battle of one line prs to add some repo that we know nothing about. The title is "associated" projects implying that we are associated with these things when that is not the case. I wiki could scale better but I have not used github wikis so I don't know how well it works. |
On Wed, Mar 16, 2016 at 03:01:07PM -0700, Michael Crosby wrote:
I'm fine with an open door (punting on curation) until we have at |
Now we have ocitools in opencontainers, thanks @mrunalp . Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
b32bb1f
to
fd37635
Compare
Updated the description of ocitools. |
sadly, the CI failures are unrelated. I opened #350 to track that separately. |
LGTM |
1 similar comment
LGTM |
Update associated projects
Now we have ocitools in opencontainers, thanks @mrunalp .
Signed-off-by: Qiang Huang h.huangqiang@huawei.com