| ExTechOp | Good morning, everyone! | 06:58 |
|---|---|---|
| Solrac[m] | Good Morning! | 06:59 |
| ViGe | Good Morning! | 06:59 |
| ViGe | #startmeeting Sailfish OS, open source, collaboration -- 13th April 2023 | 07:00 |
| sailbot | Meeting started Thu Apr 13 07:00:04 2023 UTC. The chair is ViGe. Information about MeetBot at http://wiki.debian.org/MeetBot. | 07:00 |
| sailbot | Useful Commands: #action #agreed #help #info #idea #link #topic. | 07:00 |
| *** sailbot changes topic to " (Meeting topic: Sailfish OS, open source, collaboration -- 13th April 2023)" | 07:00 | |
| ViGe | #info Meeting information and agenda can be found here: | 07:00 |
| ViGe | #link https://forum.sailfishos.org/t/community-meeting-on-irc-13th-april-2023/15242 | 07:00 |
| ViGe | 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 |
| ViGe | #topic Brief introduction (5 min). Please prefix your name/handle with #info | 07:00 |
| *** sailbot changes topic to "Brief introduction (5 min). Please prefix your name/handle with #info (Meeting topic: Sailfish OS, open source, collaboration -- 13th April 2023)" | 07:00 | |
| ViGe | #info Ville Nummela - sailor@Jolla and chairperson today | 07:00 |
| ExTechOp | #info Otto Mäkelä, community | 07:01 |
| Solrac[m] | #info LSolrac - comunity | 07:01 |
| sledges | #info Simonas Leleiva -- privateer for Jolla | 07:01 |
| abr | #info Andrew Branson - sailor | 07:01 |
| rainemak | #info Raine Mäkeläinen - sailor @ Jolla | 07:01 |
| Crabster | #info Crabster - lurker @ meeting | 07:02 |
| ViGe | Looks like a win for team Sailors, at least if I can count correctly | 07:04 |
| ViGe | #topic Support for passing QR-read Wifi information to Networksettings (3-5 min -- asked by nephros) | 07:05 |
| *** sailbot changes topic to "Support for passing QR-read Wifi information to Networksettings (3-5 min -- asked by nephros) (Meeting topic: Sailfish OS, open source, collaboration -- 13th April 2023)" | 07:05 | |
| ViGe | #info <nephros> There have been some efforts to make it possible to support `wifi:` strings as used in QR codes for network configuration. | 07:05 |
| ViGe | #info <nephros> In case there is interest at Jolla, please use the github repo for any comments, and if you like, `git apply https://raw.githubusercontent.com/nephros/wifi-qr-handler/master/patch/unified_diff.patch`. | 07:05 |
| ViGe | #info <nephros> Discussion: https://forum.sailfishos.org/t/codereader-cannot-use-wifi-code-not-supported/15193 | 07:05 |
| ViGe | #info <nephros> Some code: https://github.com/nephros/wifi-qr-handler | 07:05 |
| ViGe | And the answer: | 07:05 |
| ViGe | #info <Jolla> The wifi handler looks like a nice start, but on the details this wouldn’t be necessarily how we’d like this implemented. | 07:05 |
| ViGe | #info <Jolla> 1) not sure should the handling be in the settings app (not nice acumulating more and more to the d-bus api of the generic settings framework) or rather the connection dialog, | 07:05 |
| ViGe | #info <Jolla> 2) the patch doesn’t enable the QR code network adding from anywhere (suppose that’s called from third party app then), | 07:05 |
| ViGe | #info <Jolla> 3) the QR code shouldn’t be included in the details of network addition requests, rather the caller should consume QR code details and proceed with plain network properties. | 07:05 |
| ViGe | nephros isn't here, and neither is attah :( | 07:07 |
| Solrac[m] | Would it be acceptable to reimplement the patch to link to the native connection prompt and be automatically filled? | 07:08 |
| ViGe | Hard to say | 07:10 |
| ViGe | Let's move on to next question, also by nephros | 07:10 |
| ViGe | #topic Community contributions to Jolla closed components (10 min -- asked by nephros) | 07:10 |
| *** sailbot changes topic to "Community contributions to Jolla closed components (10 min -- asked by nephros) (Meeting topic: Sailfish OS, open source, collaboration -- 13th April 2023)" | 07:10 | |
| ViGe | #info <nephros> Over the years, there have been several modifications done to Jolla-distributed apps by community hackers. | 07:10 |
| ViGe | #info <nephros> (Sometimes distributed as so-called Patchmanager Patches, sometimes as separate packages, or just locally). | 07:10 |
| ViGe | #info <nephros> While many of these have been hacks and other modifications not suitable for inclusion in the original apps, often they are fixes to small annoyances, bugs, or provide additional features. | 07:10 |
| ViGe | #info <nephros> Some of the latter category may warrant inclusion in the original app or component. | 07:10 |
| ViGe | #info <nephros> Just for sake of discussion I'll select the following some examples: A small but useful new feature: Sandbox Indicator https://coderus.openrepos.net/pm2/project/patch-sandbox-indicator - 500+ activations. | 07:10 |
| ViGe | #info <nephros> Annoyance fix: Allowed Orientation patch https://coderus.openrepos.net/pm2/project/sailfishos-default-allowed-orientations-patch - 1800+ activations. | 07:10 |
| ViGe | #info <nephros> A new/missing feature: wifi-qr-handler - as discussed in the other meeting topic. | 07:10 |
| ViGe | #info <nephros> Now for the questions (note that they do not mean the examples above explicitly, but in general): | 07:10 |
| ViGe | #info <nephros> 1. Is there interest from Jolla, and a conceivable way to upstream some of those? | 07:10 |
| ViGe | #info <nephros> 2. If yes, what would be the preferred avenue of communication from the community to Jolla? | 07:10 |
| ViGe | #info <nephros> 3. If yes, what are requirements from Jolla to consider inclusion? | 07:11 |
| ViGe | #info <nephros> If there is interest, I would propose something similar to the Bug Coordination team who would vet any community-nominated candidates against Jolla requirements, and propose them in a way similar to we do it with bugs or PRs now. | 07:11 |
| ViGe | #info <Jolla> 1. From this particular set of patches we probably wouldn’t be merging any. | 07:11 |
| ViGe | #info <Jolla> Sandbox should be enabled more or less always and the user shouldn’t need to care. | 07:11 |
| ViGe | #info <Jolla> The orientation is overriding the Silica apis and breaks their expectations. | 07:11 |
| ViGe | #info <Jolla> The wifi handler needs a bit more work and architecture adjustments. | 07:11 |
| ViGe | #info <Jolla> However that wouldn’t mean there couldn’t be other community contributions to consider merging mainline. | 07:11 |
| ViGe | #info <Jolla> 2 & 3. We have already some precedent on enabling community to work on the closed components. This requires contribution agreement etc for the contributor. | 07:11 |
| Solrac[m] | Thats rather nice to hear. However, I'd like to ask, on behalf. Could Jolla provide some feedback regarding what kind of work and adjustments a patch may need to be considered? | 07:13 |
| ViGe | Of course | 07:13 |
| ViGe | The usual pull request review process includes that :) | 07:14 |
| Solrac[m] | I think the patch devs would appreciate that quite a bit. It can also shed light for future patches. | 07:14 |
| Solrac[m] | Even better~ | 07:14 |
| ExTechOp | Making the "wide spacebar" a switchable part of the default keyboard would be nice :-D | 07:15 |
| Solrac[m] | I completely agree, at least as a setting would be nice as well | 07:16 |
| ViGe | Time to move on to the next question, which was asked by remote, who is also not here today | 07:19 |
| ViGe | #topic can we get Filter pulley menu in Messages app to search by a contact name/phone? (3 min -- asked by remote) | 07:20 |
| *** sailbot changes topic to "can we get Filter pulley menu in Messages app to search by a contact name/phone? (3 min -- asked by remote) (Meeting topic: Sailfish OS, open source, collaboration -- 13th April 2023)" | 07:20 | |
| ViGe | #info <remote> sometimes I have to scroll for way too long to reach the conversation I need | 07:20 |
| ViGe | And here is the answer: | 07:20 |
| ViGe | #info <Jolla> Searching on Messages is indeed a feature to consider. And in fact we have an open item for that from the very beginning of the project. | 07:20 |
| ViGe | #info <Jolla> However cannot give any estimates we’d get around to implement it. | 07:20 |
| ViGe | #info <Jolla> So far this feature hasn’t seem to be requested that much, but noted that it is now. | 07:20 |
| Solrac[m] | Search by Text, Contact or Date would be incredibly useful 🤔 | 07:22 |
| ViGe | yup | 07:22 |
| ViGe | Time for the last question, asked by rinigus. Who is also not present today. | 07:23 |
| ViGe | #topic GCC update (10 min -- asked by rinigus) | 07:23 |
| *** sailbot changes topic to "GCC update (10 min -- asked by rinigus) (Meeting topic: Sailfish OS, open source, collaboration -- 13th April 2023)" | 07:23 | |
| ViGe | #info <rinigus> We are currently on GCC 8 which is showing its limitations. | 07:23 |
| ViGe | #info <rinigus> It would make sense to take GCC update into the pipeline. | 07:23 |
| ViGe | #info <rinigus> Any plans regarding it? | 07:23 |
| ViGe | #info <rinigus> Corresponding bug report: https://forum.sailfishos.org/t/gcc-update-from-gcc-8/15144 | 07:23 |
| ViGe | #info <Jolla> No, we don’t have any plans at the moment. | 07:23 |
| ViGe | #info <Jolla> Updating gcc is a relatively big effort, which includes a lot of testing. | 07:23 |
| ViGe | #info <Jolla> On the other hand, we are not aware of any blockers preventing us from updating. | 07:23 |
| rinigus | that update would be handy. just got hit by c++20 requirement of angelfish as well | 07:24 |
| ViGe | rinigus: Oh, you are here! | 07:24 |
| rinigus | in principle, those core components have to be updated. glibc as well | 07:24 |
| rinigus | (trying to reply when I can) | 07:24 |
| ViGe | rinigus: I would assume that it will be updated eventually. But like said, there are no plans, so we can't give any estimates on when that might happen. | 07:25 |
| rinigus | maybe gcc can be squeezed in into the pipeline? | 07:25 |
| piggz[m] | means rinigis will ship it in /opt in a week or so :D | 07:25 |
| rinigus | ViGe: then let's try to get that into the plans? | 07:26 |
| rinigus | piggz: its far from optimal. means that we will not use sb2 - so compilation will be slow for everything. its possible, but painful | 07:26 |
| rinigus | note that Qt6 - which we may ship in /opt - requires newer gcc as well | 07:27 |
| rinigus | so, to reformulate - how can we ask Jolla to add gcc update into the plans? | 07:30 |
| ViGe | rinigus: Well, I think there's really not much more you can do than to ask here, which you already did. | 07:30 |
| Solrac[m] | Would a seperate "runtime" (like Qt 5.15 's case) be a viable option? I'm assuming a few libs would be duplicates | 07:31 |
| rinigus | ViGe: all whats missing is a reply: "request noted and will be added to the plans" :) | 07:32 |
| ViGe | I can't promise anything added to any plans. But the request has been noted. | 07:32 |
| rinigus | Solrac: it is an option and I did it for previous gcc update - shipped it in /opt/gcc. but that means all compilation goes via qemu on OBS and it is slow for aarch64 / armv7 | 07:33 |
| rinigus | which maybe our most realistic path for now | 07:33 |
| rinigus | ViGe: thanks! | 07:33 |
| ViGe | Time's up for that one, let's move on | 07:33 |
| ViGe | #topic Open PR discussion (5 mins -- asked by jolla) | 07:33 |
| *** sailbot changes topic to "Open PR discussion (5 mins -- asked by jolla) (Meeting topic: Sailfish OS, open source, collaboration -- 13th April 2023)" | 07:33 | |
| ViGe | #info <jolla> Any open PRs to discuss? | 07:34 |
| ViGe | btw. That line basically means that there were no PRs mentioned on the forum | 07:34 |
| ViGe | #topic Untracked bug reports (5 min -- asked by Community Bug Coordination Team) | 07:38 |
| *** sailbot changes topic to "Untracked bug reports (5 min -- asked by Community Bug Coordination Team) (Meeting topic: Sailfish OS, open source, collaboration -- 13th April 2023)" | 07:38 | |
| ViGe | #info <Community Bug Coordination Team> Our regular Community Bug Coordination Team update - see the forum for the links to actual bug reports | 07:38 |
| ViGe | #info <Jolla> As always, The Community Bug Coordination Team have done a superb job. | 07:38 |
| ViGe | #info <Jolla> As a result of their work, we now have 7 high quality bug reports now recorded internally and tagged as "tracked". | 07:38 |
| ViGe | #topic General discussion (20 min) | 07:43 |
| *** sailbot changes topic to "General discussion (20 min) (Meeting topic: Sailfish OS, open source, collaboration -- 13th April 2023)" | 07:43 | |
| rinigus | with the success of docker based build env, when compared to sb2, I started to wonder if jolla has any plans for arm64 native build nodes at OBS? do you have such nodes in your closed OBS? | 07:44 |
| ViGe | I'm not aware of any such plans. | 07:47 |
| rinigus | what about your closed/private OBS? As far as I remember, suse has such nodes in their obs - so it should be supported | 07:48 |
| Keto | we don't have native nodes | 07:49 |
| rinigus | Keto and ViGe : thanks for info. | 07:50 |
| ExTechOp | Has any progress been made on debugging loss of sounds? https://forum.sailfishos.org/t/4-1-0-23-4-0-1-48-4-4-0-64-4-5-0-16-no-notification-sounds-ringing-sms-alarm/4886 | 07:51 |
| Keto | I guess it could be an option, but it's probably better that it is close to the local build env. so that there isn't cases that something builds locally but doesn't build on obs, or the other way around | 07:52 |
| ViGe | ExTechOp: not really. Some work has been done on reducing the amount of feedback sounds played, which should help. But the root cause hasn't been found. | 07:54 |
| rinigus | Keto: while compiling Qt5.15 libs, we stumbled on several sb2 bugs. all noted at the forum | 07:55 |
| rinigus | in the end, qtwebengine has to be built outside of sb2 - probably due to sdk sitting on a top of i386 | 07:55 |
| ViGe | Keto: I agree. I would rather have our SDK moved to 64 bit architecture, which should help at least some issues that rinigus is having. | 07:55 |
| rinigus | note that other projects (flatpak for example) have moved to native builds entirely. cross-compilation can have some issues and we are just spending lots of time time fighting them | 07:56 |
| rinigus | qemu has its own bugs too - for example armv7 on 64bit qemu can mess up filesystem link. have to use 32bit qemu (from jolla's sdk) to work around it | 07:58 |
| piggz[m] | oh I did enjoy those weird file permission problems :) | 07:58 |
| rinigus | so, while moving sdk to 64 bit is good, it maybe insufficient for all cases | 07:58 |
| piggz[m] | sb2 bug creating files with permission 000 | 07:58 |
| ViGe | rinigus: then again, 64 bit SDK would help also other cases, which any OBS changes would not. e.g. issues on running the SDK on Windows. | 08:01 |
| piggz[m] | there are probable cases for both? sdk for most users, and a more advanced option? | 08:02 |
| ViGe | piggz[m]: Yeah, you are right, these are not mutually exclusive things. | 08:02 |
| ViGe | But perhaps it's time to start wrapping up | 08:03 |
| ViGe | #topic Next meeting time and date (5 min) | 08:03 |
| *** sailbot changes topic to "Next meeting time and date (5 min) (Meeting topic: Sailfish OS, open source, collaboration -- 13th April 2023)" | 08:03 | |
| ViGe | Proposing Thursday 27th April at 07:00am UTC | 08:03 |
| ViGe | I don't hear any objections | 08:07 |
| ViGe | #info Next meeting will be held on Thursday 27th April 2023 at 07:00am UTC: 2023-04-27T0700Z | 08:07 |
| ViGe | Thanks for the meeting everyone! | 08:07 |
| ViGe | #endmeeting | 08:08 |
| sailbot | Meeting ended Thu Apr 13 08:08:04 2023 UTC. | 08:08 |
| sailbot | Minutes: https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2023/sailfishos-meeting.2023-04-13-07.00.html | 08:08 |
| sailbot | Minutes (text): https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2023/sailfishos-meeting.2023-04-13-07.00.txt | 08:08 |
| sailbot | Log: https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2023/sailfishos-meeting.2023-04-13-07.00.log.html | 08:08 |
| *** sailbot changes topic to "Next meeting will be held on Thursday 13th April 2023 at 07:00am UTC. Topics can be made/read here: https://forum.sailfishos.org/t/community-meeting-on-irc-13th-april-2023/15242" | 08:08 | |
| Crabster | thx @ #? | 08:08 |
| *** ChanServ changes topic to "Next meeting will be held on Thursday 27th April 2023 at 07:00am UTC. Topics can be made/read here: https://forum.sailfishos.org/t/community-meeting-on-irc-27th-april-2023/15398" | 08:12 | |
| ExTechOp | Thanks everyone! | 08:13 |
| *** fifr[m] is now known as Guest10890 | 17:37 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!