I mentioned on the call last week that I had had Gemini write up some instructions based on the discussion last week. Here they are for what it's worth:
https://docs.google.com/document/d/1fEUtC9GO7y6h6rIR0ZsRRHsMBT0qq0VO3GlPwc_W-1g/edit?usp=sharing As I said on the call today, I think the minimum viable thing here would be even simpler than that, just replacing the email interface with an interface that is actually designed for editing documents: OLD 1. RPC receives source document 2. Script sends edited document to authors in email 3. Authors respond to email 4. RPC copies document from email to RPC system NEW 1. RPC receives source document 2. RPC initializes GitHub repo with source document 3. Script sends edited document to authors in email (authors can ignore) 4. RPC copies edited document to Github repo, makes a PR, emails authors link to PR 5. Authors review PR; RPC merges 6. RPC copies document from Github repo to RPC system That seems like a workflow you could deploy this afternoon. It has a couple of manual steps, but they would take roughly 5 minutes more per AUTH48, and you could document them in less than two pages of git commands and GitHub screenshots. Hope that helps, --Richard
_______________________________________________ rfc-interest mailing list -- [email protected] To unsubscribe send an email to [email protected]
