16:00:00 <rainemak> #startmeeting Sailfish OS, open source, collaboration -- 6th November 2025
16:00:00 <sailbot> Meeting started Thu Nov  6 16:00:00 2025 UTC. The chair is rainemak. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:00 <sailbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:00:00 <rainemak> #info Meeting information and agenda can be found here:
16:00:00 <rainemak> #link https://forum.sailfishos.org/t/25254
16:00:00 <rainemak> I am the meeting's chairperson today, and will be doing my best to keep time and order. Please respect the timings and bee-hive.
16:00:00 <rainemak> #topic Brief introduction (5 min). Please prefix your name/handle with #info
16:00:11 <rainemak> #info Raine Mäkeläinen, Jolla
16:00:56 <nephros> #info Peter G., Community
16:01:00 <ExTechOp> Hello everyone!
16:01:01 <nephros> Good evening! :)
16:01:08 <ExTechOp> #info Otto Mäkelä, community
16:01:15 <rainemak> Good evening all!
16:01:16 <direc85[m]> #info Matti Viljanen, Jolla
16:01:58 <mal> #info mal, Jolla
16:02:06 <rainemak> We have again five nice topics. Please keep on asking and raising topics on forum.
16:03:25 <legacychimera247> #info 247, community member
16:03:30 <legacychimera247> hello all
16:03:42 <rainemak> Again, I took a bit of liberty to adjust expected/requested time needed for some topics.
16:04:09 <rainemak> legacychimera247, hello and welcome
16:04:58 <rainemak> let's get started
16:05:01 <rainemak> #topic Jolla C2 order backlog (5 mins -- frankps)
16:05:06 <rainemak> #info <frankps> Could Jolla give us an update on the backlog situation? Estimated
16:05:06 <rainemak> #info <frankps> shipping time October 1st was 6-8 weeks. Where are we now? When #info <frankps> will you start shipping out ordered devices?
16:05:11 <rainemak> #info <Jolla> This is covered by https://forum.sailfishos.org/t/25420
16:05:11 <rainemak> #info <Jolla>
16:05:11 <rainemak> #info <Jolla> A manufacturing slot for the next production batch Q4/25 of Jolla
16:05:11 <rainemak> #info <Jolla> C2 has been confirmed to take place at the week Nov 17, 2025.
16:05:11 <rainemak> #info <Jolla> Following from there we should be able to continue shipments by the
16:05:12 <rainemak> #info <Jolla> end of November.
16:05:14 <rainemak> #info <Jolla>
16:05:16 <rainemak> #info <Jolla> Let’s have open discussion.
16:05:18 <rainemak> #link https://forum.sailfishos.org/t/25420
16:06:26 <ExTechOp> You could also summarize: approximately how large a back log is there, ie. if one were to order today, what batch would it end up in and approximately when is delivery?
16:07:06 <rainemak> ExTechOp, there are still devices left in this batch.
16:08:27 <rainemak> When going forward we do want put for each batch some sort of a name. Like with this we're calling this Q4/25 rather than 3rd.
16:08:36 <rainemak> It's easier for us as well.
16:08:47 <rainemak> hello dcaliste
16:09:08 <rainemak> Any other questions? Did I cover ExTechOp yours?
16:09:20 <dcaliste> Hello rainemak and everyone, sorry to be late.
16:09:21 <ExTechOp> Thanks, that covers it.
16:09:36 <rainemak> Thanks, time to move on.
16:10:00 <rainemak> #topic GTK support (10 mins -- pherjung)
16:10:00 <rainemak> #info <pherjung> The Librem 5 supports an increasing number of GTK apps. While
16:10:00 <rainemak> #info <pherjung> they do not adhere to Sailfish OS UI/UX guidelines, they are
16:10:00 <rainemak> #info <pherjung> Linux apps and would increase the number of apps available on
16:10:00 <rainemak> #info <pherjung> Sailfish OS. Are there any plans to support GTK, and how much
16:10:02 <rainemak> #info <pherjung> effort would it take?
16:10:23 <rainemak> #info <Jolla> Thank for this good question. Sorry for the long answer.
16:10:23 <rainemak> #info <Jolla>
16:10:23 <rainemak> #info <Jolla> The problem behind the scene is that we’re lacking xdg-shell
16:10:23 <rainemak> #info <Jolla> support from Qt. Thus, also from our compositor (lipstick).
16:10:23 <rainemak> #info <Jolla> Implementing xdg-shell support would be a good starting point and
16:10:25 <rainemak> #info <Jolla> then we should have means to support other toolkits than Qt for app
16:10:27 <rainemak> #info <Jolla> development.
16:10:29 <rainemak> #info <Jolla>
16:10:31 <rainemak> #info <Jolla> Some years back we started a project to split homescreen (lipstick)
16:10:33 <rainemak> #info <Jolla> properly to a homescreen and a wayland compositor. Why to split?
16:10:35 <rainemak> #info <Jolla> Mostly due to robustness and performance. Composition and gestures
16:10:37 <rainemak> #info <Jolla> should never stall. Also freezes or crashes on homescreen should
16:10:39 <rainemak> #info <Jolla> not affect to the other applications. Eventually this project
16:10:41 <rainemak> #info <Jolla> didn’t materialize. With this project we could have received also
16:10:43 <rainemak> #info <Jolla> xdg-shell support.
16:10:45 <rainemak> #info <Jolla>
16:10:47 <rainemak> #info <Jolla> We should try to think out-of-the-box, try to find other possible
16:10:51 <rainemak> #info <Jolla> solutions and use existing projects when possible. Then comes
16:10:53 <rainemak> #info <Jolla> projects like Weston. A Wayland compositor that is broadly used.
16:10:55 <rainemak> #info <Jolla> Thus, it would have more developers working on it when comparing to
16:10:57 <rainemak> #info <Jolla> us (Jolla & Sailfish Community).
16:10:59 <rainemak> #info <Jolla>
16:11:01 <rainemak> #info <Jolla> Conceptually we could have a Weston compositor and the “current”
16:11:03 <rainemak> #info <Jolla> homescreen as a wayland client (an app among the other apps). On
16:11:05 <rainemak> #info <Jolla> the compositor side we should deal for example window management,
16:11:07 <rainemak> #info <Jolla> shell, gestures and effects with very limited dependencies. Surely,
16:11:09 <rainemak> #info <Jolla> there are also things like text input support.
16:11:11 <rainemak> #info <Jolla>
16:11:13 <rainemak> #info <Jolla> If all this would happen, then we should also be very close to a
16:11:15 <rainemak> #info <Jolla> situation where we actually could have support for other toolkits
16:11:17 <rainemak> #info <Jolla> (easily or relatively easily) for example for GTK. Surely, changing
16:11:21 <rainemak> #info <Jolla> compositor architecture would be most bigger task than implementing
16:11:23 <rainemak> #info <Jolla> xdg-shell support for the current compositor.
16:11:25 <rainemak> We're using deprecated wl_shell instead of xdg-shell
16:11:38 <rainemak> #link https://gitlab.freedesktop.org/wayland/weston
16:13:35 <dcaliste> Mmh, very nice answer. Was the attempted spliting based on Weston for the compositor part ?
16:14:04 <rainemak> dcaliste, more like a yet another not invented here.
16:14:20 <dcaliste> What made it stop ? Technical difficulties to separate Lipstick homescreen from compositor ? Or simply lack of time ?
16:15:22 <dodoradio[m]> #info dodoradio, community/asteroidos
16:15:31 <rainemak> dcaliste, simply lack of time and get it to a production level
16:15:43 <dodoradio[m]> hi, we've had a lot of this discussions about getting off lipstick on asteroidos. it's just really hard
16:16:08 <dodoradio[m]> kwin, the obvious choice for qt based distro (though not obvious for jolla due to licensing) doesn't support hybris backend any more
16:16:13 <nephros> Wayland aside, I guess getting GTK (and probably related libraries like things from GNOME) running would also mean getting a long tail of dependencies first.
16:16:21 <rainemak> dcaliste, also as a retrospective, I think we had too high target setting.
16:16:34 <dodoradio[m]> and there's few other options with qt bindings
16:17:12 <dodoradio[m]> just the code involved in switching from lipstick to something else is a massive commitment, even ignoring all the other needs
16:17:13 <rainemak> nephros, correct but it should still be without X11.. like GTK with Wayland only
16:17:18 <dcaliste> Could lipstick be simply a client while having to display content of other clients ? (I'm showing my ignorance on wayland composition here)
16:17:24 <rainemak> surely, that's not visible for app developers
16:17:58 <rainemak> dcaliste, it something like that indeed... we had sailfish-compositor and sailfish-homescreen
16:18:15 <rainemak> I think you can guess what is what
16:18:57 <dcaliste> Ok, I guess the homescreen part is having some privileges to get access to the other client content.
16:19:50 <dcaliste> Do you think the homescreen part could work as a poc over weston ?
16:20:02 <rainemak> dcaliste, not really needed. I could end up being from compositor point of view just an app that launches other apps
16:20:28 <dcaliste> Ah I see, indeed.
16:20:43 <rainemak> dcaliste, defined level PoC... to some degree yes
16:21:24 <rainemak> gestures, effects, appsupport addition at least should be taken into account
16:21:34 <dcaliste> As poc I mean, running Weston on device and display a full screen window of a wayland app, run from the CLI.
16:21:34 <rainemak> ^ and those are probably there tricky ones
16:22:03 <rainemak> dcaliste, one of our devs almost have it :-) but it doesn't completely work yet
16:22:14 <rainemak> done as a hoppy project
16:23:15 <nephros> ah so like craft beer! :P
16:23:35 <dcaliste> Would it make sense to open source this hobby project ? It's not necessary mean to replace anything soon, but it could be run and improved communally.
16:23:58 <roundedrectangl> hi, sorry, i am late, but wouldn't something similar to qt runner work for running gtk apps?
16:23:59 <rainemak> nephros, sorry... hobby
16:24:12 <rainemak> nephros, but yes, like a draft beer
16:24:49 <nephros> roundedrectangl: AFAIK also qt-runner is limited by wl_shell features.
16:26:26 <rainemak> thing is that adding xdg-shell support to Qt from scratch is not necessary that big of an effort.
16:27:28 <dcaliste> rauinemak, yeh, but it means yet another implementation used only in Sailfish… does it not ?
16:27:38 <dcaliste> rainemak, sorry…
16:28:06 <rainemak> dcaliste, defined protocol is still like a defacto nowadays
16:29:03 <rainemak> I think we have quite thoroughly covered this one. let's move on 30mins past.
16:29:14 <mal> it would just be about implementing the protocol in our current Qt version, well not even full implementation but updating the implementation to current xdg-shell version
16:29:37 <rainemak> +1
16:29:53 <pherjung[m]> #info pherjung, community
16:29:53 <rainemak> mal, thanks for the additions
16:30:06 <mal> Qt 5.6 supports some old unstable xdg-shell version
16:30:08 <abr> It's also something that's already present in later Qt versions though, right?
16:30:10 <nephros> this would also enable a couple of other software, like SDL2 and3 not needing backport patches any more.
16:30:13 <pherjung[m]> Hi! I found some time to be present :)
16:30:18 <pherjung[m]> There this project: https://openrepos.net/content/artur/newcompositor
16:30:18 <dcaliste> It's currently in QtWayland, or am I mistaken ?
16:30:26 <rainemak> nephros, correct that as well
16:30:32 <pherjung[m]> no clue if it works or if it's totally off-topic
16:30:32 <mal> yes, newer Qt supports current xdg-shell protocol version
16:31:44 <rainemak> going a bit over
16:32:11 <rainemak> have we covered this one or do you want a bit more time still?
16:32:31 <rainemak> let's move on
16:32:32 <rainemak> #topic Sony Xperia 10 IV/V port status (10mins -- ExTechOp)
16:32:32 <rainemak> #info <ExTechOp> A functional Sony device port has now been “real soon now” since
16:32:32 <rainemak> #info <ExTechOp> Love Day 2 in August 2024, but they still suffer from serious
16:32:33 <rainemak> #info <ExTechOp> issues because of Sony binary blobs. Also, a Jolla announcement
16:32:33 <rainemak> #info <ExTechOp> on the status of the Sony devices port has now been teased for
16:32:34 <rainemak> #info <ExTechOp> months, but even this hasn’t materialized. This is just getting
16:32:36 <rainemak> #info <ExTechOp> embarrassing. Please put out an official statement outlining
16:32:38 <rainemak> #info <ExTechOp> some kind of time scale when things will begin to happen, or
16:32:40 <rainemak> #info <ExTechOp> just admit it’s never happening. If all this fails, at least
16:32:42 <rainemak> #info <ExTechOp> give a time scale when you’ll be able to clarify things.
16:32:46 <rainemak> #info <Jolla> We fully acknowledge, we have promised to deliver Sailfish to
16:32:46 <rainemak> #info <Jolla> Xperia 10 IV/V and we remain committed to do our part with it as
16:32:48 <rainemak> #info <Jolla> far it takes and what can be feasibly done by us. By far, not all
16:32:52 <rainemak> #info <Jolla> can be done by us and with the currently chosen approach there has
16:32:54 <rainemak> #info <Jolla> been several unexpected up and downs in this project e.g. with the
16:32:56 <rainemak> #info <Jolla> vendor blobs: there has been blocker issues with battery indication
16:32:58 <rainemak> #info <Jolla> missing, camera not working, VoLTE not working and fingerprint
16:33:00 <rainemak> #info <Jolla> missing.
16:33:02 <rainemak> #info <Jolla>
16:33:04 <rainemak> #info <Jolla> Maybe we have totally wrong approach with the adaptation software
16:33:06 <rainemak> #info <Jolla> of this particular device project? Maybe it shouldn’t be done
16:33:08 <rainemak> #info <Jolla> primarily by Jolla and using the Open Device Program vendor blobs?
16:33:10 <rainemak> #info <Jolla>
16:33:12 <rainemak> #info <Jolla> We have also been thinking about completely different approaches by
16:33:14 <rainemak> #info <Jolla> enabling this thru an “officially supported community port” -
16:33:16 <rainemak> #info <Jolla> community port and we enable AppSupport to it – would that work for
16:33:18 <rainemak> #info <Jolla> the community?
16:33:22 <rainemak> #info <Jolla>
16:33:24 <rainemak> #info <Jolla> What is the definition of done in this project? What do you think
16:33:26 <rainemak> #info <Jolla> should be done to call it ready for the expected use?
16:33:28 <rainemak> #info <Jolla>
16:33:30 <rainemak> #info <Jolla> E.g. fingerprint – won’t be done, other examples?
16:36:28 <legacychimera247> i would say, the definition of done is when you have the same level of usability you got with the xa2
16:36:29 <rainemak> ExTechOp, comments?
16:36:50 <rainemak> legacychimera247, that won't happen
16:36:50 <ExTechOp> The way the Sony binary blobs work for Open Device Program is not totally clear to me, did I understand correctly that they are totally separate from the stuff Android installations use?
16:37:32 <legacychimera247> i'll be honest, not blaming jolla cause i know blobs are from sony, but my xa2 is getting quite old and i'm a little bit scared of replacing it with newer xperias
16:38:16 <rainemak> ExTechOp, Sony also have proprietary blobs that are nuked when you unlock it (afair during unlocking phase)
16:39:01 <rainemak> legacychimera247, I used Xperia 10 III many years
16:39:18 <rainemak> but that's also hard to get/find
16:39:24 <legacychimera247> that (in my opinion) is not a problem, i know what i'm getting into, but at least have the basics working
16:40:26 <legacychimera247> i get you, my xa2 is almost 7 years old, and really doesn't want to die (apart from the fact that it's getting slower)
16:40:29 <abr> whoop whoop officially supported community port though
16:40:35 <pherjung[m]> I would love to see Sailfish on top of a postmarketOS device
16:40:53 <mal> btw, I was able to fix wired headphone audio on x10v and probably same applies to x10iv
16:40:56 <legacychimera247> but still i wouldn't buy an already old device like the 10 iii
16:41:12 <rainemak> mal, that's nice!
16:41:21 <ExTechOp> And for my part, I would say software for a phone can be called "ready" when the major hardware of the phone is usable: phone calls, speaker, microphone, data connections, camera.
16:41:21 <ExTechOp> In this respect for example the Sony Xperia 10III is not "ready" since there just isn't proper echo cancellation available, so phone calls are not quite properly there.
16:41:26 <mal> still haven't done PRs for that fix
16:41:28 <dcaliste> mal, sounds great ! Thanks.
16:41:46 <legacychimera247> because i will probably change my phone next year and by then the 10 iii will be like very old already
16:42:27 <abr> If a recent fairphone gets appsupport then that might well be my next phone
16:42:46 <rainemak> ExTechOp, exactly echo cancellation kind of an issue is a good example of a difficult problem to fix
16:43:23 <rainemak> ExTechOp, if there would have been an easy fix, we would have fixed it already
16:43:43 <nephros> Question is for me, if SONY ODP is "unreliable upstream", what would be a more reilable upstream option?
16:44:34 <abr> I'm not sure there is one, as those open device guys at Sony are really trying to do something quite enormous.
16:44:42 <ExTechOp> Indeed, but missing it makes for a very frustrating user experience.
16:45:24 <abr> it does. but it's worth pointing out how appreciated that's been over the last few years. for all the gripes, it's been wonderful running sfos on all these xperias over the years.
16:45:50 <abr> x10ii and for the most part the iii were great ports
16:46:14 <ExTechOp> Followup question: Is Sony ODP future known, is it in danger of suddenly being totally terminated?
16:46:30 <legacychimera247> abr: of course it is, xperias are the best phones even without sailfish
16:46:38 <abr> but there are lots of community ports that are more functional than the iv and v will ever be?
16:46:49 <rainemak> ExTechOp, no idea
16:46:51 <abr> so maybe the future is there
16:46:54 <direc85[m]> I'm still sad my X10III died, it worked great for me.
16:47:23 <mal> I use x10iii as my main phone and works quite nicely
16:47:33 <rainemak> let's move on 50 mins past... It looks that we're pretty much covered.
16:47:54 <rainemak> I loved X10 III as well
16:47:55 <ExTechOp> Summary: no idea when/if things move forward?
16:48:15 <rainemak> impossible to say target date
16:48:41 <rainemak> but we're committed to this
16:49:20 <rainemak> let's move on
16:50:01 <rainemak> #topic Security patch level updates of the Android runtime (10 mins -- balta)
16:50:06 <rainemak> #info <balta> Google releases monthly security patches for Android, but sadly
16:50:06 <rainemak> #info <balta> these are never applied to the android app support runtime of
16:50:06 <rainemak> #info <balta> SailfishOS. You can check your security patch level in Settings →
16:50:06 <rainemak> #info <balta> Android App Support. As these patches contain security fixes they
16:50:06 <rainemak> #info <balta> should be included regularly in SailfishOS updates as well. Right
16:50:08 <rainemak> #info <balta> now on the 10V the level is from August of 2024, I think on older
16:50:09 <rainemak> #info <balta> devices this will be even older. Also some apps will check this and
16:50:11 <rainemak> #info <balta> refuse to start, e.g. I cannot use Teams for my job right now
16:50:13 <rainemak> #info <balta> because of a too old security patch level. Is this a big effort for
16:50:15 <rainemak> #info <balta> Jolla to provide an update or is it something like simply
16:50:17 <rainemak> #info <balta> triggering a CI chain?
16:50:30 <rainemak> #info <Jolla> AppSupport security patch level is usually updated on bigger
16:50:30 <rainemak> #info <Jolla> releases (4.5. ,4.6., 5.0...). Currently we are working on
16:50:30 <rainemak> #info <Jolla> AppSupport 13 security patch level update. Unfortunately,
16:50:30 <rainemak> #info <Jolla> AppSupport 11 no longer receive security patch level updates from
16:50:31 <rainemak> #info <Jolla> AOSP and it is currenty using the latest patch level. All in all,
16:50:33 <rainemak> #info <Jolla> it’s not a simple as triggering a CI chain. When going forward we
16:50:35 <rainemak> #info <Jolla> should think whether we could / should update AppSupport security
16:50:37 <rainemak> #info <Jolla> patch level also upon hotfix updates (when an update is available
16:50:39 <rainemak> #info <Jolla> and integrated).
16:55:37 <rainemak> We can keep this shorter if there no comments.
16:55:45 <rainemak> We can keep this shorter if there are no comments.
16:56:28 <rainemak> let's move on...
16:56:29 <rainemak> #topic How shall we deal with trolls in the forum (10 mins -- Fellfrosch)
16:56:29 <rainemak> #info <Fellfrosch> Trolls quite often ruin a discussion in the forum. It is quite
16:56:29 <rainemak> #info <Fellfrosch> easy for them to do so, because threads get blocked when they
16:56:29 <rainemak> #info <Fellfrosch> get flagged. This is stopping quite often good and helpful
16:56:30 <rainemak> #info <Fellfrosch> conversation. So the question is how do we want to deal with
16:56:31 <rainemak> #info <Fellfrosch> this problem in future. For me the better solution instead of
16:56:33 <rainemak> #info <Fellfrosch> freezing threads would be temporary bans for people who
16:56:35 <rainemak> #info <Fellfrosch> misbehave and don’t cling to the forum rules.
16:56:37 <rainemak> #info <Fellfrosch> I already started a thread about that problem here:
16:56:39 <rainemak> #info <Fellfrosch> Please stop closing threads because of trolls
16:56:41 <rainemak> #link https://forum.sailfishos.org/t/25369
16:56:43 <rainemak> #info <Jolla> Let’s have an open discussion on this.
16:56:45 <rainemak> #info <Jolla> Starting point could be Sailfish OS Forum FAQ.
16:56:47 <rainemak> #link https://forum.sailfishos.org/faq
16:56:58 <rainemak> There were already many comments in the forum post.
16:57:51 <rainemak> Ideas welcome, I'm all ears.
16:58:06 <rainemak> Would somebody like to be a moderator? There ain't too many of us.
16:58:39 <mal> one problem of course is that even banning rarely works as making new accounts is easy
16:59:14 <rainemak> that's a good and valid point
16:59:19 <ExTechOp> I have some experience going all the way back to the BBS and Usenet era, but unfortunately I just don't have the time these days. :-(
17:01:23 <rainemak> Feel free to PM me on Forum if you think that somebody should be a moderator or you'd like to be a moderator. Surely, I'd connect to the person and so on.
17:02:37 <rainemak> Personally, I think that a cooling period for spammers/trolls usually work after warning rounds
17:03:41 <rainemak> also worth noticing that I do not have time to start tweaking Discourse itself
17:04:09 <rainemak> if it automatically triggers something then it does so
17:05:13 <rainemak> for example closes a topic for some time period
17:05:22 <Keto> we probably should go for suspend and ban a bit more lightly, currently it is usually the very very last action
17:06:18 <rainemak> Keto, that's true. Same time we should allow discussion/debate especially when FAQ is respected.
17:08:09 <Keto> yes, having discussion in productive way, but in most of these cases there is very little productive content
17:08:57 <rainemak> Keto, that's why I'm asking who'd like to be promoted as a moderator
17:08:58 <mal> politics and other such things mixed in there ruin good discussions
17:09:34 <pherjung[m]> I may try
17:09:40 <pherjung[m]> but I don't want to be alone
17:10:38 <rainemak> pherjung[m], you wouldn't be alone. I think it's mostly ViGe and me knowadays.
17:10:57 <rainemak> any objections?
17:12:11 <rainemak> pherjung[m], I'd be happy if you'd like to give a try
17:12:42 <pherjung[m]> nice! Let's do a try for some months
17:13:26 <rainemak> for others, any objections? time to raise your voice.
17:13:44 <pherjung[m]> Perhaps the members of the Community members would be interested, too: https://forum.sailfishos.org/t/welcome-new-community-members/21374.
17:13:44 <direc85[m]> +1 from me :)
17:14:42 <rainemak> that's a closed topic :-)
17:14:52 <rainemak> ^ none public
17:15:02 <pherjung[m]> oh sorry
17:15:12 <rainemak> pherjung[m], no worry.
17:15:38 <rainemak> but let's ask there...
17:15:53 <rainemak> pherjung[m], I'll promote you
17:15:59 <rainemak> let's move on
17:16:04 <rainemak> #topic Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla)
17:17:28 <dcaliste> I'm playing with the note application, and added a file provider : https://github.com/sailfishos/jolla-notes/pull/1 It's currently under review, but if someone is interested to give a try and give feedback, you're welcome !
17:17:52 <rainemak> thanks dcaliste
17:17:59 <dcaliste> It allows to look at files from a directory as notes, edit them, delete them or add new files / notes.
17:19:55 <dcaliste> Or from another point of view, it allows to have notes saved as files that can be synced with webdav for instance.
17:20:44 <abr> ooh nice and generic
17:20:57 <pherjung[m]> is it possible to share an aarch64 package?
17:21:04 <pherjung[m]> I'd be happy to test it
17:21:35 <dcaliste> I guess I can try to make it compile on OBS tomorrow.
17:22:46 <rainemak> let's move to general discussion
17:22:51 <rainemak> #topic General discussion (10 mins or something)
17:23:29 <rainemak> I find this 6:00 PM HKI time better than 7:00 PM
17:24:10 <abr> good at 5pm CET too
17:24:23 <ExTechOp> It works for me too, I usually have sauna on Thursday evenings.
17:24:34 <dcaliste> I'm sorry, I've to leave. Thanks for the interesting discussions.
17:24:44 <rainemak> thanks dcaliste
17:24:55 <rainemak> let's keep this one
17:26:00 <nephros> Sorry: for open PRs, I fixed some 404 links in the docs.s.o repo yesterday. Should be quick to review.
17:26:10 <rainemak> nephros, will check
17:32:39 <rainemak> moving on
17:32:40 <rainemak> #topic Next meeting time and date (2 mins)
17:32:40 <rainemak> Proposing Thursday 20th November at 04:00 PM UTC
17:34:22 <nephros> fine by me :)
17:34:24 <rainemak> let's go with the same slot
17:34:26 <rainemak> #info Next meeting will be held on Thursday 20th November 2025 at 04:00pm UTC: 2025-11-20T1600Z
17:34:35 <rainemak> thank you all once again!
17:34:43 <nephros> and btw, the .ics file works nicely as a reminder
17:34:44 <rainemak> see you in two weeks
17:35:08 <rainemak> +1
17:35:19 <rainemak> #endmeeting