====== GitHub AUTH48 Experiment: RFC 8829 ====== ==== High-Level Summary ==== * The existing document repo (https://github.com/rtcweb-wg/jsep) was used: * The authors committed to a new branch (rfced) the XML files provided at the beginning of AUTH48 (both rfc8829.form.xml and rfc8829.xml but renamed draft-ietf-rtcweb-jsep.* to match previous file naming convention). * The authors created an issue from each AQ. 78 issues were raised. * Workflow: * Authors provided feedback on each issue. * When done with an issue, the authors marked it with a label to note it was ready and then assigned it to the editor. * The editor, who was added as a contributor to the repo, created a branch off the rfced branch, made updates, and submitted PRs to close the assigned issues. ==== Work Flow ==== The authors and editor agreed to use the GitHub Pull Request work flow: - The authors answer the AQ in the comments of the issue (e.g., see comments for [[https://github.com/rtcweb-wg/jsep/issues/922|#922]]). - The authors indicate that an issue is ready for editor attention by labeling the issue "editor-ready" and assigning the issue to the editor. - The editor creates a branch off the rfced branch to address the issue. - The editor makes edits in that branch. - The editor commits changes. - The editor creates a Pull Request (PR) to submit the changes to the repo (e.g., [[https://github.com/rtcweb-wg/jsep/pull/997|PR #997]]). - The authors review the PR: - If the PR is accepted, the authors merge the changes to the rfced branch, which closes the issue. - If the PR is rejected, the editor makes changes to the current branch and resubmits the PR. - Repeat for the other issues. The authors and the editor set up notifications so that many of these steps automatically generated emails to involved parties (assigning/commenting on issues, use of @mentions, creating/accepting/rejecting PRs). 766 messages were generated during AUTH48. ==== Feedback ==== * See [[github_exp_2021_feedback]].