We now have a list of derivatives and some information about them. A list of derivatives hiding away in a corner of the wiki is not that useful. Better would be to aggregate the available information about derivatives and present it in Debian infrastructure in a way that makes the derivatives visible to Debian contributors and useful to them. Got an idea about how we can do that? Add it below!
The code being written to help integrate the census into Debian infrastructure is available in git under the deriv-team project:
git clone https://salsa.debian.org/deriv-team/census.git
The data output by the census code is available here:
The census code's README documents extensively how the codebase works.
Currently the census is only minimally used for integration of derivatives with Debian:
planet.debian.org/deriv: aggregates news feeds and developer blogs from Debian derivatives
Some information about derivatives has been manually integrated:
- PTS: contains information about Ubuntu bugs, version numbers and patches
- DDPO: contains information about Ubuntu bugs, version numbers and patches
- UDD: contains information about:
- packages from aptosid, skolelinux, Ubuntu
- bugs from Ubuntu
- popcon from Ubuntu
- website: contains information about some derivatives with a few links to the census
- debtags: imports packages from Ubuntu and allows them to be tagged
- screenshots: imports packages from Ubuntu and allows them to be screenshotted
Planet Debian derivatives
Aggregates all the developer and main blogs of all derivatives in one location on https://planet.debian.org/deriv/. The derivatives census scripts perform the following steps:
look for a logo (script)
find if there are RSS feeds on those pages (script)
download the logo (script)
generate a planet config snippet (script)
resize the logo into a head (script)
compare-source-package-list iterates through all the Sources files for a derivative, iterates through all the source packages, downloads source packages when needed, checks if they were ever in Debian and if they were not, applies some heuristics to figure out which Debian source package they were derived from, runs debdiff against the relevant packages and outputs some metadata.
The patches are linked from the patches panel of the Debian PTS, but not yet from the package tracker.
Aggregate all the derivative's sources.list snippets and integrate them into the following:
Link to the derivatives bug trackers from the PTS so that Debian folks can find potential problems in their packages. This might be hard since it can be rare for derivatives to provide mappings between a bug report and the source package it applies to.
Allow folks to upload screenshots for packages that are only in derivatives. This would rely on some way to differentiate between free and non-free sections in our derivatives, since screenshots.d.n does not accept screenshots for contrib/non-free.
Publish stats about dpkg vendors on the website and in the data exports.
Import popcon information from derivatives, present on the graphs and link from Debian graphs