[rfc-i] [Ietf-and-github] RFC Editor & Github
jordan.ietf at gmail.com
Mon Feb 25 18:24:56 PST 2019
PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050
"Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg."
> On Feb 25, 2019, at 1:43 PM, Phillip Hallam-Baker <phill at hallambaker.com> wrote:
> On Mon, Feb 25, 2019 at 12:02 PM Eric Rescorla <ekr at rtfm.com <mailto:ekr at rtfm.com>> wrote:
> On Mon, Feb 25, 2019 at 7:18 AM Phillip Hallam-Baker <phill at hallambaker.com <mailto: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.
> Which I did and the response was 'make a pluto requerst' or something.
> The problem was a bit more than that. The conversation ended up fragmented across the two systems. So what was supposed to help the process meant that the discussion and the process went out of sync.
I have seen this as well. You start getting the conversation taking places all over the place.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rfc-interest