Skip to content

Clubs first quarter m3

Month 3: Specialisation and Showcase

Month 3 is where depth replaces breadth. Your most engaged members are ready for real contributions. Your job is to create the conditions for those contributions, celebrate them publicly, and use them to build momentum into the next quarter.

Step 5: Launch Real Contributions

The defining shift in Month 3 is moving from learning about open source to actually contributing something. The bar here is intentionally low. Contributions do not need to be national or international in scope. Anything that creates something real, that someone else can use or build on, counts.

What a real contribution can look like per track:

  • Technical: a pull request to any open-source project (a documentation fix, a test, a small bug), or a script or tool built for your college community and published openly
  • Localisation: translating your college website, tech fest website, or a club resource into a regional language and publishing it either on the official website or on your wiki
  • Policy: a structured discussion among club members on a digital rights topic, with notes written up and posted on the forum for others to read and respond to
  • Design: a set of reusable design assets (icons, templates, branding elements) published under an open licence, or a UX study of a tool your community uses with findings posted publicly
  • Mapping: completing the OSM map of your campus or a nearby area that is missing from the map

The point is that it is public and reusable. Someone else should be able to find it, use it, or build on it.

A note on scope: Starting local is not a compromise. Mapping your campus accurately, making your college website readable in your mother tongue, or publishing a plain-language summary of a policy that affects your community are all genuinely valuable contributions. The FOSS ethos is about building in the open, wherever you are.

Step 6: Host a Showcase Event

Plan a closing event for the quarter where members present what they built, contributed to, or learned. Keep it informal: lightning talks of 3-5 minutes per presenter. Make it explicit that showing a work-in-progress is perfectly acceptable.

This event:
- Gives contributors a deadline and a stage
- Attracts new members who missed earlier events
- Generates content for future promotion
- Creates a shared sense of accomplishment that retains members

Encourage everyone to write a blog post about what they worked on, even if it is short. A few paragraphs about what they tried, what they learned, and what they would do differently is enough. Publish these on your club wiki, a personal blog, or Dev.to. The FOSS United team cross-posts member blogs on the FOSS United website, so good write-ups get wider readership than just your campus audience. Share your posts on the forum thread and tag the FOSS United community.

Step 7: Conduct a Quarter Review

Hold a structured retrospective with your core team and the FOSS United team. A simple three-column format works well:

What Worked Well What Did Not Work What We Will Change
List 3-5 things that went as hoped List 3-5 things that fell short One concrete improvement per item

Share the retrospective notes with all members, not just the leadership team. Transparency builds trust and signals that this is a club that takes its own improvement seriously.

Step 8: Plan Quarter 2

End the quarter with a public-facing plan for what comes next. A rough event calendar and a stated focus for Q2 is sufficient.

Questions to answer before closing Q1:
- Which tracks will you continue, drop, or add?
- Are there any major FOSS events (conferences, release cycles, hackathons) to organise around?
- Is there any infrastructure that needs investment?

Month 3 Checklist

  • At least one real contribution per active track completed and published
  • Showcase event planned, promoted, and held
  • Members encouraged to write blog posts about their contributions
  • At least one blog post by a club member submitted to FOSS United for cross-posting
  • Quarter retrospective completed with core team
  • Retrospective notes shared with all members
  • Q2 event calendar drafted and published
  • Wiki page updated with Q1 highlights and Q2 plans
  • Team registry updated with new members and alumni