cncf
/
toc
mirror of https://github.com/cncf/toc.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add FAQ entry on DCO/CLA contributions 

Signed-off-by: Chris Aniszczyk <caniszczyk@gmail.com>
This commit is contained in:
Chris Aniszczyk 2022-07-02 12:45:23 -07:00 committed by GitHub
parent 67969f2444
commit 4b5d5049bc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
FAQ.md
View File

@ -75,3 +75,9 @@ CNCF uses revenues from events first and foremost to cover the cost of events. T
## Why do members join if they don’t get to control CNCF and its projects?
The main member benefit is to support the cloud native ecosystem and to be publicly seen supporting it. You can see other benefits on the [Join](https://www.cncf.io/about/join/) page, but none of them involve control over projects. The governing board has ultimate control over CNCF, but CNCF is managed through a written charter and it consists of many disparate and competing interests. As a result, decision-making is consensus-based.
## Do I have to use my real name when contributing via DCO/CLA?
Yes, no pseudonyms or anonymous contributions. The CNCF follows the same tried and true policy in the Linux Kernel and other LF projects. They have proven strong enough to defend the Linux kernel against legal attacks to date
* https://github.com/torvalds/linux/blob/master/Documentation/process/submitting-patches.rst#developers-certificate-of-origin-11