openmainframeproject · jmertic · May 19, 2026 · May 19, 2026 · May 19, 2026 · May 19, 2026
diff --git a/THIRD_PARTY.md b/THIRD_PARTY.md
@@ -1,4 +1,4 @@
-The below files are from the [sorTable.js](https://github.com/beatdjam/sorTable.js/tree/5628bb6906bf096a1bed8ed11a22868989acbacfs) and licensed under the [MIT License](https://github.com/beatdjam/sorTable.js/blob/5628bb6906bf096a1bed8ed11a22868989acbacf/LICENSE)
+The below files are from the [sorTable.js](https://github.com/beatdjam/sorTable.js/tree/5628bb6906bf096a1bed8ed11a22868989acbacf) and licensed under the [MIT License](https://github.com/beatdjam/sorTable.js/blob/5628bb6906bf096a1bed8ed11a22868989acbacf/LICENSE)
 
 - [css/img/asc.png](css/img/asc.png)
 - [css/img/bg.png](css/img/bg.png)

diff --git a/_config.yml b/_config.yml
@@ -3,14 +3,15 @@ description: Materials and processes for the Open Mainframe Project TAC
 logo: "https://artwork.openmainframeproject.org/other/open-mainframe-project/horizontal/color/open-mainframe-project-horizontal-color.svg"
 theme: just-the-docs
 repository: openmainframeproject/tac
+url: "https://tac.openmainframeproject.org"
 
 exclude: [
   "README.md",
   "completed.md",
   "dco-signoffs/",
-  "Gemfile", 
-  "Gemfile.lock", 
-  "package.json", 
+  "Gemfile",
+  "Gemfile.lock",
+  "package.json",
   "package-lock.json",
   "CODE_OF_CONDUCT.md",
   "LICENSE",
@@ -68,8 +69,8 @@ project_types:
 
 aux_links:
   "Need help or have a question? Contact us here":
-    - "//servicedesk.openmainframeproject.org"
-footer_content: Copyright &copy; The Linux Foundation&reg;. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our <a href="https://www.linuxfoundation.org/trademark-usage">Trademark Usage</a> page. Linux is a registered trademark of Linus Torvalds. <a href="http://www.linuxfoundation.org/privacy">Privacy Policy</a> and <a href="http://www.linuxfoundation.org/terms">Terms of Use</a>.
+    - "https://servicedesk.openmainframeproject.org"
+footer_content: Copyright &copy; The Linux Foundation&reg;. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our <a href="https://www.linuxfoundation.org/trademark-usage">Trademark Usage</a> page. Linux is a registered trademark of Linus Torvalds. <a href="https://www.linuxfoundation.org/privacy">Privacy Policy</a> and <a href="https://www.linuxfoundation.org/terms">Terms of Use</a>.
 
 readme_index:
   with_frontmatter: true

diff --git a/_includes/projectdetails.html b/_includes/projectdetails.html
@@ -4,7 +4,7 @@
 {%- for project in site.data.projects -%}
     {%- unless excluded_levels contains project["Level"] -%}
     <tr>
-        <td><img id="{{ project["Name"] }}" src="{{ project["Logo URL"] }}" /></td>
+        <td><img id="{{ project["Name"] }}" src="{{ project["Logo URL"] }}" alt="{{ project["Name"]}} Logo" /></td>
         <td>
             {%- if project["Github Org"] -%}
             Repo: <a href="{{ project["Github Org"] }}">{{ project["Github Org"] }}</a><br />

diff --git a/process/start_project.md b/process/start_project.md
@@ -37,7 +37,7 @@ Shared R&D with a broad ecosystem means bringing more contributors and maintaine
 
 ### Drive broad industry awareness with the press and analysts.
 
-Your project will get broad motion picture, visual effects, tech, and open source exposure through our large audience, extensive media outreach partnerships with publications such as Linux.com and TFiR, and key partners.
+Your project will get broad industry and open source exposure through our large audience, extensive media outreach partnerships with publications such as Linux.com and TFiR, and key partners.
 
 - Your project will be featured on both the [{{ site.foundation_name }}]({{ site.website_url }}) and the [Linux Foundation](https://www.linuxfoundation.org/projects) websites, as well as the [{{ site.foundation_name }} Landscape](https://l.lfenergy.org)
 - Always available guest blog post(s) on the [{{ site.foundation_name }} blog]({{ site.blog_url }}) on project updates.
@@ -97,7 +97,7 @@ The “LF Way”, which is aligned with how {{ site.foundation_name }} operates,
 The project must:
 
 - Use an approved [OSI open-source license](https://opensource.org/licenses).
-- Be supported by a [TAC member]({{ site.tac_member_list.url }}).
+- Be supported by a [TAC member]({{ site.tac_member_list_url }}).
 - Allow neutral ownership of project assets such as a trademark, domain, or GitHub account (the community can define and manage rules).
 - Technical "do-ocracy" and separation of business governance from technical governance (we're flexible on the model) are clearly documented (which we can help you establish).
 - Allow anyone to participate in the technical community, whether or not a financial member or supporter of the project.
@@ -106,13 +106,13 @@ Often projects are new open-source projects, but that isn’t a requirement - ex
 
 ### Project Preparation Checklist
 
-- Prepare draft mission and scope statement. 
-- Identify internal teams within the mission and scope. 
-- Identify developers internally 
-- Analyze code for identification of licenses, license quality, and project dependencies 
-- Assess the potential universe of project participants. Identify ecosystem constituents and concerns of each. 
-- Identify any trademarks leveraged by the project (these will be owned by the LF neutrally) 
-- Outline infrastructure, marketing any other requirements needed for the project. 
+- Prepare draft mission and scope statement.
+- Identify internal teams within the mission and scope.
+- Identify developers internally
+- Analyze code for identification of licenses, license quality, and project dependencies
+- Assess the potential universe of project participants. Identify ecosystem constituents and concerns of each.
+- Identify any trademarks leveraged by the project (these will be owned by the LF neutrally)
+- Outline infrastructure, marketing any other requirements needed for the project.
 - Complete the [project proposal](/process/proposal_template) and submit it to the TAC for consideration
 
 The {{ site.foundation_name }} staff is happy to engage and advise during this process - let us know how we can help!
@@ -133,9 +133,9 @@ Proposed projects will have a 20-minute presentation timeslot at an upcoming TAC
     *  If a project is new, it’s often helpful to share the vision for the project, the anticipated structure, and benefits.
     *  If the project is an existing open-source project proposed to join ASWF, it is often helpful to schedule a project walkthrough for the community to understand better the project, including the architecture, structure, and how to get started using the project. This often helps review progress more efficiently.
 *   How does this submission support the [{{ site.foundation_name }} Mission and Vision statements]( {{ site.mission_statement_url }})?
-*   Does the project have any users? 
+*   Does the project have any users?
     *   How do you plan to attract users if accepted?
-*   How many committers will you have upfront, and from which companies? 
+*   How many committers will you have upfront, and from which companies?
     *   How do you plan to attract committers and contributors if accepted?
 *   Demo and/or walk-through of the project
 

diff --git a/process/tsc_faq.md b/process/tsc_faq.md
@@ -20,7 +20,7 @@ The Technical Steering Committee (TSC) is the leadership of the project. This co
 
 Typically, the TSC comprises the primary committers or maintainers in a project. To start, there may be an appointed list, but over time, more individuals may join the TSC according to the policies the TSC set for adding new members. Regardless, TSC meetings are generally open to anyone interested unless there are sensitive issues to discuss, necessitating a private meeting.
 
-[LFX Project Control Center] is a tool for managing project committees and roles within a project. Each project will be set up in that tool with a voting committee named 'Technical Steering Committee (TSC)' notating the project chairperson and all voting members. Project chairpersons, in addition to the Linux Foundation staff supporting the project, will have access to manage this. 
+[LFX Project Control Center] is a tool for managing project committees and roles within a project. Each project will be set up in that tool with a voting committee named 'Technical Steering Committee (TSC)' notating the project chairperson and all voting members. Project chairpersons, in addition to the Linux Foundation staff supporting the project, will have access to manage this.
 
 Additionally, each project has a [GitHub Team][GitHub Teams Docs] set up which will provide ['Maintain' permission]((https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization#permissions-for-each-role)) for each project maintainer. Generally, the LF staff will have this set up for each project; after that, the project is expected to maintain any changes.
 
@@ -98,11 +98,11 @@ The TSC Chairperson should share an agenda at least 24 hours before the meeting
 
 ### Q: Is a TSC member required to have their employer be a member of the {{ site.foundation_name }}?
 
-A: No - All technical community work, such as projects and working groups, is open to anyone to participate and not bound by membership in the {{ site.foundation_name }}. 
+A: No - All technical community work, such as projects and working groups, is open to anyone to participate and not bound by membership in the {{ site.foundation_name }}.
 
 ### Q: Does a person lose their membership in a TSC if they leave or change employers?
 
-A: No - TSC membership is bound to an individual, not an organization. If a change of employment for a TSC member results in a key contributing organization lacking TSC representation, the TSC may invite a new TSC member affiliated with that organization, provided that person meets any requirements for TSC membership. 
+A: No - TSC membership is bound to an individual, not an organization. If a change of employment for a TSC member results in a key contributing organization lacking TSC representation, the TSC may invite a new TSC member affiliated with that organization, provided that person meets any requirements for TSC membership.
 
 ### Q: Does an individual serving on the TSC represent themselves, the project, and/or their employer?
 
@@ -134,6 +134,6 @@ Just like TSC Meetings, subgroup meetings must be open to anyone interested in p
 [Technical Leads Mailing List]: https://lists.aswf.io/g/technical-project-leads
 [LFX Project Control Center]: https://projectadmin.lfx.linuxfoundation.org/
 [Service Desk]: https://servicedesk.aswf.io
-[LFX PCC Meeting Management Docs]: https://docs.linuxfoundation.org/lfx/project-control-center-pre-release/it-services-for-a-project/meetings
-[LFX PCC Committee Management Docs]: https://docs.linuxfoundation.org/lfx/project-control-center-pre-release/setup-services-for-a-project/committees-setup-for-a-project
+[LFX PCC Meeting Management Docs]: https://docs.linuxfoundation.org/lfx/project-control-center/v2-latest-version/collaborations/meetings
+[LFX PCC Committee Management Docs]: https://docs.linuxfoundation.org/lfx/project-control-center/v2-latest-version/collaborations/committees
 [GitHub Teams Docs]: https://docs.github.com/en/organizations/organizing-members-into-teams/about-teams
diff --git a/projects_with_bestpractices.md b/projects_with_bestpractices.md
@@ -10,9 +10,9 @@ layout: minimal
 {%- if project['Level'] == 'active' -%}
   <div>
   <dt>
-    <img src="{{ project['Logo URL'] }}" >
+    <img src="{{ project['Logo URL'] }}" alt="{{ project['Name']}} Logo">
     {%- if project["Best Practices Badge ID"] and project["Best Practices Badge ID"] != 'none' and project["Best Practices Badge ID"] != 'False' -%}
-    <a href="https://www.bestpractices.dev/projects/{{ project["Best Practices Badge ID"] }}"><img src="https://www.bestpractices.dev/projects/{{ project["Best Practices Badge ID"] }}/badge?{{ "now" | date: "%s" }}"></a>
+    <a href="https://www.bestpractices.dev/projects/{{ project["Best Practices Badge ID"] }}"><img src="https://www.bestpractices.dev/projects/{{ project["Best Practices Badge ID"] }}/badge?{{ "now" | date: "%s" }}" alt="{{ project["Name"] }} Best Practices Badge"></a>
     {%- endif -%}
   </dt>
   </div>
@@ -26,9 +26,9 @@ layout: minimal
 {%- if project['Level'] == 'incubating' -%}
   <div>
   <dt>
-    <img src="{{ project['Logo URL'] }}" >
+    <img src="{{ project['Logo URL'] }}" alt="{{ project['Name']}} Logo">
     {%- if project["Best Practices Badge ID"] and project["Best Practices Badge ID"] != 'none' and project["Best Practices Badge ID"] != 'False' -%}
-    <a href="https://www.bestpractices.dev/projects/{{ project["Best Practices Badge ID"] }}"><img src="https://www.bestpractices.dev/projects/{{ project["Best Practices Badge ID"] }}/badge?{{ "now" | date: "%s" }}"></a>
+    <a href="https://www.bestpractices.dev/projects/{{ project["Best Practices Badge ID"] }}"><img src="https://www.bestpractices.dev/projects/{{ project["Best Practices Badge ID"] }}/badge?{{ "now" | date: "%s" }}" alt="{{ project["Name"] }} Best Practices Badge"></a>
     {%- endif -%}
   </dt>
   </div>

diff --git a/projects_with_contributed_by.md b/projects_with_contributed_by.md
@@ -8,7 +8,7 @@ layout: minimal
 {%- for project in site.data.projects -%}
 {%- if project['Level'] != 'working-group' -%}
   <div>
-  <dt><img src="{{ project['Logo URL'] }}" ></dt>
+  <dt><img src="{{ project['Logo URL'] }}" alt="{{ project['Name']}}" ></dt>
   <dd><p>Contributed By</p><p>{{ project['Contributed By'] }}</p></dd>
   <dd><p>Chairperson(s)</p><p>{{ project['Chair'] }}</p></dd>
   </div>

diff --git a/resources.md b/resources.md
@@ -7,7 +7,7 @@ nav_order: 60
 If you are new to open source, or have some experience in open source and looking to grow your knowledge, the following resources are recommended to help grow your open source skills.
 
 - LF Training Courses ( free to audit )
-    - Open Source Best Practices 
+    - Open Source Best Practices
         - [A Beginner’s Guide to Open Source Software Development (LFD102)](https://training.linuxfoundation.org/training/beginners-guide-open-source-software-development/)
         - [Inclusive Open Source Community Orientation (LFC102)](https://training.linuxfoundation.org/training/inclusive-open-source-community-orientation-lfc102/)
         - [Inclusive Strategies for Open Source (LFC103)](https://training.linuxfoundation.org/training/inclusive-strategies-for-open-source-lfc103/)
@@ -20,13 +20,15 @@ If you are new to open source, or have some experience in open source and lookin
         - [Secure Software Development: Implementation (LFD105x)](https://training.linuxfoundation.org/training/secure-software-development-implementation-lfd105/)
         - [Developing Secure Software (LFD121)](https://training.linuxfoundation.org/training/developing-secure-software-lfd121/)
         - [Understanding the OWASP® Top 10 Security Threats (SKF100)](https://training.linuxfoundation.org/training/owasp-top-ten-security-threats-skf100/)
+        - [OpenSSF Guide to implementing a coordinated vulnerability disclosure process for open source projects
+](https://github.com/ossf/oss-vulnerability-guide/blob/main/maintainer-guide.md)
     - Documentation
         - [Open Source Technical Documentation Essentials (LFC111)](https://training.linuxfoundation.org/training/open-source-technical-documentation-essentials-lfc111/)
         - [Creating Effective Documentation for Developers (LFC112)](https://training.linuxfoundation.org/training/creating-effective-documentation-for-developers-lfc112/)
     - Standards Development
         - [GitHub for Open Standards Development (LFD140)](https://training.linuxfoundation.org/training/github-for-open-standards-development-lfd140/)
         - [Leading High-Performance Working Group Meetings (LFC120)](https://training.linuxfoundation.org/training/leading-high-performance-working-group-meetings-lfc120/)
-- [GitHub for Developers](https://githubtraining.github.io/training-manual/#/01_getting_ready_for_class)
+- [GitHub for Developers](https://githubtraining.github.io/training-manual)
 - [Open Source Guides from GitHub](https://opensource.guide/)
 - [Open Source License Best Practices - Quick Reference Guide](https://www.linuxfoundation.org/licensebestpractices)