2024.12.11

[seanmcilroy29]

---

2024.12.11 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 Summary Notes & AI's

• 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.
• 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.

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

• 08th Jan @ 9 am P/T

Adjourn

• Motion to adjourn

---