MeetaDev

Networking for DevFest & GDG events.

Organisers create a space for their DevFest or GDG event. Attendees join it with a link or code, check in at the venue, and swipe through the people who are there (mentors, learners, people hiring, future co-founders). When two people both tap Meet, they can chat, find each other, and both tap We met.

Ayo, the buddy, guides people through a 7-step, Duolingo-style onboarding, suggests matches, and reacts as you go.

The core loop

Everything is built from five primitives. A new feature should be one of these, or read them back; it shouldn't add a second way to do the same thing.

Primitive	Stored as	Rule
Person	profiles	One badge, reused at every event.
Here	event_members.checked_in_at	For now, joining an event is enough (CHECKIN_REQUIRED is off). With CHECKIN_REQUIRED=1: set by scanning the event's check-in code (/e/<slug>/checkin?k=…), shown only at the venue; lasts for that day (Lagos time), and only on the event's date when it has one.
Want to meet	a pending row in connection_requests	One-way and private: never shown or sent to the person it's about.
Connection	the same row, accepted	Both want to meet. The only moment anyone is told. Unlocks chat and contact details.
Met	a meetings row from each person for the same event	Each taps We met; it counts once both have, at an event both are here at that day.

The deck's Pass (passes) only hides someone from your deck at that event. "Your people here" is Here plus Connection: nothing extra is stored.

The one number: of the matches made at an event, how many became meetings.

For organisers

• Only approved GDG organisers can create events. At /events/new, anyone else sees an application form (chapter name, their chapter's page on gdg.community.dev, city). A platform admin reviews it at /admin.
• Create an event once approved: name, city (required), date, welcome note. The creator becomes its organiser.
• Show in "Find events" (on by default): people who follow the event's city see it at /discover.
• Invite people: an invite link (with the join code built in), a QR code, and a 6-character join code. "Show on screen" opens a full-screen join slide for the projector.
• Check-in code (only when CHECKIN_REQUIRED=1): a second QR, for the venue only (posters, the welcome screen: "Show on screen" opens /e/<slug>/screen?show=checkin). Scanning it is what makes someone here, and only people who are here show up in the deck. "Make a new code" stops the old one working.
• Joining is open: anyone signed in can join from the event page. The invite link and code are shortcuts, not a lock. "Make a new code" stops the old code working.
• Dashboard at /e/<slug>/manage: the funnel (joined, here, swiped, matched, met), reports, members with when they checked in and how many people they've met, filterable to who's here.
• Members: make co-organisers, remove someone (they can rejoin), or ban them from the event.
• Reports filed by people at your event land in your dashboard.

Communities

• Communities (GDG chapters, GDG on Campus / student clubs, Women Techmakers, other developer communities) each have a public page at /c/<slug> with their upcoming events, listed in the sitemap.
• Organisers search the list when applying and pick their community. If it isn't listed they add it (GDG chapters must link to their gdg.community.dev page); it goes live when an admin approves the application.
• Events can be linked to a community the organiser runs, and show "Hosted by …".
• Attendees see "Communities in your cities" on Find events.
• Bulk import: on /admin, paste one community per line: name, type, city, country, link (commas or tabs, straight from a spreadsheet). Re-importing updates instead of duplicating. Template: docs/communities-template.csv.
• There's no automatic import from gdg.community.dev: its robots.txt disallows /api/ for crawlers.

For admins

• Admins are set with ADMIN_EMAILS (comma-separated Google emails) in the environment. Nobody can make themselves an admin from inside the app.
• /admin: approve or decline organiser applications, add an organiser by email, or revoke someone's right to create new events (their existing events stay).

This is the beginning of the README. Read the rest at the original. Read the full README ↗