figure how to automate scheduling of reoccurring meetings

[derberg]

Reason/Context

This PR introduced full automation of meetings scheduling but it doesn't support "automation trigger". In other words, to have automated scheduling, you need to manually trigger a dedicated workflow. @jonaslagoni would like to have this part automated too. So basically "a workflow" that triggers event schedule, like a cron running every Thursday to setup Spec 3.0 meeting for next Wednesday, without host interaction.

Description

This workflow is responsible for handling setup of spec 3.0 meeting. It is supposed to be triggered by a person and requires an hour and date of the next meeting. So basically if this part should also be automated, we need another trigger on the workflow, schedule.cron. Just the thing is that in cron you cannot set "every 2 weeks", you can say every 1 day of the month and 15 day of the month. Then you need to set some starting date from which you need to count the date of next meeting.

In workflows you can have a step that had custom JS code where you can do the calculation. So in theory it is only required to edit this workflow, add step with custom script, and inspect event there, so in case workflow_dispatch, then just take user input, and if schedule event then do calculation. Then you set output for next step and consume it in existing step

[codesherpasrocks]

Hello @derberg! Would love to contribute to this issue. Will take a look to the PR you linked and come back with some questions/comments for clarification and alignment :)

[derberg]

Awesome, I'm all yours whenever you need help

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[derberg]

@codesherpasrocks are you still up for the task?

solution is:

• add new workflow that reacts on schedule event, and run once a week
• it figures week number even with custom JS script. Then https://github.com/asyncapi/community/blob/master/.github/workflows/create-event-spec-3-0.yml#L3 workflow should be triggered for next odd week. So let's say we have week 41, so the meeting must be scheduled for week 42.
• this https://github.com/marketplace/actions/workflow-dispatch could be used to trigger the other workflow with proper inputs

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️