They are awesome, thanks a lot!
Another nail to the coffin of SFOS?
What are the reasons behind this?
I cannot imagine SFOS to be alive and usable without you (and your ‘unofficial’ contributions)!
I’m working for Aurora OS for 5 years, and searching for another hobby not related to SFOS coding. 24/7 SFOS coding is too much, exhausting and etc.
Perfectly understandable in my opinion. I also try to reduce the huge amount of time I spent behind a computerscreen.
And some point of time you have seen most challenges for creating an app and it gets more repeating. And just fixing broken apps after a SFOS update is also kind of frustrating.
For all (both?) webOS TV owners out there, updated version of harbour-lgremote-webos now available on OpenRepos.
I’ve managed to successfully start it up and connect to my LG 49UK6300PLB on armv7hl (X 10), aarch64 (X 10 II) and i486 (JT), YMMV.
Yes, it is. All extensions to coderus should have come from Jolla himself. Jolla and the users have benefited from it for a long time. If this company is intelligent, they would take over the projects from coderus, maintain them themselves and ensure this “standard” for everyone.
That is my suggestion for Finland.
…waiting for the next RoadMap from Jolla…
There’s a Roadmap? The told so often about it, but no o e ever sees it.
I remember the implementation of webdav as one of the features for Sailfish OS 3 - but they didn’t deliver it so far, and we’re on SFOS 4 now…
While complaining about Jolla and SFOS releases is a nice tradition in the community, and any thread or other conversation must have at least three posts bitching about it, I think we have achieved that now so can we get back on topic please?
I’ll step up while I’m not at all qualified technically, and try to maintain (probably not extend though) the Screencast package.
Thank you CODeRUS for all your contributions.
Regarding patchmanager, I have a question about the Web Catalog - would the web interface be also orphaned and need a new contributor, or you would still continue to add SFOS versions to it?
web service is 24/7 as always. if one want to deploy own service for future versions - welcome
as well as https://coderus.openrepos.net/whitesoft/sailversion crawler :))
Thanks for the prompt reply! My worry was that there is no 4.1.0.x version in the web catalog (https://coderus.openrepos.net/pm2) and if someone should add it by hand or not was included in the contribution.
But this seems related - should pm2 webcatalog use sailversion crawler already?
yes and no, there are a lot of versions, and patchmanager ui will be too long very soon. i’ve no solution for this, maybe different input boxes will be okay, and then it can use versions from the same list.
@nephros was kind enough to agree we should team up to maintain patchmanager3. There is a chum version already working on sfos4 + aarch64 + not requiring full bash, we’ll try to make it official on the main repo branch and then in openrepos.
Next steps will probably be adding sailjail support (can be manually added now), cleanup of existing issues and PRs, see what else challenges us.
Very great news!! Thank you!!
Thank you very very much for all you have done for the community.
This crawler unfortunately did not capture the recent 184.108.40.206 update (the second EA release of Verla).
Is the crawler code available somewhere?
I failed to find it and even have no idea where / what to scrape. As sfos-upgrade depends on the sailversion page to include all SFOS releases, it might be my task to take care of that.
Hence, @coderus please provide a pointer to the sailversion crawler code (preferably at GitHub) or fix the crawler once more.
Patchmanager 3.1.0 has been released, see Patchmanager3 for SailfishOS 4
You guys rock. Say no more.
restored personal-ringtones plugin sources here: https://github.com/CODeRUS/voicecall/commit/a610ec8ae6628a2ef08779e76ceddcfdcc26a5da