How to find collaborators for a side project

A collaborator needs to understand both the purpose and the starting point. Link to a project page, demo, screenshots, or a repository that they can inspect. Explain the problem in ordinary language and identify what is currently blocked.

“Help build the future of local events” is difficult to act on. “The event list works, but we need help testing whether people can find events near them on mobile” gives a potential contributor something to assess. Prepare the project page before sending people to it.

Write down these details before asking someone to join:

• Purpose: the person and problem the project serves.
• Current state: what works and where to see it.
• Help needed: a task and the skill it calls for.
• First result: what a finished first contribution would look like.
• Commitment: the time you can each offer and any timing constraints.
• Working arrangement: whether the contribution is voluntary or paid, without implying either by omission.
• Coordination: who reviews the work, where you will communicate, and how you will credit contributions.

For example: “I have a working event-list prototype. I’m looking for someone to review the mobile filters and send annotated screenshots. This is a voluntary one-off review; I can answer questions this weekend and will credit the contribution with your permission.”

Share the brief alongside your project’s description or an update, then link to it when introducing the work in the community. The community contact page provides a route to Naglasúpan’s discussion channels. Follow the expectations of whichever space you use.

Invite questions and make it easy to decline. Avoid sending a generic recruitment message to every creator in the directory. If someone has relevant work, mention the specific connection and ask whether they would like to discuss the task. A directory listing alone does not mean someone is available for collaboration.

Agree on the deliverable and review process before work begins. After the first task, discuss what went well, what was unclear, and whether both people want to continue. Update the brief if the scope changes.

Keep access and responsibility proportionate to the task. Record important decisions somewhere both contributors can find them, and agree on how to hand work back if either person needs to stop. The first-contribution checklist can help the new collaborator prepare a clear handoff while you make time to review it.