Skip to content

Commit 5918d3f

Browse files
author
Wendi Urribarri (Woven by Toyota
committed
Refactor QualGroup.rst: add membership rules, restructure contributors section
1 parent 1d2229f commit 5918d3f

File tree

1 file changed

+122
-21
lines changed

1 file changed

+122
-21
lines changed

llvm/docs/QualGroup.rst

Lines changed: 122 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -36,17 +36,129 @@ The Qualification Group aims to:
3636
The group is non-enforcing and does not control any part of the codebase.
3737
All technical decisions remain subject to the standard LLVM review and governance process.
3838

39+
Group Composition
40+
=================
41+
42+
Group Members
43+
-------------
44+
45+
The members of the LLVM Qualification Group represent a diverse cross-section of the LLVM community, including individual contributors, researchers, vendor representatives, and experts in the field of software qualification, including reliability, quality, safety, and/or security.
46+
They meet the criteria for inclusion below. Knowing their handles help us keep track of who’s who across platforms, coordinate activities, and recognize contributions.
47+
48+
.. list-table:: Group Members
49+
:widths: 20 20 20 20 20
50+
:header-rows: 1
51+
52+
* - Name
53+
- Affiliation
54+
- Discourse handle
55+
- Discord handle
56+
- GitHub handle
57+
* - Alan Phipps
58+
- Texas Instruments
59+
- evodius96
60+
- -
61+
- evodius96
62+
* - Carlos Andrés Ramírez
63+
- Woven by Toyota
64+
- CarlosAndresRamirez
65+
- -
66+
- CarlosAndresRamirez
67+
* - Davide Cunial
68+
- BMW A.G.
69+
- capitan-davide
70+
- capitan_davide
71+
- capitan-davide
72+
* - Oscar Slotosch
73+
- Validas
74+
- slotosch
75+
- oscarslotosch_66740
76+
- -
77+
* - Petar Jovanovic
78+
- HTECH
79+
- petarj
80+
- petarjovanovic_18635
81+
- petar-jovanovic
82+
* - Petter Berntsson
83+
- Arm Limited
84+
- petbernt
85+
- petbernt
86+
- petbernt
87+
* - Wendi Urribarri
88+
- Woven by Toyota
89+
- uwendi
90+
- uwendi
91+
- uwendi
92+
* - YoungJun Lee
93+
- NSHC
94+
- YoungJunLee
95+
- YoungJunLee
96+
- IamYJLee
97+
98+
99+
Organizations are limited to three representatives within the group to maintain diversity.
100+
39101
Participation
40-
=============
102+
-------------
41103

42-
Participation is open to anyone interested. There are several ways to get involved:
104+
There are several ways to participate:
43105

44106
* 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.
107+
* Engage in conversations on the LLVM Community Discord in the `#fusa-qual-wg <https://discord.com/channels/636084430946959380/1389362444169773117>`_ channel. Note: You need to join the community's `Discord chat server <https://llvm.org/docs/GettingInvolved.html#discord>`_ first.
46108
* Join our monthly sync-up calls. Details on working sessions and meeting minutes are shared on the :doc:`GettingInvolved` page.
47109
* Contribute ideas, feedback, or patches via GitHub, Discourse, or directly in working documents.
48110

49-
We welcome contributors from diverse backgrounds, organizations, and experience levels.
111+
Contribution Principles
112+
-----------------------
113+
114+
We understand that most members contribute in a limited capacity due to their primary responsibilities. This initiative is volunteer-driven, and we operate with the following shared principles:
115+
116+
* **Acknowledgement of limited bandwidth:** We recognize that no one is working full-time on this group, and participation will vary based on individual availability and priorities.
117+
* **Small and consistent contributions are valuable:** We believe that steady ongoing contributions, even if minimal, are crucial for long-term success, as long as there is coordination and respect for each other's time. Even small contributions (e.g., a few hours per month) can significantly advance the group's goals and have an impact.
118+
* **Realistic progress expectations:** Given the voluntary nature and no full-time involvement, we expect our progress to be slow. This group was initiated in July 2025. Concrete outcomes in 1-2 years would be considered excellent for this type of cross-company and voluntary collaboration.
119+
* **Respect for differing capacities:** We value every member’s engagement, whether large or small, often or sporadically, as it all contributes to the overall effort. Even contributions that may seem small, such as sharing an idea or pointing out a relevant resource, are meaningful and important.
120+
121+
However, we need a balance between flexibility, structure, and enough organization to move forward together. Members are expected to remain engaged through one or more of the following:
122+
123+
* Regular participation in meetings or asynchronous discussions.
124+
* Contributions to qualification artifacts, methodologies, or documentation.
125+
* Active involvement in at least one qualification-related task over the past year.
126+
127+
Membership Criteria
128+
-------------------
129+
130+
Membership in the LLVM Qualification Group is intended for individuals with relevant experience or active engagement in qualification-related efforts. Categories include:
131+
132+
**Individual Contributors**
133+
134+
* Experience in software/tool qualification (e.g., reliability, quality, safety, security); OR
135+
* Active involvement in LLVM-related qualification efforts; OR
136+
* Significant LLVM contributions related to qualification in the past year (code, discussion, resolving related challenges).
137+
138+
**Researchers**
139+
140+
* Active research, publication, or development of methodologies, frameworks, or tools aimed at improving LLVM quality and reliability.
141+
142+
**Vendor Contacts**
143+
144+
* Represent organizations building or using LLVM-based tools in safety-critical environments; OR
145+
* Require involvement due to organizational role in qualification or compliance.
146+
147+
Nomination Process
148+
------------------
149+
150+
Individuals may nominate themselves or be nominated by an existing member. Nominations should:
151+
152+
* Explain the nominee’s background and relevance to qualification efforts.
153+
* Be submitted via this form: `Participant Introduction & Membership <https://forms.gle/cE1kHjqkKNtafUrD7>`_
154+
* Be communicated to an active LLVM Qualification Group member (e.g., on the Discord channel).
155+
156+
Nominations are discussed within the group. If consensus is reached, the nominee is accepted. Otherwise, a majority vote will decide.
157+
158+
Membership Review
159+
-----------------
160+
161+
To ensure the group remains active and focused, member participation will be reviewed every six months. Inactive members may be removed following this review.
50162

51163
Meeting Materials
52164
=================
@@ -60,27 +172,15 @@ on the LLVM Discourse forum: `Meeting Agendas and Minutes <https://discourse.llv
60172
Slides used to support discussions during sync-up meetings are stored in LLVM's GitHub repository.
61173

62174
Available slides:
63-
* `September 2025 <../qual-wg/slides/202509_llvm_qual_wg.pdf>`_
64-
* `August 2025 <../qual-wg/slides/202508_llvm_qual_wg.pdf>`_
65-
* `July 2025 <../qual-wg/slides/202507_llvm_qual_wg.pdf>`_
175+
176+
* `September 2025 <qual-wg/slides/202509_llvm_qual_wg.pdf>`_
177+
* `August 2025 <qual-wg/slides/202508_llvm_qual_wg.pdf>`_
178+
* `July 2025 <qual-wg/slides/202507_llvm_qual_wg.pdf>`_
66179
* (add future entries here)
67180

68-
A future patch will migrate these slide files to the `llvm-www` repository, once
181+
Note: A future patch will migrate these slide files to the `llvm-www` repository, once
69182
a suitable hosting location is confirmed with the community.
70183

71-
Contributors
72-
============
73-
74-
The LLVM Qualification Working Group is a collaborative effort involving participants
75-
from across the LLVM ecosystem. These include community members and industry contributors
76-
with experience in compiler development, tool qualification, and functional safety.
77-
78-
While contributor names are recorded in the meeting minutes for those who attend
79-
sync-up calls, we also recognize contributions made asynchronously via Discord, GitHub,
80-
and other discussion channels.
81-
82-
All forms of constructive participation are valued and acknowledged.
83-
84184
Code of Conduct
85185
===============
86186

@@ -115,6 +215,7 @@ Transparency and Openness
115215
Unacceptable Behavior
116216
---------------------
117217
We will not tolerate:
218+
118219
* Harassment, discrimination, or exclusionary behavior.
119220
* Disruptive conduct in meetings or communication channels.
120221
* Using this group for marketing, lobbying, or promoting non-collaborative commercial agendas.

0 commit comments

Comments
 (0)