🎯 2024-02-20 Carbon Aware SDK Meeting Agenda

[Sophietn]

Date

2024-02-20 - 8am UTC

Meeting notices

Antitrust Policy

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation 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.

Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

Recordings

We're happy to start recording these meetings if we receive any requests to record them.

Roll Call

Please add a comment to this issue during the meeting to denote attendance.

Full Name	Affiliation	GitHub username (optional)
Vaughan Knight	Microsoft	vaughanknight

Any untracked attendees will be added by the GSF team below

Agenda

• Convene & Roll Call (5mins)

• Review Meeting Notices (see above)

• Review the agenda and suggest new agenda points

• Graduation - 13th January target missed.
  2 weeks ago Actions what is complete, what is still outstanding?
  What additional actions are needed so we can be 'ready' for oc graduation review?
  What is the new target date?

• Update on ADR and @vaughanknight <> NTT meeting
  ADR for Prometheus Metrics end point #455

• @danuw Update on IF <> CA SDK integration
  [Action Item] IF/CADK - Working Session After 3 October opensource-wg#97 (comment)

• Approve Past Meeting Minutes

PRs

#466

Issues

#446

Action Items

• [ ]

Meeting attended by

[danuw]

Attended

[Sophietn]

Attended

[YaSuenag]

Attended

[vaughanknight]

Attended

[tiwatsuka]

Attended

[Sophietn]

Discussed and Agreed
Incident process for Carbon Aware SDK
We identify the incident either ourselves or via community notification.
We create an issue, and tag 3 core contributors.
Anything urgent we set up a one-off call.
Anything non urgent, we discuss in the next weekly call and fix in the next release.

[nttDamien]

Attended

[danuw]

Checklist (from https://oc.greensoftware.foundation/project-lifecycle.html#graduated):

• Have a active set of contributing members from at least two member organisations https://github.com/Green-Software-Foundation/carbon-aware-sdk?tab=readme-ov-file#appointments
• Have a public GitHub repo with clear project documentation on
  • Project overview (ReadMe)
  • How to contribute (contributing.md ) Updating CONTRIBUTING.md #425
  • End User Guide (enablement.md) Draft of enablement.md #441
  • Test coverage Docs/test coverage #462
  • Fit within GSF Theory of Change https://github.com/Green-Software-Foundation/carbon-aware-sdk?tab=readme-ov-file#carbon-aware-sdk
• Have made a release deployment, even a ‘developer preview’
• Evidence of usefulness through real world use cases in the production environment, including testimonials (adopters.md) Update documentation of Usefulness (adopters.md) #414
• Have 100% of the applicable criteria for the Open SSF Best Practice Badge (security.md) Create SECURITY.md #464
• Have an incident process agreed with GSF PM
• Have GSF processes set up including
• Project meetings and mailing list
• Provide regular updates to the relevant WG
• Have defined OKRs agreed by the GSF PM
• Similar or competitive projects are allowed, but the project should not contradict with another GSF Graduated project

@Sophietn in case that helps with en initial "evidenced by"

[Sophietn]

We reviewed the final piece of documentation https://carbon-aware-sdk.greensoftware.foundation/ and made the final changes to links and wording.
We raised PR to update the security.md with @Willmish's review of Open SSF Best Practice Badge.
We made the above checklist and started linking out to evidence of fulfilling acceptance criteria

Next steps Actions

• @Sophietn to raise DRAFT issue on OC repo for Lifecycle Stage change approval request
• @vaughanknight @danuw @Willmish to review the DRAFT issue once @Sophietn emails it to them
• @Sophietn to circulate the issue with the Oversight committee mailing list and open a motion to approve, with an pass date if no objections.

[vaughanknight]

@Sophietn - After merging Dan's updates from the meeting (I just reviewed and merged), is there anything else outstanding for graduation that's top of mind? If you can not think of anything, I'm happy to go ahead.

[nttDamien]

@vaughanknight @Sophietn @danuw
Sorry, I missed most of the meeting yesterday.
We have a demonstration planed for March 10th in Tokyo (feel free to join ! it's in Asakusa https://event.ospn.jp/osc2024-spring/), but some developments are still waiting for merge (#404 #420 #421 #422 ) which is dependant on the graduation work being complete, from what I remember of our discussion last week.
Do you think the timing should work-out right, or we should think about forking waiting for the merge to occur later in March ?

[Sophietn]

@Sophietn - After merging Dan's updates from the meeting (I just reviewed and merged), is there anything else outstanding for graduation that's top of mind? If you can not think of anything, I'm happy to go ahead.

Thanks @vaughanknight.
Last thing to agree is OKRs which we are discussing on email thread. Please confirm.
Once that's confirmed I will remove the DRAFT on the issue raised on Oversight committee repo, and circulate it with the motion.

[Sophietn]

Defined OKRs agreed by the PLs and the GSF PM

• Number of adopters of the SDK (adopters.md) (also tracking privately known adopters)
• Number of contributors to the SDK (OSSinsight tracking for active participants) (contributors all time on repo insights)
• Github Stars (StarHistory)