Original text:
Discussion of this document takes place on the GitHub@ietf mailing list (ietf-and-github@ietf.org), which is archived at <del> https://mailarchive.ietf.org/arch/search?email_list=ietf-and-github [1]. </del>  Source for this draft and an issue tracker can be found at <del> https://github.com/ietf-gitwg/using-github [2]. </del>  1. The IETF has an open and transparent process for developing <del> standards.  The use of GitHub [3] or similar tools, when used as part </del>  of this process, can have several objectives.  GitHub provides tools that can be helpful in editing documents.  Use of this service has been found to reduce the time that Working Groups need to produce Version control systems are a critical component of software engineering and are also quite useful for document editing. <del> Git [4] is a distributed version control system that can operate </del>  without a central service.  Each instance of a repository contains a number of revisions.  Each revision stores the complete state of a set of files.  Users are able to create new revisions in their copy 1.2. <del> GitHub is a service operated at https://github.com/ [5].  GitHub </del>  provides centralized storage for git repositories.  GitHub is freely accessible on the open Internet. Git is not the only version control system available, nor is GitHub the only possible choice for hosting.  There are other services that host revision control repositories and provide similar additional <del> features to GitHub.  For instance, BitBucket [6] and GitLab [7] </del>  provide similar feature sets.  In addition to a hosted service, software for custom installations exists. CONTRIBUTING file. In addition to Working Group policies, notices on repositories MUST <del> include citations for the IETF Note Well [8]. </del>  3. new repositories for adopted Working Group items, or they might create repositories for individual documents on request. <del> All repositories for Working Group documents within the Working Group organization MUST be public.  Repositories for private documents MAY be kept private, but only where there is a specific reason for doing so.  For instance, a document that details a security vulnerability might be kept private prior to its initial publication as an Internet-Draft.  Once an Internet-Draft is published, repositories SHOULD be made public. </del>  The adoption status of any document MUST be clear from the contents of the repository.  This can be achieved by having the name of the An alternative is to rely on periodic email summaries of activity, such as those produced by a notification tool like github-notify-ml <del> [9].  This tool has been used effectively in several Working Groups, </del>  though it requires server infrastructure. Additionally, clear reporting about the changes that were included in 12.1.  URIs <del> [1] https://mailarchive.ietf.org/arch/search?email_list=ietf-and- github </del>  <del> [2] https://github.com/ietf-gitwg/using-github </del>  <del> [3] https://github.com/ </del>  <del> [4] https://git-scm.com </del>  <del> [5] https://github.com/ </del>  <del> [6] https://bitbucket.org/ [7] https://about.gitlab.com/ [8] https://www.ietf.org/about/note-well/ [9] https://github.com/dontcallmedom/github-notify-ml </del> 

Reviewer comments:
From Adam's AD review
Note that the URL fixes here are ineffective. The source is: The resulting XML is: The HTML shows a nice clickable link. xml2rfc produces text output of "URL (URL)". Perhaps this is a case where a small tweak to xml2rfc is in order.
Nice relaxation of the text.

Revised text:
Discussion of this document takes place on the GitHub@ietf mailing list (ietf-and-github@ietf.org), which is archived at  <ins> <https://mailarchive.ietf.org/arch/search?email_list=ietf-and- github>. </ins> Source for this draft and an issue tracker can be found at  <ins> <https://github.com/ietf-gitwg/using-github>. </ins> 1. The IETF has an open and transparent process for developing  <ins> standards.  The use of GitHub [1] or similar tools, when used as part </ins> of this process, can have several objectives.  GitHub provides tools that can be helpful in editing documents.  Use of this service has been found to reduce the time that Working Groups need to produce Version control systems are a critical component of software engineering and are also quite useful for document editing.  <ins> Git [2] is a distributed version control system that can operate </ins> without a central service.  Each instance of a repository contains a number of revisions.  Each revision stores the complete state of a set of files.  Users are able to create new revisions in their copy 1.2.  <ins> GitHub is a service operated at <https://github.com/>.  GitHub </ins> provides centralized storage for git repositories.  GitHub is freely accessible on the open Internet. Git is not the only version control system available, nor is GitHub the only possible choice for hosting.  There are other services that host revision control repositories and provide similar additional  <ins> features to GitHub.  For instance, BitBucket [3] and GitLab [4] </ins> provide similar feature sets.  In addition to a hosted service, software for custom installations exists. CONTRIBUTING file. In addition to Working Group policies, notices on repositories MUST  <ins> include citations for the IETF Note Well [5]. </ins> 3. new repositories for adopted Working Group items, or they might create repositories for individual documents on request.  <ins> Maintaining private repositories for Working Group products is not recommended without specific cause.  For instance, a document that details a security vulnerability might be kept private prior to its initial publication as an Internet-Draft.  Once an Internet-Draft is published, repositories for Working Group documents MUST be made public. </ins> The adoption status of any document MUST be clear from the contents of the repository.  This can be achieved by having the name of the An alternative is to rely on periodic email summaries of activity, such as those produced by a notification tool like github-notify-ml  <ins> [6].  This tool has been used effectively in several Working Groups, </ins> though it requires server infrastructure. Additionally, clear reporting about the changes that were included in 12.1.  URIs  <ins> [1] https://github.com/ </ins>  <ins> [2] https://git-scm.com/ </ins>  <ins> [3] https://bitbucket.org/ </ins>  <ins> [4] https://about.gitlab.com/ </ins>  <ins> [5] https://www.ietf.org/about/note-well/ </ins>  <ins> [6] https://github.com/dontcallmedom/github-notify-ml </ins>