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

[Tarun Prabhu 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.
+-   Ideally, if the RFC is discussed on a community call, reference the meeting notes directly in the summary comment, whether to indicate that a decision was reached or simply to point to the relevant discussion. 
----------------
tarunprabhu wrote:

I would be tempted to ask for a more "customized" summary than simply referencing the meeting notes. The meeting notes don't usually capture all the details of the discussions. But these details are often very relevant in a detailed discussion. We have contributors who cannot attend the calls, so this would be very useful for them.

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