cncf-toc@lists.cncf.io

Home Messages Hashtags Subgroups

Expanded

Topics Messages Polls

Export Group Data

Between

and

No CNCF Tech Writers Office Hours for December

Nate Waddington

#7747

Hello Everyone,

We usually host a CNCF Tech Writers Office Hours on the last Wednesday of every month. However, this month this lands between Christmas and New Year, so we’ll cancel this month’s Office Hours. Happy holidays everyone; see you next year!

Cheers,
Nate Waddington

--
Developer Advocate, CNCF
The Linux Foundation

nwaddington@...

Re: Notary V2 re-review / removal from the CNCF?

Davanum Srinivas

#7746

Justin,

Threads on email tend to rot out for this purpose. Could you please open an issue similar to [1]. Please add pointers to any previous public discussions (If i remember correctly, you had raised this before?)

Also, please remember that we may not see much traffic until folks come back in Jan.

thanks,

Dims

[1] https://github.com/cncf/toc/issues/900

Show quoted text

On Wed, Dec 14, 2022 at 1:05 PM Justin Cappos <justincappos@...> wrote:

As I understand it, the TOC is starting to review projects with a consideration to reassess their level in the CNCF or even to remove them altogether. I wanted to bring the Notary V2 project to the TOC's attention as a project that is misplaced and worthy of review.

First of all, the original Notary V1 project was added by the CNCF and was voted in both because it had a strong security foundation and a substantial user base.

Strangely, the Notary V2 project has none of the original Notary project members, none of the lines of code from Notary V1, and none of the security design. It is effectively a completely different project that has taken the same name in order to preserve the incubating status in the CNCF. Even worse, it is at incubation level and making use of CNCF resources / marketing / reputation, yet has had no security reviews, etc.

I would kindly suggest that the TOC consider either removing Notary V2 from the CNCF or asking it to reapply to the CNCF.

Notary V1 (the original) likely could also plausibly be archived or reviewed at some point, but this is of less urgency as it did actually receive due diligence at some point.

I know I raised the same concern back in July 2021, but after talking with others in the community I thought it was worth raising again. As transparency is an important part of open source foundations and projects, after raising this issue a week ago to the TOC privately, I am now making this request public.

Thanks,
Justin

Davanum Srinivas :: https://twitter.com/dims

Notary V2 re-review / removal from the CNCF?

Justin Cappos <justincappos@...>

#7745

As I understand it, the TOC is starting to review projects with a consideration to reassess their level in the CNCF or even to remove them altogether. I wanted to bring the Notary V2 project to the TOC's attention as a project that is misplaced and worthy of review.

First of all, the original Notary V1 project was added by the CNCF and was voted in both because it had a strong security foundation and a substantial user base.

Strangely, the Notary V2 project has none of the original Notary project members, none of the lines of code from Notary V1, and none of the security design. It is effectively a completely different project that has taken the same name in order to preserve the incubating status in the CNCF. Even worse, it is at incubation level and making use of CNCF resources / marketing / reputation, yet has had no security reviews, etc.

I would kindly suggest that the TOC consider either removing Notary V2 from the CNCF or asking it to reapply to the CNCF.

Notary V1 (the original) likely could also plausibly be archived or reviewed at some point, but this is of less urgency as it did actually receive due diligence at some point.

I know I raised the same concern back in July 2021, but after talking with others in the community I thought it was worth raising again. As transparency is an important part of open source foundations and projects, after raising this issue a week ago to the TOC privately, I am now making this request public.

Thanks,

Justin

Re: Sandbox Inclusion Results from December 13, 2022

Davanum Srinivas

#7744

Thanks Amye

