2024.11.13

[seanmcilroy29]

---

2024.11.13 Agenda/Minutes

---

Time: Bi-weekly @ 1700 (BST) - See the time in your timezone

• Co-Chair - Chris Xie- (Futurewei)
• Co-Chair - Vacant
• 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 link

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

Introductions - Chris

• Any new members?

Previous meeting Summary notes

The group discussed developing and implementing a new software labelling system. Chris emphasized the need for easy adoption and business value, stressing the importance of making the label accessible and verifiable. Asim provided detailed specifications for the label, which included using a QR code linking to a manifest file for verification. They also discussed potential policy benefits, such as compliance with EU policies like the CSRD. The conversation ended with the decision to create a comprehensive white paper outlining the new labelling system's business value, policy implications, and the importance of providing tools for easy adoption.

Previous meeting AI's

• Engage the design team to provide guidelines on the visual representation of the SCER label.
• Explore options for verification mechanisms, including using a manifest file and potential third-party attestation.
• Develop a white paper outlining the business value and policy alignment of the SCER label.

Discussions

• Review Spec proposed updates
• [Question] Design considerations for SCER spec/label #90
• Design a draft label for SCER with design guidelines.  #92

Future meeting Agenda submissions

• If you have any Agenda submissions, please let Sean know via email [email protected] or open an Issue

Next Meeting

• 27th Nov @ 9 am P/T

Adjourn

• Motion to adjourn

---

Previous meeting AI's

• Chris/Adi - Start setting up an SCR certification lab folder and documentation.
• All - Review Asim's previous comments and suggestions on strengthening the SCR standard.
• All - Provide direct feedback and comments on the SCR documentation.

[adityamanglik]

attended

[seanmcilroy29]

MoM

Summary Notes

The team proposed adding label components, including a timestamp, standard number, and the name of the issuing authority. They also discussed the impact framework for calculating software carbon emissions (SCI) scores and emphasized the importance of maintaining the integrity of existing references. The following steps involve updating the proposed development branch, creating a new feature branch, and finalizing the label design. finalizing the label design.

Minutes

Challenges with Current Specification and Labeling
Sean and Chris discuss the changes proposed by Asim, with Chris expressing his support for the current proposal. Sean talks about the label's components, which include the ICI score and a QR code. Chris suggests adding a timestamp and a standard number to the label for clarity. They continue discussing the various elements of the label, such as the ICI score, version number, and QR code.

Refinement of Labeling and Use Cases
Chris suggests adding a label name and issuing authority to improve clarity. Sean agrees and proposes creating a mock-up of the updated label. They discuss the label's use cases, with Chris advocating for a simplified version for quick reference and a more detailed version for comprehensive information. Sean mentions the impact framework as a tool for generating SCI scores and suggests using it in the labelling process. Chris expresses interest in utilizing the impact framework and agrees to review the proposed updates.

Branch Management and Future Development
In a discussion about managing the development branch and minimizing disruption to existing references, Sean proposed creating a new feature branch called "old dev" to preserve the current information. In contrast, Chris preferred maintaining the current development branch intact and suggested creating a new branch for upcoming updates. Ultimately, they agreed to create a new branch named "new dev" for the proposed updates and make it the default branch for future development. Sean plans to update this proposed development branch with the new components and will create a pull request accordingly.

Next Steps and Collaboration
Sean will update the proposed development branch with the new components and create a pull request. Chris suggests that the label should include the name and issuing authority. Sean will raise an issue to outline the objectives and ask Jenny to update the label design.

Action Items

• Update the proposed SCI label design to include the label name and issuing authority name.
• Create a mockup of the updated SCI label design.
• Push the updated SCI label specification into the new dev branch and create a pull request.

[chrisxie-fw]

attended