2024.04.17

[seanmcilroy29]

---

2024.04.17 Agenda/Minutes

---

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

• Co-Chair - Pindy Bhullar (Ubs)
• 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

• [x] Approve agenda
• [x] Approve previous Meeting Minutes

Welcome New Members

• [x] Any new members?

Initial visual/diagram of the framework

• [x] Draft End to End spec diagram
• Miro board

Issues - Project Dashboard

• [x] #8
• [ ] #9
• [ ] #10
• [ ] #11
• [x] #12
• [x] #13

Previous Meeting AI's

• [x] How do we create a structure and strategy to make an organisation greener?
• [x] Assess and check during the transformation On point solution and during the transformations.
• [x] Gaps in the data
  • Transformational Journey Swim Lanes
  • Links to Real-time cloud, SCER, Maturity Model, Indeed, Patterns

AOB

• [ ] Other Member submissions

Future meeting Agenda submissions

• [x] If you have any Agenda submissions, please let Sean know via email sean@greensoftware.foundation or open an Issue

Next Meeting

• [x] 01 May @ 8am PT / 4:00 pm GMT

Adjourn

• [ ] Motion to adjourn

Documentation

• Analysis across the GSF Pillars .xlsx
• Assumptions Document.docx
• Terms of Reference.docx
• CNCF - Environmental Sustainability Maturity Model
  • https://github.com/cncf/tag-env-sustainability/issues/50
  • https://maturitymodel.cncf.io/#the-cloud-native-maturity-model-30-updated-in-autumn-2023

[seanmcilroy29]

MoM

Pindy opened the meeting at 1600 (BST)

Software development framework for sustainability and compliance. The group discussed the structured stages and ideas that were submitted. Sean O and Pindy reviewed the swim lane approach and how it overlapped in certain areas. Pindy shared her approach of compartmentalizing strategy and operations and emphasized prioritizing sustainability metrics. She also outlined a framework for software project delivery that focused on a circular process of development and improvement. Pindy and Sean also discussed the "rubric" project donated by Indeed and its software engineering component. The group will look to invite Mohammed for his input, which is part of the execution piece.

Software development framework. Pindy and Sean O discussed measuring software development progress. They stressed the need to establish a baseline and monitor environmental reports. They brainstormed project-specific business cases and defined what should be measured, including software applications and infrastructure changes. Sean O presented a visual diagram to help identify steps for compliance and operations. Pindy provided feedback on Sean's diagram, emphasizing the importance of adhering to compliance and structure.

Maturity model for project management, focusing on structure and benchmarks. Pindy and Sean discuss the maturity model for the compliance project, seeking structure and synchronization. Sean M and Sean O discuss the maturity matrix and its impact on their project.

Software development lifecycle and project management. Pindy discusses measuring scope and compliance in software development. Sean O offers to co-chair the project, and Pindy agrees.

Action Items

• [ ] Add the compliance section to Pindy's diagram to overlay compliance considerations across strategy and operations.
• [ ] Have Sean O formally take on the role of co-chair for the project.
• [ ] Continue iterating and building out the diagrams and frameworks discussed, with the following review in two weeks.
• [ ] Schedule a follow-up meeting with Muhammad from Indeed to better understand their Rubric project.
• [ ] Present the work to the SC next week for additional support and resources.
• [ ] Review Pindy's diagram outlining the stages of a software project and provide feedback on any missing elements or changes needed.