Welcome to the stats section. This is a huge attempt to get a full overview of IPv6 inside and outside Debian. The reason why I have spent time in building this is to drive people to better prioritize their IPv6 work. It is not meant to rule it of course, but Ivo Timmermans and I just saw that there was not much logic in the way packages have been uploaded/patched in Debian or here, often jumping from one class of packages to another. This is generaly an unstructured way of working. So the idea emerged to classify packages according to different criteria (or at least try). The first section is a global overview of the archives in terms of simple numbers. The second and the third are a more detailed output of the status. All stats refer to Debian sid/main only, though you might find some extra packages listed in the second section that do not belong to it.

1. Identify IPv6 packages to provide a structured analysis.
2. Prioritise list of packages.
3. Review enabled IPv6 packages.
4. Enable more IPv6 packages.
5. Provide the best IPv6 quality as possible to "main".

The statistics are dynamically generated. Click here to access them.

The system is based on a set of scripts that parses the entire Debian source archive in order to identify potential IPv6 packages and networking packages. In this way we isolate non networking from the networking packages and classify them according to their position in the archive (Priority/Section). The system in general is quite simple (in terms of logic flow) and modular (modules of any kind can be added at any time).
The automatic scan system run every day around 8:10 UTC and it performs all the checks it can. From updating the database of packages to check their source code. During this phase the database is locked in readonly mode and people will not be able to update status of packages. Looking closer to the statitistic in Section 2 are grouped all the packages that have a 100% known status. Clicking on a package will give a more detailed output as well the possibility to update its information and/or add, modify, remove comments. In Section 3 instead there are 3 lists of packages grouped by Priority/Section and their IPv6ness status is guessed. The scanning engine searches for several network keywords inside the code and try to guess the status. Clicking on packages in that section will provide a very detailed output of the matches the scan engine made inside the code. It is possible here as well to change the status of the package. Be careful not to change the status of a package only because it contains IPv6 keywords. The package must be tested. This system is here to be useful. DO NOT START PLAYING WITH IT. It is not a toy for people to fight their sexual problems or to escape their real life. Respect its contents and if something does not reflect your expectation discuss it on the debian-ipv6 mailing list.

Start by selecting a package following the suggested order from the drawing on the left.
Once you have done your choice you can follow 2 paths starting from the second drawing (Package Identification Process), that includes the third one as well, or from the third one directly (Quality check process). Every time you complete a package you will have to update the related entries via the web interface inside the results page.

Who did this crap?

Other than ik5pvx and me, the following people wast^H^H^H^Hspent their time:

• Ivo Timmermans
• Marco D'Itri
• Richard Foden

They have my eternal gratitude for all their suggestions, time and ideas.