Add your name/nick using the template below to suggest a topic.
Indicate how much time you’ll need so we can time-box the meeting accordingly.
Please be as thorough as you can with your question/topic.
If you can’t make the meeting please ask and name a substitute.
It is expected that you show up and present your topic, or name a substitute and make sure they attend in your absence. These IRC meetings are for real time participation and live discussions, otherwise you can post the topic on here and get responses that way.
We need you to be present to clarify details in the topic, and to ensure the discussion is leading to the answers you are looking for! If you do not participate or your question/topic isn’t clear enough it will be postponed. Also: always ask for more time than you anticipate your topic needs!
Please have your topics ready at least 3 days before the meeting so we can prepare good answers. Topics announced afterwards will be postponed to the next meeting.
Template for topic proposal: (post your topic proposals as comments to this forum topic).
* Name/IRC nick:
* Topic:
* Some details about the topic:
* Approx. time needed:
* Substitute (optional):
Some details about the topic: We are getting close to the anniversary of the announcement regarding community OBS (Community OBS - Refurbished and re-floated). As the commitment by Jolla was made for a year, it would be great to hear what are the plans regarding OBS.
Approx. time needed: 10 min
Substitute (optional): I doubt I can make it to the meeting. Please reply and I am sure there will be others who can fill for me regarding discussion on the topic. Hopefully, @piggz can attend.
OBS is primarily used for application development/distribution, and device porting. These two different use cases have a different set of stats.
Application development/distribution using the “chum” repository:
At the time of writing, chum contains 215 packages, built for 10 Sailfish releases over 3 architectures.
Currently, the latest aarch64 repository contains 622 unique binary packages
Developers have contributed a wide range of packages to chum, with many abandoned apps being revitalised within the chum github repository at SailfishOS:Chum community · GitHub. 62 repositories have been created for either abandoned apps, or as packaging repositories for existing linux tools under the chum organisation. For those at Jolla who may not be clear as to how Chum operates, there is extensive documentation at GitHub - sailfishos-chum/main: Documentation and issue tracker for the SailfishOS:Chum community repository.
Hardware adaptation ports are typically subprojects of the “nemo:devel:hw” project on 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.
As the current Storeman maintainer, I would like to add another point to the list @piggz started, why the SailfishOS-OBS is crucial and indispensable:
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 crucial and indispensable for building and distributing Storeman. Because Storeman is the only maintained OpenRepos client app for long (many years), without it SailfishOS would lack a client app for downloading, installing and managing RPMs and repositories at OpenRepos.
Summary / TL;DR
Without the SailfishOS-OBS, both community app stores will be obsoleted 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 the Jolla 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 has 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 (of the built RPMs) capabilities to the same extent as the SailfishOS-OBS.
References:
I hope that depicting the consequences of shutting down the SailfishOS-OBS is helpful to keep it alive: It has become a crucial piece of the infrastructure for SailfishOS apps and ports over the years.
