How ampproject/wg-amp4email works
Project type and purpose
• This is not a runnable codebase or a full-stack application: it’s a coordination repository for the “AMP for Email” Working Group. Its primary goal is to host meeting agendas, status-update templates, issue templates, Code of Conduct, and to serve as the canonical place where the WG publishes its bi-weekly status updates and events.
File structure
• Top level:
• .github/ISSUE_TEMPLATE – Markdown files for “discussion,” “meeting-agenda-notes,” and “status-update” templates.
• CODE_OF_CONDUCT.md – The WG’s code of conduct.
• LICENSE.txt, METADATA.yaml – Licensing and repository metadata.
• README.md – An overview of the WG, its members, and communication channels.
• No source code or service definitions are present; instead, the repo produces and maintains documentation.
README for additional insights
• Describes the “AMP for Email” spec working group, members, and facilitator.
• Lists communication channels: GitHub issues (with templates), Slack, and a mailing list.
• Points external bug/feature tracking to the amphtml repository.
a. Main components
• Working Group (stakeholders)
• wg-amp4email GitHub repository (templates & status updates)
• amphtml repository (actual email spec)
• GitHub Issues & Pull Requests
• Slack channel (#wg-amp4email)
• Mailing List
• General AMP community / external collaborators
b. Relationships & interactions
• WG members use the repo’s issue templates to file status updates and meeting agendas.
• External contributors open spec issues in amphtml repo (not here).
• WG discusses in Slack; archives decisions in this repo and amphtml.
• WG sends announcements via mailing list; channels feedback back into GitHub issues.
c. Architectural patterns / design principles
• “Centralized coordination” pattern: this repo is the WG’s authoritative coordination hub.
• Separation of concerns:
• Spec lives in amphtml repo
• Coordination and status updates live here
• Communication via Slack and mailing list
d. Key technologies / platforms
• GitHub (repo, issue templates, issues/PRs)
• Markdown (templates and docs)
• Slack (real-time discussion)
• Google Groups (mailing list)