[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'm fine with just referring to the "combined" call as the "community" call going forward and replacing any references to "combined" with something else. 

The point here was to make it clear what we are referring to when we say "community call". This document is intended for (relative) newcomers, who probably don't have as much context, so providing examples just makes it easier. We could include links to the non-flang calls in the examples as well.

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