🎯 2024-06-04 Carbon Aware SDK Weekly Meeting

[danuw]

Date

2024-06-04 - 7am 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

• Approve Past Meeting Minutes

• Review Pull Requests

• Discuss Issues

• Watt time v3

• .NET8 article review needed @vaughanknight @danuw

• OSWG Question: Define our 'value add' in our documentation #525

• IF Plugin update @danuw Finalise Impact Framework Plug-In #502

• Call for Features - request this is shared on LinkedIn @Sophietn

PRs

PRs Updated:

• Add GHA workflow for generating WebAPI client library for Java #471 Add GHA workflow for generating WebAPI client library for Java

Issues

Issues Updated:

• 🎯 2024-06-04 Carbon Aware SDK Weekly Meeting #529 🎯 2024-06-04 Carbon Aware SDK Weekly Meeting
• [Bug]: Avoid inotify limit in WebAPI container on Kubernetes #528 [Bug]: Avoid inotify limit in WebAPI container on Kubernetes
• 🎯2024-05-28 Carbon Aware SDK Weekly Meeting  #527 🎯2024-05-28 Carbon Aware SDK Weekly Meeting
• Define our 'value add' in our documentation #525 Define our 'value add' in our documentation
• Finalise Impact Framework Plug-In #502 Finalise Impact Framework Plug-In
• [Bug]: Unhandled exception. CarbonAware.Exceptions.ConfigurationException: No data sources are configured #426 [Bug]: Unhandled exception. CarbonAware.Exceptions.ConfigurationException: No data sources are configured

Issues Closed

• 🎯2024-05-21 Carbon Aware SDK Weekly Meeting #526 🎯2024-05-21 Carbon Aware SDK Weekly Meeting
• [Feature Contribution]: Publish the docker file in a docker registry #262 [Feature Contribution]: Publish the docker file in a docker registry

Discussion

• [ ]

Action Items

• [ ]

Meeting attended by

[danuw]

Attended

[vaughanknight]

Attended

[danuw]

Cover #340 and #471

[nttDamien]

Attended

[tiwatsuka]

Attended

[YaSuenag]

Attended

[danuw]

• WattTime v3 updates expected next week @vaughanknight Gap Analysis for WattTime v3 #510 - code updates coming first and then some docs updates on highlighting main changes
  • we should try and hold off major changes
• .NET8 blog article #501 needs review @vaughanknight @danuw
• Define our 'value add' in our documentation #525 - @Sophietn any updates on this?
  • @vaughanknight brought up some points: are we sure this is what we need to focus on?
• Carbon Aware SDK - Call for Features #521 - @vaughanknight and others to try and share with whom they know are using the SDK as a chance to help influence more relevant scenario aligned to their priorities
• PR:
  • Add example for 'podman play kube' #340 - pending evidence it works on a different machine (system test) - @YaSuenag
  • Add GHA workflow for generating WebAPI client library for Java #471 - giving the latest changes a week for comments - overall this generally improves efficiency of workflow to detect for changes to create a new container and launches new client generations too + this is sample that @YaSuenag will use, so we can iterate as we get new feedback