Re: Vitess follow up


Chris Aniszczyk
 

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.


- Take over funding (and ownership) of vitess.iovitess.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, what are your thoughts?



On Tue, 25 Apr 2017, 02:48 Sugu Sougoumarane, <sougou@...> wrote:
Hi Alexis,

Here are areas where we'd love to get help for Vitess:

- Help with marketing & PR. This is one area we're severely lacking.
- Advocacy through the ambassador program.
- Take over funding (and ownership) of vitess.io, vitess.slack.io, github repository, travis builds, and other CI & CD resources.
- Help with setting up governance.

I'm still working on the product comparison (distracted by the Percona conference). I'll try to get that done by next week.


On Wed, Apr 19, 2017 at 12:59 PM, Alexis Richardson <alexis@...> wrote:
Sugu

Thank-you.  Those are good reasons!  Are there specific places where
you'd like help winning or keeping more contributors?

Look forward to your view on systems & tradeoffs.  Can I humbly ask
that you include Cockroach, Rethink & Goshawk?  Maybe others.

a



On Wed, Apr 19, 2017 at 8:31 PM, Sugu Sougoumarane via cncf-toc
<cncf-toc@...> wrote:
> Hi Chris, Alexis,
>
> For the license, we already intend to change it to ALv2:
> https://github.com/youtube/vitess/issues/2694.
>
> For the comparison of various systems and trade-offs, we'll try to put
> something together in the next few days.
>
> As for why we're excited about wanting to join CNCF, I think this issue
> describes it well: https://github.com/youtube/vitess/issues/2670.
>
> PS: Thanks for the adopters suggestion on github. I'll work on that, and
> also see if we can feature them on vitess.io.
>
> On Wed, Apr 19, 2017 at 9:16 AM, Chris Aniszczyk via cncf-toc
> <cncf-toc@...> wrote:
>>
>> Also in terms of process, I believe Brian Grant on today's call has
>> expressed interest in sponsoring the project from the TOC. I'd suggest at a
>> following or next TOC meeting to decide whether the TOC desires to formally
>> invite the project.
>>
>> Another thing to bring up is that Vitess is currently under the BSD-3
>> license (https://github.com/youtube/vitess/blob/master/LICENSE), which isn't
>> a major issue, but we will have to decide what approach to take (move to
>> ALv2 or go for an exception) if they become a project.
>>
>> On Wed, Apr 19, 2017 at 11:02 AM, Alexis Richardson via cncf-toc
>> <cncf-toc@...> wrote:
>>>
>>> Sugu
>>>
>>> Thank you again for your pres today.
>>>
>>> What would *help Vitess the most* from a project advancement & end user
>>> POV?  How can CNCF help?
>>>
>>> a
>>>
>>>
>>>
>>> _______________________________________________
>>> cncf-toc mailing list
>>> cncf-toc@...
>>> https://lists.cncf.io/mailman/listinfo/cncf-toc
>>>
>>
>>
>>
>> --
>> Chris Aniszczyk (@cra) | +1-512-961-6719
>>
>> _______________________________________________
>> cncf-toc mailing list
>> cncf-toc@...
>> https://lists.cncf.io/mailman/listinfo/cncf-toc
>>
>
>
> _______________________________________________
> cncf-toc mailing list
> cncf-toc@...
> https://lists.cncf.io/mailman/listinfo/cncf-toc
>




--
Chris Aniszczyk (@cra) | +1-512-961-6719

Join cncf-toc@lists.cncf.io to automatically receive all group messages.