Re: Vitess follow up
toggle quoted messageShow quoted text
Once you're an official CNCF project, most of these benefits are included so it's not an issue :)
The next step would be to finalize the TOC sponsor (Brian), potentially sketch out a proposal (you can find examples one here: https://github.com/cncf/toc/tree/master/proposals) and on the next CNCF TOC call, have the TOC discuss whether to formally invite the project for a proposal per request of the TOC sponsor (Brian).
I'll respond to your specific points below:
- Help with marketing & PR. This is one area we're severely lacking.
We take care of this for projects and I think it's one of the most valuable things we provide for CNCF projects (also conference space etc). We list most of the benefits on this page: https://www.cncf.io/projects/
- Advocacy through the ambassador program.
Not a problem either: https://www.cncf.io/
- Take over funding (and ownership) of vitess.io, vitess.slack.io, github repository, travis builds, and other CI & CD resources.
In terms of financial and neutral ownership, not a problem either.
- Help with setting up governance.
This we can help with if projects request it. For example, we are currently working with the Prometheus team to finalize their governance and more than willing to help if projects request it.
On Tue, Apr 25, 2017 at 1:30 AM, Alexis Richardson <alexis@...> wrote:
That's a great list.
Chris Aniszczyk (@cra) | +1-512-961-6719