It seems the announcement of closing OBS has ignited confusion. I’ll try my best to open details related to what has caused the decision. The main rationale has two factors:
The cost of maintenance. The service has not been maintained in a long time. We are at a point where we need to decide if we want to invest development time to keep the OBS alive and working. When deciding on the investment, we analyzed how the service is used and how often it is currently used, by ourselves and the community. We also evaluated if the additional investment will enable us a more efficient Sailfish OS development environment. As a result we concluded that we are not using it internally or with our commercial partners and there is no clear path how we could develop the OBS so that it would solve our future needs.
Jolla as a company has legal responsibilities. We do not want to carry the risk of hosting content that we do not have means to review and validate.
In addition, there are secondary factors that justify the decision. There is a need for offline development environment for adaptations and apps development, and in addition we cannot find all the build-time problems with OBS. We need to innovate new ways to solve these problems. In fact, there are already available solutions that can be used outside of OBS. Our conclusion is that we should focus on improving these new processes and ways of working.
We want to address the known issues that this causes for Sailfish OS ports. For example we are updating HADK, as a result OBS is no longer needed for porting. We will also deliver the instructions for the community on how they can host updates for their ports. We are open for workaround proposals, discussion and questions in this thread. For example we would like to understand what are other major use cases for OBS that are no longer possible - can’t promise we can address all of them, but we want to know if there are any issues where we could help.