You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The task is to evaluate these enhancements, if they are sound, proper and make sense to integrate them (or a subset of them) into the MeeCast lockscreen code and test the result with the recent release of SailfishOS.
[Optional] Convert the MeeCast lockscreen Patch from an RPM file to a ZIP file for Patchmanager's Web Catalog and upload it there
Actually I think it is better to perform the two tasks separately, i.e. publish a release of MeeCast lockscreen between the two steps.
The text was updated successfully, but these errors were encountered:
Olf0
changed the title
[Suggestion] Update MeeCast lockscreen with enhancements by anig and convert it to a Web Catalog Patch
[Suggestion] Update MeeCast lockscreen with enhancements by anig and (optionally) convert it to a Web Catalog Patch
Sep 8, 2024
Side note: This is a clearly determined task perfect for a contributor
anig
enhanced theMeeCast lockscreen
Patch for Patchmanager in 2017, see https://openrepos.net/content/anig/meecast-widgetUnfortunately no source code was provided, but its source code should be easy to obtain by unpacking the
noarch
RPM file: https://openrepos.net/sites/default/files/packages/5538/meecast-widget-0.2-1.noarch.rpmThe task is to evaluate these enhancements, if they are sound, proper and make sense to integrate them (or a subset of them) into the
MeeCast lockscreen
code and test the result with the recent release of SailfishOS.[Optional] Convert the
MeeCast lockscreen
Patch from an RPM file to a ZIP file for Patchmanager's Web Catalog and upload it thereThis is pretty straight-forward, see https://github.com/sailfishos-patches/patchmanager#information-for-patch-developers
Background: Patches in Patchmanager's Web Catalog are much easier to handle for users.
Actually I think it is better to perform the two tasks separately, i.e. publish a release of
MeeCast lockscreen
between the two steps.The text was updated successfully, but these errors were encountered: