#sailfishos-meeting: Sailfish OS, open source, collaboration -- 12th January 2023

Meeting started by flypig at 08:00:52 UTC (full logs).

Meeting summary

    1. Meeting information and agenda can be found here: (flypig, 08:01:02)
    2. https://forum.sailfishos.org/t/community-meeting-on-irc-12th-january-2023/13729 (flypig, 08:01:05)

  1. Brief introduction (5 min). Please prefix your name/handle with #info (flypig, 08:01:19)
    1. Otto Mäkelä, community (ExTechOp, 08:01:24)
    2. pherjung, community (pherjung[m], 08:01:29)
    3. Ville Nummela, sailor @ Jolla (ViGe, 08:01:38)
    4. Simonas Leleiva -- privateer for Jolla (sledges, 08:01:53)
    5. David Llewellyn-Jones, sailor @ Jolla & chair (flypig, 08:01:59)
    6. Björn Bidar, sailor @ Jolla (Thaodan, 08:02:32)
    7. Damien Caliste, community (dcaliste, 08:03:29)
    8. Sebix, Community (sebix[m], 08:07:24)

  2. Background services and unified push (10 mins -- asked by thigg) (flypig, 08:07:52)
    1. <thigg> E.g. native messaging apps are not very convenient to use on Sailfish OS because they do not run in the background. (flypig, 08:08:03)
    2. Pawel Radomychelski (ExPLIT), community member (ExPLIT[m]1, 08:08:06)
    3. <thigg> 1) are there any advances made towards supporting background services in Sailfish OS? (flypig, 08:08:17)
    4. <thigg> Is this just a Harbour problem or are we lacking infrastructure in the OS, or are we lacking concepts or is it just not used very much? (flypig, 08:08:25)
    5. <thigg> 2) Are there plans for something like a unified push client that could be used to wake up apps in background? (or maybe just send a notification for now?) (flypig, 08:08:34)
    6. <Jolla> Background services are already possible in apps on Sailfish, but not allowed in Harbour. We've looked internally into allowing them in Harbour many times in the past, because we know how useful this functionality is for developers. (flypig, 08:08:52)
    7. <Jolla> Background services are easier to support than unified push, and don't have the same privacy concerns, so are likely to be come first. (flypig, 08:09:07)
    8. <Jolla> Unfortunately on each occasion we've looked at it, we've concluded we don't yet have the right mechanisms to constrain services to avoid impacting performance or security. We would still love to support them though. (flypig, 08:09:25)
    9. <Jolla> As a first step we would need automated screening of service files using rpmvalidator to ensure services are sandboxed to the same level as the associated app, and to allow sandbox compliant DBus communication between service and app. (flypig, 08:09:38)
    10. <Jolla> Updating systemd would allow us enforce stricter resource limits, e.g. for idle execution. (flypig, 08:09:50)
    11. <Jolla> To progress this further, we welcome use-cases from the community, contributions to rpmvalidator and support updating systemd. (flypig, 08:09:57)
    12. https://github.com/sailfishos/sdk-harbour-rpmvalidator (flypig, 08:10:02)
    13. https://github.com/sailfishos/systemd (flypig, 08:10:06)

  3. VoWIFI support (15 mins -- asked by inte) (flypig, 08:25:05)
    1. <inte> Most (if not all) mobile networks which have implemented VoLTE do also support VoWIFI, which is a very useful feature especially in areas with poor indoor coverage (but good WiFi reception) or to avoid roaming costs. (flypig, 08:25:21)
    2. <inte> Implementation would probably be easy at least for the Xperia 10ii/iii, as these phones already support VoLTE and the voice channel only needs to be routed through the Wifi interface instead of the LTE connection (hopefully). (flypig, 08:25:32)
    3. <Jolla> This isn't something we've looked into in great detail and we don't expect to have any VoWifi support in the upcoming release. (flypig, 08:25:59)
    4. <Jolla> Unfortunately the implementation may not be as straightforward as it sounds, as not much from VoLTE could be used. (flypig, 08:26:05)
    5. <Jolla> When we get to looking into it properly, if there are good areas for community contribution, we'll certainly aim to publicise the fact. (flypig, 08:26:15)

  4. Untracked bug reports (5 mins -- asked by pherjung) (flypig, 08:40:28)
    1. <pherjung> Untracked bug reports... (flypig, 08:40:33)
    2. <Jolla> Thank you again for all of your work in checking and collating bug reports. (flypig, 08:41:02)
    3. <Jolla> Here are the results for this fortnight: (flypig, 08:41:06)
    4. <Jolla> - 7 high quality bug reports now recorded internally and tagged as "tracked". (flypig, 08:41:10)
    5. <Jolla> - 4 bug reports tagged as "fixed". (flypig, 08:41:14)
    6. <Jolla> - 4 marked as duplicates and closed. (flypig, 08:41:18)
    7. <Jolla> It wasn't possible to go through the full list, but please do provide them for the next meeting as you suggested. (flypig, 08:41:45)

  5. Open PR discussion (5 mins -- asked by jolla) (flypig, 08:56:12)
    1. <jolla> Any open PRs to discuss? (flypig, 08:56:25)

  6. General discussion (15 min) (flypig, 09:00:16)
    1. <ViGe> "it's really easy to make PRs to the documentation, you can do them right on the github UI" (flypig, 09:15:03)

  7. Next meeting time and date (5 min) (flypig, 09:18:14)
    1. https://forum.sailfishos.org/tag/community-news.rss (flypig, 09:24:07)
    2. https://forum.sailfishos.org/c/community-news/25.rss should work as well (ViGe, 09:25:29)
    3. Next meeting will be held on Thursday 2nd February 2023 at 08:00am UTC: 2023-02-02T0800Z (flypig, 09:28:19)

Meeting ended at 09:28:45 UTC (full logs).

Action items

  1. (none)

People present (lines said)

  1. flypig (120)
  2. Thaodan (24)
  3. ViGe (16)
  4. pherjung[m] (10)
  5. ExTechOp (9)
  6. ExPLIT[m]1 (4)
  7. sailbot (3)
  8. sebix[m] (3)
  9. jpwalden (3)
  10. sledges (1)
  11. dcaliste (1)

Generated by MeetBot 0.1.4.