Excellent! This is a project that will help a lot of our use cases

Welcome!

Very promising project! Welcome to CNCF OPA community! P@

Excellent news! Welcome to CNCF SPIFFE community! P@

Awesome! Welcome SPIFFE community! - Lee

Spectacular! Much value to be found in OPA. - Lee

Hey everyone, we are happy to announce that OPA project has been accepted into CNCF as a SANDBOX level project (https://github.com/cncf/toc/blob/master/process/sandbox.md) sponsored by Brian Grant and

Hey everyone, we are happy to announce that SPIFFE project has been accepted into CNCF as a SANDBOX level project (https://github.com/cncf/toc/blob/master/process/sandbox.md) sponsored by Brian Grant,

The place we usually ask for help is in reviewing upcoming project proposals: https://github.com/cncf/toc/pulls A current place we could use help is in driving an update to the reference architecture

Yes. Great suggestion. With the current model we aimed for the simplest, most basic structure that still captured what we thought was important (some maintainers are experts in a subsystem; some

Hi TOC, I just signed up to be a TOC Contributor, and am trying to understand what sort of contributions would be the most valuable to the TOC. I'd like to understand what the TOC's biggest

I assume the maintainers govern all linkerd repositories, since other repositories do not contain MAINTAINERS.md

Whoops, thanks for pointing that out. I count 3 PRs out of the last 18 or so that violated the governance rules about requiring a super-maintainer review, all minor. We're still adjusting to some of

0 (non binding) The governance seems confused and I am not sure it technically meets the criteria of number of committers. The governance doc[1] states "All PRs must receive approval from at least one

Most that we're aware of run Linkerd per host. There are a couple companies that use it as a sidecar, and don't Linkerd's resource requirements heavyweight relative to the existing footprint of their

Yes. I can't speak for the other community folks, but Buoyant is planning its Q2 Linkerd roadmap right now. Dark traffic, rate limiting, backup requests, configurable communication policy in namerd,

+1 (non-binding)

At the moment, it looks like linkerd maybe still has more user mindshare, though envoy has more

Hi, William. Are there any specific large areas of upcoming development in linkerd, which would provide an opportunity for onboarding new contributors? Most post-1.3.0 (reasonably) looks like fixes

I am on vacation this week and will not be dailing in 😀