Meeting Bot

[Stebalien]

I'd like a meeting bot (github action) that manages everything around taking meeting notes. This bot would be configured through issues labeled "call".

Setup

• Each meeting would have an issue labeled call.
• The issue body would describe the call and include machine readable metadata indicating:
  • The zoom URL.
  • The meeting schedule. Linking to an ical calendar would be even better.
  • The meeting notes template (stored in this repo).

4 days before the meeting

The bot will:

1. Read the template from this repo.
2. Create a PR from this template.
3. Add a comment to a running issue about the meeting issue linking to both the zoom room and to the PR.
4. Link the PR back to the issue comment.

Meeting participants would then push agenda items to this PR.

1 day before the meeting

The bot will:

1. Create a hack pad (hackmd.io) or some kind of cooperative notepad from the open PR.
2. Comment on the PR indicating the open HackMD (future: maybe temporarily protect the branch? I'd like to avoid conflicts once the HackMD is live).
3. Optional: Link to the HackMD from the meeting issue comment as well.

1 hour after the meeting.

The bot will:

1. Retrieve the content from the HackMD if nobody is editing it (should be possible to tell?).
2. Commit the content to the in-progress PR. If the PR body has changed, the bot should make a PR against the open PR.
3. Remove the HackMD link from the meeting issue comment.
4. Maybe replace the HackMD text with a link to the meeting PR?

At any time

• Users should be able to reschedule a meeting by editing the meeting issue body.
• Authorized users should be able to reschedule/delay a specific meeting by commenting on or closing the meeting PR.
  • @ipfsbot reschedule ...
  • @ipfsbot cancel ....

[willscott]

is there a reason to only open the HackMD 1 hour before the meeting?

[Stebalien]

is there a reason to only open the HackMD 1 hour before the meeting?

I was thinking people would commit updates to the PR, but that's probably going to cause a bunch of conflict issues. We should probably open the HackMD a day in advance.