WMF is interested in having panels/dashboards displaying data only for a subset of code repositories, namely those ones deployed on the WMF servers.
This subset list should be defined in an external source to reduce maintenance costs (do not manually update yet another list).
The long-term goal is to add a "default" view filter to display data only for WMF-deployed repositories in panels/dashboards on https://wikimedia.biterg.io.
Bitergia can add metadata for repositories, to use that later with a filter.
Per the discussion at FOSDEM 2025 between Santiago, Luis and @Aklapper:
Could WMF's CI/CD create another file which follows Bitergia's schema (and then potentially commit that into Bitergia's repository)?
Bitergia's schema is still the same format as the (nowadays unused and outdated) file https://gitlab.com/Bitergia/c/Wikimedia/sources/blob/master/projects.json .
- This overlaps strongly with / may be a subtask of T190891: Develop canonical/single record of origin, machine readable list of all repos deployed to WMF sites.
- Similar requests have been made before, e.g. filtering data for MW extensions deployed on WMF servers
- This ticket likely supersedes my idea in T146135: Exclude upstream repositories in the default view in development metrics (by setting up "Projects" once Bestiary is available?).
- Currently Bitergia's schema is non-public; there are ideas to allow changing it via the API and have it public in the future.