🎯2024-02-06 Carbon Aware SDK Meeting Agenda

[Sophietn]

Date

2024-02-06 - 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)

• Approve Past Meeting Minutes

• Review the agenda and suggest new agenda points

• v1.2 release retrospective
  15 minutes Easyretro board

• Progress to graduation
  Project board
  Target date 13th January
  What actions do we need to take now to ensure we're ready?

• Architectural Decision Recordhttps://github.com/ADR for Prometheus Metrics end point #455

• Sync with IF ([Action Item] IF/CADK - Working Session After 3 October opensource-wg#97)

• Review Pull Requests

• Discuss Issues

Action Items

• [ ]

Meeting attended by

[danuw]

Attended

[vaughanknight]

Attended

[YaSuenag]

Attended

[Willmish]

Attended

[Sophietn]

Attended

[tiwatsuka]

Attended

[nttDamien]

Attended

[vaughanknight]

Vaughan catching up with NTT crew this week to discuss the ADR.

[vaughanknight]

Dan and Vaughan catching up on the Test Coverage documentation for graduation

[Sophietn]

Actions

• @Willmish security.md Update documentation of secureness (security.md) #415
• @danuw docusaurus [Bug]: Fix and update doc deployment workflow #344 (comment)
• @vaughanknight readme Update documentation for Project overview (ReadMe) #411
• @Sophietn update shortlink of docusaurus to mirror the IF one
• @everyone to look at outstanding 1.3 issues ahead of graduation release

[Sophietn]

Notes from our easy retro v1.2 release retrospective

Common themes
Went well - we had a release, worked well together, lots of contributors (9 individuals), new contributors from NTT was a great help
To improve - we aimed to release on 12th Dec, we released 16th Jan, one month late, long delays waiting for automated release notes, surprise when we went to merge, hard to communicate with each other in between meetings

Actions

• Let's set a release schedule of every month, whatever is ready (avoiding holiday periods like Christmas)
• Let's not use copilot4prs again - we're on a waitlist so this automation wasn't accessible to us, but it took us a while to work this out.We created a dependency on something else. We should take ownership of our own releases. Not rely elsewhere or wait unless critical.
• @Sophietn Set up a free calendar HOLD for release, 2nd Wednesday of every month. And 1 week previous HOLD to check everything is ready, release notes
• Use the mailing list to communicate, respond to the agenda email to ask to add on 30 mins before or after the weekly call if needed