Governance and Survival of a Hobbyist Open Source Project: The JabRef Story
MCLD 2002 | Fri 07 Aug 5:30 p.m.–6:15 p.m.
Presented by
-
Oliver Kopp
@https://mastodon.acm.org/@koppor
@koppor
https://www.inf.uni-hamburg.de/en/inst/ab/swk/team/kopp.html
Dr. Oliver Kopp is Acting Professor at the University of Hamburg, where he leads the Software Engineering and Construction Methods (SWK) group. He is an active open-source maintainer and contributor, best known in the community for his long-running work on JabRef, the open-source reference manager — including how the project is governed in practice, how responsibilities are distributed, and how contributors grow into maintainers over time.
Beyond JabRef, Oliver is active in the open-source adr community, where he co-developed the widely adopted Markdown Architectural Decision Records (MADR) format and its successor YADR, and he maintains the LaTeX Template Generator, a tool for producing robust, reusable LaTeX templates backed by GitHub Actions. His research focuses on software architecture and on making architectural decisions sustainable and usable in practice, spanning software engineering, business process management, and cyber-physical systems.
His industrial career includes a leading role in the BMWK-funded Software-Defined Car (SofDCar) project at Mercedes-Benz AG and a position at Nokia Bell Labs. He holds a PhD from the University of Stuttgart. Outside of work, he values spending quality time with his family.
Oliver Kopp
@https://mastodon.acm.org/@koppor
@koppor
https://www.inf.uni-hamburg.de/en/inst/ab/swk/team/kopp.html
Dr. Oliver Kopp is Acting Professor at the University of Hamburg, where he leads the Software Engineering and Construction Methods (SWK) group. He is an active open-source maintainer and contributor, best known in the community for his long-running work on JabRef, the open-source reference manager — including how the project is governed in practice, how responsibilities are distributed, and how contributors grow into maintainers over time.
Beyond JabRef, Oliver is active in the open-source adr community, where he co-developed the widely adopted Markdown Architectural Decision Records (MADR) format and its successor YADR, and he maintains the LaTeX Template Generator, a tool for producing robust, reusable LaTeX templates backed by GitHub Actions. His research focuses on software architecture and on making architectural decisions sustainable and usable in practice, spanning software engineering, business process management, and cyber-physical systems.
His industrial career includes a leading role in the BMWK-funded Software-Defined Car (SofDCar) project at Mercedes-Benz AG and a position at Nokia Bell Labs. He holds a PhD from the University of Stuttgart. Outside of work, he values spending quality time with his family.
Abstract
How does a project with no company behind it renew its maintainers and keep going year after year? JabRef has had to answer that question repeatedly over a history spanning more than two decades. It is a BibTeX-based literature management application written in Java, run entirely by volunteers, with more than 3,000 GitHub stars and over 500 contributors.
Much of the contributor base is short-lived: students and first-time contributors who arrive through university courses or events like Hacktoberfest, resolve an issue, and move on. Over roughly the past ten years, JabRef has built considerable infrastructure to make this work — structured onboarding, mentoring, curated issues, and cultural norms that keep the door open without overwhelming the core team. But turning any of these newcomers into lasting maintainers has proven rare. In practice, the project's durable maintainers came through other paths: Google Summer of Code, and a couple of contributors who simply stayed because they enjoyed the work.
We close with concrete lessons learned along the way — from GitHub workflows and onboarding practices to the structures that hold a volunteer project together — that those who maintain or study such projects can adapt to their own communities.
How does a project with no company behind it renew its maintainers and keep going year after year? JabRef has had to answer that question repeatedly over a history spanning more than two decades. It is a BibTeX-based literature management application written in Java, run entirely by volunteers, with more than 3,000 GitHub stars and over 500 contributors.
Much of the contributor base is short-lived: students and first-time contributors who arrive through university courses or events like Hacktoberfest, resolve an issue, and move on. Over roughly the past ten years, JabRef has built considerable infrastructure to make this work — structured onboarding, mentoring, curated issues, and cultural norms that keep the door open without overwhelming the core team. But turning any of these newcomers into lasting maintainers has proven rare. In practice, the project's durable maintainers came through other paths: Google Summer of Code, and a couple of contributors who simply stayed because they enjoyed the work.
We close with concrete lessons learned along the way — from GitHub workflows and onboarding practices to the structures that hold a volunteer project together — that those who maintain or study such projects can adapt to their own communities.