Hackerspace Mumbai Events Archive

Canonical public archive for Hackerspace Mumbai events.

This repository is a permanent, open-source, community-maintained knowledge base for event details, agendas, speaker profiles, slides, demos, code samples, videos, resource links, recaps, and community contributions.

It is GitHub-native and designed for contribution through Pull Requests.

Events are moments.

Communities are journeys.

This archive preserves knowledge generated by the community. It does not manage event logistics.

Roles

System	Role
This repository (GitHub)	Canonical event archive: metadata, resources, speakers, recaps, community contributions
hackmum.in	Public presentation layer. Consumes structured metadata from this repository
Bethuya	Community operations: registrations, attendees, curation, capacity, notifications. Out of scope here

GitHub  = Community Archive
Hackmum = Community Website
Bethuya = Community Operations Platform

Repository structure

.
├── .github/                 GitHub issue forms, PR template, and CI
├── docs/                    Architecture, taxonomy, Phase 2 recommendations, and integration notes
├── templates/               Starter files for events, series, speakers, and community contributions
├── schema/                  Machine-readable event.yml contract
├── events/
│   ├── 2026/
│   └── 2027/
├── CONTRIBUTING.md
├── CODE_OF_CONDUCT.md
└── README.md

Single event

events/2026/2026-09-05-github-copilot-dev-days-mumbai/
├── event.yml
├── README.md
├── agenda.md
├── recap.md
├── contributors.md
├── media/
│   ├── photos/              Official event photography
│   ├── videos/              Official recordings and playlists
│   ├── social/              Official Hackerspace Mumbai posts
│   ├── cover.jpg            Primary event identity graphic
│   ├── banner.jpg           Optional secondary promotional banner
│   └── README.md
├── speakers/
│   └── <github-handle>/
│       ├── speaker.md
│       └── card.jpg
├── resources/
└── community/
    ├── photos/
    ├── notes/
    ├── stories/
    ├── highlights/
    └── social/

media/ is the canonical archive of official event artifacts maintained only by organizers and volunteers. It is consumed by hackmum.in for event galleries, past-event pages, social content, and recaps. Speakers own speaker-specific artifacts under speakers/<github-handle>/; attendees and community members contribute perspectives under community/. See Visual Assets Archival Standard and Community contributions.

Event series

events/2026/2026-02-mangaluru-dev-days-tour/
├── README.md
├── event.yml
├── stop-01-sahyadri/
├── stop-02-nmamit/
└── stop-03-...

Event taxonomy

Valid eventType values in event.yml:

Type	Typical use
meetup	Monthly gatherings such as #mumtechup
workshop	Hands-on sessions such as AI Workshop or Open Source Fridays
conference	One-off or multi-day conferences, including Dev Days
hackathon	Timed building events
community-day	Partner or community days
series	Multi-stop tours and regional initiatives
summit	Named summits

Unknown types fail CI. See docs/event-taxonomy.md.

Documentation

• Architecture and contracts
• Community contributions
• Event messaging (closing slides and follow-up email copy)
• Event taxonomy
• Phase 2 recommendations
• Bethuya integration notes (documented only)

Speaker workflow

Speaker submissions are conflict-free: each speaker only changes their own folder.

1. Find the event under events/YYYY/.
2. Create speakers/<your-github-handle>/speaker.md (optional card.jpg for the published speaker card; optional assets/ for session files).
3. Prefer links for slides, repos, and recordings.
4. Open a Pull Request that only modifies speakers/<your-github-handle>/**.

CI rejects speaker PRs that touch event.yml, README.md, agenda.md, recap.md, contributors.md, or another speaker's folder.

Ownership model

• speakers/ — speaker-owned artifacts such as profiles, cards, slides, repositories, and recordings.
• media/ — official event media maintained only by organizers and volunteers.
• community/ — attendee and community-contributed perspectives, including notes, stories, highlights, photos, and social links.

Community workflow

Attendees contribute photos, notes, stories, highlights, and social links under community/<type>/ using their GitHub handle. Links to public posts, galleries, blogs, and videos are welcome — no file uploads required. See Community contributions and CONTRIBUTING.md.

How to contribute

• Organizers: create the event folder, metadata, agenda, and empty community/ tree. See CONTRIBUTING.md.
• Speakers: add your session folder and resources.
• Community: add photos, notes, stories, highlights, and social links under community/; improve recaps and recognize people in contributors.md.

Please follow the Code of Conduct.

License

Content in this repository is licensed under Creative Commons Attribution 4.0 International (CC-BY-4.0).