Differences

This shows you the differences between two versions of the page.

--- rpc-github-phase-0-pilot-test [2025/12/16 19:17] – added link jmahoney
+++ rpc-github-phase-0-pilot-test [2026/07/01 17:55] (current) – updated to refer to Final Review instead of auth48 sginoza
@@ Line 1: / Line 1: @@
-====== RPC Pilot Test: AUTH48 in GitHub ======
+====== RPC Pilot Test: Final Review in GitHub ======
-The RFC production Center is modernizing their tools infrastructure and will be using GitHub for version control in 2026 (please see the RPC GitHub roadmap for details). However, before the full solution is rolled out, the RPC intends to offer Phase 0 as a transitional step so we can support those authors that want to use GitHub for AUTH48 sooner. This process will be offered to authors whose documents are entering the RFC Editor Queue starting 1 November 2025
+The RFC production Center is modernizing their tools infrastructure and will be using GitHub for version control in 2026 (please see the [[rpc_github_roadmap|RPC GitHub roadmap]] for details). However, before the full solution is rolled out, the RPC intends to offer [[rpc_github_roadmap#phase_0minimal_github_support_for_auth48_in_progress|Final Review GitHub repos]] on a limited basis as a transitional step so we can support those authors that want to use GitHub for Final Review sooner. This process will be offered to authors whose documents are entering the RFC Editor Queue starting 1 November 2025.
 The goal is to further support the authoring community and facilitate author reviews using tools they are familiar with.
-To start, the RPC will accept at least 5 GitHub AUTH48 requests per month. The RPC will ask authors if they want to participate when their document enters the queue. If so, then RPC will do the following when the document enters AUTH48:
+To start, the RPC will accept at least 5 requests for Final Reviews in GitHub per month. The RPC will ask authors if they want to participate when their document enters the queue. If so, then RPC will do the following when the document enters Final Review:
-  * Create a GitHub repository in the rfc-editor organization
+  * Create a GitHub repository in the rfc-editor-drafts organization
   * Add the approved source file to the repo
   * Add questions regarding the document in the issue tracker
@@ Line 14: / Line 14: @@
 Note that authors can choose to participate in this pilot program and also the [[pilot_test_kramdown_rfc|kramdown-rfc pilot program]].
-Authors will provide feedback using GitHub's review and issue-tracking tools. Once the authors approve changes, the PR will be merged. If the document source is kramdown-rfc, there will be an additional step of approving the RFCXML and output formats.
+Authors will provide feedback on the RFC-to-be using GitHub's review and issue-tracking tools. Once the authors approve changes, the PR will be merged. If the document source is kramdown-rfc, there will be an additional step of approving the RFCXML and output formats. The README will provide further details of the process.
 We expect to pilot this process while our version control solution is being developed. We thank you in advance for your patience while we work through the process kinks.