[rfc-i] [Ietf-and-github] RFC Editor & Github

Eric Rescorla ekr at rtfm.com
Mon Feb 25 09:02:18 PST 2019


On Mon, Feb 25, 2019 at 7:18 AM Phillip Hallam-Baker <phill at hallambaker.com>
wrote:

> What worries me about the Github workflow is that it is really really easy
> to respond to an email. Learning how to use a tool that was not well
> thought out in the first place for a purpose it was not intended to serve
> is not easy.
>

Note that you can actually respond to Github comments in email.

-Ekr


> My experience of the OpenPGP working group was that the contributions were
> quickly reduced to the set of people who were familiar with Git and that
> set of people wasn't enough to sustain the group.
>
> Workflow tools are great. We can surely do better than email for workflow.
> But if people want to use Github, They have to be prepared to at the very
> least write up a description of how to use it.
>
>
>
> On Sun, Feb 24, 2019 at 11:25 PM Ted Lemon <mellon at fugue.com> wrote:
>
>> I’m mostly whining about the issue tracker, which I don’t find all that
>> useful.   It’s better than nothing, but easy to understand why it didn’t
>> fit into the RFC editor workflow. We haven’t actually used the github pull
>> request workflow in the documents I’ve edited.   If it’s similar to the
>> atlassian workflow, it’s possible that it’s perfectly fine and I should
>> shut up. :)
>>
>> _______________________________________________
>> rfc-interest mailing list
>> rfc-interest at rfc-editor.org
>> https://www.rfc-editor.org/mailman/listinfo/rfc-interest
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20190225/7385f952/attachment.html>


More information about the rfc-interest mailing list