@jmfontaine thanks :)

Pre-submission checklist:

Please check each of these after submitting your pull request:

• [x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
• [x] Is your project closed source or, if it is open source, does your project have at least 250 GitHub stars?
• [x] Have you picked the single best (existing) category for your project?
• [x] Does it follow the other guidelines from the new entries section?
• [x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
• [x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
• [x] Does your project/product name match the text on the logo?
• [x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
• [ ] ~10 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Signed-off-by: Chris Aniszczyk [email protected]

Signed-off-by: Chris Aniszczyk [email protected]

Bumps lodash from 4.17.15 to 4.17.19. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lodash/lodash/releases">lodash's releases</a>.</em></p> <blockquote> <h2>4.17.16</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li><a href="https://github.com/lodash/lodash/commit/1144918f3578a84fcc4986da9b806e63a6175cbb"><code>1144918</code></a> Rebuild lodash and docs</li> <li><a href="https://github.com/lodash/lodash/commit/3a3b0fd339c2109563f7e8167dc95265ed82ef3e"><code>3a3b0fd</code></a> Bump to v4.17.16</li> <li><a href="https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12"><code>c84fe82</code></a> fix(zipObjectDeep): prototype pollution (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4759">#4759</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/e7b28ea6cb17b4ca021e7c9d66218c8c89782f32"><code>e7b28ea</code></a> Sanitize sourceURL so it cannot affect evaled code (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4518">#4518</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/0cec225778d4ac26c2bac95031ecc92a94f08bbb"><code>0cec225</code></a> Fix lodash.isEqual for circular references (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4320">#4320</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4515">#4515</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/94c3a8133cb4fcdb50db72b4fd14dd884b195cd5"><code>94c3a81</code></a> Document matches* shorthands for over* methods (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4510">#4510</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4514">#4514</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.19">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~mathias">mathias</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

Adding umoci blog post

@amye the build was broken + you didn't DCO sign off

I created a new PR and fixed it here: https://github.com/opencontainers/opencontainers.org/pull/61

Signed-off-by: Chris Aniszczyk [email protected]

Signed-off-by: Chris Aniszczyk [email protected]

@amye

1. failed DCO, please sign off the commit
2. build error

I'll see if I can fix this quickly

making this into a pull request so Chris can have final OK

The Orbit team is interested in learning more from the CNCF and Kubernetes community about how they deal with contributor ladders and metrics, and potentially mapping their model to the k8s contributor model: https://github.com/orbit-love/orbit-model/issues/29

We had some CNCF projects pilot their tool through their respective organizations and it's been found useful to provide insights on new potential contributors/maintainers. We also demo'd the tool recently at k8s contribx to get volunteers:

https://docs.google.com/document/d/1qf-02B7EOrItQgwXFxgqZ5qjW0mtfu5qkYIF1Hl4ZLI/edit

Interested people from Contribex: Matt Broberg Kaslin Fields Jonas Rosland Jenny Warnke Paris Pittman Bob Killen

Hi CNCF TOC,

My name is Shilla and I am a CNCF Ambassador. We are creating an open source project (not yet released) that we want to eventually sandbox under the CNCF umbrella. We would like to use the name "Prombox" as in Prometheus Sandbox for the project name. The application will create an environment for editing and testing Prometheus configuration on the fly. Wondering if it would be ok to use that name and what the steps would be if needed to get approvals. Thank you!

Shilla

@shillasaebi that isn't a question for the TOC, more for CNCF staff due to the legal implications here, I don't think this will be an issue though: https://www.linuxfoundation.org/trademark-usage/

There is a "memberdesk" that Comcast should have access to as part of the CNCF End User Program where you can ask questions like this or even a note to [email protected], especially if there are legal ramifications.

Includes a link to a csv file.

2020 results. Accept this PR when ready.

This PR should be accepted once the 2020 results are published.

email [email protected] and I'll get you sync'd up with LF IT :)

On Sun, Jul 26, 2020 at 8:42 PM Calvin Weng [email protected] wrote:

@amye https://github.com/amye Regarding website domain and GA transfer, who should we work with on the CNCF side?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cncf/toc/issues/493#issuecomment-664075854, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPSINMETRP3YAAVBEIYD3R5TLPHANCNFSM4OZVHD5A .

-- Cheers,

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

@jmfontaine it not works :) so please continue adding adopters

The simple answer is that it's a weak copy left license versus a permissive one, which we don't allow by default.

We could go for an exception if you and the Prometheus team wishes.

You're the only contributor so you can easily re-license the code to another license. For your troubles, happy to send you a bunch of Prometheus swag if that was your thing, but all up to you: https://store.cncf.io/collections/prometheus

just file an issue against devstats to track https://github.com/cncf/devstats/issues

On Thu, Jul 23, 2020 at 3:02 PM Amye Scavarda Perrin < [email protected]> wrote:

That would be a @lukaszgryglicki https://github.com/lukaszgryglicki question, @tsurdilo https://github.com/tsurdilo. He maintains DevStats.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cncf/toc/issues/494#issuecomment-663204723, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPSIOHUDIJTPACJMGAKQ3R5CJNFANCNFSM4OZVH7OA .

-- Cheers,

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

Amye, can you actually request design to do an updated logo, they need something better imho :)

On Thu, Jul 23, 2020 at 12:34 PM Amye Scavarda Perrin < [email protected]> wrote:

Yes please!

On Thu, Jul 23, 2020 at 10:33 AM Tihomir Surdilovic < [email protected]> wrote:

@amye https://github.com/amye @caniszczyk https://github.com/caniszczyk thanks for adding us to https://devstats.cncf.io/ !! Wanted to ask - should we provide the project logo SVG?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cncf/toc/issues/494#issuecomment-663136794, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AAA2FGOA3MH4TP5FQZUVXU3R5BX6XANCNFSM4OZVH7OA

.

-- Amye Scavarda Perrin | Program Manager | [email protected]

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cncf/toc/issues/494#issuecomment-663137182, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPSINATVWV7VWQMUYX3TLR5BYBTANCNFSM4OZVH7OA .

-- Cheers,

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

Bumps lodash from 4.17.15 to 4.17.19. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lodash/lodash/releases">lodash's releases</a>.</em></p> <blockquote> <h2>4.17.16</h2> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lodash/lodash/commit/d7fbc52ee0466a6d248f047b5d5c3e6d1e099056"><code>d7fbc52</code></a> Bump to v4.17.19</li> <li><a href="https://github.com/lodash/lodash/commit/2e1c0f22f425e9c013815b2cd7c2ebd51f49a8d6"><code>2e1c0f2</code></a> Add npm-package</li> <li><a href="https://github.com/lodash/lodash/commit/1b6c282299f4e0271f932b466c67f0f822aa308e"><code>1b6c282</code></a> Bump to v4.17.18</li> <li><a href="https://github.com/lodash/lodash/commit/a370ac81408de2da77a82b3c4b61a01a3b9c2fac"><code>a370ac8</code></a> Bump to v4.17.17</li> <li><a href="https://github.com/lodash/lodash/commit/1144918f3578a84fcc4986da9b806e63a6175cbb"><code>1144918</code></a> Rebuild lodash and docs</li> <li><a href="https://github.com/lodash/lodash/commit/3a3b0fd339c2109563f7e8167dc95265ed82ef3e"><code>3a3b0fd</code></a> Bump to v4.17.16</li> <li><a href="https://github.com/lodash/lodash/commit/c84fe82760fb2d3e03a63379b297a1cc1a2fce12"><code>c84fe82</code></a> fix(zipObjectDeep): prototype pollution (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4759">#4759</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/e7b28ea6cb17b4ca021e7c9d66218c8c89782f32"><code>e7b28ea</code></a> Sanitize sourceURL so it cannot affect evaled code (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4518">#4518</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/0cec225778d4ac26c2bac95031ecc92a94f08bbb"><code>0cec225</code></a> Fix lodash.isEqual for circular references (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4320">#4320</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4515">#4515</a>)</li> <li><a href="https://github.com/lodash/lodash/commit/94c3a8133cb4fcdb50db72b4fd14dd884b195cd5"><code>94c3a81</code></a> Document matches* shorthands for over* methods (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4510">#4510</a>) (<a href="https://github-redirect.dependabot.com/lodash/lodash/issues/4514">#4514</a>)</li> <li>Additional commits viewable in <a href="https://github.com/lodash/lodash/compare/4.17.15...4.17.19">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~mathias">mathias</a>, a new releaser for lodash since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

@tsurdilo the repo is xferred over and re-directs work fine, it's up to you how you want to split it apart if at all

yes I can do it later this afternoon

On Jul 14, 2020, at 2:53 PM, Tihomir Surdilovic [email protected] wrote:

@caniszczyk sure, is it possible to move everything over from https://github.com/cncf/wg-serverless-workflow without losing the commits ?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

@tsurdilo we will also move your repo over to https://github.com/serverlessworkflow if that works for you

Signed-off-by: Chris Aniszczyk [email protected]

approved in today's SC meeting on 7/14/2020, thanks all!

approved in today's SC meeting on 7/14/2020, thanks all!

feedback from SC:

• vm: need a concrete proposal on how this can work with limited participation; needs time to review, encourages to scope this more versus leaving it wide open
• kevin: only three people have volunteered so far, so limited participation
• kevin: intent was to ensure that TODO Group member is telling prospective members, have content that we share that's focused on participating in the group itself (vs the guides), some examples could be a one page or intro presentation; also working with the LF marketing + social media team to manage channels
• ashley: happy to help evolve this proposal

SC recommendation is to update the charter and scope, bring back for review after that

+1 from me

Signed-off-by: Chris Aniszczyk [email protected]

Signed-off-by: Chris Aniszczyk [email protected]

Signed-off-by: Calvin Weng [email protected]

In this proposal, we would like to propose Chaos Mesh as a CNCF sandbox project. Chaos Mesh is a Chaos Engineering platform that orchestrates chaos experiments on Kubernetes environments. See more in the proposal. Thanks.

This was accepted into the Sandbox from today's TOC meeting to go over the sandbox backlog.

Project onboarding will be here: #493

Signed-off-by: Tihomir Surdilovic [email protected]

This was accepted into the Sandbox from today's TOC meeting to go over the sandbox backlog.

Project onboarding will be here: https://github.com/cncf/toc/issues/494

Welcome to CNCF Project Onboarding!

Please ensure that you:

• [ ] Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/master/process/project_proposals.adoc#introduction
• [ ] Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/
• [ ] Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy
• [ ] Has your project adopted open governance already? see http://opengovernance.dev

Formal onboarding:

• [ ] Domain: transfer domain to CNCF/LF (ITx)
• [ ] Trademarks: transfer any trademark and logo mark assets over to the LF
• [ ] GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners
• [ ] Artwork: Ensure logos present on https://github.com/cncf/artwork
• [ ] Website: ensure LF footer is there and website guidelines followed, analytics transferred
• [ ] Create maintainer list + added to aggregated https://maintainers.cncf.io list - OWNERS file needed
• [ ] Devstats: add to devstats https://devstats.cncf.io/
• [ ] Marketing: update relevant intro + slide decks
• [ ] Trail Map: update CNCF trail map if relevant (incubating projects and above)
• [ ] Update https://landscape.cncf.io
• [ ] Events: update CFP + Registration + CFP Area forms
• [ ] ServiceDesk: confirm maintainers have read https://www.cncf.io/services-for-projects/
• [ ] CNCF Welcome Email Sent to confirm maintainer list access
• [ ] Schedule monthly project sync with CNCF staff

Welcome to CNCF Project Onboarding!

Please ensure that you:

• [ ] Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/master/process/project_proposals.adoc#introduction
• [ ] Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/
• [ ] Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy
• [ ] Has your project adopted open governance already? see http://opengovernance.dev

Formal onboarding:

• [ ] Domain: transfer domain to CNCF/LF (ITx)
• [ ] Trademarks: transfer any trademark and logo mark assets over to the LF
• [ ] GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners
• [ ] Artwork: Ensure logos present on https://github.com/cncf/artwork
• [ ] Website: ensure LF footer is there and website guidelines followed, analytics transferred
• [ ] Create maintainer list + added to aggregated https://maintainers.cncf.io list - OWNERS file needed
• [ ] Devstats: add to devstats https://devstats.cncf.io/
• [ ] Marketing: update relevant intro + slide decks
• [ ] Trail Map: update CNCF trail map if relevant (incubating projects and above)
• [ ] Update https://landscape.cncf.io
• [ ] Events: update CFP + Registration + CFP Area forms
• [ ] ServiceDesk: confirm maintainers have read https://www.cncf.io/services-for-projects/
• [ ] CNCF Welcome Email Sent to confirm maintainer list access
• [ ] Schedule monthly project sync with CNCF staff

Added the RO Language code of conduct

Hi, This is CNCF code of conduct in Persian for your consideration.

you can always reach out via the https://github.com/cncf/servicedesk in CNCF or ping Ihor on the CNCF Slack

On Sat, Jul 11, 2020 at 1:38 AM Anuraag Agrawal [email protected] wrote:

Heard from @alolita https://github.com/alolita that she is following up on this, tracking down the stakeholders on the Linux Foundation side. Hope to hear more soon, sorry it's taking so long.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/open-telemetry/community/issues/392#issuecomment-657002058, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPSINNYAZ6NE6JBZWUEB3R3ACH3ANCNFSM4OB7CUHA .

-- Cheers,

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

Thank you @zacharysarah

cc @caniszczyk @idvoretskyi

@amye is Dex almost set?

Following @gerred's step-down notice for SIG Contributor Strategy, this PR reflects Gerred's recommendation and proposes me as a SIG Contributor Strategy Chair.

Signed-off-by: Stephen Augustus [email protected]

cc(SIG Contributor Strategy Chairs): @parispittman @jberkus

Please let us know if there is a preferred SIG to present to first. Thanks in advance!

Operator Framework SDK and OLM sub-projects have applied to join as incubating projects

+1 Binding: note: Quorum is 10 as Jeff Brewer has been away Katie Gamanji: https://lists.cncf.io/g/cncf-toc/message/4799 Liz Rice: https://lists.cncf.io/g/cncf-toc/message/4833 Justin Cormack: https://lists.cncf.io/g/cncf-toc/message/4834 Xiang Li: https://lists.cncf.io/g/cncf-toc/message/4835 Alena Prokharchyk: https://lists.cncf.io/g/cncf-toc/message/4849 Brendan Burns: https://lists.cncf.io/g/cncf-toc/message/4839 Michelle Noorali: https://lists.cncf.io/g/cncf-toc/message/4939