Real Name Policy for CNCF

[dims]

As far as i can tell our CNCF individual CLA allows distinguishing a “Full Name” from a “Public Name” ( see https://github.com/cncf/cla/blob/master/individual-cla.pdf ) Looks like this was adapted from the ASF’s ICLA ( https://www.apache.org/licenses/icla.pdf )

Also the DCO itself does not prohibit using a Pseudonym (reading https://developercertificate.org/)

So questions are as follows

• What is the policy? is it discussed anywhere?
• Is there a documented policy for CNCF? (or for LF?)
• Is there precedent where a project can override the policy?
• Do tools like EasyCLA inform/enforce the policy?

Thanks,
Dims

[dims]

cc @caniszczyk @mkdolan

[dims]

some prev discussion/links:

• https://wiki.hyperledger.org/display/TSC/DCO+and+Pseudonyms
• https://github.com/torvalds/linux/blob/master/Documentation/process/submitting-patches.rst#developers-certificate-of-origin-11

[mkdolan]

Hi @dims the policy is in the second link you provided.

"using your real name (sorry, no pseudonyms or anonymous contributions.)"

I know a few people have tried to bring this up in the past, but the DCO representation that the contribution is authorized is for a real person to make. The DCO was a "hack" to keep the legal overhead burden low and facilitate rapid development models. There are no system checks or audits, so it doesn't prevent someone from making a false representation, but that should be discouraged as a policy.

[dims]

@mkdolan thanks for the quick response. Should we codify this in https://github.com/cncf/foundation (or) in https://github.com/cncf/toc ?

[mkdolan]

If it's helpful for you all to have it restated somewhere in CNCF, that's fine with me. I don't know personally what location would make most sense...

[caniszczyk]

I'll add it to the FAQ and close this out https://github.com/cncf/toc/blob/main/FAQ.md

…

On Sat, Jul 2, 2022 at 12:20 PM Mike Dolan ***@***.***> wrote: If it's helpful for you all to have it restated somewhere in CNCF, that's fine with me. I don't know personally what location would make most sense... — Reply to this email directly, view it on GitHub <#379 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAPSIJ23P6KGHRQNWY6I5DVSCI7JANCNFSM52PAAI7A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Cheers, Chris Aniszczyk https://aniszczyk.org

[caniszczyk]

cncf/toc@4b5d504

[dims]

@caniszczyk we need to

• Drop "Public Name" from https://github.com/cncf/cla/blob/master/individual-cla.pdf
• Check if the EasyCLA process shows a "Public Name" and drop it if it does https://docs.linuxfoundation.org/lfx/easycla/v2-current/contributors/individual-contributor

[jberkus]

Er, this feels like a rather consequential decision to be making over a holiday weekend with no community input. Could we maybe not do that kind of thing in the future? It causes distrust.

[caniszczyk]

@jberkus no decision has been made outside of highlighting what was the policy already across LF projects

If folks want to propose changes they can do it through board members and their legal representatives

[dims]

@jberkus what @caniszczyk said! ended up documenting what was already being given as guidance to folks, but not written down.

[dims]

FWIW, the thread is still collecting feedback here:
https://lists.cncf.io/g/cncf-toc/topic/92137934#7204

We may end up reopening this issue or opening a fresh issue.