[core-workflow] Workflow for applying b.p.o patches to GitHub

[Mariatta Wijaya]

Hi,

I'd like to get clarification of the proper workflow for applying patches
from b.p.o to GitHub.

Technically, one can use patch command, or using hg diff --git, and this
will be documented in https://github.com/python/devguide/issues/193

The ideal situation is to have the patch author prepare their own GitHub
PR. Most of them have been happy to do this :)

However, I've seen situations where the patch author is unable to upload
their patch to GitHub:

1. author is no longer active, but we want to apply their patch.
2. author is not caught up with GitHub workflow, and asked someone else to
prepare the PR.
3. author refuses to use GitHub, but wants their patch applied anyway.

Couple questions:
1. Can anyone prepare the GitHub PR based on the patch? or only core
developers?
2. If anyone can prepare the GitHub PR, what do we need in terms of CLA? I
prefer not to have to guess on this matter.
In the rare situation like bpo-30181, author signed CLA in bpo, but we
can't verify it on GitHub since they don't have a GitHub account. How
should we go forward with it?

Anything else we need to worry about?
I'd like to get all of these documented in the devguide.

Thanks :)

Mariatta Wijaya
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20170515/7654113c/attachment.html>