Transforming Organisational Software Sustainability (TOSS) - Using software emission calculation data for organisational decision making during the development and use of technology applications.
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
Once the Project Group has approved the Scope, a blog will be drafted for circulation
SummarySoftware project scope and name.
Pindy and Massimodiscuss scheduling a meeting, with Pindy needing to check with another group at the same time. Pindy and Massimo discuss renaming a project from "Software Emissions" to something more catchy.
Project scope and maturity model for IT organization.
Pindy and Massimo brainstorm project names, including "Triple S P" and "Implementation Transformation. Pindy is working on scoping a project with Sean and his team to assess organizations' maturity levels in software development using a matrix model similar to CMMI. Sean and Massimo discuss the potential overlap between the matrix and existing maturity models like CNCF and sustainableIT playbook for technology leaders.
IT project scope, assumptions, and questions for organizations.
Pindy outlines the scope of a project, including meeting cadence and governance structure, for the benefit of Massimo.
Pindy provides updates on two documents related to her PhD research, including the Terms of Reference and Assumptions documents. Pindy outlines the scope of a project, including defining boundaries and identifying key questions to address. Pindy maps the questions to JSF pillars and organization functions to create a framework for companies to calculate their GSI or Sei.
Reducing carbon emissions in software development.
Massimo asks about calculating carbon emissions and baselining them to understand energy usage in software applications. Pindy suggests understanding energy usage by baselining carbon emissions, switching off servers in the weekend, and implementing a project to log out VDI sessions at night. Pindy explains how to calculate the reduction in carbon emissions by implementing small changes in daily operations, such as turning off lights and using energy-efficient machines. Sean provides feedback on the terms of the reference document and commits to reading and giving feedback on the other documents within the week.
Accelerating a project with UBS and the Sustainable Technology guild.
Pindy and Sean discuss the scope of a project, agreeing on the document's name and scope, and Massimo suggests referencing the charter for terms of conditions. Sean will keep everyone honest and update the document, and the group agrees on the least amount of people to involve in the project. Pindy and SMassimo discuss accelerating a project through the Sustainable Technology guild at UBS, with Pindy expressing enthusiasm for the opportunity to bring the project back to the organization and highlight the good work being done. Massimo mentions the need to finalize the scope and name of the project before moving forward, and Pindy looks forward to coming up with a creative name for the project.
Maturity Matrix
[x] Project overlap alignment
AOB
[x] 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
2024.01.24 Agenda/Minutes
Time 1600 (GMT) - See the time in your timezone
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:
Agenda
Welcome New Members
Review & Approve Project Scope
Summary Software project scope and name. Pindy and Massimodiscuss scheduling a meeting, with Pindy needing to check with another group at the same time. Pindy and Massimo discuss renaming a project from "Software Emissions" to something more catchy.
Project scope and maturity model for IT organization. Pindy and Massimo brainstorm project names, including "Triple S P" and "Implementation Transformation. Pindy is working on scoping a project with Sean and his team to assess organizations' maturity levels in software development using a matrix model similar to CMMI. Sean and Massimo discuss the potential overlap between the matrix and existing maturity models like CNCF and sustainableIT playbook for technology leaders.
IT project scope, assumptions, and questions for organizations. Pindy outlines the scope of a project, including meeting cadence and governance structure, for the benefit of Massimo. Pindy provides updates on two documents related to her PhD research, including the Terms of Reference and Assumptions documents. Pindy outlines the scope of a project, including defining boundaries and identifying key questions to address. Pindy maps the questions to JSF pillars and organization functions to create a framework for companies to calculate their GSI or Sei.
Reducing carbon emissions in software development. Massimo asks about calculating carbon emissions and baselining them to understand energy usage in software applications. Pindy suggests understanding energy usage by baselining carbon emissions, switching off servers in the weekend, and implementing a project to log out VDI sessions at night. Pindy explains how to calculate the reduction in carbon emissions by implementing small changes in daily operations, such as turning off lights and using energy-efficient machines. Sean provides feedback on the terms of the reference document and commits to reading and giving feedback on the other documents within the week.
Accelerating a project with UBS and the Sustainable Technology guild. Pindy and Sean discuss the scope of a project, agreeing on the document's name and scope, and Massimo suggests referencing the charter for terms of conditions. Sean will keep everyone honest and update the document, and the group agrees on the least amount of people to involve in the project. Pindy and SMassimo discuss accelerating a project through the Sustainable Technology guild at UBS, with Pindy expressing enthusiasm for the opportunity to bring the project back to the organization and highlight the good work being done. Massimo mentions the need to finalize the scope and name of the project before moving forward, and Pindy looks forward to coming up with a creative name for the project.
Maturity Matrix
AOB
Future meeting Agenda submissions
Next Meeting
Adjourn
[x] Motion to adjourn
Meeting Action Items / Standing Agenda / Future Agenda submissions