- Name / IRC nick: piggz
- topic: Update on the future of the community OBS
- some details about the topic:
It has been some time since an update was given on the future of the community OBS, can you give one? We value current solution via OBS as it:- Supports porters by allowing for automatic builds of saiflish adaptation packages in the cloud
- Provides a central location to host port packages, so that individual porters do not need to find hosting packages on random cloud providers
- Supports application devs by allowing easy building of packages on a range of architectures and sailfish releases
- Provides trusted package generation from source to RPM. something we don’t have when we upload blobs to OpenRepos or Jolla Store
- Provides repositories for multiple architectures and sailfish releases to app devs when required. OpenRepos cant do this without horrendous hacks (multiple accounts) and I assume Jolla store also cant provide different packages per release
There has been excellent work by @rinigus on tbuilder to plug some of the gaps that would be left if OBS was removed, but it doesnt support hosting, so each porter would be looking to host packages wherever they can find. It also means that all builds must be done locally, which is a huge drain on local resources of individual devs/porters. It is incredibly convenient to just trigger a build, and get on with something else locally while it happens on OBS.
Finally, I firmly believe that if Jolla wants to have a community of porters and app devs, they should at least provide some services around that. Whether thats OBS, or something else, it should meet the requirements above and server the community. As has been said by others, once you have all the features of parallel, clean, cloud builds, you have effectively re-created OBS anyway 
- approx. time needed: 2 hours
- optional: rinigus