Differences

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

--- rpc_github_roadmap [2026/08/03 18:41] – added link to interim mtg where the roadmap was discussed jmahoney
+++ rpc_github_roadmap [2026/08/20 19:20] (current) – Added an FAQ jmahoney
@@ Line 127: / Line 127: @@
 Estimated rollout timeframe: Fall 2026
+===== Frequently Asked Questions =====
+**Q:** Why doesn't the RPC fork the working group's repo?
+**A:** The use of GitHub and its features is not consistent across working groups. A working group may not even have a GitHub repo. Some working groups place all their drafts in one repo, others construct repos for each document. Some working groups use repos that belong to the authors. Working groups will differ in their processes and how they use GitHub features. For example, some repos use actions, some don't. The RPC cannot know the status and processes for each repo that has been used for the documents that have entered the RFC Editor queue.
+**Q:** But isn't the RPC's repo redundant with the document's repo?
+**A:** The RPC's repos are separate from the document's working repo. The RPC's repos support the RPC's editing and publication work. Each RPC repo contains configurations for editing tools and files that support integration with the queue management system and publication automation. When an RFC is published, the repo serves as the archive of the published files.
 ----