[flang-commits] [flang] [flang] Reference LLVM RFC process in Flang docs, with caveats (PR #190836)

[Alexis Perry-Holby via flang-commits]

================
@@ -22,13 +22,18 @@ To understand the status of various developments in Flang please join the respec
 Contributions to Flang are done using GitHub Pull Requests and follow the
 [LLVM contribution process](https://llvm.org/docs/Contributing.html).
 
+In the case of proposing substantive changes to either the Flang codebase or community practices, please follow the LLVM [Request for Comment (RFC) process](https://llvm.org/docs/RFCProcess.html) with the following caveats:
+-   Currently, there is no Flang Area Team to facilitate decision making. The present best practice is for the RFC author to periodically summarize the discussion to date, clearly state the apparent next steps, and list any outstanding questions needing resolution. If a rough consensus has been reached, please indicate this in the summary comment.
----------------
AlexisPerry wrote:

I put in the part about periodic summaries mostly because I have found it helpful when the discussion has gone on for a bit and there have been a lot of contributions (admittedly, fuzzy numbers there).  It's also a good way to get an RFC un-stuck, particularly the part about listing apparent next steps as it gives the commenters something concrete to agree with or object to.

https://github.com/llvm/llvm-project/pull/190836