Re: New candidate JEP: 369: Migrate to GitHub – contributors should not be required to have a GitHub account
kim.barrett at oracle.com
Fri Nov 15 22:11:30 UTC 2019
> On Nov 15, 2019, at 4:20 PM, Joe Darcy <joe.darcy at oracle.com> wrote:
> On 11/15/2019 10:08 AM, František Kučera wrote:
>> Dne 12. 11. 19 v 17:00 mark.reinhold at oracle.com napsal(a):
>>> - Mark
>> I see that there is:
>> - Ensure that workflows structurally similar to the existing e-mail and
>> webrev based workflows are supported.
>> - Do not require developers to install OpenJDK specific tools in order
>> to contribute.
>> - For contributors not wishing to create an account on GitHub, we would
>> continue to accept patches sent to the OpenJDK mailing lists.
>> Could you please make it explicit (in the Goals section), that
>> contributors will not be required to have a GitHub account? (and that
>> users without such account will not be discriminated)
> In the "Workflow" section the JEP explicitly states:
> "However, creating a PR requires an account on GitHub. For contributors not wishing to create an account on GitHub, we would continue to accept patches sent to the OpenJDK mailing lists. Such patches would, however, require a contributor with a GitHub account to create a PR, similar to how many contributors today help newcomers to create and upload webrevs to cr.”
An important difference between those two cases is that the
expectation with a newcomer is that if they continue to contribute
they will eventually be granted the appropriate credentials and
permissions and no longer need such help.
I'm guessing that if a GitHub account is required to create a pull
request, the associated push to the repository will also require a
GitHub account. In which case a long-time OpenJDK contributor who is
unwilling to create a GitHub account (for whatever reasons) will
effectively be losing a key part of their committer status.
More information about the discuss