fix: [META] - CLA Guidance improvement#5428
Open
SillyZir wants to merge 3 commits intognolang:masterfrom
Open
Conversation
Collaborator
🛠 PR Checks Summary🔴 Pending initial approval by a review team member, or review from tech-staff Manual Checks (for Reviewers):
Read More🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers. ✅ Automated Checks (for Contributors):🟢 Maintainers must be able to edit this pull request (more info) ☑️ Contributor Actions:
☑️ Reviewer Actions:
📚 Resources:Debug
|
Member
Member
|
@alexiscolin can you check with legal? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rewrote
CLA.mdto include clear explanations of what the CLA is, why contributors must sign it, and step-by-step instructions on how to sign it — addressing the lack of guidance reported in #5333.Fixes #5333
Problem
Contributors interacting with
gnokeyencountered a "user did not sign CLA" error with no context — no explanation of what a CLA is, why it's required, or how to actually sign it. The existingCLA.mdwas a dense legal document with no onboarding guidance, and the gnoweb render offered no additional clarity or trust signals.Solution
Restructured
CLA.mdby adding three new sections — "What is the CLA?", "Why must contributors sign it?", and "How to sign the CLA" — above the existing legal text. These sections provide a plain-language overview of the agreement, explain the legal rationale (licensing rights, IP confirmation), and walk contributors through the signing flow. The original legal terms were preserved and reformatted for readability.Impact
New and existing contributors will no longer hit a dead-end error without recourse. The improved
CLA.mdreduces friction in the contribution onboarding process and builds trust by making the legal requirements transparent and actionable.