Skip to content

City Chapters

City chapters are local hubs of the Flarehub network. They bring the global playbooks—bounties, Hacker Houses, meetups, and residencies—into specific cities.

Each chapter is led by a trusted operator who adapts the model to their local context while staying aligned with Flarehub values.

Who should start a city chapter

  • Stewards or high-XP Operators with a track record of shipped work.
  • People already convening builders or students in their city.
  • Contributors prepared to be accountable for budgets, events, and reporting.

Launch sequence

Use this path to go from "group of friends" to an official Flarehub [City] chapter.

  1. Informal nucleus
    • Start a small chat (Telegram/Discord) with 5–10 active builders or students.
    • Share upcoming Flarehub bounties, calls, and events.
  2. Pizza fund meetups
    • Apply for a small meetup budget (for example, around $200 equivalent for food and space).
    • Run a focused meetup: short talks, then co-working.
    • Log attendance, photos, and recap notes as proof-of-work.
  3. Global hackathon participation
    • Assemble at least one team to participate in a Flare or ecosystem hackathon.
    • Use local meetups and hack rooms to prep.
    • Ship a project and document the journey.
  4. Chapter application
    • Submit an application summarising:
      • Who is in the core team.
      • What you have already shipped (meetups, content, projects).
      • Your plan for the next 3–6 months.
    • Include links to proof-of-work and any Community GDP your group has generated.
  5. Recognition as "Flarehub [City]"
    • If approved, you receive an official chapter designation, public listing, and an initial quarterly budget.

Operating guidelines

City chapters are expected to:

  • Run a predictable cadence of meetups, hack rooms, or Hacker Houses.
  • Funnel local builders into global bounties, hackathons, and Fast Track.
  • Maintain basic reporting:
    • Attendance and scope summaries.
    • Community GDP estimates tied to local activity.
    • Retros highlighting what worked and what did not.

Budgets for chapters are typically tied to performance and GDP generation over time.

Relationship to governance

  • City leads are usually Stewards or high-XP Operators.
  • Chapters operate with local autonomy on tactics while staying aligned with core values and brand guidelines.
  • Budget decisions and major changes use the same transparent decision trails as other programmes.

A more detailed overview of the broader governance model lives in the governance section.

Disclaimers

  • Event frequency, budgets, and chapter structures may vary by region.
  • Local organisers are responsible for complying with venue rules, safety requirements, and local laws.
  • The "Flarehub [City]" label can be revoked if a chapter consistently misrepresents the brand or fails to report activity.

Next steps

  • If you already convene local builders, start logging your meetups as proof-of-work.
  • Once you have meetups and at least one shipped hackathon team, submit a chapter application.
  • If you are a Steward reviewing chapters, prioritise groups with clear artefacts and a realistic 3–6 month plan.