Skip to content

[flang] Reference LLVM RFC process in Flang docs, with caveats #190836

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
AlexisPerry wants to merge 2 commits into
base: main
Choose a base branch
from
+6 −1
Open

[flang] Reference LLVM RFC process in Flang docs, with caveats #190836

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0e17eae
Reference LLVM RFC process in Flang docs, with caveats
AlexisPerry Apr 7, 2026
33bca20
Address reviewer comments - move text location
AlexisPerry Apr 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion flang/docs/GettingInvolved.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Copy link
Copy Markdown
Contributor

@tblah tblah Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 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.

- 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.


[Commits Archive (flang-commits)](http://lists.llvm.org/pipermail/flang-commits)

This list contains all commit messages that are made when Flang developers
Expand Down
Loading