08:00:57 <pvuorela> #startmeeting Sailfish OS, open source, collaboration -- 14th November 2024
08:00:57 <sailbot> Meeting started Thu Nov 14 08:00:57 2024 UTC. The chair is pvuorela. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:57 <sailbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:01:05 <pvuorela> #info Meeting information and agenda can be found here:
08:01:16 <pvuorela> #link https://forum.sailfishos.org/t/community-meeting-on-14th-november-2024/20923
08:01:26 <arisel> #info arisel, community
08:01:26 <pvuorela> 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.
08:01:36 <pvuorela> #topic Brief introduction (5 min). Please prefix your name/handle with #info
08:01:43 <pvuorela> arisel: too fast :)
08:01:44 <tuplasuhveli[m]> #info tuplasuhveli, community
08:01:46 <arisel> #info arisel, community
08:01:49 <pvuorela> #info Pekka Vuorela, Jolla
08:01:58 <ViGe> #info Ville Nummela, community
08:02:26 <Crabster> #info Crabster - lurker
08:02:58 <sebix[m]> #info Seix, community
08:02:58 <sebix[m]> s/Seix/Sebix/
08:03:17 <direc85> #info Matti Viljanen, Jolla
08:06:44 <pvuorela> alright, let's get started. we have two topics that were requested late for last meeting so handling now. and this time one topic arriving late so it'll go to next meeting for proper handling.
08:06:58 <pvuorela> #topic C2 software issues - Do you need testers to get things resolved? (5 mins -- asked by RXShorty)
08:07:12 <pvuorela> #info <RXShorty> I read about and experience the issues myself (eg. unable to get passed by the unlock code).
08:07:29 <pvuorela> #info <Jolla> This has turned out to be difficult to reproduce. That said, we have figured out some issues
08:07:32 <pvuorela> #info <Jolla> that could have been causing issues and those are fixed in upcoming Sailfish 5.0.0.28.
08:07:35 <pvuorela> #link https://forum.sailfishos.org/t/poll-continue-jolla-c2-shipments/21028
08:09:46 <pvuorela> there's been all sort of little things to improve the first time use. some errors spotted, now shutting down automatically if booting to startup wizard but not doing anything. extra check for battery before starting encryption.
08:11:27 <Keto> 5.0.0.29 ;)
08:11:37 <pvuorela> right :)
08:11:46 <pvuorela> anyhow, let's move forward
08:11:56 <pvuorela> #topic Sailfish OS 5.x: What is in the current pipeline? (3 mins -- asked by JoshStrobl)
08:12:06 <pvuorela> #info <JoshStrobl> While I am sure the team is focused heavily on addressing some of the issues
08:12:09 <pvuorela> #info <JoshStrobl> raised by the community on the forums, is there anything specific the team
08:12:12 <pvuorela> #info <JoshStrobl> would like to call out as being items that are going to be addressed
08:12:15 <pvuorela> #info <JoshStrobl> in forthcoming updates? If so, could some time set aside for a
08:12:18 <pvuorela> #info <JoshStrobl> forum post to be written on the matter?
08:12:21 <pvuorela> #info <Jolla> We have a dedicated VoLTE group, and aim is to get that also out the soonest.
08:12:24 <pvuorela> #info <Jolla> Due to the shipping issues that we have seen that VoLTE testing has been pushed
08:12:27 <pvuorela> #info <Jolla> a bit background. We are now checking if we could deliver VoLTE packages for
08:12:30 <pvuorela> #info <Jolla> early testing via Community OBS even before CBeta testing.
08:12:33 <pvuorela> #info <Jolla> Besides that in near future we are working on other enhancements to C2.
08:14:51 <pvuorela> and bunch of core component updates are at least in the pipeline.
08:15:23 <pvuorela> maybe that's about it.
08:15:32 <pvuorela> #topic Open PR discussion (5 mins -- asked by Jolla)
08:15:42 <pvuorela> anything to discuss?
08:19:34 <rinigus> does that volte group work on C2 only or is it something more generic?
08:19:40 <rinigus> (morning)
08:19:57 <pvuorela> this is for C2
08:20:04 <rinigus> thanks
08:20:35 <pvuorela> no PRs so moving to generic discussion.
08:20:36 <pvuorela> #topic General discussion (10 mins)
08:21:01 <tuplasuhveli[m]> I was wondering, if it would make sense to add the table of community hardware adaptations (https://forum.sailfishos.org/t/community-hardware-adaptations/14081) to the list of supported devices in the documentation? This way, all the device-related information could be found in one place.
08:22:33 <pvuorela> i
08:22:48 <pvuorela> i'd guess it shouldn't be too bad to have a link there
08:23:05 <ViGe> I agree, link would be great
08:23:20 <pvuorela> suppose you mean from something like this https://docs.sailfishos.org/Support/Supported_Devices/
08:23:43 <tuplasuhveli[m]> Yes, exactly!
08:23:46 <direc85> I'm in favor of adding the link as well
08:24:50 <rinigus> maybe then we, as porters, will remember to update that table
08:25:08 <direc85> There's also https://wiki.merproject.org/wiki/Adaptations/libhybris
08:26:01 <rinigus> or maybe such update is something that users could do instead
08:26:02 <tuplasuhveli[m]> Although, adding just a link does have the disadvantage of those devices not showing up, when doing a search in the documentation with a device name as a keyword.
08:26:14 <mal> that has been rarely updated, maybe having similar in github would be better
08:26:32 <mal> I mean that wiki page
08:26:50 <pvuorela> mal: libhybris?
08:28:13 <mal> probably some repo to mer-hybris github or something
08:31:33 <arisel> I'd just like to know if my question on the android layer + bluetooth was precise enough to know what kind of statement/vision I think would be needed. If not I'd be happy to clarify.
08:32:03 <pvuorela> i think it was precise enough.
08:32:48 <pvuorela> ok, if no other things, let's wrap up.
08:32:49 <pvuorela> #topic Next meeting time and date (1 min)
08:33:01 <pvuorela> Proposing Thursday 28th November at 08:00am UTC.
08:33:09 <pvuorela> i.e. same time in two weeks
08:33:28 <tuplasuhveli[m]> Works for me!
08:34:05 <pvuorela> #info Next meeting will be held on Thursday 28th November 2024 at 08:00am UTC: 2024-11-28T0800Z
08:34:30 <pvuorela> #endmeeting