diff --git a/llvm/docs/QualGroup.rst b/llvm/docs/QualGroup.rst index cf0e0aa57a20f..5cf07607dbb4f 100644 --- a/llvm/docs/QualGroup.rst +++ b/llvm/docs/QualGroup.rst @@ -36,23 +36,146 @@ The Qualification Group aims to: The group is non-enforcing and does not control any part of the codebase. All technical decisions remain subject to the standard LLVM review and governance process. +Group Composition +================= + +Group Members +------------- + +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. +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. + +.. list-table:: + :widths: 20 20 20 20 20 + :header-rows: 1 + + * - Name + - Affiliation + - Discourse handle + - Discord handle + - GitHub handle + * - Alan Phipps + - Texas Instruments + - evodius96 + - \- + - evodius96 + * - Carlos Andrés Ramírez + - Woven by Toyota + - CarlosAndresRamirez + - carlos\_andres\_ramirez + - CarlosAndresRamirez + * - Davide Cunial + - BMW A.G. + - capitan-davide + - capitan_davide + - capitan-davide + * - Oscar Slotosch + - Validas + - slotosch + - oscarslotosch_66740 + - \- + * - Petar Jovanovic + - HTECH + - petarj + - petarjovanovic_18635 + - petar-jovanovic + * - Petter Berntsson + - Arm Limited + - petbernt + - petbernt + - petbernt + * - Wendi Urribarri + - Woven by Toyota + - uwendi + - uwendi + - uwendi + * - YoungJun Lee + - NSHC + - YoungJunLee + - YoungJunLee + - IamYJLee + + +Organizations are limited to three representatives within the group to maintain diversity. + Participation -============= +------------- -Participation is open to anyone interested. There are several ways to get involved: +There are several ways to participate: * Join discussions on the `LLVM Discourse `_ forum, under the "Community" category. -* Engage in conversations on the LLVM Community Discord in the `#fusa-qual-wg `_ channel. +* Engage in conversations on the LLVM Community Discord in the `#fusa-qual-wg `_ channel. Note: You need to join the community's `Discord chat server `_ first. * Join our monthly sync-up calls. Details on working sessions and meeting minutes are shared on the :doc:`GettingInvolved` page. * Contribute ideas, feedback, or patches via GitHub, Discourse, or directly in working documents. -We welcome contributors from diverse backgrounds, organizations, and experience levels. +Contribution Principles +----------------------- + +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: + +* **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. +* **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. +* **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. +* **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. + +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: + +* Regular participation in meetings or asynchronous discussions. +* Contributions to qualification artifacts, methodologies, or documentation. +* Active involvement in at least one qualification-related task over the past year. + +Membership Criteria +------------------- + +Membership in the LLVM Qualification Group is intended for individuals with relevant experience or active engagement in qualification-related efforts. Categories include: + +**Individual Contributors** + + * Experience in software/tool qualification (e.g., reliability, quality, safety, security); OR + * Active involvement in LLVM-related qualification efforts; OR + * Significant LLVM contributions related to qualification in the past year (code, discussion, resolving related challenges). + +**Researchers** + + * Active research, publication, or development of methodologies, frameworks, or tools aimed at improving LLVM quality and reliability. + +**Vendor Contacts** + + * Represent organizations building or using LLVM-based tools in safety-critical environments; OR + * Require involvement due to organizational role in qualification or compliance. + +Nomination Process +------------------ + +Individuals may nominate themselves or be nominated by an existing member. Nominations should: + +* Explain the nominee’s background and relevance to qualification efforts. +* Be submitted via this form: `Participant Introduction & Membership `_ +* Be communicated to an active LLVM Qualification Group member (e.g., on the Discord channel). + +Nominations are discussed within the group. If consensus is reached, the nominee is accepted. Otherwise, a majority vote will decide. + +Membership Review +----------------- + +To ensure the group remains active and focused, member participation will be reviewed every six months. Inactive members may be removed following this review. + +Current Topics & Backlog +======================== + +Our working group is actively engaged in discussions about the project's +direction and tackling technical challenges. You can find our current +discussions, challenges, and the project backlog in the following +document: `Backlog `_ + +This document serves as our central hub for all ongoing topics and will +be updated regularly to reflect our progress. We welcome your +contributions and feedback. Meeting Materials ================= -Agendas, meeting notes, and presentation slides for the LLVM Qualification Working Group sync-ups -are shared to ensure transparency and continuity. +Agendas, meeting notes, and presentation slides for the sync-ups are shared to ensure transparency and continuity. Upcoming and past meeting agendas, and meeting minutes are published in a dedicated thread on the LLVM Discourse forum: `Meeting Agendas and Minutes `_ @@ -60,27 +183,15 @@ on the LLVM Discourse forum: `Meeting Agendas and Minutes `_ -* `August 2025 <../qual-wg/slides/202508_llvm_qual_wg.pdf>`_ -* `July 2025 <../qual-wg/slides/202507_llvm_qual_wg.pdf>`_ + +* `September 2025 `_ +* `August 2025 `_ +* `July 2025 `_ * (add future entries here) -A future patch will migrate these slide files to the `llvm-www` repository, once +Note: A future patch will migrate these slide files to the `llvm-www` repository, once a suitable hosting location is confirmed with the community. -Contributors -============ - -The LLVM Qualification Working Group is a collaborative effort involving participants -from across the LLVM ecosystem. These include community members and industry contributors -with experience in compiler development, tool qualification, and functional safety. - -While contributor names are recorded in the meeting minutes for those who attend -sync-up calls, we also recognize contributions made asynchronously via Discord, GitHub, -and other discussion channels. - -All forms of constructive participation are valued and acknowledged. - Code of Conduct =============== @@ -115,6 +226,7 @@ Transparency and Openness Unacceptable Behavior --------------------- We will not tolerate: + * Harassment, discrimination, or exclusionary behavior. * Disruptive conduct in meetings or communication channels. * Using this group for marketing, lobbying, or promoting non-collaborative commercial agendas.