-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ethics] Realname policy excludes marginalized individuals. #7389
Comments
Thank you for asking these questions. The approach we are using with the DCO is what is used to protect everyone involved in the project (this includes users of Gitea, and also contributors/maintainers) from legal issues with regards to licensing of the intellectual property provided to the project. The project does not have the legal resources to determine how best to accept this information, and so we must rely on larger projects (such as The Linux foundation who created the DCO) who have already engaged with lawyers. It does have issues, some of those issues you have mentioned above. Personally I have to rely on assuming good-faith from users who open PRs that what they are putting into commits is what is legally binding. Like the Linux Kernel, Git itself, and many other projects this information is stored directly, and as a matter of policy it is immutable, in git history. I would I recommend asking The Linux Foundation the the questions you have asked as they would be able to provide a better response than I could. My personal goal is that the project moves to a way of providing a similar guarantee of assigning IP rights to the project under the terms of the license without special commit information, one such way that other projects use is a CLA. Switching to a CLA would involve legal advice, so I can't offer any timelines, nor can I guarantee that it will happen, but I can't say it won't happen either. I want to thank you again for raising these concerns. As the majority of this ticket is questions I will now close it as we request that questions are directed to Discord (https://discord.gg/gitea) or the forum (https://discourse.gitea.io), but I will open a PR for documentation. |
Thank you, I appreciate the thorough reply. |
* Update CONTRIBUTING.md with information about DCO References: #7389 More information: https://about.gitlab.com/handbook/marketing/community-relations/code-contributor-program/#developer-certificate-of-origin-dco * Update CONTRIBUTING.md Co-Authored-By: zeripath <art27@cantab.net>
* Update CONTRIBUTING.md with information about DCO References: go-gitea#7389 More information: https://about.gitlab.com/handbook/marketing/community-relations/code-contributor-program/#developer-certificate-of-origin-dco * Update CONTRIBUTING.md Co-Authored-By: zeripath <art27@cantab.net>
Under the sign-off section in the contributing guidelines, this line caught my eye:
There's a lot of ignorance, reinforcement of marginalization, and failure to understand identity that are baked into the next few sentences:
Requiring someone to reveal their "real" name to add anything to your source code brings up several questions:
I'd like to propose that these lines be excised, along with the realname policy, from the contributing guidelines document.
The text was updated successfully, but these errors were encountered: