Re: [Ietf-and-github] Tracking drafts

[Rob Sayre <[e-mail]>]

On Wed, Feb 12, 2020 at 8:57 AM STARK, BARBARA H <[e-mail]> wrote:

> 
>
>    - This patch is well-meaning, but it does not meet the IESG guidelines
>    for design teams. For example, it enables completely closed groups that
>    throw their output over the fence into Github. The edit does say "open
>    participation", but that's not really defined. In particular, the IESG
>    design team recommendations require named members, and periodic reports.
>
>
>
> Perhaps adding “(such as making the repo public)” fixes that.
>
>
> Since it costs money to make a GitHub repo private, and there is no
> suggestion that IETF spend money on official WG GitHub repos, I’m curious
> how such an addition to the text would make any difference.
> If people want to set up a private and paid-for repo to stage changes
> before putting them in an IETF repo, I think it will be hard to stop them
> and I’m not convinced they would be doing something wrong.
> Or am I an anomaly and misbehaving when I communicate with fellow draft
> authors off-list using direct email? Is *all* communication between draft
> authors and design team members required to be public? This is news to me.
>

Of course that kind of stuff happens, and it's ok. But if it's long-term
and coordinated, it should be transparent. This means the participants
should be known, which is where this edit seems a bit off imho. In this
sense, a design team is more tightly defined than a mailing list or a
github repo, even if less open.

thanks,
Rob