16:00:05 <rainemak> #startmeeting Sailfish OS, open source, collaboration -- 23rd October 2025
16:00:05 <sailbot> Meeting started Thu Oct 23 16:00:05 2025 UTC. The chair is rainemak. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:05 <sailbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:00:05 <rainemak> #info Meeting information and agenda can be found here:
16:00:05 <rainemak> #link https://forum.sailfishos.org/t/25096
16:00:05 <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:05 <rainemak> #topic Brief introduction (5 min). Please prefix your name/handle with #info
16:00:09 <ExTechOp> #info Otto Mäkelä, community
16:00:17 <rainemak> #info Raine Mäkeläinen, Jolla
16:00:39 <direc85[m]> #info Matti Viljanen, Jolla
16:00:56 <roundedrectangl> #info roundedrectangle, community
16:01:54 <Keto> #info Pami Ketolainen, Jolla
16:02:20 <Fellfrosch> #info Fellfrosch. community
16:02:34 <rainemak> Hopefully mal can join as well. He would have good input for few topics.
16:02:49 <piggz[m]> #info piggz community
16:02:59 <mal> #info mal, Jolla
16:04:30 <rainemak> We have five topics today. Please keep on asking. On last week's newsletter
16:04:30 <rainemak> pherjung started a new community meeting summary. Great initiative.
16:04:30 <rainemak> #link https://forum.sailfishos.org/t/sailfish-community-news-16th-october-2025-a-new-writer/25006
16:05:07 <rainemak> Alright, let's start
16:05:09 <rainemak> #topic WPA3 status update (5 mins -- KeeperoftheKeys)
16:05:21 <rainemak> #info <KeeperoftheKeys> I recently installed some simple Open Source IoT
16:05:21 <rainemak> #info <KeeperoftheKeys> switches and was very surprised to find them supporting
16:05:21 <rainemak> #info <KeeperoftheKeys> WPA3, this makes my Jolla phone the only thing
16:05:21 <rainemak> #info <KeeperoftheKeys> preventing me from switching our home network to WPA3. I
16:05:21 <rainemak> #info <KeeperoftheKeys> recall that there has been some work on this in the past
16:05:23 <rainemak> #info <KeeperoftheKeys> where do things stand? Based on a little of my own
16:05:24 <rainemak> #info <KeeperoftheKeys> testing (see below) it seems like it should be “in
16:05:26 <rainemak> #info <KeeperoftheKeys> reach/spitting distance”.
16:05:28 <rainemak> #info <KeeperoftheKeys>
16:05:30 <rainemak> #info <KeeperoftheKeys> WPA3 is mostly a software issue, I have seen it working
16:05:32 <rainemak> #info <KeeperoftheKeys> on Linux laptops that were built years before anyone
16:05:34 <rainemak> #info <KeeperoftheKeys> even thought about WPA3, as far as I recall connman
16:05:38 <rainemak> #info <KeeperoftheKeys> / wpasupplicant would need to be updated for this.
16:05:40 <rainemak> #info <KeeperoftheKeys>
16:05:42 <rainemak> #info <KeeperoftheKeys> Software versions:
16:05:44 <rainemak> #info <KeeperoftheKeys>
16:05:46 <rainemak> #info <KeeperoftheKeys> * Connman 1.41 shipped initial WPA3-SAE support based on phoronix, the current version on my phone [SFOS 5 (10ii)] is 1.38
16:05:49 <rainemak> #info <KeeperoftheKeys> * Per a wpa_supplicant changelog it added WPA3 in 2.10
16:05:51 <rainemak> #info <KeeperoftheKeys>   and on my phone I find 2.11 and I was able to manually
16:05:53 <rainemak> #info <KeeperoftheKeys>   connect using it (wpa_supplicant -i wlan0 -c
16:05:55 <rainemak> #info <KeeperoftheKeys>   local.conf) this did not set the correct IP address
16:05:57 <rainemak> #info <KeeperoftheKeys>   from my router, I need to check with another device if
16:05:59 <rainemak> #info <KeeperoftheKeys>   this is a config issue of the testing SSID or an issue
16:06:01 <rainemak> #info <KeeperoftheKeys>   with the phone but after manually setting the correct
16:06:03 <rainemak> #info <KeeperoftheKeys>   IP address (ip addr add…) I was able to “prove” that I
16:06:05 <rainemak> #info <KeeperoftheKeys>   indeed connected successfully to the WPA3 SSID.
16:06:09 <rainemak> #info <KeeperoftheKeys>   To do all of this I also had to do some gymnastics
16:06:11 <rainemak> #info <KeeperoftheKeys>   with enabling/disabling wireless in the GUI to allow
16:06:13 <rainemak> #info <KeeperoftheKeys>   wpa_supplicant to grab control of wlan0 from connman.
16:06:15 <rainemak> #link https://www.phoronix.com/news/ConnMan-1.41-IWD-1.23
16:06:17 <rainemak> #link https://android.googlesource.com/platform/external/wpa_supplicant_8/+/refs/heads/main/wpa_supplicant/ChangeLog
16:06:20 <rainemak> #info <Jolla> The support for WPA3 in newer connman version would not directly
16:06:22 <rainemak> #info <Jolla> enable WPA3 support in Sailfish OS because we have a custom wifi
16:06:24 <rainemak> #info <Jolla> plugin which needs adapting to support WPA3. Also higher level
16:06:26 <rainemak> #info <Jolla> code using connman needs to be adapted to support WPA3 type. There
16:06:28 <rainemak> #info <Jolla> is work in progress code for those but it does not work reliably
16:06:30 <rainemak> #info <Jolla> on all devices yet and was missing some parts about correctly
16:06:32 <rainemak> #info <Jolla> reporting type to higher level.
16:06:55 <legacychimera247> hello, 247 community member :)
16:07:58 <pherjung[m]> #info pherjung, Community
16:08:03 <flypig> #info David Llewellyn-Jones, community; and of course late.
16:08:45 <rainemak> no worry flypig pherjung[m] legacychimera247 . Nice that you were able to join as well.
16:08:52 <flypig> :D
16:08:54 <Raymaen[m]> #info Raymaen, Community
16:08:59 <flypig> Perhaps an obvious quustion (sorry), but is the plugin on GitHub?
16:09:30 <flypig> (in case anyone wants to help... I know I wouldn't know where to start).
16:09:59 <rainemak> Let's immediately extend this by 5mins
16:10:00 <rainemak> :-)
16:10:39 <rainemak> flypig, I don't recall by heart. Maybe mal or Keto would?
16:10:59 <Keto> probably this https://github.com/sailfishos/connman/blob/master/connman/plugins/sailfish_wifi.c
16:11:17 <rainemak> Keto, that was it
16:11:20 <flypig> Nice; thank you Keto.
16:12:11 <rainemak> #link https://github.com/sailfishos/connman/blob/master/connman/plugins/sailfish_wifi.c
16:12:51 <rainemak> #info Link to Sailfish OS wifi plugin
16:13:40 <mal> and there is the branch in there with the wip code, jb63050
16:13:41 <Keto> and there are probably some wip branches...
16:13:53 <Keto> right :)
16:14:07 <direc85[m]> WPA3 seems to depend on the access point as well.
16:14:24 <rainemak> 1 minute
16:14:28 <nephros> #info nephros, community, later-comer
16:15:04 <rainemak> please, let's continue leftover discussions at the end
16:15:13 <rainemak> let's move on to the next topic
16:15:14 <rainemak> #topic Allow apps to use nextcloud client or add ability to configure folder sync (10mins -- KeeperoftheKeys)
16:15:14 <rainemak> #info <KeeperoftheKeys> As documented in this topic Sailsync OwnCloud does not
16:15:14 <rainemak> #info <KeeperoftheKeys> work out of the box with recent versions of nextcloud
16:15:14 <rainemak> #info <KeeperoftheKeys> and due to Qt limitations this is only going to get
16:15:15 <rainemak> #info <KeeperoftheKeys> worse, @nephros has built a newer drop in binary with Qt
16:15:17 <rainemak> #info <KeeperoftheKeys> 5.15 but that is also a solution that will only hold so
16:15:19 <rainemak> #info <KeeperoftheKeys> long and while those who run NC instances where they
16:15:21 <rainemak> #info <KeeperoftheKeys> have full control can lower the
16:15:23 <rainemak> #info <KeeperoftheKeys> minimum.supported.desktop.version they are taking a risk
16:15:25 <rainemak> #info <KeeperoftheKeys> as per the NC devs.
16:15:27 <rainemak> #info <KeeperoftheKeys> IMHO Sailsync OwnCloud provides a functionality that
16:15:29 <rainemak> #info <KeeperoftheKeys> should just be part of the NC account settings, if that
16:15:31 <rainemak> #info <KeeperoftheKeys> is not a possibility then it would be nice if it could
16:15:33 <rainemak> #info <KeeperoftheKeys> leverage the builtin client (and credentials) instead of
16:15:35 <rainemak> #info <KeeperoftheKeys> needing to ship its own.
16:15:39 <rainemak> #link https://forum.sailfishos.org/t/22969
16:15:41 <rainemak> #info <Jolla> NextCloud account (and related components) could be our next
16:15:43 <rainemak> #info <Jolla> component to open source which would also enable contributions
16:15:45 <rainemak> #info <Jolla> from the Sailsync OwnCloud towards platform NextCloud. We shall
16:15:47 <rainemak> #info <Jolla> take this into account as we plan this. In many cases app
16:15:49 <rainemak> #info <Jolla> functionalities easily provide more value when / if they are
16:15:51 <rainemak> #info <Jolla> implemented as an operating system feature.
16:15:56 <rainemak> This is especially for cases like NextCloud
16:17:05 <poetaster> #info poetaster is late
16:17:06 <rainemak> From my personal point of view, I'd not limit too much NextCloud folders that are being synced
16:19:05 <rainemak> for the late comers as well, let's continue leftover discussions at the end.
16:19:23 <poetaster> ahoi.
16:19:24 <rainemak> surely, if we need more time to this, we could consider extending this topic
16:19:31 <rainemak> poetaster, hi there
16:20:09 <rainemak> how would see if NextCloud account would be the next one to be open sourced?
16:20:31 <rainemak> I'll give 5 mins more to this
16:20:56 <abr> +1 for nextcloud. that's got great potential.
16:20:57 <rainemak> Ah, I already extended to 10mins :-)
16:21:02 <flypig> This would be really positive. It already works really well, but there's scope for new features like this syncing.
16:21:18 <rainemak> flypig, indeed
16:21:19 <pherjung[m]> This may open various features!
16:21:33 <poetaster> I'd be happy, for sure. I've done a bit of nextcloud module hacking and it would be nice to couple the work more tightly.
16:21:37 <rainemak> one thing that I'd like myself is notes syncing
16:21:38 <abr> does that syncing include auto photo upload?
16:21:42 <pherjung[m]> syncing, tasks, better gallery integration
16:22:09 <flypig> rainemak, same here, Notes sync would be wonderful.
16:22:23 <abr> There's an official nextcloud notes app that just syncs text files. something like that would be great.
16:22:34 <rainemak> flypig, I use notes almost like a todo-list
16:23:18 <rainemak> 2mins
16:23:30 <nephros> AFAIK syncing Notes is just WebDAV file syncing.
16:23:42 <poetaster> I did some work on task list sfos apps and next cloud. non-trivial though there is some work done.
16:23:45 <nephros> At least that's what I do regularly.
16:23:55 <Cryx[m]> Opening Nextcloud would be nice. We  already have same apps like Talk and for Phone Track, both somehow in alpha/beta state, but a good start for more.
16:24:07 <poetaster> nephros, I also use your rclone method :)
16:24:36 <rainemak> time runs...
16:24:46 <nephros> Yea, and for Tasks, I use a TODO.txt formated Notes file
16:24:56 <flypig> abr, I currently use this https://openrepos.net/content/scharel/nextcloud-notes , but would love it to work with the default Notes app synced in both directions.
16:25:22 <rainemak> I think this really needs a bit attention when we are prioritizing components
16:25:28 <rainemak> based on your feedback
16:25:40 <abr> the key is using single account, so you're just signed in once
16:25:41 <direc85[m]> I have to check that app as well, flypig :)
16:25:56 <rainemak> but NextCloud has been on our mind
16:26:05 <poetaster> I was using https://openrepos.net/content/gmc/tasks for a while
16:26:07 <rainemak> it's also a great example
16:26:07 <flypig> direc85[m], it's nice, but I just don't want two Notes apps :)
16:26:15 <nephros> abr: true, and while it's possible to get apps to access the Account, I don't think that will fly in Harbour.
16:26:38 <ExTechOp> I haven't looked at the Nextcloud integration, are things like caldav supported?
16:26:58 <flypig> ExTechOp, yes!
16:27:04 <rainemak> I'll move to next top 30min past -> 4 mins to this
16:27:10 <rainemak> topic
16:27:17 <abr> caldav and carddav
16:27:54 <rainemak> having NextCloud plugin available that you really open up new directions
16:27:54 <nephros> I think first step for all the notes apps is to agree on a common storage location. Currently in Jolla Notes it's a SQLite DB.
16:28:07 <Cryx[m]> And viewing photos from the Nextcloud (as well as manual upload).
16:28:08 <ExTechOp> flypig abr Excellent, I know I have a case coming up where I can make use of both
16:28:39 <rainemak> nephros, damien already proposed a way to change backend type
16:29:03 <abr> there are generic accounts for both of those anyway I think. older than the nextcloud plugin.
16:29:10 <abr> i think they're open sourced already?
16:29:40 <rainemak> abr, I don't think so
16:30:13 <rainemak> very good thinking and discussion
16:30:15 <flypig> buteo?
16:30:32 <abr> https://github.com/sailfishos/buteo-sync-plugin-caldav/
16:30:32 <rainemak> flypig, yeah but the actual accounts / settings integration is elsewhere
16:30:42 <flypig> Ah, yes, I see.
16:30:57 <rainemak> flypig, I might remember wrong
16:31:11 <abr> that bit might be a good candidate for moving over to oss then
16:31:20 <rainemak> abr, correct
16:31:42 <rainemak> but NextCloud is one of the best examples if not the best
16:31:51 <abr> yeah it is
16:32:04 <rainemak> let's move on
16:32:11 <rainemak> #topic Support more codecs in QtMultimedia GStreamer plugin (5 mins -- roundedrectangl)
16:32:22 <rainemak> #info <roundedrectangl> Information about supported audio capture codecs in
16:32:22 <rainemak> #info <roundedrectangl> QtMultimedia GStreamer plugin seems to be hardcoded in
16:32:22 <rainemak> #info <roundedrectangl> Qt 5.6 here: qtmultimedia/src/plugins/gstreamer/mediacapture/qgstreameraudioencode.cpp
16:32:22 <rainemak> #info <roundedrectangl> at mer-5.6 · sailfishos/qtmultimedia · GitHub. I know
16:32:22 <rainemak> #info <roundedrectangl> that there are no plans for changing the core behaviour
16:32:24 <rainemak> #info <roundedrectangl> of this in the near future, because that would require a
16:32:26 <rainemak> #info <roundedrectangl> Qt update. But are there any plans for, at least, adding
16:32:28 <rainemak> #info <roundedrectangl> more codecs (such as Opus) to that hard-coded list? And
16:32:30 <rainemak> #info <roundedrectangl> would a pull request adding this get accepted?
16:32:32 <rainemak> #info <roundedrectangl> Related: How to record opus audio programatically?
16:32:34 <rainemak> #link https://github.com/sailfishos/qtmultimedia/blob/mer-5.6/src/plugins/gstreamer/mediacapture/qgstreameraudioencode.cpp
16:32:39 <rainemak> #link https://forum.sailfishos.org/t/how-to-record-opus-audio-programatically/25139
16:32:41 <rainemak> #info <Jolla> It might be possible to enable some additional codecs but it needs
16:32:43 <rainemak> #info <Jolla> to be tested that those actually work. Pull requests are always
16:32:45 <rainemak> #info <Jolla> welcome and we’ll review and test them.
16:35:15 <poetaster> currently: mpeg, vorbis, speex, gsm, pcm, amr and flac correct?
16:35:24 <roundedrectangl> hello, i got disconnected, sorry
16:35:41 <rainemak> no problem roundedrectangl
16:35:55 <flypig> poetaster, are you getting that from the code?
16:36:03 <poetaster> yup.
16:36:09 <flypig> Nice; thanks.
16:36:21 <piggz[m]> this ... codecCandidates << "audio/AAC" << "audio/mpeg" << "audio/vorbis" << "audio/speex" << "audio/GSM"
16:36:21 <piggz[m]> << "audio/PCM" << "audio/AMR" << "audio/AMR-WB" << "audio/FLAC";
16:36:35 <poetaster> yup.
16:36:39 <roundedrectangl> poetaster: as i said in my post, from QAudioRecorder::supportedAudioCodecs i get only “audio/vorbis”, “audio/speex”, “audio/PCM”, “audio/FLAC”
16:37:27 <flypig> roundedrectangl, you think Opus support is just a case of letting it through?
16:37:34 <piggz[m]> looks like the candidate list is looped over later
16:37:36 <rainemak> poetaster, roundedrectangl : based on variable name there's probably some checks elsewhere
16:37:52 <rainemak> piggz[m], +1
16:37:54 <abr> opus works well in sfos afaik. in gst at least
16:38:03 <roundedrectangl> flypig: yeah
16:38:30 <rainemak> let's move forward 40min past
16:38:34 <flypig> That's neat. Well sort of: it'd be nice if a PR wasn't needed.
16:38:39 <Keto> opus seems to be inclued in gst-plugins-bad
16:39:00 <abr> (sorry rainemak I only just saw your request to extend the meeting when I logged on today! i'm not on irc very much anymore...)
16:39:09 <poetaster> there would need to be work for setup. so it's not just enable and go.
16:39:10 <roundedrectangl> in code, if i understood correctly, it goes through codecs in that hard-coded list and filters for ones which the pulseaudio installation supports
16:39:25 <rainemak> no worry... I said earlier that we can use 90mins when needed
16:39:39 <abr> it's the start time that's important!
16:40:00 <rainemak> if 40mins past is not enough then we add another 5mins :-)
16:40:47 <poetaster> roundedrectangl, there is also minimal setup required for most codecs. not sure on the opus front
16:41:06 <rainemak> 5mins more to this
16:41:13 <rainemak> 45mins past
16:41:51 <roundedrectangl> well, if what i said is correct (it checks if a codec is installed and only marks it as supported if it is), then simply adding opus would not hurt much
16:42:14 <poetaster> true
16:42:31 <poetaster> but it's probably a no-op
16:43:49 <roundedrectangl> either way i think i will try to add opus to that list and compile and install the modified version of qtmultimedia on my device, then i will see if it will work and if it does make a PR
16:44:03 <rainemak> roundedrectangl, great
16:44:52 <rainemak> time to move on
16:44:52 <roundedrectangl> although, last commit date being 4 months ago scares me ;)
16:45:08 <rainemak> roundedrectangl, don't worry about it
16:45:15 <rainemak> #topic Linux on Mobile stand at FOSDEM in 2026 (10mins -- flypig)
16:45:15 <rainemak> #info <flypig> FOSDEM (https://fosdem.org) will take place again in Brussels on
16:45:15 <rainemak> #info <flypig> the weekend of 31 January 2026. In previous years we’ve had a
16:45:15 <rainemak> #info <flypig> very successful Linux on Mobile stand with Jolla being a big and
16:45:15 <rainemak> #info <flypig> important presence. The submission deadline for 2026 is
16:45:17 <rainemak> #info <flypig> approaching and I’m planning to request a Linux on Mobile stand
16:45:18 <rainemak> #info <flypig> again. As in previous years, it’d be fantastic to have Jolla on
16:45:20 <rainemak> #info <flypig> the stand. Would you consider joining the effort once again?
16:45:41 <rainemak> #info <Jolla> Excellent flypig that you’re again orchestrating this once again.
16:45:41 <rainemak> #info <Jolla> Very much appreciated. Indeed, the Linux on Mobile stand has been
16:45:41 <rainemak> #info <Jolla> successful in previous years.
16:45:41 <rainemak> #info <Jolla>
16:45:41 <rainemak> #info <Jolla> Yes, we are joining. Who are joining is not yet confirmed but most
16:45:43 <rainemak> #info <Jolla> likely at least Sami and Raine.
16:45:44 <rainemak> #info <Jolla>
16:45:46 <rainemak> #info <Jolla> Flypig, do you need anything from us?
16:46:22 <flypig> That's great news! In that case I can mention this in the submission. I think that's all I need to know right now.
16:46:23 <rainemak> I'm joining for sure
16:46:27 <flypig> Great!
16:46:55 <flypig> There will also be a "Free Your Android workshop" where people can come and flash their phones. It would be great to have Sailfish OS represented there too.
16:47:00 <rainemak> we could organize Sailfish OS meeting as well -- the usual one
16:47:25 <flypig> rainemak, we should look out of the Birds-of-a-Feather call and book a room for that.
16:47:36 <rainemak> flypig, that sounds good (both)
16:47:39 <flypig> I'm pretty sure that's not out yet though.
16:48:09 <rainemak> anybody else joining?
16:48:14 <flypig> So as a rallying call to the community as well, if anyone would like to help flash phones, please get in touch!
16:48:57 <flypig> In case anyone hasn't been before, it's always a great experience with chance to meet lots of Sailfish people.
16:49:13 <rainemak> +1 for that
16:49:13 <flypig> Including Sailors :)
16:49:16 <abr> Always a lot of SFOS people at FOSDEM!
16:49:27 <abr> and we always have a community evening somewhere too
16:49:45 <rainemak> abr, and so we shall 2026 as well
16:49:46 <Keto> I could finally this year try to join. Meant to couple of past years, but had always something else at the same time :)
16:49:52 <rainemak> abr, and so we shall have 2026 as well
16:50:03 <flypig> Keto, clear your calendar!
16:50:06 <direc85[m]> Last year it was my first FOSDEM and it was great in so many ways :)
16:50:38 <poetaster> I can't make it this coming year. sigh. Good chance to catch up!
16:50:45 <rainemak> 5mins extra
16:50:56 <flypig> direc85[m], I hope we'll see you this year too.
16:51:09 <rainemak> again, I already extended this to 10mins :-)
16:51:13 <TheKit[m]> flypig, talking about flashing phones, I'd definitely like to join
16:51:18 <flypig> But I'm sorry to hear that poetaster. I've always enjoyed your company at FOSDEM in previous years.
16:51:41 <direc85[m]> flypig, thanks, looking forward to it :)
16:51:45 <flypig> TheKit[m], superb! I'll put you in touch with the organisers if you're not already.
16:51:52 <poetaster> Yeah, it's a bit of a bummer cause it's nice to see u'all ;)
16:53:33 <TheKit[m]> flypig, I'm curious how that event would work in practice given the relatively limited list of devices though
16:54:28 <flypig> TheKit[m], you mean for Sailfish OS in particular? The room will cover all alternatives and there's no reason why community ports couldn't also be offered?
16:55:11 <rainemak> do you want more time for this?
16:55:12 <poetaster> And piggz[m] has a tablet port on offer :)
16:55:15 <pherjung[m]> whats the purpose of flashing devices? Is it like a stand where you come with your phone and choose which distribution to flash? Or is it only for Sailfish OS?
16:55:30 <rainemak> 5mins more
16:55:57 <flypig> pherjung[m], that's exactly it, but it's not Sailfish OS specific. Iit's being run by the FSFE.
16:56:14 <TheKit[m]> flypig: not only for SailfishOS, but in general for alternative OSes the list is relatively limited
16:56:45 <flypig> I suppose it's built around this campaign:
16:56:46 <flypig> https://fsfe.org/activities/android/
16:57:38 <flypig> TheKit[m], you make a good point, but I think that's nevertheless the arrangement: bring your phone and have it flashed.
16:59:16 <flypig> It seems most of the operating systems listed are AOSP-based. All the more reason to have Sailfish OS (and other GNU/Linux variants) there too.
16:59:17 <rainemak> let's to the last topic
16:59:21 <rainemak> let's move to the last topic
16:59:28 <flypig> Ack
16:59:33 <rainemak> #topic SFOS / Jolla pot. changes regarding the already inforced EU Cyber Resilience Act (5mins -- tmindrup)
16:59:33 <rainemak> #info <tmindrup> The EU Cyber Resilience Act (CRA) L_202402847EN.000101.fmx.xml
16:59:33 <rainemak> #info <tmindrup> imposes mandatory cybersecurity requirements on all products
16:59:33 <rainemak> #info <tmindrup> with digital elements sold in the EU, with consequences
16:59:33 <rainemak> #info <tmindrup> including significant fines, market access restrictions, and
16:59:35 <rainemak> #info <tmindrup> the loss of the CE marking for non-compliant products.
16:59:39 <rainemak> #info <tmindrup> Manufacturers, importers, and distributors face obligations to
16:59:41 <rainemak> #info <tmindrup> integrate security into product lifecycles, and some critical
16:59:43 <rainemak> #info <tmindrup> products must undergo third-party assessments. The regulation’s
16:59:45 <rainemak> #info <tmindrup> aim is to increase product security, but it creates challenges
16:59:47 <rainemak> #info <tmindrup> for businesses, especially smaller ones, in terms of compliance
16:59:49 <rainemak> #info <tmindrup> costs, testing, and the need for continuous security updates.
16:59:51 <rainemak> #link https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=OJ:L_202402847
16:59:53 <rainemak> #info <Jolla> Let’s take this more like a discussion topic.
17:03:21 <poetaster> Well, it would require a legal team the size of fort knox to even untangle that legislation so who knows where to begin. Assume it's theater.
17:03:33 <flypig> :)
17:03:43 <rainemak> poetaster, something like that
17:03:57 <rainemak> presumably
17:04:38 <Keto> Haven't had time to read through the whole thing, so not sure of all the parts that might afect Sailfish OS. But would assume that basic things like requirement for security updates can be considered covered
17:04:58 <rainemak> Keto, correct
17:05:30 <rainemak> time for open pull requests
17:05:42 <rainemak> it sounds
17:05:46 <rainemak> #topic Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla)
17:06:56 <flypig> This hasn't yet reached the 3-week point, but I'll mention it anyway as I'd appreciate views on it.
17:06:57 <piggz[m]> So, i understand the big scratchbox2 PR had some good testing, building all of devel?
17:06:57 <flypig> https://github.com/sailfishos/gst-droid/pull/83
17:07:37 <piggz[m]> flypig: was good to read your progress on that PR
17:07:46 <mal> piggz[m]: yes, seemed to work fine but still needs a proper review
17:07:47 <direc85[m]> piggz, I was just going to ask if anyone has more feedback about it :)
17:07:49 <rainemak> #link https://github.com/sailfishos/gst-droid/pull/83
17:08:02 <mal> I haven't yet had time to test that
17:08:58 <flypig> Thanks piggz[m], mal. It's not an area I really know about.
17:09:26 <rainemak> shall we move to general discussion
17:09:39 <mal> also the python 3.11 cross build issue mentioned in one earlier meeting was solved and python update should get integrated soon
17:09:53 <rainemak> mal, that I like to cover still
17:10:17 <roundedrectangl> that is very nice
17:10:28 <poetaster> 3.11 would be nice indeed.
17:10:39 <flypig> +1 on that.
17:10:57 <rainemak> mal, do you have still pending others PRs that are related
17:11:35 <mal> nope, just the main python PR is still open
17:11:41 <rainemak> great!
17:12:08 <rainemak> to the general then
17:12:11 <rainemak> #topic General discussion (10 mins or something)
17:12:54 <rainemak> How did you like the new newsletter section by pherjung[m] -- Community meeting summary
17:13:18 <rainemak> I find it great!
17:13:22 <flypig> Loved it! Great work pherjung[m]
17:13:34 <ExTechOp> Any date for the Xperia 10 IV / V posting on the forum?
17:13:38 <poetaster> works for me :)
17:13:38 <pherjung[m]> thank you very much! A good way to practice my English :)
17:13:42 <flypig> I may stop coming to the meetings now ;)
17:14:01 <rainemak> flypig, please don't :-)
17:14:21 <piggz[m]> If anyone wants to see SailfishOS on a nice tablet, the volla tablet port is working quite nicely :)
17:15:00 <rainemak> ExTechOp, not from me unfortunately. Do you mal anything new to share regarding Xperia 10 IV / V?
17:15:24 <poetaster> I thought it'd be a nice buzz for fossdem to show off a volla tablet with sfos.
17:15:36 <flypig> piggz[m], looks amazing.
17:15:38 <flypig> https://fosstodon.org/@piggz/115383533267498846
17:16:15 <mal> camera has still been causing issues on x10iv and v
17:17:15 <flypig> https://fosstodon.org/@piggz/115385355972301576
17:17:21 <poetaster> mal, video related?
17:17:55 <mal> I mean camera doesn't work at all
17:18:29 <poetaster> ah. sigh. blob's your uncle.
17:18:41 <direc85[m]> :D
17:19:10 <ExTechOp> mal Is there any kind of idea when better blobs could arrive, or should I just give the 10V away?
17:23:03 <rainemak> ExTechOp, hard to put an estimate on that
17:23:59 <rainemak> same time, we surely want to get this released
17:24:19 <pherjung[m]> Now that issues are on Github, would it be possible to use a label "Easy issue"?
17:24:40 <pherjung[m]> Maybe some people would be interested to contribute to Sailfish, but don't have all the skills
17:24:52 <rainemak> pherjung[m], afair that's something similar already.
17:24:58 <rainemak> there's
17:25:33 <rainemak> good first issue
17:26:28 <rainemak> let's start wrapping up
17:26:47 <poetaster> it's wordle time. good evening to you all!
17:26:56 <flypig> Best of luck poetaster!
17:27:01 <rainemak> poetaster, you too! nice to have you here as well
17:27:18 <rainemak> let's schedule next meeting
17:27:19 <rainemak> #topic Next meeting time and date (2 mins)
17:27:27 <rainemak> Proposing Thursday 6th November at 04:00 PM UTC
17:27:29 <ExTechOp> rainmak Meta question: do you think there'll be a time when you can answer the question?
17:27:45 <flypig> I think the clocks will change between now and then, right?
17:28:07 <direc85[m]> Ah, yes.
17:28:08 <rainemak> flypig, you're right I guess. didn't even check
17:28:11 <ExTechOp> Question: would moving the time one hour earlier be inconvenient for participants, because this gets a bit late in Finland?
17:28:35 <rainemak> ExTechOp, it'd be fine with one hour earlier
17:28:39 <roundedrectangl> quick update, i compiled qtmultimedia with opus support and guess what? it works!
17:28:48 <rainemak> ExTechOp, and you're right. it's kind of late already
17:28:51 <flypig> roundedrectangl, amazing work!
17:29:06 <roundedrectangl> yeah, but compiling took a while
17:29:16 <roundedrectangl> i guess i will make the pr now
17:29:45 <direc85[m]> Well that was fast :) That's great!
17:29:51 <rainemak> 6PM HKI time?
17:30:01 <ExTechOp> % date --date=2025-11-25T16:00:00Z
17:30:01 <ExTechOp> 2025-11-25T18:00:00 EET
17:30:24 <rainemak> yeap
17:30:30 <direc85[m]> Works for me
17:30:35 <flypig> So, that will leave it at the same start time in Finland?
17:30:52 <flypig> Or did I misunderstand?
17:31:38 <flypig> It's fine either way though :)
17:32:03 <ExTechOp> Leave the same time in UT, so daylight saving time will make it start at 18
17:32:10 <ExTechOp> in Finland
17:32:27 <direc85[m]> That's correct.
17:32:36 <rainemak> so 04:00 PM UTC
17:32:37 <flypig> Okay, so that's an hour earlier compared to today. Got it; thanks!
17:33:00 <rainemak> #info Next meeting will be held on Thursday 6th November 2025 at 04:00pm UTC: 2025-11-06T1600Z
17:33:10 <rainemak> thank you all!
17:33:17 <rainemak> #endmeeting