On Jan 12, 2026, at 14:30, Rebecca VanRheenen <[email protected]> wrote: > > Hi Paul, > > Thanks for your feedback and the set of questions below. It helps us > understand where clarification in the processing instructions are needed. > > >> https://www.rfc-editor.org/rpc/wiki/doku.php?id=rpc-github-phase-0-pilot-test2 >> says: >> >> 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. >> >> - How are we meant to use the review tools? I assume that we are not >> expected to leave a comment for every red-green pair in >> https://github.com/rfc-editor/AUTH48-rfc9920/pull/1/files >> Do we just put in comments for the ones where we have questions? If so, how >> do you know when we are finished? How do we know when the RPC has agreed or >> disagreed with every comment that we do make? > > We do not expect you to leave a comment for every instance of change. We > imagined authors would include comments for any additional changes needed > (e.g., if you disagree with a change or want to make additional changes) or > submit additional PRs as needed, ideally against the RPC-edits branch.
Excellent, thanks. I did not get the feeling that the second option was allowed. We'll go with it because it makes the "we did this; please do that" much clearer, and follows the current AUTH48 communication model much better. > The RPC would use comments to discuss any issues, as needed. You can send us > an email when you have finished your review, and we will then respond to any > comments. We'll email when we have a pull request that is our next step, each time that happens. >> - Do we authors close issues where there is no action needed, or does the >> RPC? > > The RPC will close the issues as they are resolved. That's good to know; I think that's the right model. And if authors close the issues, it is reasonable of you to re-open them just so that you can close them yourself. Some would find that passive-agressive, but I think the right model is "the RPC is responsible for issue lifecycle". --Paul Hoffman -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
