2023-12-12 Carbon Aware SDK Weekly Meeting Agenda 🎯
Closed this issue · 12 comments
Date
2023-12-12 - 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
@Sophietn It's now down to the Project team to decide whether we record our project meetings or not.
Would we like to record these meetings?
If we do, are we happy to share it with members subscribed to this project?
Meeting link - clarification as we have 2 meeting invites with 2 links?
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
-
v1.2 Release today!
-
Progress to Graduation (documentation updates) - project board
-
Review Pull Requests
11 Open PRs
PRs
- Discuss Issues
24 Open Issues
Issues
Discussion
Action Items
- copilot4prs - can we get help from GitHub? @Sophietn to organise a call with @seanmcilroy29 and @vaughanknight and if no progress, organise a further one with GitHub...
- #366 @vaughanknight to look at
- aim to manually create the release notes - @danuw #434
Meeting attended by
Attended
Attended
Attended
Attended
Attended
Attended
- #340 pushed back to vNext
- Release notes to be shared by @danuw in a PR - prerequisite for v1.2 #434
- @Sophietn to confirm with @vaughanknight it is fine to release without him present/ release async when Release notes/CHANGELOG updated?
- Graduation criteria (FYI for where the requirements for graduations are coming from): https://github.com/Green-Software-Foundation/oc/blob/main/project-lifecycle.md#graduated
- For anyone looking to contribute, feel free to pick up any of the documentation required issues for project graduation: https://github.com/orgs/Green-Software-Foundation/projects/15/views/2?filterQuery= (TODO)
@Shady-Hegazy is interested in viewing our open issues on the project board that are looking for a contributor (see above) But he doesn't have access to the board.
I have tried inviting him but it's not letting me.
Can anyone else? @vaughanknight @zanete you 2 are listed as the only 2 other Carbon aware sdk project board admins.
Looks like the reason gh4prs is not working is because we never got off the waitlist :( . Here is the dashboard under which i was able to access it: https://copilot4prs.githubnext.com
IEF is generating their changelogs like so:
- https://github.com/Green-Software-Foundation/if/releases
it is a github builtin @narekhovhannisyan if you could share some information on how to set this up, this would be helpful!
FYI: @vaughanknight @danuw this is the feature thats used : https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
here is an example of how this looks like for us:
LGTM - I think automation is the way to go...
A bit less impactful, but if we really want to add text to a release we could add a link to a discussion that lists more details? Not that I think we would.
What I think is missing is the closed issues though no?
@Willmish Hi! For generating a proper changelog on release, the best practice is to organize the git flow with well-defined pull requests. Then on release creation, there is a button to automatically generate a changelog which is based on pull requests.
One more automated version is conventional commit based changelog