I just realized I do have permission to close issues, although the readme says that the RPC will close the issues. Please clarify whether you expect the editors to close issues or if we should avoid closing them, in particular the "FYI" ones. Thanks!
On Fri, Jul 17, 2026 at 3:54 PM Aaron Parecki <[email protected]> wrote: > Thank you. I just accepted the invitation, although I don't appear to have > edit access to the repo. Is that intentional? It is fine with me to work > via pull requests. > > > On Fri, Jul 17, 2026 at 3:42 PM Alanna Paloma < > [email protected]> wrote: > >> Hi Authors, >> >> Thank you for sending over the usernames. >> >> We have just sent invitations to each of you. Please accept those >> invitations to join the repo as collaborators. >> >> Best regards, >> Alanna Paloma >> RFC Production Center >> >> > On Jul 17, 2026, at 3:35 PM, Aaron Parecki <aaron= >> [email protected]> wrote: >> > >> > Thank you. Here are the authors' GitHub handles: >> > >> > aaronpk >> > philippederyck >> > dwaite >> > >> > >> > >> > On Fri, Jul 17, 2026 at 3:31 PM <[email protected]> wrote: >> > *****IMPORTANT***** >> > >> > RFC Author(s): >> > -------------- >> > >> > Your document has now entered Final Review (previously AUTH48). >> > >> > The document was edited in kramdown-rfc as part of the RPC pilot test >> (see >> > https://www.rfc-editor.org/rpc/wiki/doku.php?id=pilot_test_kramdown_rfc >> ). >> > >> > Final Review is being handled in GitHub as part of the GitHub pilot test >> > (see >> https://www.rfc-editor.org/rpc/wiki/doku.php?id=rpc-github-phase-0-pilot-test). >> >> > >> > Your document is available for review at: >> > https://github.com/rfc-editor-drafts/FinalReview-rfc10017 >> > >> > Please do the following: >> > >> > a) provide your GitHub username so that we can send you an invite to >> join >> > the repo as a collaborator. We can also send an invite to Hannes >> Tschofenig >> > (WG Chair). We have already added Deb Cooley (AD) and Rifaat >> Shekh-Yusef >> > (Document Shepherd and WG Chair) >> > >> > b) see the README for details on the Final Review process: >> > >> https://github.com/rfc-editor-drafts/FinalReview-rfc10017/blob/Approved/README.md >> > >> > c) review the edits in the RPC-edits pull request: >> > https://github.com/rfc-editor-drafts/FinalReview-rfc10017/pulls >> > >> > d) address the issues: >> > https://github.com/rfc-editor-drafts/FinalReview-rfc10017/issues >> > >> > Once the content of the .md file is stable, we will convert it to .xml >> > and provide the .html, .pdf, .txt, and .xml files for review. >> > >> > You and your coauthors are responsible for engaging other parties >> > (e.g., Contributors or Working Group) as necessary before providing >> > your approval. >> > >> > Once the document has been reviewed and approved by all of the authors, >> > it will be published as an RFC. If an author is no longer available, >> > there are several remedies; see the Unavailable Authors section >> > (https://authors.ietf.org/rfc-publication-process#unavailable-authors). >> > >> > Details on the status of your Final Review are here: >> > https://queue.rfc-editor.org/final-review/rfc10017/ >> > >> > Please let us know if you have any questions. >> > >> > Thank you for your cooperation, >> > >> > RFC Production Center >> > >> > -------------------------------------- >> > RFC 10017 (draft-ietf-oauth-browser-based-apps) >> > >> > Title : OAuth 2.0 for Browser-Based Applications >> > Author(s) : A. Parecki, >> > P. Ryck, >> > D. Waite >> > WG Chair(s) : Hannes Tschofenig, Rifaat Shekh-Yusef >> > Area Director(s) : Deb Cooley, Christopher Inacio >> >>
-- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
