On Community Building ⚓
07 Feb 2026I’ve somehow been parts of lots of different communities at early stages. This includes:
- SDSLabs1, a student group in IIT Roorkee to promote building and shipping software.
- InfosecIITR, a security-focused student group in a similar vein. They have a fairly successful CTF team
- RFCs We Love, a meetup of technical standard enthusiasts, inspired by paperswelove. Now run by the India Internet Engineering Society.
- Hillhacks/Hackbeach, which I attended in 2015.
- Puzzled Pint Bangalore, the Bangalore chapter of Puzzled Pint - a global monthly puzzling event.
In the last 2 years, I’ve tried to bootstrap few more:
- Open Justice India
- 521ab, a Software Research group dedicated to interoperability research in India.
- Recursive Coworking.
Here’s some of the interesting2 things I’ve learned, especially from the last 2 attempts:
Cadence is your friend
The coworking meetup has been among my most successful attempts. It happens “every tuesday”, and that makes it very easy for everyone to both remember and schedule for it. I don’t think we’ve skipped a single Tuesday since I started it in August 2024, and the tuesday=cowork correlation is very strong in all who attend.
Avoid becoming another group chat
Sometimes, it is okay becoming a large group chat, but I find it more fun to create smaller and more engaged communities.
Every single one of your members has a dozen group chats on different messaging platforms that they are a part of. To meet your goal of remaining alive (and needing activity) even with a few members, you have a few pathways:
- Find the right people. If you find the right people in your small niche, they will stay engaged even with minimal activity.
- Force engagement (do regular calls, show&tells etc). If nothing organic is coming up, you can try a few different things, and try what works and what doesn’t.
- Do not create chat rooms unless you really need them. Splitting your discussions to topics is great if you need it, but too early means you lose spontaneity.
Seeding Communities
For the coworking meetup, as a Recurser, I used an existing community (RC friends I knew were in Bangalore) to show up first. It became an “RC+Friends” meetup as a result because we asked people to refer to someone else who might be interested.
Seeding works, because it lets you copy over a lot more than just people - it let us carry social norms, a code-of-conduct, and the “vibes” across.
Having an on-boarding plan
I’m always good at on-boarding people to events and communities, but it takes some work to make it something repeatable and reusable by anyone else. Another decision you should think about is how and where do you want to find your new members. For the Coworking meetup, relying on referrals turned out to be great. But for 521ab, as a private security community (with personal risk), I decided to share the burden of vetting people.
Share your workload
Find ways to reduce your work. Tell people what all you’re doing and see if others are interested in taking over some of those responsibilities. Ideally, you want to keep the things you do like, and find someone who likes doing the things you don’t.
For me - I love taking over “final-day” stuff. At the venue, on the call, running the event etc.
Make Showing up Easier
Find your community anchors (you’re one if you’re reading this), and make it easy for them to show up.
Having a cadence means you sign up for this in advance and it gets easier. Having physical events similarly makes it easier. But showing up in a chat room every day gets exhausting for me somehow - I still need to find ways to improve that.
Define your boundaries
A community exists as a combination of [people x space x interest]. Define the bounds in all 3. People is easy (you’re a member if you’ve shown up to a meetup, or joined a group, or subscribed to the mailing list). Interests are tougher - 521ab is a reverse-engineering community, but we allow anything-security-relevant. RFCsWeLove encompasses all sorts of standards (not just the IETF RFCs). And a coworking meetup has to be about more than coworking - lunch turned out to be our highlight.
Spaces was hard for me: Defining the space (A chat group) and what it can be used for can be fuzzy. For Coworking, I defined the “Community is whoever shows up on that Tuesday”, and that means explicitly not allowing chatter on the Signal group beyond Monday/Tuesday.
Find Audacious Targets
For InfosecIITR, I set a founding mission of “taking a team from IIT Roorkee to the Defcon World Finals”. For 521ab, we’re trying to reverse-engineer UPI. Setting far-reaching targets as your north star gives you a guiding star to decide if you’re on the right path.
Published on February 07, 2026