(Sorry this has been taking too long for me to continue)
I’ve previously brought this up in the mailing list, and I’ve discussed this with various people:
- with @brettcannon during core Python sprint
- with @EWDurbin via emails and video chats
- with Ewa, Betsy, Van via emails
Ernest had set up our own instance of the CLA assistant at: https://psf-cla-assistant-staging.herokuapp.com/
If you’d like you can install it in your own repo, or see a couple examples of how it works:
We’ve also asked several core developers to try it out and give feedback.
At this point, if there is no strong objection from the core developers, Steering Council and active core contributors, I’d like to get this rolled out soon (in the next couple weeks before I go OOOS).
The one important information with this new workflow:
Instead of trying to “migrate” our existing CLA records from bpo to CLA-assistant, we will be asking folks to re-sign the CLA in CLA-assistant. It will take several clicks, which might seem bothersome, but it will take effect immediately, instead of waiting for a staff from The PSF to review your CLA (one or two business days), and you only do this once.
(@EWDurbin can clarify in case I misunderstood this part?)
Other changes based on early testing (thanks to @willingc and Van L for feedback and clarification)
- we’ve made bpo field optional in the CLA.
- CLA will only be accepted under Apache v2 (removed the option of Academic Free license)
Let me know if you have any questions or concerns.
EDITED with link to the original thread in core-workflow ML: https://email@example.com/thread/2OY2KGVCKIRJDX325DGKZSVY2IKSDTJJ/
EDIT #2: The PSF still has records of your previously signed CLA. You will only need to re-sign if you make new pull requests to Python.