Last Call Review of draft-ietf-git-using-github-04
review-ietf-git-using-github-04-genart-lc-carpenter-2020-02-23-00

Request Review of draft-ietf-git-using-github
Requested rev. no specific revision (document currently at 06)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2020-03-03
Requested 2020-02-18
Authors Martin Thomson, Barbara Stark
Draft last updated 2020-02-23
Completed reviews Opsdir Last Call review of -04 by Qin Wu (diff)
Secdir Last Call review of -05 by Derek Atkins (diff)
Genart Last Call review of -04 by Brian Carpenter (diff)
Tsvart Last Call review of -04 by David Black (diff)
Genart Telechat review of -05 by Brian Carpenter (diff)
Assignment Reviewer Brian Carpenter
State Completed
Review review-ietf-git-using-github-04-genart-lc-carpenter-2020-02-23
Posted at https://mailarchive.ietf.org/arch/msg/gen-art/qQY9gGda7QaNotffqCZdiFogFQc
Reviewed rev. 04 (document currently at 06)
Review result Ready with Issues
Review completed: 2020-02-23

Review
review-ietf-git-using-github-04-genart-lc-carpenter-2020-02-23

Gen-ART Last Call review of draft-ietf-git-using-github-04

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-git-using-github-04.txt
Reviewer: Brian Carpenter
Review Date: 2020-02-24
IETF LC End Date: 2020-03-03
IESG Telechat date:  

Summary: Ready with issue
--------

Comment:
--------

I've tracked this document since the -00 version and I think it is clear
and represents WG consensus.

Issues:
-------

Is this draft intended to become part of BCP25? I think it would be
useful for the IESG to clarify this rather than leave it to the RFC Editor.

Nit:
----

> 3.4.  Document Formats
>
>   In addition to the canonical XML format [RFC7991], document editors
>   might choose to use a different input form for editing documents,
>   such as Markdown.  Markdown-based formats are more accessible for new
>   contributors, though ultimately decisions about format is left to
>   document editors.

s/is/are/