The concept designs are a set of technical documents covering many aspects of the project, written through the history of the project, taking into account the status of the project at that time. These documents cover topics that have been researched but not necessarily implemented in Apertis at the time of writing.

Information in these documents may be outdated, but nonetheless provide important context for the decision making process and overall vision of the project.

Scancode evaluation

Posted on 2024-04-10

Currently, scan-copyrights (which uses licensecheck under the hood) is used in Apertis to scan copyright/license notices. This tool has some downsides, thus we are evaluating to use scancode-toolkit instead. A comparison of licensecheck vs scancode is available on the ScanCode’s website, TL;DR: scancode is more accurate but slower. scancode-toolkit has an option to export results as DEP5 format (see GH#472) which is the format currently use by Apertis license tooling. That means, scancode-toolkit is potentially compatible with the rest of the Apertis licensing tooling. [Read More]

Evaluation of PipeWire with JACK clients

Posted on 2023-11-16

PipeWire is de facto the new audio server used by all major Linux distributions (including Debian and Apertis). It provides a low-latency, graph-based processing engine on top of audio and video devices that can be used to support the use cases currently handled by both PulseAudio and JACK. The goal for this task is to evaluate PipeWire in known problematic use-cases with JACK, primarily in supporting multiple audio streams and dynamic switching between them between outputs. [Read More]

Apertis test strategy

Posted on 2022-05-09

Apertis is an Open Source project which consists of multiple parts that are reflected in the current structure of Apertis Gitlab: Packages as the fundamental building blocks of the images Infrastructure to provide the tools and automation to build the images Tests which ensure that Apertis provides high quality standards This structure also shows that tests are one of the pillars of this distribution. The QA process takes advantage of the tests to confirm that the behavior of each component is the expected one. [Read More]