Why is the SailfishOS-OBS a crucial part of the larger SailfishOS-ecosystem.
This is a concatenated version of the pieces originally written by @piggz and @olf, see https://forum.sailfishos.org/t/community-meeting-on-irc-12th-may-2022/11334/7 and https://forum.sailfishos.org/t/community-meeting-on-irc-12th-may-2022/11334/10.
The SailfishOS-OBS is primarily used for application development/distribution, and device porting. These two different use cases have different sets of statistics.
Application development/distribution using the “SailfishOS:Chum” repository:
Hardware adaptation ports are typically subprojects of the “nemo:devel:hw” project on the SailfishOS-OBS. That project contains 102 device ports at the time of writing, though no claim is made for how active each is. I know of 2 other active ports which will arrive on OBS shortly, for a total of 104 device adaptations.
Storeman as the only maintained OpenRepos client app, depends on being built and distributed by the SailfishOS-OBS.
In detail: The Storeman Installer for initially deploying Storeman on a SailfishOS device and also Storeman’s self-updating mechanism relies on the SailfishOS-OBS for providing SailfishOS release version specific builds in order to support a wide range of SailfishOS releases. Hence the SailfishOS-OBS is necessary for building and distributing Storeman. Because Storeman is and has been the only maintained OpenRepos client app for long (many years), without it SailfishOS would lack an app for downloading, installing and managing RPMs and repositories from / at OpenRepos.
Summary / TL;DR
By shutting down the SailfishOS-OBS, both community app stores would become obsolete and cease to work: SailfishOS:Chum, because it directly utilises the SailfishOS-OBS for building and distributing the software it contains (point 1), and OpenRepos, because its only client app Storeman relies on being built and distributed by the SailfishOS-OBS (point 3).
Furthermore, most community ports of SailfishOS depend on the SailfishOS-OBS for their hardware adaptation (point 2). Switching off the SailfishOS-OBS means to discard more than 100 device ports (and additional ones in the pipeline)!
- Additional perspectives
- Jolla should consider which effects shutting down Jolla’s internal OBS would have (and using the SailfishOS-SDK instead for building SailfishOS and its core apps): It is the same for the community!
- This topic (need for the SailfishOS-OBS) has already been discussed in depth almost two years ago: A proper alternative to the SailfishOS-OBS needs to provide the mass-building for different SailfishOS releases, dependency management (e.g., for complex projects as Pure Maps) and distribution capabilities (of the built RPMs) to the same extent as the SailfishOS-OBS.
- These and some additional points have been brought up at the Community meeting on IRC 12th May 2022 in the general discussion, from 07:45 to 08:15.
@lbt intends to provide some access / download statistics for the SailfishOS-OBS.
We hope that depicting the vast value of the SailfishOS-OBS and the potential consequences of shutting down the SailfishOS-OBS is helpful for Jolla to consider maintaining it sustainably, because it has become a indispensable piece of the infrastructure for many third-party SailfishOS apps and most SailfishOS ports over the years.
Clearly denoting such a commitment would be much appreciated, because some tasks and actions using the SailfishOS-OBS were put on the hold due to its unclear future.