Community meeting on IRC 12th May 2022

[piggz]

Ill add and update the Action stats here.

OBS is primarily used for application development/distribution, and device porting. These two different use cases have a different set of stats.

1. 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.

2. 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.

Additionally, id like to link to these comments

Community OBS - Refurbished and re-floated

So, the last Community Meeting repeats that sentiment. Something is expected to be put forth to Jolla that hopefully will lead to another commitment of keeping OBS. Personally I believe Chum to be a great success, and the Porters Community is also benefitting as always from the OBS workflow. Question: how can we as the community help to make a good case?