Re: [Ietf-and-github] Tracking drafts

I can understand the motivation for this, but I think it just confuses
things as-is.

In general, we've long had a tradition that editors have a lot of
discretion in how they prepare documents, with the assumption being that if
they make changes without WG consensus, then those changes need to be taken
to the WG. And of course the editor could have private conversations about
the document, or even public ones outside the WG. So in some respects GH is
like that. In any case, I think the Design Team analogy is confusing. I
would simply say:

Work done in GitHub -- even when there is extensive discussion -- has no
special status. That is, the output of any activity using GitHub needs to
be taken into the Working Group
and subject to approval, rejection or modification by the Working Group as
with any other input.

Note that I have removed the "mailing list" text as well, because 2418 is
actually somewhat vague on exactly how work done offline in drafts is to be
brought to the WG. The key point is that this is like any such input.

-Ekr

On Thu, Feb 13, 2020 at 2:03 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Fri, Feb 14, 2020, at 08:45, Martin Thomson wrote:
> > +A choice to use GitHub is similar to the formation of a design
> > +team (see Section 6.5 of {{!RFC2418}}) provided that the work uses a
> public
> > +repository.  That is, the output of any activity using GitHub needs to
> be taken
> > +to the Working Group mailing list and subject to approval, rejection, or
> > +modification by the Working Group as with any other input.
>
> Updated as per Rich and Rob.  Thanks for the prompt review.
>
> _______________________________________________
> Ietf-and-github mailing list
> Ietf-and-github@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-and-github
>