Changes between Version 32 and Version 33 of WikiStart


Ignore:
Timestamp:
Jul 30, 2019, 8:23:10 AM (6 months ago)
Author:
mahoney@…
Comment:

fixed some typos, clarified when telechat assignments are made

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v32 v33  
    22= General Area  =
    33
    4 == General Area Review Team (GEN-ART) Guidelines ==
     4== General Area Review Team (Gen-ART) Guidelines ==
    55
    6 These are guidelines for document review within the GEN-ART.
     6These are guidelines for document review within the Gen-ART.
    77
    88See also: [wiki:GenArtfaq FAQ], [wiki:GenArtReviewers Reviewers], [wiki:DatatrackerReviewToolHowto New Review Tool!]
     
    1010=== Timeline of Review ===
    1111
    12 Documents are typically assigned to a GEN-ART reviewer during IETF-LC.  The
     12Documents are typically assigned to a Gen-ART reviewer during IETF Last Call.  The
    1313documents may be re-reviewed once they appear on a Telechat agenda. 
    14 Documents may also be reviewed at the request of ADs prior to IETF-LC.
     14Documents may also be reviewed at the request of ADs prior to IETF Last Call.
    1515
    1616The process for reviewing Early documents:
     
    2323The process for reviewing documents at Last Call:
    2424
    25  * The Secretary assigns a reviewer using a round robin order based on availability,  within a week of the Last Call announcement – typically on Thursday evenings.
     25 * The Secretary assigns a reviewer using a round-robin order based on availability,  within a week of the Last Call announcement – typically on Thursday evenings.
    2626 * We expect the reviewer to be done before the end of Last Call.
    27  * The reviewer sends the review to the Gen-ART list
     27 * The reviewer sends the review to the Gen-ART list.
    2828 * The reviewer also sends the review to the AD, WG chairs & authors, and optionally to the WG mailing list.  Since IETF Last Call comments are commonly sent to the IETF discussion list, the reviewer may also choose to do that; in any case the review will be public.
    2929
    3030The process for reviewing documents when they appear on the IESG agenda:
    3131
    32  * Secretary checks the IESG agenda one week before the IESG telechat. The agenda is typically finalized Thursday evening PDT, with late agenda items sometimes being added on Friday morning, thus the assignments are out either late Thursday evening or early Friday morning (PDT).
    33  * For documents reviewed at Last Call, the same reviewer is assigned and a new review is only asked for if the document is revised or issues resolved.
    34  * The Secretary assigns a reviewer using a round robin order based on availibility for any new document not previously assigned or reviewed.
    35  * Reviewers send their review to the Gen-ART list no later than COB  (i.e., 8 PM EDT) the Tuesday before the telechat (earlier is better!)
     32 * The Secretary makes Telechat review assignments at the same time as Last Call assignments. 
     33 * For documents reviewed at Last Call, the same reviewer is assigned and a new review is only asked for if the document is significantly revised or issues have not been resolved.
     34 * The Secretary assigns a reviewer using a round-robin order based on availability for any new document not previously assigned or reviewed.
     35 * Reviewers send their review to the Gen-ART list no later than COB (i.e., 8 PM EDT) the Tuesday before the Telechat (earlier is better!)
    3636 * Reviews should be copied to authors, responsible ADs and WG chairs, unless the review finds no issues. Also, including a link to the FAQ in the email has proved essential for the recipients of the review in understanding the context.
    3737 * If the AD concludes that the concerns raised by the reviewer warrant blocking the document, the AD will do so.
    3838
    39 The telechats are every other Thursday, with the [https://datatracker.ietf.org/iesg/agenda/ agenda] finalized on the Thursday evening one week prior to the telechat.
     39The Telechats are every other Thursday, with the [https://datatracker.ietf.org/iesg/agenda/ agenda] finalized on the Thursday evening one week prior to the telechat.
    4040
    4141=== Form of review ===
     
    7575The length of a review will vary greatly according to circumstances, and it is acceptable for purely editorial comments to be sent privately if it's obvious that the document will have to be substantially revised anyway. All substantive comments must be included in the public review. Wherever possible, they should be written as suggestions for improvement rather than as simple criticism. Explicit references to prior work and prior IETF discussion should be given.
    7676
    77 Reviewers should review for all kinds of problems, from basic architectural or security issues, Internet-wide impact, technical nits, problems of form and format (such as IANA Considerations or incorrect references),and editorial issues. Since these reviews are on documents that are supposed to be finished, the review should consider "no issue too small" - but cover the whole range from the general architectural level to the editorial level. However, a review which consists only of copy-editing is not productive. If the reviewer feels that a draft is too badly written to advance, it will be sufficient to say so with one or two examples.
     77Reviewers should review for all kinds of problems, from basic architectural or security issues, Internet-wide impact, technical nits, problems of form and format (such as IANA Considerations or incorrect references), and editorial issues. Since these reviews are on documents that are supposed to be finished, the review should consider "no issue too small" - but cover the whole range from the general architectural level to the editorial level. However, a review which consists only of copy-editing is not productive. If the reviewer feels that a draft is too badly written to advance, it will be sufficient to say so with one or two examples.
    7878
    7979The review should apply generally agreed IETF criteria, such as
     
    135135
    136136=== Mailing List ===
    137 All reviews are sent to the IETF gen-art mailing list: https://datatracker.ietf.org/group/genart/archives/, and also to the authors, ADs, and/or WG chairs/Document Shepherds. Reviewers may also send the reviews to the IETF discussion list, which is done by default if the Review Tool mentioned below is used to submit reviews. 
     137
     138All reviews are sent to the IETF gen-art mailing list: https://mailarchive.ietf.org/arch/browse/gen-art/, and also to the authors, ADs, and/or WG chairs/Document Shepherds. Reviewers may also send the reviews to the IETF discussion list, which is done by default if the Review Tool mentioned below is used to submit reviews. 
    138139
    139140=== Review Tool ===
     
    145146
    146147=== Archiving of reviews ===
     148
    147149All reviews are archived. They are visible in the mailing list archive, along with any subsequent discussion copied to the list: https://datatracker.ietf.org/group/genart/archives/
https://trac.ietf.org/trac/gen/wiki/WikiStart?action=diff&version=33
trac.ietf.org
crawl=CC-MAIN-2020-05
27054
application/http; msgtype=response
sha1:QWV6YICT4FDOKP3VD2EFUXWJ5SJKMSJ3
<urn:uuid:7248f640-1a6c-4616-ab22-0972c5b6204b>
2020-01-25T00:04:32Z
4.31.198.44
application/xhtml+xml
sha1:C2EH5DSWL7SRLLVGMG2WSJSDW5NJH4DQ
<urn:uuid:ebb330df-c0f2-4885-823b-6ad15b14492d>
https://trac.ietf.org/trac/gen/wiki/WikiStart?action=diff&version=33
response
<urn:uuid:288248d3-c884-46d4-b689-cc76bf190408>
isPartOf: CC-MAIN-2020-05
publisher: Common Crawl
description: Wide crawl of the web for January 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-103.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/