You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[QualGroup] Add slides and documentation updates after July 2025 sync-up (#147196)
This patch updates the Qualification Working Group documentation with
improvements based on our first sync-up meeting in July 2025:
- Added July 2025 meeting slides to `qual-wg/slides/`
- Updated Participation section to include clickable links to Discourse
and Discord
- Clarified contributor recognition to include async contributors
- Added new sections for Meeting Minutes and Presentation Slides
- Linked to the initial RFC and Discord channel in the Contact section
- Added Code of Conduct section
- Minor formatting consistency fixes across the document
This change also updates `GettingInvolved.rst` to add the Qualification
WG with calendar links and Discourse minutes.
These updates aim to improve clarity, traceability, and contributor
onboarding.
---------
Co-authored-by: Wendi Urribarri (Woven by Toyota <wendi.urribarri@woven-planet.global>
Copy file name to clipboardExpand all lines: llvm/docs/QualGroup.rst
+87-12Lines changed: 87 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ but currently lacks a shared structure to address the specific needs of function
18
18
such as systematic assurance arguments, tool qualification artifacts, and their associated
19
19
documentation.
20
20
21
-
An more open, upstream, reusable, and collaborative approach would benefit the wider ecosystem.
21
+
A more open, upstream, reusable, and collaborative approach would benefit the wider ecosystem.
22
22
This group serves as a public forum for those interested in improving LLVM’s suitability for
23
23
use in such environments.
24
24
@@ -39,22 +39,97 @@ All technical decisions remain subject to the standard LLVM review and governanc
39
39
Participation
40
40
=============
41
41
42
-
Participation is open to anyone interested. The group currently coordinates via:
42
+
Participation is open to anyone interested. There are several ways to get involved:
43
43
44
-
* LLVM Discourse (under the "Community" category): https://discourse.llvm.org/
45
-
* Public working sessions and collaborative documents
46
-
* [Details on working sessions will be shared soon on the GettingInvolved page]
47
-
* Informal discussions on the LLVM Community Discord server (channel to be announced)
44
+
* Join discussions on the `LLVM Discourse <https://discourse.llvm.org/>`_ forum, under the "Community" category.
45
+
* Engage in conversations on the LLVM Community Discord in the `#fusa-qual-wg <https://discord.com/channels/636084430946959380/1389362444169773117>`_ channel.
46
+
* Join our monthly sync-up calls. Details on working sessions and meeting minutes are shared on the :doc:`GettingInvolved` page.
47
+
* Contribute ideas, feedback, or patches via GitHub, Discourse, or directly in working documents.
48
48
49
-
Initial Contributors
50
-
====================
49
+
We welcome contributors from diverse backgrounds, organizations, and experience levels.
51
50
52
-
The initial participants include community members and industry contributors with experience
53
-
in compiler development, tool qualification, and functional safety. (To be filled in after PR review.)
51
+
Meeting Minutes
52
+
===============
53
+
54
+
Meeting notes for the LLVM Qualification Working Group are published on the
55
+
LLVM Discourse forum. These notes provide a summary of topics discussed,
* Refer to our initial `RFC: Proposal to Establish a Safety Group in LLVM <https://discourse.llvm.org/t/rfc-proposal-to-establish-a-safety-group-in-llvm/86916>`_ on the LLVM Discourse forum.
135
+
* Join the conversation on the LLVM Community Discord in the `#fusa-qual-wg <https://discord.com/channels/636084430946959380/1389362444169773117>`_ channel.
0 commit comments