| Crabster | morning | 07:52 |
|---|---|---|
| tuplasuhveli[m] | Good morning! | 07:52 |
| pvuorela | morning! | 07:53 |
| direc85 | Good morning! | 07:53 |
| ViGe | Good Morning! | 07:59 |
| pvuorela | it's time to get started | 08:00 |
| pvuorela | #startmeeting Sailfish OS, open source, collaboration -- 14th November 2024 | 08:00 |
| 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 |
| sailbot | Useful Commands: #action #agreed #help #info #idea #link #topic. | 08:00 |
| *** sailbot changes topic to " (Meeting topic: Sailfish OS, open source, collaboration -- 14th November 2024)" | 08:00 | |
| pvuorela | #info Meeting information and agenda can be found here: | 08:01 |
| pvuorela | #link https://forum.sailfishos.org/t/community-meeting-on-14th-november-2024/20923 | 08:01 |
| arisel | #info arisel, community | 08:01 |
| 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 |
| pvuorela | #topic Brief introduction (5 min). Please prefix your name/handle with #info | 08:01 |
| *** sailbot changes topic to "Brief introduction (5 min). Please prefix your name/handle with #info (Meeting topic: Sailfish OS, open source, collaboration -- 14th November 2024)" | 08:01 | |
| pvuorela | arisel: too fast :) | 08:01 |
| tuplasuhveli[m] | #info tuplasuhveli, community | 08:01 |
| arisel | #info arisel, community | 08:01 |
| pvuorela | #info Pekka Vuorela, Jolla | 08:01 |
| ViGe | #info Ville Nummela, community | 08:01 |
| Crabster | #info Crabster - lurker | 08:02 |
| sebix[m] | #info Seix, community | 08:02 |
| sebix[m] | s/Seix/Sebix/ | 08:02 |
| direc85 | #info Matti Viljanen, Jolla | 08:03 |
| 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 |
| pvuorela | #topic C2 software issues - Do you need testers to get things resolved? (5 mins -- asked by RXShorty) | 08:06 |
| *** sailbot changes topic to "C2 software issues - Do you need testers to get things resolved? (5 mins -- asked by RXShorty) (Meeting topic: Sailfish OS, open source, collaboration -- 14th November 2024)" | 08:06 | |
| pvuorela | #info <RXShorty> I read about and experience the issues myself (eg. unable to get passed by the unlock code). | 08:07 |
| pvuorela | #info <Jolla> This has turned out to be difficult to reproduce. That said, we have figured out some issues | 08:07 |
| pvuorela | #info <Jolla> that could have been causing issues and those are fixed in upcoming Sailfish 5.0.0.28. | 08:07 |
| pvuorela | #link https://forum.sailfishos.org/t/poll-continue-jolla-c2-shipments/21028 | 08:07 |
| 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:09 |
| Keto | 5.0.0.29 ;) | 08:11 |
| pvuorela | right :) | 08:11 |
| pvuorela | anyhow, let's move forward | 08:11 |
| pvuorela | #topic Sailfish OS 5.x: What is in the current pipeline? (3 mins -- asked by JoshStrobl) | 08:11 |
| *** sailbot changes topic to "Sailfish OS 5.x: What is in the current pipeline? (3 mins -- asked by JoshStrobl) (Meeting topic: Sailfish OS, open source, collaboration -- 14th November 2024)" | 08:11 | |
| pvuorela | #info <JoshStrobl> While I am sure the team is focused heavily on addressing some of the issues | 08:12 |
| pvuorela | #info <JoshStrobl> raised by the community on the forums, is there anything specific the team | 08:12 |
| pvuorela | #info <JoshStrobl> would like to call out as being items that are going to be addressed | 08:12 |
| pvuorela | #info <JoshStrobl> in forthcoming updates? If so, could some time set aside for a | 08:12 |
| pvuorela | #info <JoshStrobl> forum post to be written on the matter? | 08:12 |
| pvuorela | #info <Jolla> We have a dedicated VoLTE group, and aim is to get that also out the soonest. | 08:12 |
| pvuorela | #info <Jolla> Due to the shipping issues that we have seen that VoLTE testing has been pushed | 08:12 |
| pvuorela | #info <Jolla> a bit background. We are now checking if we could deliver VoLTE packages for | 08:12 |
| pvuorela | #info <Jolla> early testing via Community OBS even before CBeta testing. | 08:12 |
| pvuorela | #info <Jolla> Besides that in near future we are working on other enhancements to C2. | 08:12 |
| pvuorela | and bunch of core component updates are at least in the pipeline. | 08:14 |
| pvuorela | maybe that's about it. | 08:15 |
| pvuorela | #topic Open PR discussion (5 mins -- asked by Jolla) | 08:15 |
| *** sailbot changes topic to "Open PR discussion (5 mins -- asked by Jolla) (Meeting topic: Sailfish OS, open source, collaboration -- 14th November 2024)" | 08:15 | |
| pvuorela | anything to discuss? | 08:15 |
| rinigus | does that volte group work on C2 only or is it something more generic? | 08:19 |
| rinigus | (morning) | 08:19 |
| pvuorela | this is for C2 | 08:19 |
| rinigus | thanks | 08:20 |
| pvuorela | no PRs so moving to generic discussion. | 08:20 |
| pvuorela | #topic General discussion (10 mins) | 08:20 |
| *** sailbot changes topic to "General discussion (10 mins) (Meeting topic: Sailfish OS, open source, collaboration -- 14th November 2024)" | 08:20 | |
| 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:21 |
| pvuorela | i | 08:22 |
| pvuorela | i'd guess it shouldn't be too bad to have a link there | 08:22 |
| ViGe | I agree, link would be great | 08:23 |
| pvuorela | suppose you mean from something like this https://docs.sailfishos.org/Support/Supported_Devices/ | 08:23 |
| tuplasuhveli[m] | Yes, exactly! | 08:23 |
| direc85 | I'm in favor of adding the link as well | 08:23 |
| rinigus | maybe then we, as porters, will remember to update that table | 08:24 |
| direc85 | There's also https://wiki.merproject.org/wiki/Adaptations/libhybris | 08:25 |
| rinigus | or maybe such update is something that users could do instead | 08:26 |
| 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 |
| mal | that has been rarely updated, maybe having similar in github would be better | 08:26 |
| mal | I mean that wiki page | 08:26 |
| pvuorela | mal: libhybris? | 08:26 |
| mal | probably some repo to mer-hybris github or something | 08:28 |
| 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:31 |
| pvuorela | i think it was precise enough. | 08:32 |
| pvuorela | ok, if no other things, let's wrap up. | 08:32 |
| pvuorela | #topic Next meeting time and date (1 min) | 08:32 |
| *** sailbot changes topic to "Next meeting time and date (1 min) (Meeting topic: Sailfish OS, open source, collaboration -- 14th November 2024)" | 08:32 | |
| pvuorela | Proposing Thursday 28th November at 08:00am UTC. | 08:33 |
| pvuorela | i.e. same time in two weeks | 08:33 |
| tuplasuhveli[m] | Works for me! | 08:33 |
| pvuorela | #info Next meeting will be held on Thursday 28th November 2024 at 08:00am UTC: 2024-11-28T0800Z | 08:34 |
| pvuorela | #endmeeting | 08:34 |
| sailbot | Meeting ended Thu Nov 14 08:34:30 2024 UTC. | 08:34 |
| sailbot | Minutes: https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2024/sailfishos-meeting.2024-11-14-08.00.html | 08:34 |
| sailbot | Minutes (text): https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2024/sailfishos-meeting.2024-11-14-08.00.txt | 08:34 |
| sailbot | Log: https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2024/sailfishos-meeting.2024-11-14-08.00.log.html | 08:34 |
| *** sailbot changes topic to "Next meeting will be held on Thursday 31st October 2024 at 07:00am UTC: 2024-10-31T0700Z" | 08:34 | |
| pvuorela | thanks! | 08:34 |
| tuplasuhveli[m] | Thanks everyone :--) | 08:34 |
| Crabster | thx #? | 08:34 |
| arisel | :) | 08:35 |
| direc85 | Thanks! | 08:39 |
| arisel | am I the only one who thinks that this channels topic is now broken? | 08:45 |
| ViGe | looks a bit broken indeed | 08:46 |
| sebix[m] | On Matrix there's no topic at all | 08:46 |
| pvuorela | arisel: nope, was just wondering how that was supposed to get changed outside the meeting :) | 08:47 |
| mal | pvuorela: sailbot changed it to incorrect one | 08:48 |
| mal | at 10:34 | 08:48 |
| arisel | think maybe just set it with /topic. sailbot seems to restore the old one upon meeting end. | 08:48 |
| pvuorela | the channel has +t so that shouldn't work. | 08:49 |
| ViGe | pvuorela: I'm quite sure the instruction page has that info somewhere there, probably on the bottom | 08:49 |
| ViGe | I think just #topic might do the trick | 08:53 |
| Keto | needs to be updated via chanserv, just a moment. the meetbot automatically reverts it to the one that was there before the meeting | 08:55 |
| ViGe | #topic Next meeting will be held on Thursday 28th November 2024 at 08:00am UTC: 2024-11-28T0800Z | 08:56 |
| *** ChanServ changes topic to "Next meeting will be held on Thursday 28th November 2024 at 08:00am UTC: 2024-11-28T0800Z" | 08:57 | |
| sebix[m] | thanks! | 08:57 |
| *** amccarthy is now known as Guest9415 | 17:16 | |
| *** amccarthy_ is now known as amccarthy | 17:16 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!