Folks, if you have questions after watching the discussion in recording, please drop a note on email or slack (privately or publicly - https://github.com/cncf/toc#mailing-list)

-- Dims

Show quoted text

On Tue, Dec 13, 2022 at 12:59 PM Amye Scavarda Perrin <ascavarda@...> wrote:

The TOC met today to discuss the following sandbox proposals:
Passes with a majority vote of the TOC:
Merbridge
DevSpace
Capsule
zot
Paralus
Carina
ko

Passes with a majority vote of the TOC with conditions:
Open Policy Registry (OPCR) - service and product would need to be
renamed on acceptance
werf - several project forks need to realign with upstream
Kubescape - service and product would need to be renamed on acceptance

Projects not included
Goblet: Reapply with an more robust multivendor ecosystem
ViveNAS: Reapply with a larger community
Devbox: Unclear how this connects with the cloud native ecosystem,
reapply showing stronger connection
Kepler: reapply with more clarity about what is being contributed
Slime: reapply with project roadmap, match update cadence with
Kubernetes and consider a more robust multivendor ecosystem
Talos Linux - reapply with more technical details + clarification
around how this connects with the cloud native ecosystem

The recording is available here: https://youtu.be/558604kpBSE

--
Amye Scavarda Perrin | Director of Developer Programs, CNCF |
amye@...

Davanum Srinivas :: https://twitter.com/dims

Sandbox Inclusion Results from December 13, 2022

Amye Scavarda Perrin

#7743

The TOC met today to discuss the following sandbox proposals:
Passes with a majority vote of the TOC:
Merbridge
DevSpace
Capsule
zot
Paralus
Carina
ko

Passes with a majority vote of the TOC with conditions:
Open Policy Registry (OPCR) - service and product would need to be
renamed on acceptance
werf - several project forks need to realign with upstream
Kubescape - service and product would need to be renamed on acceptance

Projects not included
Goblet: Reapply with an more robust multivendor ecosystem
ViveNAS: Reapply with a larger community
Devbox: Unclear how this connects with the cloud native ecosystem,
reapply showing stronger connection
Kepler: reapply with more clarity about what is being contributed
Slime: reapply with project roadmap, match update cadence with
Kubernetes and consider a more robust multivendor ecosystem
Talos Linux - reapply with more technical details + clarification
around how this connects with the cloud native ecosystem


The recording is available here: https://youtu.be/558604kpBSE

-- 
Amye Scavarda Perrin | Director of Developer Programs, CNCF |
amye@...

🚨 Action Required | New addition to the landscape needs maintainer input!

Catherine Paganini

#7742

Dear Maintainers and Project Owners,

The Cloud Native Landscape will soon get a new section: The CNCF Project Summary Table. The goal of the summary table is to provide end users with more context, so they can better assess which projects to evaluate further. We would like to invite you to participate to ensure the table reflects your project in its best light!

As you'll see, some fields already have data in them. This is pulled directly from the CNCF's landscape.yml that powers the landscape, as well as your project's GitHub repositories. But because we want to provide end users with more information than the landscape provides, we need projects to submit a PR and fill in the gaps. For an example of how the populated table might look, view our PoC here.

What to do

Please update the fields listed here. Note that the tags are key and must be meaningful to help end users evaluate your project.

We plan to announce the Project Summary Table early next year and would like your project’s information up to date by December 31. Once the table is more or less complete, there will be a way to navigate from the landscape directly to this page.

How

Please follow these instructions. They provide the location of landscape.yml and guidance on updating it. You may use your current/traditional process for raising a PR against the CNCF landscape.yml or take advantage of a new web UI available for the landscape.

Why

Our ecosystem is growing, and the Landscape initiative is evolving to maximize your project's profile amongst end-users who are new to cloud native. To learn more about this project (e.g., the why, problem statement, and goals), please refer to this document.

If you have questions, reach out via Slack to Catherine Paganini, Simon Forster, or Richard Collins, and they can guide you through this process. The CNCF is here to help, so please use this team to ensure your project is promoted properly.

Thank you,

The CNCF Business Value Subcommittee Team

Catherine Paganini

Head of Marketing and Community

Buoyant, creators of Linkerd

Service Mesh Academy, monthly hands-on, engineer-focused training from the creators of the service mesh. Sign up today!

[RESULT] Argo approved for graduation

Amye Scavarda Perrin

#7741

Amye Scavarda Perrin | Director of Developer Programs, CNCF | amye@...

Re: [VOTE] Argo for graduation

Lyubomir Angelov

#7740

+1 NB

Lyubomir Angelov
SAP

Re: Agenda for 12/6

Richard Hartmann

#7739

That would be 0100 local for me this week; I need to skip, sorry.

On Mon, Dec 5, 2022 at 11:01 PM Amye Scavarda Perrin
<ascavarda@...> wrote:

Hi all,

We'll be meeting tomorrow at 8am Pacific with TAG updates.
Agenda: https://docs.google.com/document/d/1jpoKT12jf2jTf-2EJSAl4iTdA7Aoj_uiI19qIaECNFc/edit#
Presentation: https://docs.google.com/presentation/d/12VuinW4H7N7PjIMPAGY5Vh2h6-r15ew7ISamGcAxa24/edit?userstoinvite=m.koerbaecher@reply.de&actionButton=1#slide=id.g25ca91f87f_0_0

--
Amye Scavarda Perrin | Director of Developer Programs, CNCF | amye@...

Agenda for 12/6

Amye Scavarda Perrin

#7738

Hi all,

We'll be meeting tomorrow at 8am Pacific with TAG updates.

Agenda: https://docs.google.com/document/d/1jpoKT12jf2jTf-2EJSAl4iTdA7Aoj_uiI19qIaECNFc/edit#

Presentation: https://docs.google.com/presentation/d/12VuinW4H7N7PjIMPAGY5Vh2h6-r15ew7ISamGcAxa24/edit?userstoinvite=m.koerbaecher@...&actionButton=1#slide=id.g25ca91f87f_0_0

Amye Scavarda Perrin | Director of Developer Programs, CNCF | amye@...

Proposal: add governance review requirement to Graduating DD

Josh Berkus

#7737

TOC,

Proposal here: https://github.com/cncf/toc/issues/963

Can discuss at tommorrow's meeting.

-- 
-- Josh Berkus
   Kubernetes Community Architect
   OSPO, OCTO

Re: [VOTE] Argo for graduation

Daniel Deeney

#7736

+1 NB

Daniel Deeney | Co-Founder & CEO

m: 908.343.3622 | www.paladincloud.io

Show quoted text

On Thu, Dec 1, 2022 at 3:18 AM Hao Weng <wenghao@...> wrote:

+1 NB

On Thu, Dec 1, 2022 at 4:03 PM dimitar.kapashikov via lists.cncf.io <dimitar.kapashikov=sap.com@...> wrote:
+1 NB

Re: [VOTE] Argo for graduation

Philippe Robin

#7735

+1 NB

Show quoted text

From: cncf-toc@... <cncf-toc@...> On Behalf Of Amye Scavarda Perrin via lists.cncf.io
Sent: 23 November 2022 18:28
To: CNCF TOC <cncf-toc@...>
Subject: [cncf-toc] [VOTE] Argo for graduation

Argo has applied for graduation.
- PR: https://github.com/cncf/toc/pull/604
- DD: https://docs.google.com/document/d/1R4WjMG9s9JX8onZvOzEFSjBBFAInurN8tSiAFLqj-FE
Lei Zhang and Cathy Zhang are the TOC sponsors and have approved a call for a public vote. (https://lists.cncf.io/g/cncf-toc/message/7611)

Please vote (+1/0/-1) by replying to this thread.

Remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

Amye Scavarda Perrin | Director of Developer Programs, CNCF | amye@...

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

Re: [VOTE] Argo for graduation

Hao Weng

#7734

+1 NB

Show quoted text

On Thu, Dec 1, 2022 at 4:03 PM dimitar.kapashikov via lists.cncf.io <dimitar.kapashikov=sap.com@...> wrote:

+1 NB

Re: [VOTE] Argo for graduation

Herve LECLERC

#7733

+1 NB

Hervé Leclerc

CTO

Alter Way, a Smile group company

Mob : +33 6 83 97 95 98

1, rue royale, 227 bureaux de la colline

92210 St Cloud

herve.leclerc@... - www.alterway.fr

Re: [VOTE] Argo for graduation

dimitar.kapashikov@...

#7732

+1 NB

Re: [VOTE] Argo for graduation

Manish Kapur

#7731

+1 NB

Re: [VOTE] Argo for graduation

ApeCloud Marketing

#7730

+1 NB 🥳

From: "Amye Scavarda Perrin"<ascavarda@...>

Date: Thu, Nov 24, 2022, 02:28

Subject: [cncf-toc] [VOTE] Argo for graduation

To: "CNCF TOC"<cncf-toc@...>

Amye Scavarda Perrin | Director of Developer Programs, CNCF | amye@...

Re: [Proposed] NEW CNCF TAG Environmental Sustainability Tech Lead

Ricardo Rocha

#7729

+1 binding

Show quoted text

On Wed, Nov 30, 2022 at 11:40:17AM -0500, Matt Farina via lists.cncf.io wrote:
+1 binding

On Wed, Nov 16, 2022, at 3:12 PM, Marlow Weston wrote:
Hello TOC,

The TAG Environmental Sustainability co-chairs would like to propose Cara Delia as a TAG Technical lead.  She has been incredibly helpful with many items since before the formation of the TAG, and it would be a great benefit to have her.  For those unfamiliar with her, a brief bio is below.

Bio:  Cara is a Principal Community Architect for Financial Services and Sustainability at Red Hat.  Her role is to advocate open source principles and contribute to external open source communities. She speaks with customers, regulators and other vendors across the world regularly to better understand the challenges and opportunities that sustainability presents.
She has contributed to several open source foundations and communities but the two main ones are the Fintech Open Source Foundation (FINOS) and OS-Climate. In FINOS, She also contributes to the Open Source Readiness SIG, the Compliant Financial Infrastructure and also sit on the technical steering committee. She was a key contributor in bringing OS-Climate to the Linux Foundation as a project. In addition, 50% of her time was dedicated to the project to stand up the community with governance, policies, community calendar- including meeting cadences, agenda creation and other administrative aspects that support the community strategy for growing member engagement. Internally at Red Hat, Cara is a leader in the Climate Change Community of Practice specifically for the Open Source Sustainable Technology work stream.

The TAG chairs are available for any questions.

Many thanks,
--Marlow

signature.asc

[RESULT] Flux approved for graduation

Amye Scavarda Perrin

#7728

Amye Scavarda Perrin | Director of Developer Programs, CNCF | amye@...

261 - 280 of 7995

Home Hashtags Subgroups Terms