Update associated projects

[hqhq]

Now we have ocitools in opencontainers, thanks @mrunalp .

Signed-off-by: Qiang Huang h.huangqiang@huawei.com

[wking]

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.

[hqhq]

I think the plan is we(huawei guys) will backport as many features as we can from oct to ocitools, then we can remove oct here and rewrite the scope of ocitools. Or maybe @mrunalp can give a better description of scope for ocitools now?

[liangchenye]

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)

1. generate
2. bundle validate
3. runtime validate

[mrunalp]

@liangchenye Yes, those are the initial tools and we could always add more tooling as the project evolves.

[mrunalp]

@hqhq Can you update the PR?

[wking]

While we're touching these references, maybe drop in a reference to
jfrazelle/riddler (mentioned on IRC on Monday 1).

[crosbymichael]

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?

[mrunalp]

@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?

[crosbymichael]

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.

[wking]

On Wed, Mar 16, 2016 at 03:01:07PM -0700, Michael Crosby wrote:

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.

I'm fine with an open door (punting on curation) until we have at
least twenty or so referenced projects here ;). Any consumer that a
spec maintainer links to on IRC sounds like fair game for curation
anyway.

[hqhq]

Updated the description of ocitools.

[vbatts]

sadly, the CI failures are unrelated. I opened #350 to track that separately.

[vbatts]

LGTM

[crosbymichael]

LGTM