Re: [RESULT] Kubernetes Vote by TOC


Sarah Novotny <sarahnovotny@...>
 

Ok... that's a very different scope than asset transfer.  Most of those are simply adding additional admins or access and some (such as Google Groups) have distributed control in the community as opposed to any direct Google control.

Who is getting added for these? They all require individuals to be given access.

Twitter - @kubernetesio
YouTube - Kubernetes Channel
G+ - Kubernetes Page
Github Administration - github.com/kubernetes

I'll chase these as part of the Copyright and Work Product transfer.

Contributor List and copies of the CLAs 
Domains - kubernetes.io and k8s.io

These don't feel like asset transfers because they're equally or more community controlled

Google Groups -- numerous most have 1 community leader and 1 google employee as owners
Meetup Groups -- numerous and most are lead from the community.  



On Fri, Mar 18, 2016 at 12:02 PM, Alexis Richardson <alexis@...> wrote:
Correct

All social media.

Any WordPress accounts, blogs etc that are relevant 

Websites and domain administration rights

Admin for github groups 

Google Groups admin

Copyright and trademarks transfer 

List of contributors & database of CLAs if possible 

I'd think all of the above might be considered! 

Apologies for poor formatting.  Am using phone email.....





On Fri, 18 Mar 2016 18:56 Patrick Reilly, <patrick@...> wrote:
What about the social media handles, etc?

— Patrick

On Fri, Mar 18, 2016 at 11:54 AM, Sarah Novotny via cncf-toc
<cncf-toc@...> wrote:
> given the website is generated from the github.com/kubernetes organization,
> I think that the domains are the only outstanding thing to chase.  I'll find
> with whom they're registered and send a list.
>
>
>
> On Fri, Mar 18, 2016 at 11:31 AM, Alexis Richardson <alexis@...>
> wrote:
>>
>> How about websites, and related addresses?
>>
>>
>> On Fri, Mar 18, 2016 at 6:09 PM, Sarah Novotny <sarahnovotny@...>
>> wrote:
>>>
>>> The assets being transferred are the Kubernetes organization and all
>>> associated repositories "The Work" in the transfer agreement and the
>>> attached trademark registrations and applications.  Please let me know if
>>> you have any further questions.
>>>
>>> sarah
>>>
>>>
>>> On Tue, Mar 8, 2016 at 1:35 PM, Alexis Richardson via cncf-toc
>>> <cncf-toc@...> wrote:
>>>>
>>>> All,
>>>>
>>>> Here are the results from this week's vote re accepting Kubernetes
>>>> project proposal into the CNCF, towards supporting the statement below.  The
>>>> Kubernetes proposal is here:
>>>> https://docs.google.com/document/d/1AgoEf4Wdshcn2ttlGRVQLciLJe6liV_ZiGocRg9JxJE/edit#
>>>>
>>>> TOC votes:
>>>> +1 Ben Hindman
>>>> +1 Bryan Cantrill
>>>> +1 Camille Fournier
>>>> +1 Jonathan Boulle
>>>> +1 Kenneth Owens
>>>> +1 Alexis Richardson
>>>>
>>>> The motion to accept Kubernetes into CNCF was carried unanimously by the
>>>> binding votes of the TOC.  In addition several members of the CNCF community
>>>> emailed to support the motion.
>>>>
>>>> Thank-you,
>>>>
>>>> alexis
>>>>
>>>>
>>>>
>>>> **********
>>>>
>>>> Target: CNCF announcement on Thursday 10th March at Kubecon
>>>>
>>>> “On behalf of the CNCF TOC:
>>>>
>>>> We have accepted Kubernetes into the Cloud Native Computing Foundation.
>>>> While Kubernetes is the first project to be accepted, our intention is to
>>>> welcome many open source projects into the foundation. Our remit is broad
>>>> and we encourage applicants across the spectrum of cloud native, containers
>>>> and microservices technology.
>>>>
>>>> We now invite the Kubernetes community to work with the TOC to help
>>>> shepherd the project through a formal transition to the foundation.  All
>>>> CNCF projects will pass through the same process of Incubation(**).
>>>>
>>>> The first step is that Google transfer copyright and trademarks(*)
>>>> associated with Kubernetes to the Linux Foundation. When this is complete,
>>>> the TOC will work with the Kubernetes community to finalise the project
>>>> governance model.
>>>>
>>>> In summary: we are pleased to announce that Kubernetes is now an
>>>> Incubated Project(**) at the CNCF.”
>>>>
>>>> (*) Sarah Novotny will provide a complete list of assets.  Our
>>>> understanding is that a "yes" vote will lead to Google initiating the IP
>>>> transfers to LF for the CNCF.
>>>> (**) A full and formal definition of "Incubation” and “Incubated
>>>> Project” will be published by the CNCF TOC.
>>>>
>>>> **********
>>>>
>>>> _______________________________________________
>>>> 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
>

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