8000 Add instructions on how to sign CLA using CLA-assistant. · Mariatta/devguide@e28b688 · GitHub
[go: up one dir, main page]

Skip to content

Commit e28b688

Browse files
committed
Add instructions on how to sign CLA using CLA-assistant.
CLA can be signed before or after a contributor made a pull request. Remove paragraph about re-checking the CLA. It is effective immediately. Closes python/core-workflow#314
1 parent 2f50f09 commit e28b688

File tree

2 files changed

+33
-30
lines changed

2 files changed

+33
-30
lines changed

committing.rst

Lines changed: 4 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -97,13 +97,13 @@ original check-in message in that case).
9797

9898
Finally, make sure that the submitter of the
9999
patch has a CLA in place (indicated by an asterisk following their username
100-
in the `issue tracker`_ or by the "CLA Signed" label on the pull request).
101-
If the submitter lacks a signed CLA and the patch is non-trivial, direct them
102-
to the electronic `Contributor Licensing Agreement`_
100+
in the `issue tracker`_ or by the ``license/cla`` status check on the pull request).
101+
If the submitter lacks a signed CLA, direct them to the `Contributor Licensing Agreement`_
103102
to ensure the PSF has the appropriate authorizations in place to relicense
104103
and redistribute their code.
105104

106105

106+
107107
Contributor Licensing Agreements
108108
--------------------------------
109109

@@ -128,18 +128,8 @@ for inclusion.
128128

129129

130130
.. _Contribution: https://www.python.org/psf/contrib/
131-
.. _Contributor Licensing Agreement:
132-
https://www.python.org/psf/contrib/contrib-form/
133-
134-
135-
Checking if the CLA has been received
136-
-------------------------------------
137-
138-
To check if a contributor's CLA has been received, go to the following website::
139-
140-
https://check-python-cla.herokuapp.com/
131+
.. _Contributor Licensing Agreement: https://psf-cla-assistant-staging.herokuapp.com/python/cpython
141132

142-
and put in their GitHub username.
143133

144134
For further questions about the CLA process, write to: contributors@python.org.
145135

pullrequest.rst

Lines changed: 29 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -243,30 +243,42 @@ license your code for use with Python (you retain the copyright).
243243
You only have to sign this document once, it will then apply to all
244244
your further contributions to Python.
245245

246-
Here are the steps needed in order to sign the CLA:
246+
You can sign the CLA before, or after you have created a pull request.
247247

248-
1. If you don't have an account on `bugs.python.org <https://bugs.python.org>`_
249-
(aka b.p.o), please
250-
`register <https://bugs.python.org/user?@template=register>`_ to create one.
248+
To sign a CLA before you created a pull request:
251249

252-
2. Make sure your GitHub username is listed in the `"Your Details"
253-
<https://cloud.githubusercontent.com/assets/2680980/23276970/d14a380c-f9d1-11e6-883d-e13b6b211239.png>`_
254-
section at b.p.o.
250+
1. Go to The PSF's instance of `CLA Assistant`_.
255251

256-
3. Fill out and sign the PSF `contributor form`_. The "bugs.python.org username"
257-
requested by the form is the "Login name" field under "Your Details".
252+
2. Sign in with the GitHub account that you will use to contribute to Python.
258253

259-
After signing the CLA, please **wait at least one US business day** and
260-
then check the status by going to the `check-python-cla <https://check-python-cla.herokuapp.com>`_
261-
website. The check will also be run automatically the next time you push changes
262-
to your PR.
254+
3. Read the CLA.
263255

256+
4. Enter your information in the form: Full name, address, and email address.
257+
It should be the email address associated with your GitHub account.
258+
259+
5. Tick the "I have read and agree to the CLA" checkbox.
260+
261+
6. Press the "I agree" button.
262+
263+
To sign the CLA after you have created a pull request:
264+
265+
1. Click on the ``[CLA|not signed yet]`` button in the comment by ``psf-cla-assistant`` bot.
266+
267+
2. Sign in with the GitHub account used to create the pull request.
268+
269+
3. Read the CLA.
270+
271+
4. Enter your information in the form: Full name, address, and email address.
272+
It should be the email address associated with your GitHub account.
273+
274+
5. Tick the "I have read and agree to the CLA" checkbox.
275+
276+
6. Press the "I agree" button.
264277

265278
.. _PSF license: https://docs.python.org/dev/license.html#terms-and-conditions-for-accessing-or-otherwise-using-python
266-
.. _contributor agreement: https://www.python.org/psf/contrib/
267-
.. _contributor form: https://www.python.org/psf/contrib/contrib-form/
279+
.. _contributor agreement: https://psf-cla-assistant-staging.herokuapp.com/python/cpython
268280
.. _Python Software Foundation: https://www.python.org/psf/
269-
281+
.. _CLA Assistant: https://psf-cla-assistant-staging.herokuapp.com/python/cpython
270282

271283
Submitting
272284
----------
@@ -441,3 +453,4 @@ Non-trivial contributions are credited in the ``Misc/ACKS`` file (and, most
441453
often, in a contribution's news entry as well). You may be
442454
asked to make these edits on the behalf of the core developer who
443455
accepts your pull request.
456+

0 commit comments

Comments
 (0)
0