Re: [Ietf-and-github] Adam Roach's No Objection on draft-ietf-git-using-github-05: (with COMMENT)

As an aside, I just worked out how to do bare links in kramdown.  It's not intuitive.

BAD:
[https://github.com](https://github.com)
BAD:
<https://github.com>
GOOD:
[](https://github.com)

On Thu, Mar 12, 2020, at 12:11, Martin Thomson wrote:
> On Thu, Mar 12, 2020, at 11:48, Adam Roach via Datatracker wrote:
> >    GitHub is a service operated at https://github.com/
> >    (https://github.com/).
> > 
> > The parenthetical seems unnecessary.
> 
> That's a consequence of attempting to turn the link into a link.  In 
> HTML, this looks fine and having a link is good.  This is the result of 
> the xml2rfc text rendering.  I'm opening an issue.
>  
> A couple of your comments are addressed already in 
> https://github.com/ietf-gitwg/using-github/pull/43
>  
> > Section 3.2:
> >    Repositories for private documents MAY
> >    be kept private, but only where there is a specific reason for doing
> >    so.
> > 
> > This seems really odd, completely undetectable/unenforceable, and actually
> > harmful. It is common practice for editors to just keep their source local and
> > only submit the output of such source to the i-d repository; and that’s just
> > fine. This seems to say that such users are effectively forbidden to have their
> > source equally private but also effectively backed-up and revision-controlled
> > by one specific online service. It seems strictly better to allow and even
> > encourage this, to prevent a loss of data.
> 
> I might revise this statement.  As you say, it's meaningless.  But the 
> admonition about operating in secret is probably worth retaining.  How 
> about: https://github.com/ietf-gitwg/using-github/pull/49
> 
> _______________________________________________
> Ietf-and-github mailing list
> Ietf-and-github@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-and-github
>