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

[Alexis Perry-Holby via flang-commits]

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

>From 0e17eae1e9c7808f9e86aa76e2842c7af4e03637 Mon Sep 17 00:00:00 2001
From: AlexisPerry <aperry at lanl.gov>
Date: Tue, 7 Apr 2026 13:45:48 -0600
Subject: [PATCH 1/2] Reference LLVM RFC process in Flang docs, with caveats

---
 flang/docs/GettingInvolved.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/flang/docs/GettingInvolved.md b/flang/docs/GettingInvolved.md
index 1b8fc1df3a58e..e07f1941e55f5 100644
--- a/flang/docs/GettingInvolved.md
+++ b/flang/docs/GettingInvolved.md
@@ -28,6 +28,10 @@ Contributions to Flang are done using GitHub Pull Requests and follow the
 
   Flang forums are for technical discussions, questions about writing code for, or using Flang tools.
 
+  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. 
+-   If the RFC results in a pull request (or series thereof), the author should provide a link to it in the RFC discussion.
 
 [Commits Archive (flang-commits)](http://lists.llvm.org/pipermail/flang-commits)
 

>From 33bca20dd4883edbec840542f88a34a3a0d719c6 Mon Sep 17 00:00:00 2001
From: AlexisPerry <aperry at lanl.gov>
Date: Tue, 7 Apr 2026 14:25:41 -0600
Subject: [PATCH 2/2] Address reviewer comments - move text location

---
 flang/docs/GettingInvolved.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/flang/docs/GettingInvolved.md b/flang/docs/GettingInvolved.md
index e07f1941e55f5..5b57030b6e86a 100644
--- a/flang/docs/GettingInvolved.md
+++ b/flang/docs/GettingInvolved.md
@@ -22,17 +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. 
+-   If the RFC results in a pull request (or series thereof), the author should provide a link to it in the RFC discussion.
+
+
 ## Forum and Mailing Lists
 
 [Forum](https://discourse.llvm.org/c/subprojects/flang)
 
   Flang forums are for technical discussions, questions about writing code for, or using Flang tools.
 
-  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. 
--   If the RFC results in a pull request (or series thereof), the author should provide a link to it in the RFC discussion.
-
 [Commits Archive (flang-commits)](http://lists.llvm.org/pipermail/flang-commits)
 
   This list contains all commit messages that are made when Flang developers