carmenfdezb
commented
1 year ago Wow, thank you @carmenfdezb! See sailfishos...carmenfdezb:meecast:sfos4-fixes, plus a Meecast 1.1.32 release of this. Really excellent, the only thing I am not completely happy about is to unconditionally (i.e., statically) "Lockscreen option isn't needed in sfos 4 -> disabled", because Jolla 1 users (the few remaining) are stuck on SailfishOS 3.4.0 and some community ports also ceased to be maintained on various SFOS 3.x releases. When it comes to fixing other things (i.e., not specifically SFOS4-related), one would have to pay attention to submit them to all SFOS-branches, if there are multiple, hence I believe the development for SailfishOS should be kept in a single
sailfishosbranch.
Thank you for your kind words. You are right, this aims to avoid to enable this option for sfos 4 devices, because I enabled this option in my Xperia 10 II by mistake and it does weird things, screen blinks when I move from events page to homescreen and viceversa. To be honest, I don't know how to do that, maybe someone with more experience can help and know how this option is visible only for <sfos4 users.
@carmenfdezb, as I value you as calmly and responsibly acting and you have been contributing to SailfishOS apps for many years, would you be willing to be part of such a team in order to share the admin workload (which is small, as everything is voluntarily)? Most importantly IMO is to have at least three people which are basically reachable in case some action becomes necessary, because one cannot achieve much with repos, whose owners do not respond to issues, PRs etc. at all.
Of course, you can count on me for being part of the team, but you have to know that I'm a newbie and I do small things, but I would do the best :)
Olf0
CepiPerez
poetaster
vasvlad
a-dekker
Wow, thank you @carmenfdezb! See https://github.com/Meecast/meecast/compare/sailfishos...carmenfdezb:meecast:sfos4-fixes, plus a Meecast 1.1.32 release of this. Really excellent, the only thing I am not completely happy about is to unconditionally (i.e., statically) "Lockscreen option isn't needed in sfos 4 -> disabled", because Jolla 1 users (the few remaining) are stuck on SailfishOS 3.4.0 and some community ports also ceased to be maintained on various SFOS 3.x releases. When it comes to fixing other things (i.e., not specifically SFOS4-related), one would have to pay attention to submit them to all SFOS-branches, if there are multiple, hence I believe the development for SailfishOS should be kept in a single
sailfishosbranch.P.S.: I am considering to gather a few applications for SailfishOS which became unmaintained and which I love to use under the Storeman-developers organisation or to create a new GitHub organisation for that. The whole aim would be to provide minimal maintenance (i.e., keep these apps running acceptably under recent SFOS releases) and to make things easier for developers, by employing a GitHub CI workflow, using Transifex for translations (even though I don not like Atlassian at all; but lacking an alternative, what else can one do?) etc. @nephros, @b100dian and me have been doing this for Patchmanager, @nephros supports me doing that for Storeman, potential candidates are Mashka (easy, small), MeeCast, AlienDaivik-Control (might require some Android know-how), FileCase and DailyComics.
The aim is not to fork these repos, but to convince the repo owners, either to grant others admin rights to the original repo or to transfer that repo to a GitHub organisation, where the original developers plus a maintenance core team are provided with full admin rights for it. The latter is more elegant and organisationally flexible, plus by transferring, all issues, PRs etc. are also transferred, in contrast to "forking", which only clones the git repo proper, without all the GitHub extras; furthermore all web-accesses to the old repo are redirected to the transferred one.
The hard thing is to trigger or convince the original repo owner(s): Petr Tsymbarovich (@mentaljam) did that with Storeman and Storeman-Installer, but did not answer my request to also do that with Mashka and Beerware, Coderus preferred to provide @nephros, @b100dian and me with admin access to the original repo (well, the process was was a bit more convoluted, but that is the result), Matias Perez (@CepiPerez) provided me with commit rights, but not with admin rights for his FileCase repo, hence I cannot add people to the team there or transfer it to a GitHub "organisation" (at Matias' choice), and I still have to ask Damien Tardy-Panis (@tardypad) and Oleg Linkin (@Maledictus) WRT DailyComics for which PRs have been piling up since March 2020 (or try address them via email, the addresses are denoted on their GitHub account pages).
What makes these considerations tricky for Meecast, is the fact that SailfishOS is only one of many platforms: While most of the other ones are dead, at least the Linux desktop appears worth being retained (I would tend to set the other branches to read-only, which can be undone at any time). I would like to hear @vasvlad's (Uladzislau Vasilyeu) opinion on that, but unfortunately he did not react in the last couple of years, while I had conversations with him more than five years ago. OTOH, a GitHub organisation Meecast already exists, which makes it easy to share admin responsibilities for that (and makes a repo transfer more or less superfluous), if he would provide, e.g., me with these (I can organise the rest, i.e., providing a few other trustworthy people with admin rights).
@carmenfdezb, as I value you as calmly and responsibly acting and you have been contributing to SailfishOS apps for many years, would you be willing to be part of such a team in order to share the admin workload (which is small, as everything is voluntarily)? Most importantly IMO is to have at least three people which are basically reachable in case some action becomes necessary, because one cannot achieve much with repos, whose owners do not respond to issues, PRs etc. at all.