Go through CII Best Practices Badging

[caniszczyk]

https://bestpractices.coreinfrastructure.org/

This is for @yurishkuro and a requirement of CNCF graduation (down the road). This isn't a super high priority.

[jpkrohling]

If this is something I could help, assign it to me.

[caniszczyk]

@jpkrohling go for it, I don't think @yurishkuro has started this work.

[codefromthecrypt]

@caniszczyk curious ... is there a label for a project that isn't yet CNCF graduated? or is that something undefined in CNCF. This is the first I've seen a mention of graduation related to CNCF

[yurishkuro]

@adriancole inception, incubating, graduated - https://www.cncf.io/projects/graduation-criteria/

[caniszczyk]

@adriancole the project maturity levels are here: https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc

You can see the status of each CNCF project here: https://github.com/cncf/toc#projects

No project has graduated yet, but we plan to go through a graduation process for some of our projects before the end of this year. As part of bootstrapping a foundation, it took awhile to come up with maturity levels / a process :)

[codefromthecrypt]

Thx all

…

On 21 Sep 2017 23:38, "Chris Aniszczyk" ***@***.***> wrote: @adriancole <https://github.com/adriancole> the project maturity levels are here: https://github.com/cncf/toc/blob/master/process/ graduation_criteria.adoc You can see the status of each CNCF project here: https://github.com/cncf/toc#projects No project has graduated yet, but we plan to go through a graduation process for some of our projects before the end of this year. As part of bootstrapping a foundation, it took awhile to come up with maturity levels / a process :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/uber/jaeger/issues/404#issuecomment-331195578>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAD612XL6mboSHiAinXqoMSzt4Zxofatks5skoLfgaJpZM4PbsPE> .

[jpkrohling]

Started https://bestpractices.coreinfrastructure.org/projects/1273

[objectiser]

@jpkrohling Is it supposed to be one badge per git repo, or one for the whole project? If whole project, then possibly the URL for versioned repo should point to the org instead of the jaeger repo? And the programming languages should also cover the clients and js for the UI.

[jpkrohling]

@caniszczyk can confirm, but I understand it is one for the whole project (nodejs can be seen as reference for this)

[caniszczyk]

generally you can use one badge for the whole project

…

On Fri, Sep 22, 2017 at 7:13 AM, Juraci Paixão Kröhling < ***@***.***> wrote: @caniszczyk <https://github.com/caniszczyk> can confirm, but I understand it is one for the whole project (nodejs can be seen as reference for this) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#404 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAD5IU-CeLm7yA1Y3btx5QHdP0Cl-XnHks5sk6RxgaJpZM4PbsPE> .

-- Cheers, Chris Aniszczyk http://aniszczyk.org +1 512 961 6719

[jpkrohling]

I just finished going over the items for this badge and I think we are in a good shape. The missing parts are mostly regarding security and I created issues on this repository to handle that.

[caniszczyk]

Thanks!

On Fri, Oct 6, 2017 at 6:17 AM Juraci Paixão Kröhling < ***@***.***> wrote: I just finished going over the items for this badge and I think we are in a good shape. The missing parts are mostly regarding security and I created issues on this repository to handle that. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#404 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAD5IchopSYEzPiQBWuWjE5mKlxp12mgks5spf5IgaJpZM4PbsPE> .

-- Cheers, Chris Aniszczyk http://aniszczyk.org +1 512 961 6719

[jpkrohling]

I'm closing this, as I believe this has been done already.