RPC Wiki

This fourth experiment involved a small document (4 authors, 14 pages, not in a cluster, 12 questions at the end of the EDIT pass). One of the authors (Tim Evens) and the AD agreed to the experiment when the document entered the queue.

• GitHub repo for the I-D

In this experiment, the RPC created and controlled the repo. Both pull requests and issue tracking were used.

• rfc9069-AUTH48
• Initially set to private.
• Contains:
  • rfc9131.xml
  • README.md
  • CONTRIBUTING.md
  • note-well.md

• rfc9069-AUTH48/issues
• Initial number of issues: 12
• Issue labels:
  • rfced - initial AQ
  • question - follow-on question added to an issue
  • AD approval required - document update requires AD review and approval
  • editor-ready - the editor can update the document and/or close the issue based on issue discussion

AUTH48 started 2021 Oct 18.
Published 2022 Feb 16.

process change: Editor should copy updated XML to inc-work to make sure xml2rfc runs correctly. This will avoid embarrassing formatting mistakes that break the XML. Ultimately, may want to be able to run xml2rfc inside github instance.

candence is different; can't just update the doc to help the authors see the proposed updates; must wait for confirmation before making changes.

this was hybrid process: 2 authors, the doc shepherd, and the AD engaged via github; others just approved at the end via email.

Survey sent 23 Feb 2022 and 8 March 2022.