2025.03.24

[seanmcilroy29]

---

22025.03.24 Agenda/Minutes

---

Time 1600 (BST) - See the time in your timezone

• Co-Chair - Pindy Bhullar (UBS)
• Co-Chair - Sean O'Keefe (Microsoft)
• Convener – Sean Mcilroy (Linux Foundation)

---

Antitrust Policy

Joint Development Foundation meetings may involve participation by industry competitors, and the Joint Development Foundation intends to conduct all of its activities in accordance with applicable antitrust and competition laws. It is, therefore, extremely important that attendees adhere to meeting agendas and be aware of and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.

If you have questions about these matters, please contact your company counsel or counsel to the Joint Development Foundation, DLA Piper.

---

Recordings

WG agreed to record all Meetings. This meeting recording will be available until the next scheduled meeting.
Meeting recording

---

Roll Call

Please add 'Attended' to this issue during the meeting to denote attendance.

Any untracked attendees will be added by the GSF team below:

• Full Name, Affiliation, (optional) GitHub username

---

Agenda

• Approve agenda
• Approve previous Meeting Minutes

---

Review TOSS Framework v1

• Transforming Organizations for Sustainable Software (TOSS) Framework

• Each stage within a pillar covers the following key topics:

  • The flow has been enhanced, and each stage within a pillar covers the following key topics:
  • A simple intro to the stage
  • The personas required for the stage
  • A capability assessment for organisations to assess where they are in the pillar - enabling organisations to start at any point within a pillar

---

Next Meeting

• 2025.04.07

---

Adjourn

• Motion to adjourn

---

[seanmcilroy29]

Pindy opened the meeting at 17:00 GMT

Minutes

Discussion on Data Collection and Anonymization
Pindy outlines two modes of data collection: one for the GSF partnership and another for anonymous research. Sean recommends initially keeping the GitHub repository private until data is anonymized, while Parul suggests anonymising feedback from multiple organisations to protect contributors' identities. Sean clarifies the contributor licence agreement (CLA) and the consistency review process for public releases.

Document Review and Pilot Study Roadmap
Pindy presents the document structure, including the business case and capability assessment tables. Sean advises making the steps more actionable based on the assessment. Pindy suggests embedding checklist options within the capability assessment for clearer next steps and discusses the potential use of AI copilots and workflow tools like Flowable for automation.

Tooling and Workflow Automation
Sean mentions exploring various workflow automation tools, including Periodic and Flowable. Sean advocates using AI copilots for non-coding tasks, while Pindy introduces Flowable as a potential tool for documenting workflows. Sean and Pindy agree on the need for a dynamic tool to guide users through the assessment stages.

Finalising the Document and Next Steps
Pindy plans to add actionable steps to the capability assessment and merge cells in the checklist. Sean will convert the document to Markdown for easier maintenance and public feedback tracking. The team will review the document and provide feedback on the checklist and capability assessment before Pindy shares the updated version for a quick review.

Action Items

• Pindy will add actionable steps to the capability assessment and merge the cells in the checklists.
• Sean will migrate the TOSS documentation to a Markdown format in GitHub.
• Sean will explore using AI-powered tools, such as Copilot, to develop a workflow automation solution for the TOSS framework.
• The team will continue reviewing the TOSS documentation and provide feedback.
• Pindy will share the roadmap and plan for the TOSS pilot study.