Why Further Development on Publiccode.yml Is Necessary
Talkat Open Source Summit Europe 2025 · on Wednesday, 2025-08-27· at 14:10· Elicium 2A (Elicium Level 1)·
summary
European government catalogs (FR/DE/EU/IT) standardize on publiccode.yml but the schema treats only large applications and fails to describe APIs, components and modules; the Dutch developer portal already indexes about 3,000 repositories and plans an hourly scraper and a new public-first catalog. Proposed fixes include extending the JSON schema (make categories optional and add reuse/quality flags) and building a publiccode.yml bot that opens PRs with prefilled metadata to increase adoption.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:04Publiccode.yml standard
- 2:31COVID tracing challenges
- 7:12Dutch government portal
- 7:54Developer portal features
- 12:55Stop reinventing wheels
- 15:45Publiccode.yml limitations
- 19:39Further development needed
- 20:42Call to action
- 21:24Question and answer session
related talks
25mHelping public organizations collectively develop and maintain public code
05mHow the Standard for Public Code can help you collaborate over time & space
05mStandard for Public Code: Self Assessment
42mFederal Source Code Study: An Analysis of Publishing the People's Code
47mPolicing Open-Source Projects at Scale
47mThe Challenges of Public Code: Building an Open Source Culture at BBC
13mOpen Source Collaboration by Public Sector Stakeholders
28mCodeCommons_ Towards transparent, richer and sustainable datasets for code generation model training