#sailfishos-meeting: Sailfish OS, open source, collaboration -- 13th April 2023

Meeting started by ViGe at 07:00:04 UTC (full logs).

Meeting summary

    1. Meeting information and agenda can be found here: (ViGe, 07:00:09)
    2. https://forum.sailfishos.org/t/community-meeting-on-irc-13th-april-2023/15242 (ViGe, 07:00:12)

  2. Brief introduction (5 min). Please prefix your name/handle with #info (ViGe, 07:00:19)
    1. Ville Nummela - sailor@Jolla and chairperson today (ViGe, 07:00:46)
    2. Otto Mäkelä, community (ExTechOp, 07:01:06)
    3. LSolrac - comunity (Solrac[m], 07:01:08)
    4. Simonas Leleiva -- privateer for Jolla (sledges, 07:01:31)
    5. Andrew Branson - sailor (abr, 07:01:41)
    6. Raine Mäkeläinen - sailor @ Jolla (rainemak, 07:01:42)
    7. Crabster - lurker @ meeting (Crabster, 07:02:28)

  3. Support for passing QR-read Wifi information to Networksettings (3-5 min -- asked by nephros) (ViGe, 07:05:07)
    1. <nephros> There have been some efforts to make it possible to support `wifi:` strings as used in QR codes for network configuration. (ViGe, 07:05:10)
    2. <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`. (ViGe, 07:05:14)
    3. <nephros> Discussion: https://forum.sailfishos.org/t/codereader-cannot-use-wifi-code-not-supported/15193 (ViGe, 07:05:18)
    4. <nephros> Some code: https://github.com/nephros/wifi-qr-handler (ViGe, 07:05:21)
    5. <Jolla> The wifi handler looks like a nice start, but on the details this wouldn’t be necessarily how we’d like this implemented. (ViGe, 07:05:34)
    6. <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, (ViGe, 07:05:38)
    7. <Jolla> 2) the patch doesn’t enable the QR code network adding from anywhere (suppose that’s called from third party app then), (ViGe, 07:05:43)
    8. <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. (ViGe, 07:05:46)

  4. Community contributions to Jolla closed components (10 min -- asked by nephros) (ViGe, 07:10:23)
    1. <nephros> Over the years, there have been several modifications done to Jolla-distributed apps by community hackers. (ViGe, 07:10:27)
    2. <nephros> (Sometimes distributed as so-called Patchmanager Patches, sometimes as separate packages, or just locally). (ViGe, 07:10:30)
    3. <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. (ViGe, 07:10:33)
    4. <nephros> Some of the latter category may warrant inclusion in the original app or component. (ViGe, 07:10:37)
    5. <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. (ViGe, 07:10:40)
    6. <nephros> Annoyance fix: Allowed Orientation patch https://coderus.openrepos.net/pm2/project/sailfishos-default-allowed-orientations-patch - 1800+ activations. (ViGe, 07:10:44)
    7. <nephros> A new/missing feature: wifi-qr-handler - as discussed in the other meeting topic. (ViGe, 07:10:47)
    8. <nephros> Now for the questions (note that they do not mean the examples above explicitly, but in general): (ViGe, 07:10:50)
    9. <nephros> 1. Is there interest from Jolla, and a conceivable way to upstream some of those? (ViGe, 07:10:53)
    10. <nephros> 2. If yes, what would be the preferred avenue of communication from the community to Jolla? (ViGe, 07:10:57)
    11. <nephros> 3. If yes, what are requirements from Jolla to consider inclusion? (ViGe, 07:11:00)
    12. <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. (ViGe, 07:11:04)
    13. <Jolla> 1. From this particular set of patches we probably wouldn’t be merging any. (ViGe, 07:11:17)
    14. <Jolla> Sandbox should be enabled more or less always and the user shouldn’t need to care. (ViGe, 07:11:22)
    15. <Jolla> The orientation is overriding the Silica apis and breaks their expectations. (ViGe, 07:11:26)
    16. <Jolla> The wifi handler needs a bit more work and architecture adjustments. (ViGe, 07:11:31)
    17. <Jolla> However that wouldn’t mean there couldn’t be  other community contributions to consider merging mainline. (ViGe, 07:11:36)
    18. <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. (ViGe, 07:11:41)

  5. can we get Filter pulley menu in Messages app to search by a contact name/phone? (3 min -- asked by remote) (ViGe, 07:20:11)
    1. <remote> sometimes I have to scroll for way too long to reach the conversation I need (ViGe, 07:20:14)
    2. <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. (ViGe, 07:20:29)
    3. <Jolla> However cannot give any estimates we’d get around to implement it. (ViGe, 07:20:32)
    4. <Jolla> So far this feature hasn’t seem to be requested that much, but noted that it is now. (ViGe, 07:20:35)

  6. GCC update (10 min -- asked by rinigus) (ViGe, 07:23:09)
    1. <rinigus> We are currently on GCC 8 which is showing its limitations. (ViGe, 07:23:12)
    2. <rinigus> It would make sense to take GCC update into the pipeline. (ViGe, 07:23:15)
    3. <rinigus> Any plans regarding it? (ViGe, 07:23:18)
    4. <rinigus> Corresponding bug report: https://forum.sailfishos.org/t/gcc-update-from-gcc-8/15144 (ViGe, 07:23:19)
    5. <Jolla> No, we don’t have any plans at the moment. (ViGe, 07:23:23)
    6. <Jolla> Updating gcc is a relatively big effort, which includes a lot of testing. (ViGe, 07:23:26)
    7. <Jolla> On the other hand, we are not aware of any blockers preventing us from updating. (ViGe, 07:23:29)

  7. Open PR discussion (5 mins -- asked by jolla) (ViGe, 07:33:59)
    1. <jolla> Any open PRs to discuss? (ViGe, 07:34:02)

  8. Untracked bug reports (5 min -- asked by Community Bug Coordination Team) (ViGe, 07:38:08)
    1. <Community Bug Coordination Team> Our regular Community Bug Coordination Team update - see the forum for the links to actual bug reports (ViGe, 07:38:11)
    2. <Jolla> As always, The Community Bug Coordination Team have done a superb job. (ViGe, 07:38:15)
    3. <Jolla> As a result of their work, we now have 7 high quality bug reports now recorded internally and tagged as "tracked". (ViGe, 07:38:19)

  9. General discussion (20 min) (ViGe, 07:43:08)
  10. Next meeting time and date (5 min) (ViGe, 08:03:23)
    1. Next meeting will be held on Thursday 27th April 2023 at 07:00am UTC: 2023-04-27T0700Z (ViGe, 08:07:06)


Meeting ended at 08:08:04 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. ViGe (83)
  2. rinigus (20)
  3. Solrac[m] (8)
  4. piggz[m] (4)
  5. ExTechOp (3)
  6. sailbot (2)
  7. Keto (2)
  8. sledges (1)
  9. abr (1)
  10. rainemak (1)
  11. Crabster (1)


Generated by MeetBot 0.1.4.