Re: Real Name Policy for CNCF


Chris Aniszczyk
 

Hey folks, just to let you know, this is a policy that has been in place for awhile in multiple LF communities like the Linux Kernel, Hyperledger etc.

I'm not reverting the change as this is what the policy is and it makes that clear.

If you want to change this, I'd advise you open a new issue and talk to your developer reps who will have to bring it up to the GB.


On Wed, Jul 6, 2022 at 5:23 PM Aeva <aeva.online@...> wrote:
+1 to the concerns here, and +1 to having the appropriate folks discuss this issue, in ways that consider both the legal requirements regarding copyright assignment, and precedent in other organizations, and the societal implications.

Without commenting in any way on the merits of ChrisA's update, I would like to suggest reverting that FAQ change to give time for the conversation to happen and so that the guidance (and its ramifications) can be properly thought out.

Best,
--Aeva


On Wed, Jul 6, 2022 at 3:09 PM Davanum Srinivas <davanum@...> wrote:
Josh,

I would tell folks to NOT change anything that they are doing today. 

ChrisA jumped the gun and pushed the change directly to master. I was looking to have a conversation + debate.

I am waiting for some notes from the original person who asked the questions, so then we could figure out how to get it in front of the GB Legal Committee.

So tell them to hang tight and not change a thing. Let this be a FAQ for *new* project(s) for now.

-- Dims

On Wed, Jul 6, 2022 at 5:27 PM Josh Berkus <jberkus@...> wrote:
Dims,

Can you explain how we reconcile this with the CNCF code of conduct?

Asking because a simple reading of it would require "deadnaming" many of
our trans contributors.  How do we avoid that?


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



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



--
Chris Aniszczyk (@cra)

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