How ethereum/pm works
Project type and purpose
• This is primarily a documentation‐heavy “protocol meetings archive” repository with an embedded automation tool (“ACDbot”) under .github/ACDbot.
• ACDbot is a Python CLI application that fetches meeting metadata (from Google Calendar, Zoom, YouTube, etc.), processes transcripts and recordings, and publishes updates via GitHub, Discord, email, Telegram, Farcaster, Discourse, and an RSS feed.
• The rest of the repo is a static archive of Markdown meeting notes and process guidelines.
Top‐level components
• Orchestration (GitHub Actions workflows in .github/workflows)
• Application code (ACDbot Python package under .github/ACDbot/)
– cli.py (entry point)
– modules/ (plugin‐style modules for each external service)
– scripts/ (higher‐level scripts wiring modules to tasks)
– meeting_topic_mapping.json, pyproject.toml, requirements.txt (config & dependencies)
• Data storage
– Markdown meeting archives (e.g. AllCoreDevs-EL-Meetings/, AllCoreDevs-CL-Meetings/, Breakout-Room-Meetings/, etc.)
– processes/ docs
• External services
– Google Calendar API, Zoom API, YouTube API
– Discord (webhook), Telegram, Farcaster, Discourse, email SMTP
– RSS feed generator
Key interactions and data flows
• A GitHub Action (e.g. zoom-transcript-poll.yml, rss-feed-generator.yml, discord-notify.yml, etc.) triggers on schedule or issue events.
• The workflow checks out the repo and invokes ACDbot CLI or specific scripts/*.py.
• ACDbot loads configuration, then calls one or more modules:
• gcal to fetch upcoming meeting info
• zoom to poll recordings and transcripts
• youtube_utils to refresh/upload recordings
• transcript to assemble or clean text
• rss_utils to rebuild the public RSS feed
…and notifies channels via discord_notify, tg, email_utils, farcaster, or posts to discourse.
• After processing, ACDbot writes updated Markdown notes or metadata into the meeting‐archive directories and commits them back to GitHub.
• The workflow then pushes any changes back to the repository, automatically updating the static archive.
Architectural patterns and design principles
• Modular “plugin” architecture: each external service has its own module under modules/.
• Scripts orchestrate modules per task, but the core CLI can also be used interactively.
• Event‐driven CI/CD: GitHub Actions as the scheduler and orchestrator.
• Clear separation of concerns between fetching data, processing it, and publishing notifications or repository updates.