GNOME is made of three things:
All of these are important, and while we correctly celebrate the people who maintain projects, and the software they maintain, we often leave processes aside, and rely on wiki pages that haven't been updated in a decade, or oral histories of how to maintain a project.
In this presentation, I will outline what a maintainer does; shed some light on the process of maintaining a GNOME project; describe the best practices accrued over more than 20 years, as well as the known traps lying in wait. I will also try to establish how to improve those practices for the modern free and open source software development tools and infrastructure.
|Level of Difficulty