🎯2023-04-25 Carbon Aware SDK Weekly Meeting Agenda

[Willmish]

Date

2023-04-25 - 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

GSF project meetings may be recorded for use solely by the GSF team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

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
• Discuss : Google Groups usage
• Approve Past Meeting Minutes
• Review Pull Requests
• Look through the Action Points
• Pick up back at: ADR Dynamic DataSource Registration #288 at the next meeting
• V1.1 release planning: @vaughanknight to lead discussion
• Consider: [Feature Contribution]: Geocode support in the API #179
• Discuss Issues

Wednesday meeting Agenda

• Convene & Roll Call (5mins)
• Review Meeting Notices (see above)
• Review the agenda and suggest new agenda points
• Discuss : Google Groups usage
• Approve Past Meeting Minutes
• Pick up back at: ADR Dynamic DataSource Registration #288 at the next meeting
• Look through the Action Points
• V1.1 release planning: @vaughanknight to lead discussion
• Consider: [Feature Contribution]: Geocode support in the API #179
• Review Pull Requests
• Discuss Issues

PRs

Issues

Discussion

• [ ]

Action Items

• @FabioTurati-NTT to add feature request on filter feature
• @bderusha to modify [Feature Contribution]: Geocode support in the API #179 with comments on geolocation feature
• Discuss: Accepting ADRs merged in as 'Proposed' to the repo: https://github.com/Green-Software-Foundation/carbon-aware-sdk/blob/dev/docs/architecture/decisions/0012-electricity-maps-free.md @Willmish to open PR
• Add CHANGELOG to dev @vaughanknight
• @vaughanknight to manually compare swagger.yaml as its moved in Publish OpenAPI spec YAML from WebApi server #149 (that's why its failing)
• Current timeline: Release v1.1 next week [Release]: v1.1 offical release - CHANGELOG discussion  #308
• @vaughanknight to create new branch for testing workflows for [Feature Contribution]: Initial DevOps and github actions clean up #252 (@YaSuenag @danuw )
• @danuw : Devops: [Feature Contribution]: Initial DevOps and github actions clean up #252
• @tmcclell to look into setting up CA SDK with the most recent changes from dev and to resurface previous issues encountered when polling data from the US region
• @Willmish reopen [Sample]: Jupyter notebook Demo of web API  #114
• @Willmish to raise CODEOWNERS discussion
• @Willmish log or start with configurations docs changes to make them more intuitive see [Bug]: Documentation improvement possibilities: Configurations #325
• @Willmish @vaughanknight @danuw - Bring a task list for v1.1 for next meetign
• @Willmish Create invite list for google groups

Meeting attended by

[nttDamien]

attended

[vaughanknight]

Attended

[Willmish]

Attended

[danuw]

Attended

[YaSuenag]

Attended

[otsuyo]

attended

[Willmish]

• Waiting 1 more week for an update on ADR state from "Accepted" to "Proposed" in the PR ADR Dynamic DataSource Registration #288
• Added JsonForecast datasource #312 under review by @vaughanknight
• @Willmish to look at Integration tests coverage for WebAPI and CLI #294
• feat: Update appsettings with default datasources #330 - being considered, might get rejected as test-json being the default for initial testing of the SDK is the desired behaviour (@vaughanknight to talk to the PR owner first)
• feat: Add General Dockerfile and build/publish workflow #332 partial duplicate of Add workflow for publishing container image #327 - to consider pulling what's new (@danuw to connect with PR owner)
• feat: Update the helm chart #333 - @danuw to connect with PR owner, @Willmish to look at the PR, if README can be updated to not only target AKS (or accept with AKS documentation and update afterwards)
• @danuw to talk to @seanmcilroy29 on Github Package permissions (Add @vaughanknight to the discussion)

v1.1 release:

• Outstanding PRs to be merged
• CHANGELOG to be added
• Github Packages permissions issue fixed [Bug]: Github package is not public #336

[vaughanknight]

Quick one regarding this item assigned to me

@vaughanknight to manually compare swagger.yaml as its moved in #149 (that's why its failing)

this is merged and we did review it, is there anything outstanding?

[Willmish]

Attended: Wednesday meeting

[bderusha]

Attended: Wednesday meeting

[FabioTurati-NTT]

Attended: Wednesday meeting

[danuw]

Attended: Wednesday meeting

[danuw]

Packages are now public for the repo and we should be able to create packages on merge but will monitor the next merges to dev

cc @YaSuenag

[Willmish]

Notes Wednesday meeting:

• ADR dynamic DataSource Registration @bderusha adding an issue for the feature request and mentioned a possibility of someone /team at MS contributing this feature
• What we need to consider: Tracking which ADRs that are accepted got implemented/and which might be missing (on example of ADR 14 and ADR 6 - ADR 6 already is accepted and mentions dynamic datasource registration and was not implemented)
• Mentioned by @bderusha : opening a new issue for discussion on the currently proposed ADRs sitting in the repo
• Possibly: reflect this in documentation
• Suggestion: using "for discussion" tag for the weekly rundown of repo activitiy (email) @jawache
• Suggestion: For synchronous meetings, surface issues for people to discuss asynchronously (e.g. bringing up "for discussion" issues during the call plus hosting an initial discussion on the call) - maybe add GH bot looking at newest issues to add to the agenda in a comment
• To discuss next time: [Feature Contribution]: Geocode support in the API #179 (mentioned by @bderusha was to consider adding an ADR for this feature as it deviates from the current structure of the SDK)

[helayoty]

• feat: Update the helm chart #333 - @danuw to connect with PR owner, @Willmish to look at the PR, if README can be updated to not only target AKS (or accept with AKS documentation and update afterwards)

@Willmish This PR is for the general helm chart, nothing related to AKS.

[YaSuenag]

@helayoty README.md which you make changes mentions for AKS only. https://github.com/Green-Software-Foundation/carbon-aware-sdk/blob/df4a3c6c28bbdea144d455d3f79b1bed70566f4c/samples/helm-deploy/README.md

I think it is better to remove description for AKS from README.md. We can require that the user need to prepare Kubernetes cluster by themselves in this case.

[bderusha]

@Willmish New issue added to implement ADR-0006 #348