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
This patch updates the LLVM Qualification Group documentation to reflect
current group structure and practices:
- Restructures the **Group Composition** section (previously
"Participation" + "Contributors")
- Adds a formal **member table** with affiliations and community handles
- Introduces **participation principles**
- Documents **membership criteria**, **nomination process**, and
**review cycle**
- Corrects references to **meeting materials** (wrong path)
These changes aim to improve clarity, inclusiveness, and alignment with
similar working groups (e.g., LLVM Security Response Team).
---------
Co-authored-by: Wendi Urribarri (Woven by Toyota <wendi.urribarri@woven-planet.global>
@@ -41,17 +41,141 @@ The Qualification Group aims to:
41
41
The group is non-enforcing and does not control any part of the codebase.
42
42
All technical decisions remain subject to the standard LLVM review and governance process.
43
43
44
+
Group Composition
45
+
=================
46
+
47
+
Group Members
48
+
-------------
49
+
50
+
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.
51
+
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.
52
+
53
+
.. list-table::
54
+
:widths: 20 20 20 20 20
55
+
:header-rows: 1
56
+
57
+
* - Name
58
+
- Affiliation
59
+
- Discourse handle
60
+
- Discord handle
61
+
- GitHub handle
62
+
* - Alan Phipps
63
+
- Texas Instruments
64
+
- evodius96
65
+
- \-
66
+
- evodius96
67
+
* - Carlos Andrés Ramírez
68
+
- Woven by Toyota
69
+
- CarlosAndresRamirez
70
+
- carlos\_andres\_ramirez
71
+
- CarlosAndresRamirez
72
+
* - Davide Cunial
73
+
- BMW A.G.
74
+
- capitan-davide
75
+
- capitan_davide
76
+
- capitan-davide
77
+
* - Oscar Slotosch
78
+
- Validas
79
+
- slotosch
80
+
- oscarslotosch_66740
81
+
- \-
82
+
* - Petar Jovanovic
83
+
- HTECH
84
+
- petarj
85
+
- petarjovanovic_18635
86
+
- petar-jovanovic
87
+
* - Petter Berntsson
88
+
- Arm Limited
89
+
- petbernt
90
+
- petbernt
91
+
- petbernt
92
+
* - Wendi Urribarri
93
+
- Woven by Toyota
94
+
- uwendi
95
+
- uwendi
96
+
- uwendi
97
+
* - YoungJun Lee
98
+
- NSHC
99
+
- YoungJunLee
100
+
- YoungJunLee
101
+
- IamYJLee
102
+
103
+
104
+
Organizations are limited to three representatives within the group to maintain diversity.
105
+
44
106
Participation
45
-
=============
107
+
-------------
46
108
47
-
Participation is open to anyone interested. There are several ways to get involved:
109
+
There are several ways to participate:
48
110
49
111
* Join discussions on the `LLVM Discourse <https://discourse.llvm.org/>`_ forum, under the "Community" category.
50
-
* Engage in conversations on the LLVM Community Discord in the `#fusa-qual-wg <https://discord.com/channels/636084430946959380/1389362444169773117>`_ channel.
112
+
* 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.
51
113
* Join our monthly sync-up calls. Details on working sessions and meeting minutes are shared on the :doc:`GettingInvolved` page.
52
114
* Contribute ideas, feedback, or patches via GitHub, Discourse, or directly in working documents.
53
115
54
-
We welcome contributors from diverse backgrounds, organizations, and experience levels.
116
+
Contribution Principles
117
+
-----------------------
118
+
119
+
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:
120
+
121
+
* **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.
122
+
* **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.
123
+
* **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.
124
+
* **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.
125
+
126
+
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:
127
+
128
+
* Regular participation in meetings or asynchronous discussions.
129
+
* Contributions to qualification artifacts, methodologies, or documentation.
130
+
* Active involvement in at least one qualification-related task over the past year.
131
+
132
+
Membership Criteria
133
+
-------------------
134
+
135
+
Membership in the LLVM Qualification Group is intended for individuals with relevant experience or active engagement in qualification-related efforts. Categories include:
136
+
137
+
**Individual Contributors**
138
+
139
+
* Experience in software/tool qualification (e.g., reliability, quality, safety, security); OR
140
+
* Active involvement in LLVM-related qualification efforts; OR
141
+
* Significant LLVM contributions related to qualification in the past year (code, discussion, resolving related challenges).
142
+
143
+
**Researchers**
144
+
145
+
* Active research, publication, or development of methodologies, frameworks, or tools aimed at improving LLVM quality and reliability.
146
+
147
+
**Vendor Contacts**
148
+
149
+
* Represent organizations building or using LLVM-based tools in safety-critical environments; OR
150
+
* Require involvement due to organizational role in qualification or compliance.
151
+
152
+
Nomination Process
153
+
------------------
154
+
155
+
Individuals may nominate themselves or be nominated by an existing member. Nominations should:
156
+
157
+
* Explain the nominee’s background and relevance to qualification efforts.
158
+
* Be submitted via this form: `Participant Introduction & Membership <https://forms.gle/cE1kHjqkKNtafUrD7>`_
159
+
* Be communicated to an active LLVM Qualification Group member (e.g., on the Discord channel).
160
+
161
+
Nominations are discussed within the group. If consensus is reached, the nominee is accepted. Otherwise, a majority vote will decide.
162
+
163
+
Membership Review
164
+
-----------------
165
+
166
+
To ensure the group remains active and focused, member participation will be reviewed every six months. Inactive members may be removed following this review.
167
+
168
+
Current Topics & Backlog
169
+
========================
170
+
171
+
Our working group is actively engaged in discussions about the project's
172
+
direction and tackling technical challenges. You can find our current
173
+
discussions, challenges, and the project backlog in the following
0 commit comments