Skip to content

docs: Update DCO real name requirement to reflect official CNCF guidance#7286

Open
robertsamples wants to merge 1 commit into
Klipper3d:masterfrom
robertsamples:master
Open

docs: Update DCO real name requirement to reflect official CNCF guidance#7286
robertsamples wants to merge 1 commit into
Klipper3d:masterfrom
robertsamples:master

Conversation

@robertsamples

Copy link
Copy Markdown

The existing text states contributors must use their real name, with a parenthetical explicitly banning pseudonyms. This language was inherited from the Linux kernel's submitting-patches documentation, but it does not reflect the current official policy for CNCF projects.
The CNCF Foundation formally addressed this in (cncf/foundation#379, cncf/foundation#383, and linux kernal commit d4563201f33a022fc0353033d9dfeb1606a88330). The outcome, authored with input from Linux Foundation legal counsel, revised DCO Guidelines, which state:

A real name does not require a legal name, nor a birth name, nor any name that appears on an official ID (e.g. a passport). Your real name is the name you convey to people in the community for them to use to identify you as you. The key concern is that your identification is sufficient enough to contact you if an issue were to arise in the future about your contribution.

The requirement is identifiability and reachability, not disclosure of legal identity. The prohibition on pseudonyms is explicitly not part of DCO policy.
This PR updates the contributing guide to match what the governing bodies actually require, replacing the inaccurate parenthetical with a plain-language summary of the official guidelines.

Signed-off-by: Robert Samples rsamples@smith.edu

The "no pseudonyms" language was inherited from Linux kernel docs but
does not reflect current CNCF policy. The official CNCF DCO Guidelines
clarify that a real name need not be a legal name - only sufficient to
identify and contact the contributor. See cncf/foundation#383.
@dewi-ny-je

Copy link
Copy Markdown

It seems to me that a pseudonym, provided a real email address is used, would just be fine.
After all which protection for the maintainers would a "real name" (which never gets checked) provide over a pseudonym, once the person is reachable by email?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants