[QualGroup] Add slides and documentation updates after July 2025 sync-up

llvm/docs/GettingInvolved.rst

@@ -208,6 +208,11 @@ what to add to your calendar invite.
      - 3rd Tuesday of the month
      - `ics <https://drive.google.com/file/d/1ten-u-4yjOcCoONUtR4_AxsFxRDTUp1b/view?usp=sharing>`__
      - `Meeting details/agenda: <https://docs.google.com/document/d/1Glzy2JiWuysbD-HBWGUOkZqT09GJ4_Ljodr0lXD5XfQ/edit>`__
+   * - LLVM Qualification Working Group
+     - 1st Tuesday/Wednesday of the month
+     - `ics <https://calendar.google.com/calendar/ical/c_fe5774fa2769c5085d6b87e8fac272e8940e7d0089bc0e0a58dc3ead7978504b%40group.calendar.google.com/public/basic.ics>`__
+       `gcal <https://calendar.google.com/calendar/embed?src=c_fe5774fa2769c5085d6b87e8fac272e8940e7d0089bc0e0a58dc3ead7978504b%40group.calendar.google.com&ctz=Asia%2FTokyo>`__
+     - `Minutes/docs <https://discourse.llvm.org/t/llvm-qualification-wg-sync-ups-meeting-minutes/87148>`__
 
 
 For event owners, our Discord bot also supports sending automated announcements

llvm/docs/QualGroup.rst

@@ -18,7 +18,7 @@ but currently lacks a shared structure to address the specific needs of function
 such as systematic assurance arguments, tool qualification artifacts, and their associated 
 documentation.
 
-An more open, upstream, reusable, and collaborative approach would benefit the wider ecosystem.
+A more open, upstream, reusable, and collaborative approach would benefit the wider ecosystem.
 This group serves as a public forum for those interested in improving LLVM’s suitability for
 use in such environments.
 
@@ -39,22 +39,97 @@ All technical decisions remain subject to the standard LLVM review and governanc
 Participation
 =============
 
-Participation is open to anyone interested. The group currently coordinates via:
+Participation is open to anyone interested. There are several ways to get involved:
 
-* LLVM Discourse (under the "Community" category): https://discourse.llvm.org/
-* Public working sessions and collaborative documents
-* [Details on working sessions will be shared soon on the GettingInvolved page]
-* Informal discussions on the LLVM Community Discord server (channel to be announced)
+* Join discussions on the `LLVM Discourse <https://discourse.llvm.org/>`_ forum, under the "Community" category.
+* Engage in conversations on the LLVM Community Discord in the `#fusa-qual-wg <https://discord.com/channels/636084430946959380/1389362444169773117>`_ channel.
+* 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.
 
-Initial Contributors
-====================
+We welcome contributors from diverse backgrounds, organizations, and experience levels.
 
-The initial participants include community members and industry contributors with experience
-in compiler development, tool qualification, and functional safety. (To be filled in after PR review.)
+Meeting Minutes
+===============
+
+Meeting notes for the LLVM Qualification Working Group are published on the 
+LLVM Discourse forum. These notes provide a summary of topics discussed, 
+decisions made, and next steps. 
+
+You can access all minutes here:
+https://discourse.llvm.org/t/llvm-qualification-wg-sync-ups-meeting-minutes/87148
+
+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.
+
+Presentation Slides
+===================
+
+Slides used to support discussions during sync-up meetings are stored in the
+ `qual-wg/slides/` directory of the LLVM repository.
+
+ Available slides:
+
+* :download:`July 2025 <qual-wg/slides/202507_llvm_qual_wg.pdf>`
+* (add future entries here)
+
+Code of Conduct
+===============
+
+We are committed to fostering a respectful, inclusive, and constructive environment 
+where contributors from diverse backgrounds and organizations can collaborate 
+on qualification-related efforts in the LLVM ecosystem. 
+To support this goal, we adopt the following principles:
+
+Let's Build This Together
+-------------------------
+This is a space for shared ownership and mutual learning. If you're here, you belong. 
+Help us shape a group where trust, technical rigor, and collaboration go hand in hand.
+
+Respect and Inclusion
+---------------------
+* Treat all participants with respect and dignity, regardless of background, experience level, employer, or role in the community.
+* Be welcoming and supportive. We value a diversity of opinions and expertise.
+* Assume good intent, and ask questions before drawing conclusions.
+
+Constructive Collaboration
+--------------------------
+* Keep discussions focused, technical, and solution-oriented.
+* Provide thoughtful, actionable feedback. Avoid sarcasm, dismissive remarks, or personal criticism.
+* Recognize that contributors have different constraints and priorities. Seek alignment, not perfection.
+
+Transparency and Openness
+-------------------------
+* Share relevant information openly to enable others to contribute effectively.
+* Document decisions and rationales so others can understand and build on them.
+* Clearly distinguish between personal opinions, organizational positions, and community consensus.
+
+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.
+
+Safety and Trust
+----------------
+* We aim to build qualification artifacts that others can trust. Similarly, we aim to be trustworthy collaborators.
+* If you see something concerning, speak up respectfully or contact the group organizer(s) privately.
+* We follow the LLVM Community :doc:`Code of Conduct <CodeOfConduct>`, which applies across all official LLVM communication spaces.
 
 Contact
 =======
 
-For more information or to get involved, please refer to the ongoing Discourse thread:
-https://discourse.llvm.org/t/rfc-proposal-to-establish-a-safety-group-in-llvm/86916 
+For more information or to get involved:
 
+* 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.
+* Join the conversation on the LLVM Community Discord in the `#fusa-qual-wg <https://discord.com/channels/636084430946959380/1389362444169773117>`_ channel.

llvm/docs/index.rst

@@ -98,8 +98,7 @@ LLVM welcomes contributions of all kinds. To learn more, see the following artic
 
 * :ref:`report-security-issue`
 
-* :doc:`QualGroup`  
-  LLVM Qualification Group
+* :doc:`QualGroup`
 
 Indices and tables
 ==================