On Thu, Jun 14, 2018, 17:31 Mariatta Wijaya, <mariatta.wijaya@gmail.com> wrote:
Currently, people wanting to contribute to projects like peps, devguide, core-workflow, bedevere, need to sign CLA, which requires a bpo account, and then they need to add their GitHub account to their bpo account.

I find this quite complicated process and a barrier of entry.

I think it will be great to have this process simplified. I think people should not need to have bpo account unless they're actually participating in the bug tracker for CPython.

1. Can we have people sign CLA and not require their bpo account?

Yes, we just need a record that's independent of GitHub (or can at least be easily backed up).

2. Other big issue with bpo as CLA host is we don't have easy way that can let the-knights-who-say-ni update the label in the PR once the contributor has signed the CLA.

I've been thinking about this and I think we can with a bit of effort (basically we need some way to know what repos Ni is hooked up to and then a cron job that checks all "CLA not signed" PRs). We could also provide a URL people can visit to trigger a check.


I've brought this up at the language summit, as one of the necessary step before we can start using GitHub issues. (that is not yet decided, and this is not the thread to argue about it).

But whether we are using GitHub issues or not, the current process needs improvement anyway.

core-workflow mailing list -- core-workflow@python.org
To unsubscribe send an email to core-workflow-leave@python.org
This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct