-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meeting setup automation [working PoC] #100
Comments
one other common thing is to create a google doc for the meeting minutes. I have this project that could be used to upload the doc once created: https://www.npmjs.com/package/google-drive-wrapper |
In terms of hosting the hangout, it would be good to create the hangout in advance so that it is visible, also those links needs to go into the item/minutes doc so would be good to automate creation of that as well |
Its been mentioned a few times that automating the generation of meeting artifacts would be a great help, its just that nobody has had time to get to it yet. |
I should have said, not specific to diagnostics but across all of the WG/teams. |
Sounds like something I could do one summer weekend. |
You would make a lot of people happy :) |
@mhdawson is it mandatory to use google docs? could it be hackmd.io instead? |
I published v1 of the script with minimal functionality of creating the markdown for agenda and minutes. https://github.com/naugtur/wg-meeting-cli Questions:
|
Is there anything left to be done here? /cc @naugtur @mhdawson @mike-kaufman |
@mhdawson has meeting auto-scheduling working (using github.com/mhdawson/create-node-meeting-artifacts/) so I think this can be closed. |
Closing. Feel free to reopen if you feel there's anything left to be discussed |
Inspired by #96
@joshgav If you could add to the list of things you do to host a meeting, we could automate that a bit or at least anybody could take over without thinking if they didn't miss anything if we had the list documented.
Meeting prep:
I would look into automating some of it.
The text was updated successfully, but these errors were encountered: