RPC Wiki

• RPC forked the author's repo and edited the markdown file using PRs per section (38 total PRs).
• Each author query was included as an issue (15 total) - some later became PRs (see next point below).
• An issue was created for each document-wide/global edit to later be incorporated as a PR.
• The (single) author and ISE were invited as a collaborators.
• References were manually handled in XML after other PRs/Issues etc. resolved and markdown--> XML used.

This eleventh experiment is an Independent Stream document (one author, 28 pages, not in a cluster). The ISE sent mail (9/13/2023) requesting that this document be a GitHub experiment, as would be a good candidate to work out ISE processes. The author agreed prior to the document entering the queue.

• Database page
• ARO page
• GitHub repo for the I-D

This experiment involved moving edits from an XML file to a markdown file using github for RFCED and AUTH48. In this experiment, the RPC controls the repo. Both pull requests and issue tracking were used.

• AUTH48 repo for RFC 9518
• forked Mark's repo so it was public to start (i.e., forked repos cannot be set to private)
• Contains:
  • rfc9518.xml
  • README.md
  • CONTRIBUTING.md
  • note-well.md

• draft-nottingham-avoiding-internet-centralization/issues
• Initial number of issuses: 15
• Issue labels:
  • rfced

• AUTH48 started 2023 Dec 6 and ended 2023 Dec 18. This document was published 2023 Dec 18.

• Switching between XML --> Markdown --> XML was confusing and time consuming.
• We only used the rfced label. Didn't know we needed the other labels added at RFCED.
• Using Issues to mention global edits and then PRs to implement them once authors agree.
• We figured out how to update the header/boilerplate to be Independent Submission in markdown. (See header of the markdown file at https://github.com/rfc-editor/draft-nottingham-avoiding-internet-centralization/blob/rpc-main/draft-nottingham-avoiding-internet-centralization.md).

[awaiting reply]