Update PSF's contribution forms to reflect new CLA process

[Mariatta]

Is your feature request related to a problem? Please describe.
We're in the process of starting to use CLA assistant to check for CLA for contributions to Python.

1. The page: https://www.python.org/psf/contrib/ should be updated to reflect the new process.
   Currently it contains links to the PSF contribution form (https://www.python.org/psf/contrib/contrib-form/)

• It should be updated to point to our instance of CLA assistant:

https://psf-cla-assistant-staging.herokuapp.com/python/cpython (TODO: replace with correct URL)

2. Under new CLA process, we will only be accepting the contributions under the Apache 2.0 license.

• The Academic free license should be removed from the page

3. Under the "Submission instructions" heading, the link to online form points to the legacy cla form.

• It should be updated to the new CLA assistant page
• Provide a PDF version of the form.

4. The legacy cla form can be removed.

• Remove https://www.python.org/psf/contrib/contrib-form/

Additional context

See the Migrating to CLA Assistant core-workflow project.

See also devguide PR outlining how to sign the CLA under the new process: python/devguide#490

[Mariatta]

I don't have access to update the page myself, so assigning to @ewdurbin to follow up.

[nicktimko]

While updating/moving the CLA, can the form be changed (or wording around the form be added) to clarify how the "bugs.python.org username" relates to your GitHub username, especially if being prompted to sign the CLA from a GH PR?

(Was going to try to PR something here, but I don't see how /psf/contrib/contrib-form/ is handled in the code/where that content lives)

[malemburg]

I guess this can be closed now that we are using a Github bot: https://discuss.python.org/t/https-github-com-python-is-now-using-a-new-cla-bot/

[vstinner]

I'm surprised that in 2023, https://www.python.org/psf/contrib/contrib-form/ asks for a "bugs.python.org username". Is it still possible to create new accounts? The server was switched to read-only, no?

[hugovk]

Yes, https://bugs.python.org is read-only:

[ewdurbin]

Looks like this was updated at https://devguide.python.org/getting-started/pull-request-lifecycle/#licensing but not in the CMS when @ambv rolled out the new CLA tool. Perhaps this url just redirect to the dev guide?

[malemburg]

The form itself is managed using Adobe DocuSign, so it has to be changed there.

Note that the contrib forms are still needed for org contributions, since the Github process only works for individual contributions. Contributions to other repos under PSF control are also not necessarily managed by the Github bot, so need this process as well.

There are also a couple of other changes needed:

• https://www.python.org/psf/contrib/contrib-form/ still lists the "Academic Free License v. 3.0" which is no longer being accepted
• https://www.python.org/psf/contrib/ has the same issue
• neither of these page mentions the process for cpython Github contributions or the fact that org contributions have to use the form based approach

Someone in the PSF should take leadership of making sure we have a consistent story for IP contributions across all PSF owned repos and management of org contributions. I guess Deb Nicholson would be the right person to oversee this (just can't find her Github nick).

[ewdurbin]

Deb is @eximious