PEP 581 - Using GitHub Issues

Core Workflow
20

BTW, if people have any idea of how to resolve this, do tell :slight_smile:

My current ideas:

  • Now that we have experience building out blurb-it and miss-islington aka bots that write codes to CPython, I think it is possible to come up with another web form that accepts the .patch file, and the bot can create the pull request using that patch.
    This solves the issue for people who wants to contribute by uploading patches but unable to create GitHub account.
    But we need to figure out how the CLA check will work in this case. The plan is to start using cla-assistant quite soon. Not sure how cla-assistant will work for this situation.
  • Similar to the above, we can come up with a web form so people can submit issues there, and it gets automatically transformed into an issue on GitHub by the bot.
    This solves the issue for people who wants to report bugs but unable to create GitHub account. This form should require their name and email address. The bot will use the email address to send updates about the issue.
  • Create a new mailing list python-issues. Any activities on GitHub (issue created, issue commented, etc) will be posted to the mailing list. So people without access to GitHub can still follow along.
1 Like