Clarify how to sign actually sign the CLA in the bot comment
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation
Research direction
Start in clabot/comments.py around line 50 and review the existing CLA bot comment and badge link. Update the comment so contributors can tell how to sign the CLA, incorporating the agreed guidance about the signing page or additional information link; done means the rendered message gives clear signing instructions.
Written by the indexing model from the issue text.
Description
The current CLA bot comment reads:
The following commit authors need to sign the Contributor License Agreement:
I’ve seen some contributors that were confused by this and didn’t realize that they needed to click on the “CLA Not Signed” badge to sign the CLA. Can we make this more clear? Some ideas:
- Add an instruction to click on the badge, e.g. “Click the button below to sign”
- Mention clicking in the badge text, e.g. “CLA Not Signed - Click Here to Sign”
- Include the raw URL to the CLA website, e.g. "visit https://cla.python.org/ to sign"
Also, would it be a good idea to add a link to https://www.python.org/psf/contrib/contrib-form/, which has more information about other options for signing?
- Dominant language
- Python
- Stars
- 8
- Forks
- 15
- Avg merge
- 7m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from psf/clabot
-
Bug normalising plus emails: "[email protected] is not verified with GitHub"Possibly taken @YS-OH-CORE claimed this 50 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Clarification of local development requirements and separation of basic vs GitHub-integrated testingOpen
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
User email displayOpen
Difficulty 3/5 1-2 days Newbie friendliness 50/100
Similar issues
-
add entry to blockOpen
Difficulty 1/5 Under an hour Newbie friendliness 65/100
StevenBlack/hosts#3299 ·
-
`garak --report` overwrites the input report when its name has no ".report"Possibly taken @0z5a claimed this today. Openneeds-triage
Difficulty 2/5 Half a day Newbie friendliness 72/100
Maintainers usually reply within 2 days
-
plot_graph crashes when a mesh node has no m2m edgePossibly taken @tygvi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mllam/neural-lam#883 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
future-agi/future-agi#4092 · 1 comment ·
Maintainers usually reply within 1 day
-
transcript analytics: a text whose only protected spans the prose pass redacts is withheld wholeOpen
Difficulty 1/5 Under an hour Newbie friendliness 82/100
WingedGuardian/GENesis-AGI#4641 ·
Maintainers usually reply within 1 day