fix(meetings): align P4W schedule anchor to land on Jun 15

[bjohansebas]

The 2026-05-16 change to a P4W (4-week) cadence kept the original anchor (2025-05-05), so the series landed on 2026-06-01 / 2026-06-29 and skipped the expected 2026-06-15 meeting. No agenda issue was created for it.

Move the anchor to 2026-05-18 (4 weeks before 2026-06-15) so the 4-week series falls on 2026-06-15, 2026-07-13, ... while keeping the monthly cadence intact.

Summary

What kind of change does this PR introduce?

Did you add tests for your changes?

Does this PR introduce a breaking change?

If relevant, what needs to be documented once your changes are merged or what have you already documented?

Use of AI

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ Unknown (6fbcca6)
• ✅ login: bjohansebas / name: Sebastian Beltran (6fbcca6)

One or more co-authors of this pull request were not found. You must specify co-authors in commit message trailer via:

Co-authored-by: name <email>

Supported Co-authored-by: formats include:

1. Anything <id+login@users.noreply.github.com> - it will locate your GitHub user by id part.
2. Anything <login@users.noreply.github.com> - it will locate your GitHub user by login part.
3. Anything <public-email> - it will locate your GitHub user by public-email part. Note that this email must be made public on Github.
4. Anything <other-email> - it will locate your GitHub user by other-email part but only if that email was used before for any other CLA as a main commit author.
5. login <any-valid-email> - it will locate your GitHub user by login part, note that login part must be at least 3 characters long.

Alternatively, if the co-author should not be included, remove the Co-authored-by: line from the commit message.

Please update your commit message(s) by doing git commit --amend and then git push [--force] and then request re-running CLA check via commenting on this pull request:

/easycla

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the meeting agenda generation workflow schedule anchor date for the recurring meeting series.

Changes:

• Bumped the schedules start date from 2025-05-05 to 2026-05-18 for the P4W recurrence.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[evenstensberg]

@bjohansebas you can rebase and remove claude from the co-author as a bypass to the CLA for now.

[ovflowd]

@bjohansebas you can rebase and remove claude from the co-author as a bypass to the CLA for now.

I don't think this is something you should recommend/we should do as that pretty much means, @bjohansebas would be faking their DCO (Developer Certificate of Origin) which violates Linux Foundation's CLA's

[evenstensberg]

@ovflowd aha! Thanks for the catch!

I don't know why the co-author sign is not working. @alexander-akait wasnt this fixed for you earlier?

[bjohansebas]

I think it's only available for certain repositories.

[avivkeller]

to land on Jun 15

@bjohansebas Can we land this today, June 16th?

Edit: oh you meant the meeting landed on a given day, not land the PR on a given day. Ignore this

[bjohansebas]

/easycla

[jarias-lfx]

/easycla

[alexander-akait]

@bjohansebas feel free to merge

[bjohansebas]

@alexander-akait I don't have write access to the repository