nodejs
Admin Access: Google Calendar / Google Drive for `create-node-meeting-artifacts`
I'm helping @mhdawson with the transitioning for create-node-meeting-artifacts and updating/refactoring the code so that it can work on GitHub Actions and with modern dependencies / outside of Michael's machine.
Hence I need access to Google Cloud, for the time being to generate a new set of tokens for the transition (and local testing)
I'll be (as a CPC Voting Member) bringing this to the Foundation Staff so we can transition these accounts/resources to LFX/Linux Foundation IT.
cc @nodejs/tsc @mhdawson
On top of migrating to GHA, we should probably also consider migrate to hackmd.io, Google Docs is just not great when it comes to markdown.
I think to start no special priviledge is required to access the google calendar as the tool only reads a public calendar.
Access to the repos in which issues are create will be needed, but to start it should be possible to experiment by creating issues in a repo you already have access to.
I'm happy with whatever. If we want HackMD I need instructions on how to make the script actually be able to create documents there.
We would need an OpenJS account there then, so it can create such documents (and probably a token)... What concerns me is collaboration and pricing. How would pricing work?
There's a free open source alternative to this HackMD: https://hedgedoc.org/
FYI @nodejs/tsc Ive reached out to the team at HackerMD, they're happy to support us for free with an open source license of their service. I'll add @mcollina to the e-mail and @bensternthal
Hi @nodejs/tsc / @mcollina our updated Bot for creating meeting artifacts is LIVE ✨
Example run:
- https://github.com/nodejs/TSC/issues/1788
- https://hackmd.io/@openjs-nodejs/BkcXA9Osxg
We created this GitHub App specially for this: https://github.com/apps/openjs-meetings-bot
@mhdawson I believe you can finally sunset your local CRON job🙏
Example run:
* [Node.js Technical Steering Committee (TSC) Meeting 2025-09-24 TSC#1788](https://github.com/nodejs/TSC/issues/1788) * https://hackmd.io/@openjs-nodejs/BkcXA9Osxg
The hackmd.io link returns a 404 error page.
Example run:
* [Node.js Technical Steering Committee (TSC) Meeting 2025-09-24 TSC#1788](https://github.com/nodejs/TSC/issues/1788) * https://hackmd.io/@openjs-nodejs/BkcXA9OsxgThe hackmd.io link returns a 404 error page.
It is probably limited to registered users only. Works for me 👀
Nevermind, I deleted the file there, that's why, as it was a test issue generation. I also believe https://github.com/nodejs/TSC/issues/1788 should be deleted.
Can the org be called nodejs instead of openjs-nodejs to match the github org? Alternatively it can openjs if it's shared with multiple projects.
BTW the automation works fantastically. Is it possible to automatically land them on the project? (But I can easily script that).
Can the org be called
nodejsinstead ofopenjs-nodejsto match the github org? Alternatively it canopenjsif it's shared with multiple projects.
Nope. There is one already named nodejs from some random user at their platform. Our agreement with HackMD will have all our teams be prefixed with openjs-. But we have an agreement that allows all projects @ OpenJS to have their dedicated space ✨
BTW the automation works fantastically.
You can manually trigger it on https://github.com/nodejs/create-node-meeting-artifacts/actions/workflows/create-meeting-artifacts-manual.yml by clicking on "Run Workflow" and select the Meeting Group. It also runs on a scheduled manner weekly.
Is it possible to automatically land them on the project?
Not sure what you mean by this? 👀
Not sure what you mean by this? 👀
Having the minutes automatically dumped into a repository via a PR the day after the meeting.
Not sure what you mean by this? 👀
Having the minutes automatically dumped into a repository via a PR the day after the meeting.
We can do that. Can you open an issue on create-meeting-artifacts repo?