More than an event : How Academic OSPOs build better Hackathons
Introduction
Hackathons have long been a fixture of university life but academic Open Source Program Offices (OSPOs) are transforming them into something far more purposeful. Across CURIOSS member institutions, OSPOs are designing and facilitating hackathons that go well beyond a weekend of competitive coding. At their best, these events are strategic tools for skills development, community building and open source sustainability. They also have the potential to foster external partnerships that benefit universities long after the final pitch ends.
This article draws on a suite of new CURIOSS patterns and insights from a recent CURIOSS Deep Dive on Reboot the Earth — a global social coding initiative run in partnership with the United Nations — to explore how academic OSPOs are leveraging hackathons to advance their open source mission.
The OSPO Advantage: A Unique Convening Role
An OSPO is particularly well-placed to run or support hackathons because of its cross-cutting position within a university. Unlike a single department or student club, an OSPO has relationships across its institution with faculty, student organizations, IT teams, communications departments, research centers and senior leadership. This makes it an exceptionally effective hackathon coordinator. The Organize an Open Source Hackathon pattern captures this multi-stakeholder reality in detail. Identifying internal partners is one of the critical early steps and the OSPO is uniquely positioned to make those connections happen quickly.
This coordinating capacity also extends outward. The University of California OSPO Network and the Carnegie Mellon University OSPO found that one of the most valuable things an OSPO can offer is its ability to connect students and faculty to a wider network including, as demonstrated through Reboot the Earth, the United Nations and its partner organizations. This level of ‘reach’ is difficult for any single department to replicate.
For OSPOs that are newer to hackathon organization, engaging an experienced external facilitator is another way to leverage this convening role without being constrained by limited in-house expertise. The Engage a Hackathon Facilitator pattern describes how industry partners or professional facilitators can provide end-to-end structure and lead on delivery while allowing the OSPO to focus on what it does best: bringing together the right people, managing institutional relationships and ensuring the event serves participants well.
Over time, each facilitated hackathon builds internal capacity, so that OSPOs develop their own facilitation expertise and become progressively less dependent on external support.
Building Open Source Skills and Culture — From Beginners to Experienced Contributors
CURIOSS members’ hackathons regularly build in introductory workshops to open source and to embed good open source practices into the fabric of events from the outset. This approach does more than support skills development. It creates a grounded understanding of what good open source contribution means in practice and also leads to greater inclusion of more diverse participants.
The Lower the Barriers to Entry for Student Hackathons pattern addresses this directly. Pre-event workshops covering tools such as GitHub, Python and Jupyter Notebooks help less experienced students get up to speed before the hackathon begins. Framing these sessions as “optional but useful” signals that participation is genuinely open to all skill levels without implying any deficit.
The University of Texas OSPO has embedded this approach into its regular practice — offering pre-training on GitHub and Jupyter Notebooks ahead of each hackathon and providing dedicated mentor training to support students working at different levels of experience.
The Design a Collaborative Open Source Hackathon pattern makes the case for shifting away from purely competitive formats altogether. Cash prizes can intensify competition in ways that deter experimentation and collaboration — a critical feature of open source. The pattern recommends rewarding good open source practices such as documentation, testing, licensing, community building and accessibility as highly as technical output, both in the judging criteria and in the event’s culture.
CURIOSS members all agreed that replacing or supplementing cash prizes with participation prizes, mentorship opportunities or recognition for good open source practice (e.g. best use of documentation, best community engagement or best research advancement) creates a richer and more inclusive learning environment.
The George Washington University OSPO’s approach to the annual GeorgeHacks Innovation Hackathon exemplifies this. Teams who made their projects open source and followed explicit guidelines (e.g. sharing code on GitHub and applying an appropriate license) qualified for a dedicated $500 open source spot prize.
One of the recurring themes across CURIOSS members’ hackathon experiences is intentionality around inclusion. Competitive hackathons can inadvertently exclude students who are newer to programming or unfamiliar with open source practices. Members noted that pre-training workshops and a collaborative focus can reverse this trend. Members also noted that collaborative hackathons tend to attract more diverse participant cohorts, including more women.
Embedding Wellbeing and Safety
Multi-day hackathons introduce responsibilities around participant welfare that academic OSPOs take seriously. The Embed Wellbeing into Student Hackathons pattern provides a framework for designing safety and wellbeing into the event from the planning stage, rather than leaving it to chance.
Core recommendations include establishing a clear position on sleep as a non-negotiable requirement for participation; ensuring food, snacks and water are available on-site throughout the event to eliminate the safety risk of participants making food runs alone at night; providing explicit guidance to mentors on the hackathon’s approach to wellbeing; and appointing a dedicated welfare support person whose sole responsibility is to monitor and support participant welfare. Where minors participate, additional coordination with campus risk management teams is essential.
CURIOSS members’ practice of intentionally caring for participants distinguishes well-run academic hackathons from events that can leave participants exhausted and disengaged.
Promoting Open Source Sustainability
A recurring challenge with hackathons is what happens after the event ends. Prototype projects that excite participants and judges on the day often fade away within weeks. Academic OSPOs are developing strategies to address this and to use hackathons as a vehicle for promoting the open source practices that support sustainable contribution.
Rather than treating the hackathon as a self-contained event, Reboot the Earth offers winning teams follow-on supports to develop their solutions and think beyond the immediate prototype. In 2024, more than 60 Salesforce employee volunteers mentored winning teams in this way. In 2025, the organizers explored voluntary cross-location pairing, connecting winning teams from different countries to combine perspectives and scale impact. This model offers a compelling example of how hackathons can be designed from the outset with sustainability in mind — not as an afterthought.
Where projects are extensions of existing campus research, there is also potential for hackathon contributions to feed directly into live open source projects. The Design a Collaborative Open Source Hackathon pattern recommends working with existing campus open source projects as a default where possible, with project maintainers labelling beginner-friendly issues in advance and being present to support participants. This approach grounds hackathon activity in real-world open source contribution rather than greenfield projects that are likely to be abandoned.
The OSPO as Advocate and Enabler for Student-Led Activity
One of the most distinctive contributions an OSPO can make is enabling students to lead and organize their own hackathons. This applies as much to smaller, focused student club events as it does to full-scale hackathons.
The UC Santa Cruz OSPO observed that co-hosting one-off events can be a valuable and a low-pressure first step for student groups that are new to open source. The Co-hosting Student Events pattern captures this lighter-touch approach. This approach distributes the organizational workload effectively with a clear division of tasks between OSPO staff and student co-organizers. The OSPO manages venues, sponsorship and formal promotion while students handle peer advertising, social media amplification, event set-up and facilitation. This allows both parties to contribute based on their comparative strengths.
The Enable Student-led Hackathons pattern addresses the ways in which OSPOs can support more experienced student groups to run larger events. In these cases, the OSPO can provide valuable support in accessing funding; navigating administrative processes; negotiating with external sponsors; and establishing contractual agreements.
CURIOSS members all agreed that student organizers need an advocate. At CMU, the OSPO may provide support in a number of areas, including managing contracts and memoranda of understanding with external partners; acting as the institutional representative in sponsor negotiations; and facilitating peer-to-peer leadership training by connecting student organizers across different hackathon groups.
At the annual GeorgeHacks event, students retain full ownership of the event with the George Washington University OSPO co-sponsoring their annual Innovation Hackathon and co-designing the open source prize track.
Structuring Effective External Partnerships
External partners such as technology companies, nonprofits and government agencies can dramatically enhance the quality of a hackathon by providing real-world problem statements, specialized tools, technical mentors and prizes. Engaging external partners also introduces coordination considerations that are worth planning for carefully - particularly where partners bring established playbooks that may need some adaptation for the university context.
The Collaborate with External Partners on Open Source Hackathons recommends establishing the OSPO as the central coordination point through which all parties - external sponsors, faculty and student groups - interact with one another. Clarity on roles, responsibilities and decision-making authority should be established before the event, not negotiated on the day under time pressure. A shared run-of-show document, circulated with enough lead time for all parties to engage with it, is highlighted as an essential tool.
The pattern also draws an important distinction between partners who have a well-developed facilitation playbook and those who are newer to hackathons. In both cases, the OSPO’s role is to ensure that partner contributions serve participants rather than primarily showcasing the partner organization.
It was also observed during the Reboot the Earth Deep Dive that bringing in the right local partners can be genuinely transformative. The theme for University of California, Santa Cruz Reboot the Earth hackathon was addressing wildfires. The presence of CAL FIRE (California’s state fire agency) at the hackathon gave participants direct access to fire chiefs and firefighters. The availability of firefighting expertise grounded the participants’ technical solutions in a way that no workshop or lecture could replicate. This on-the-ground authenticity also opened longer-term doors: the relationship with CAL FIRE has continued beyond the hackathon itself.
The Strategic and Reputational Opportunity
The value of hackathons for academic OSPOs extends beyond the immediate learning and community outcomes. Well-designed hackathons with high-profile external partners or real-world relevance generate significant visibility for both the OSPO and the university.
For the participating universities, University of California, Santa Cruz and Carnegie Mellon University, association with a globally recognized UN initiative and focusing on the UN Sustainable Development Goals, positions them as leaders in open source for social good.
Even without UN-scale partnerships, the reputational benefits of hosting a well-run open source hackathon are meaningful. Industry partners who contribute problem statements, mentors or prizes develop a firsthand understanding of the talent coming through a university’s programs. Hackathons also offer partners such as government agencies and nonprofits an opportunity to build ongoing relationships with university researchers.
For internal stakeholders, a successful hackathon with clear open source outputs provides concrete evidence that helps OSPOs demonstrate their value to senior leadership.
Conclusion
The patterns and experiences shared by CURIOSS members show that the OSPO’s role in the hackathon space is genuinely distinctive. As conveners, OSPOs can bring together students, faculty, industry and government partners around shared open source challenges in ways that no single department could manage alone. As advocates, they can ensure that student organizers have the institutional backing they need to run ambitious events. As hackathon designers, they can make the structural choices — collaborative formats, open contribution tracks, wellbeing provisions, sustainability planning — that determine whether a hackathon leaves a lasting impact or fades with the weekend.
In terms of partnerships, the OSPO approach to collaboration offers a compelling model of what is possible in terms of real-world problem solving, building external relationships and showcasing the role that universities play in creating social impact.
Acknowledgements
These CURIOSS patterns and insights were developed through collaboration between CURIOSS members and were enriched by the CURIOSS Deep Dive, ‘Reboot the Earth – Social Coding Events’ with the United Nations Office of Information and Communication Technology.
Many thanks to: Angela Newell (University of Texas OSPO), David Lippert (George Washington University OSPO) Emily Lovell (UC Santa Cruz OSPO), Laura Langdon (UC OSPO Network), Omar Mohsine and Mithusa Kajendran (UN OSPO, UN Office of Information and Communications Technology) and Tom Hughes (Carnegie Mellon University OSPO).
Photo by algoleague on Unsplash
A note on AI use: In addition to working from Deep Dive transcripts and capturing learning from our community discussions, this article was drafted with the help of AI. As a small organization, tools like this help us turn rich conversations into written resources without losing the ideas along the way. As always, there were plenty of human eyes reviewing, editing and improving the content before this article made it to publication. Thanks go to our community for the insights. If you do spot any errors, please let us know so we can correct them!