07:00:08 #startmeeting Sailfish OS, open source, collaboration -- 17th Aug 2023 07:00:08 Meeting started Thu Aug 17 07:00:08 2023 UTC. The chair is rainemak. Information about MeetBot at http://wiki.debian.org/MeetBot. 07:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 07:00:27 #info Meeting information and agenda can be found here: 07:00:31 #link https://forum.sailfishos.org/t/community-meeting-on-irc-17th-august-2023/15962 07:00:37 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. 07:00:47 #topic Brief introduction (5 min). Please prefix your name/handle with #info 07:00:52 Morning 07:00:55 #info Otto Mäkelä, community 07:01:02 morning b100dian 07:01:02 #info Vlad G, community 07:01:04 #info Johannes Fuchs - community 07:01:13 #info Raine Mäkeläinen, sailor @ Jolla, chairperson today 07:01:14 #info Matti Viljanen, community 07:01:49 #info sebix, community 07:01:57 #info xenial-user - lurker 07:04:41 #info Pami Ketolainen, sailor @ Jolla 07:05:25 We have only one topic today and let's get move to that one soon. We were fine to take it even though it arrived a bit late. 07:05:33 #topic Helping with Community OBS (10 mins -- asked by vlagged[m] / b100dian) 07:05:46 #info The current build time for some projects (qt5.15, nodejs) may take a 07:05:52 #info full day on ARM slaves. Is there anything the community can help with, like making more build 07:05:58 #info slaves available? Alternatively, is setting up another OBS instance something Jolla can help with 07:06:02 #info configuring? 07:06:09 #info Thank you for raising this issue. 07:06:16 #info We briefly discussed qt5.15 issue earlier but unfortunately, we do not have a proposal yet. Need more investigation. 07:07:31 So, to be clear, there was more to this question - like if community can participate with hardware. 07:07:50 Not sure this was explained clearly 07:08:08 It was clear enough. Thank you for your clarification. 07:08:19 Ok, thanks for confirming 07:08:41 Is that the complete answer? 07:08:43 My personal take is that let's say Qt5.15 should really take full day with whatever HW 07:08:59 sebix[m], yes 07:09:32 That is correct, but a such build time easily beats any network lag, so in this case it should be possible to add machines from far away somehow 07:09:35 No comments / updates regarding how could community help / participate 07:11:33 is it a problem where more hardare would help? 07:12:05 In general when a chum build is happening, it might be difficult to build something else 07:12:32 indeed that is a transient state, which does not happen that often now 07:13:05 right 07:13:38 correcting myself whilst probably was clear... building Qt5.15 shouldn't take full day 07:14:35 b100dian, noted by Jolla. let's think what can be done. 07:14:46 thank you 07:14:47 Maybe it's time to move on 07:15:14 #topic Untracked bug reports (5 min -- asked by pherjung) 07:15:20 #info Untracked bug reports 07:15:25 #link https://forum.sailfishos.org/t/community-meeting-on-irc-17th-august-2023/15962/2 07:15:41 #info The Community Bug Coordination Team have done a superb job once again this fortnight. 07:16:06 #info Unfortunately we didn't manage to check these after summer vacation period which is still ongoing. 07:16:24 #info We'll comment results to the forum post later this week. Thank you for your understanding. 07:17:28 I'm not sure if pherjung[m] is around to comment? 07:19:33 Time to move on 07:20:05 #topic Open PR discussion (5 mins -- asked by jolla / b100dian) 07:20:11 I think most of us would want to know have there been any developments on the funding and ownership front that could be shared here? 07:20:54 let's say for a moment on a topic. generic is coming. 07:20:58 let's stay for a moment on a topic. generic is coming. 07:21:03 #info Open PR URL: Buffers are not always recycled automatically by b100dian 07:21:03 #link https://github.com/sailfishos/droidmedia/pull/111 07:21:15 Oops, sorry, I read that as "Open discussions" 07:21:32 #info The PR solves a situation observed on Zenfone 8, port based on lineage-18.1, and video playback - 07:21:32 #info with new media buffers coming in with the same slot as existing ones, but without recycling old buffers 07:21:32 #info (they should have been null if they were recycled). The PR tracks the old buffers and the memory 07:21:32 #info pointing at them, and does two things: releases old buffers ASAP and reclaims memory only when the 07:21:34 #info client (gecko-camera, gst-droid) is not using them anymore. 07:21:40 #info We'll try to find somebody to review this. Thank you for your contribution. 07:22:14 thank you. I'm available if there are questions 07:22:22 thank you for that b100dian 07:23:17 questions/comments should be written down to the PR as usual 07:23:21 ^ as well 07:23:27 #info Any open PRs to discuss? 07:23:33 How device/port specific that issue is? Is it possible that some other device unknowingly benefits from the PR? 07:24:15 let's cover direc85[m] 's question first before moving to "any open PRs to discuss?" 07:24:21 It is. I think it is specific to media handling in Android CCodec, with newer (>=Lineage 18.1/AOSP 11) ports 07:25:03 I have read about a possible playback error on Volla 22 (I think?) but maybe it is not related 07:25:32 However, the PR should not bring any material change to device behaving as before 07:25:37 there are also still some async issues in the video playback 07:26:01 I guess there are no other PRs to discuss 07:27:01 #info Maybe worth noting that we're review Qt6 PRs that community has created 07:27:13 Let's move on to the general discussion. 07:27:18 #topic General discussion (20 min) 07:27:30 Again: I think most of us would want to know have there been any developments on the funding and ownership front that could be shared here? 07:27:32 #info David Llewellyn-Jones - community (sorry for the late entry) 07:28:14 ExTechOp, no comments at this stage. 07:28:23 Sigh 07:28:27 good morning flypig 07:28:38 I just wanted to mention that so far my Sailfish device has been working great on the chaos camp including their custom GSM network (just no VoLTE, but I am not sure if they even have that) 07:28:53 Good morning :) 07:28:54 #info Nico - community 07:30:42 Nico, pleased to hear 07:31:19 Nico, could you share a link to the camp? 07:31:34 yes please! :-) 07:31:54 Uhm, let me look, I always struggle to find the right page, but I probably can find the blog... 07:32:14 no worries if you don't find it 07:33:01 Chaos camp blog with details: https://events.ccc.de/camp/ 07:33:47 Or maybe that is the start page rather :D 07:34:28 #info Chaos camp blog with details https://events.ccc.de/camp/ 07:36:23 One very interesting development related thingie is that flypig has started looking into newer gecko engine. I bet that at point he'd appreciate if others would contribute as well. 07:37:14 Nice 07:37:45 First stages are problematic to distribute for multiple developers as he needs to get it building first. 07:38:16 but I do know that he has right kind of knowledge for this 07:38:28 Great to hear! Is that started in the gecko-dev fork? Is it needing a rust update? 07:39:04 let's see if flypig himself is able to comment on this 07:39:48 personally I'd definitely would like to give a look to this. 07:41:30 Sorry, I have an intermittent connection. 07:41:45 no worries 07:42:01 So far, I've not hit antyneed for a rust update, but it might come. 07:42:19 The Sailfish OS Rust repo is at 1.61: https://github.com/sailfishos/rust 07:43:07 Which is a great upgrade over 1.52, which doesn't support Rust Edition 2021. 07:43:09 Once it's building, I'd love help. I'm putting info here: https://www.flypig.co.uk/gecko 07:43:36 Thank you flypig! 07:44:43 Thanks :) I could do with your help with rust info direc85[m] :) 07:45:04 flypig, once you're done. I'd like to document your findings docs.sailfishos.org as well. 07:45:26 great stuff! 07:46:21 documenting to docs.sailfishos.org together with you of course (and that goes without saying) 07:46:37 let's move on 07:46:40 That sounds good rainemak, although right now it's all very similar to ESR 78 (which is good in my opinion), so not much to add yet :) 07:46:58 I'm thinking more about the process 07:47:08 as you happen to take notes 07:47:26 Oh, yes, excellent! 07:47:40 only few Sailors have "notes" regarding this :-) 07:48:07 I'm following yours, he he:) 07:49:27 #topic Next meeting time and date (5 min) 07:49:38 Proposing Thursday 31st August at 07:00am UTC. 07:50:28 Sounds good, for what it's worth :) 07:50:31 How does that sound like? Back to bi-weekly schedule that is. 07:50:39 Works4me. 07:51:24 It'll be nice to have the meetings running again. 07:51:30 settled then 07:51:38 #info Next meeting will be held on Thursday 31st August 2023 at 07:00am UTC: 2023-08-31T0700Z 07:51:47 Thank you everyone for the meeting! 07:52:04 thx all 07:52:20 Hope everybody have had chance to relax and recharge during summer time. 07:52:40 Thanks rainemak, all! 07:52:51 #endmeeting