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

[Tom Eccles 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.
----------------
tblah wrote:

Maybe we should discuss this as a community, but my assumption was always that in the absence of an area team, maintainers make decisions in their area and the [lead maintainers](https://github.com/llvm/llvm-project/blob/main/flang/Maintainers.md#lead-maintainers) have the final say in anything contested. If others agree, perhaps we should link to `Maintainers.md` here.

As a maintainer I am happy to be pinged on any relevant RFCs that I have missed.

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