Maintain-a-thon 2.0 at UN Open Source Week 2026

The Technical Maintenance track focuses on the day-to-day practice of open source maintenance work: how projects handle dependency updates and security patching, how release processes are structured, how difficult triage or community governance decisions get made. Using and contributing to Software Heritage Tackling Organizational Debt and Contributor Friction in Large FOSS Communities Governments, Open Source and Accessibility: Contributing to a Common Solution Trusted Publishing - Eliminating Credentials from Your Release Workflow The Vulnerability Flood: Open Source Security in the Age of LLMs Having a general interest in open source? What does it mean to maintain open-source software when the use of AI Tools is rapidly reshaping all aspects of software development, from writing code, documentation, and infrastructure to submitting and reviewing contributions? The Python perspective will ground the discussion in a concrete ecosystem experience: how increased report volume is affecting security teams, how teams are adapting, and where current processes are under strain. Groups will discuss possible responses, such as improving threat models, adapting security policies, reducing duplicate or low-quality reports, handling coordinated disclosure under new constraints, and tooling for triage and corroboration. In structured small-group work, you'll look at your own project through a shared set of lenses (community and group, the shape and legitimacy of authority, governance hygiene versus practice, and the gap between a project's reach and the hands that maintain it) and diagnose what it needs now, not what worked elsewhere.