#sailfishos-meeting: Sailfish OS, open source, collaboration -- 24th November 2022

Meeting started by flypig at 08:01:10 UTC (full logs).

Meeting summary

    1. Meeting information and agenda can be found here: (flypig, 08:01:25)
    2. https://forum.sailfishos.org/t/community-meeting-on-irc-24th-november-2022/13495 (flypig, 08:01:31)

  2. Brief introduction (5 min). Please prefix your name/handle with #info (flypig, 08:01:46)
    1. Otto Mäkelä, community (ExTechOp, 08:02:08)
    2. David Llewellyn-Jones - sailor @ Jolla and meeting chair (flypig, 08:02:19)
    3. Solrac, comunity (Solrac[m], 08:02:48)
    4. Simonas Leleiva - privateer for Jolla (sledges, 08:03:39)
    5. Björn Bidar - sailor @ Jolla (Thaodan, 08:03:52)
    6. daneos - community (daneos, 08:05:10)
    7. thigg, community (thilo[m], 08:05:29)
    8. Nico, community slacker (Nico, 08:05:50)

  3. Log persistence/easing gathering of logs (10 mins -- asked by thigg) (flypig, 08:06:58)
    1. <thigg> The journalctl Logs are rolled over quite quickly in Sailfish OS. (flypig, 08:07:11)
    2. <thigg> It is likely that some bug reports are struggling to collect logs because when the person is back home and thinks about getting those logs, they are gone already. (flypig, 08:07:20)
    3. <thigg> For example see https://forum.sailfishos.org/t/browser-bookmarks-does-not-show-typing-hides-keyboard/13579/3 (flypig, 08:07:34)
    4. <thigg> It might be helpful to collect logs for a longer period of time (e.g. one week)? (flypig, 08:07:41)
    5. <thigg> They still might forget this, thus maybe we could add a userfriendly button somewhere to save the whole journal with a dedicated name? (flypig, 08:07:49)
    6. <thigg> (Maybe even able to select a broad category, e.g. bugs with connection, in browser,...). That way the gathering of logs would take ~30 seconds for the user and it is way more likely they do it. (flypig, 08:07:58)
    7. <Jolla> Log collection unfortunately remains tricky for many reasons, not least the need to remove private data before sharing them. We have several help articles related to collecting logs. (flypig, 08:08:29)
    8. https://jolla.zendesk.com/hc/en-us/articles/360013910599-Collecting-basic-logs-from-a-Sailfish-device (flypig, 08:08:39)
    9. https://jolla.zendesk.com/hc/en-us/articles/4405752484242-Gathering-logs-related-to-audio-Bluetooth-and-phonecalls-from-a-Sailfish-OS-device (flypig, 08:08:44)
    10. <Jolla> The first article provides a script collect-logs.sh that can be used to simplify the process of collecting logs. (flypig, 08:08:49)
    11. <Jolla> The second article provides a script gather_logs.sh which is a little more complicated to run and with a focus on audio/bluetooth, but which will also make your logs persistent. (flypig, 08:08:59)
    12. <Jolla> We really like your suggestion to add a user interface for this. We have an internal task for improving the process, but no timeline. We're always open to nice suggestions like this. (flypig, 08:09:11)
    13. <thilo[m]>: "If someone could contribute a poc to bugger, i think that would help" (flypig, 08:25:02)

  4. VoLTE for Ports (10 mins -- asked by LSolrac) (flypig, 08:26:43)
    1. <LSolrac> I vaguely remember someone mentioning VoLTE for unofficial ports in the forums. However, I have not been able to see any talk about it again. (flypig, 08:26:53)
    2. <LSolrac> So I ask, is there a plan to implement a standard for porters to implement VoLTE in their devices? (flypig, 08:26:58)
    3. <Jolla> We discussed something similar back in May (see point 5) and it’s worth reviewing that answer. (flypig, 08:27:16)
    4. https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2022/sailfishos-meeting.2022-05-26-07.00.html (flypig, 08:27:21)
    5. <Jolla> Back then we highlighted the eight layers of the Sailfish OS VoLTE stack: (flypig, 08:27:28)
    6. <Jolla> 1. Hardware adaptation: Sony proprietary. (flypig, 08:27:35)
    7. <Jolla> 2. modem_auto_config: Jolla proprietary. (flypig, 08:27:41)
    8. <Jolla> 3. ofono-vendor-qti-radio-plugin: Jolla proprietary. (flypig, 08:27:47)
    9. <Jolla> 4. ofono-modem-switcher: Jolla proprietary, Xperia 10 II only. (flypig, 08:27:55)
    10. <Jolla> 5. libgbinder-radio: https://github.com/mer-hybris/libgbinder-radio/ (flypig, 08:28:02)
    11. <Jolla> 6. ofono-binder-plugin: https://github.com/mer-hybris/ofono-binder-plugin (flypig, 08:28:08)
    12. <Jolla> 7. ofono: https://github.com/sailfishos/ofono/ (flypig, 08:28:14)
    13. <Jolla> 8. libqofono: https://github.com/sailfishos/libqofono (flypig, 08:28:19)
    14. <Jolla> We said at the time we intended to release 2, 3 and 4 to the hw:common repositories for use by porters. We've not been able to do this yet. (flypig, 08:28:25)
    15. <Jolla> It’s worth noting however that they're device-specific, so may not be useful for ports more generally. (flypig, 08:28:39)
    16. <Jolla> In terms of a standard, slava has made available an example ofono binder plugin extension, which is a template for porters to replace layer 3. (flypig, 08:28:47)
    17. https://github.com/monich/ofono-binder-plugin-ext-sample (flypig, 08:28:56)
    18. <Jolla> The extension interfaces are defined in the following headers. (flypig, 08:29:02)
    19. https://github.com/mer-hybris/ofono-binder-plugin/tree/master/lib/include (flypig, 08:29:08)
    20. <Jolla> Hopefully this can be of help to porters looking at this. (flypig, 08:29:14)
    21. fridlmue - community (sorry for being late) (fridl, 08:33:32)
    22. <Solrac[m]>: "letting layers 2,3,4 read a configuration file (which I asusme might be similar to Slava's extension) to ease this for future builds might not be a bad suggestion?" (flypig, 08:39:46)
    23. <Thaodan>: "Besides modem switching pretty much anything else is specific to the vendor of the soc" (flypig, 08:40:11)

  5. Untracked bug reports (5 mins -- asked by thigg) (flypig, 08:41:05)
    1. Our regular Community Bug Coordination Team update, provided by thigg. (flypig, 08:42:05)
    2. <Jolla> Thank you once again to the amazing work of the Community Bug Coordination Team. As a result of their work, we now have an additional: (flypig, 08:42:11)
    3. <Jolla> 4 high quality bug reports now recorded internally and tagged as "tracked"; (flypig, 08:42:17)
    4. <Jolla> 1 bug report marked as "pending" more info; (flypig, 08:42:22)
    5. <Jolla> 3 bug reports tagged as "fixed"; (flypig, 08:42:26)
    6. <Jolla> 3 duplicate/moved/closed for other reasons. (flypig, 08:42:32)
    7. Thank you also to everyone who has reported issues. We've been pushing within Jolla to address as many of these reports as we can over the last month and your efforts have been invaluable. (flypig, 08:42:38)
    8. The Community Bug Coordination Team are inviting new members. (flypig, 08:46:38)
    9. <thilo[m]> added: "Only the invitation to the team ;) Help categorizing bug reports is appreciated :)" (flypig, 08:46:54)

  6. Open PR discussion (10 mins -- asked by jolla) (flypig, 08:49:04)
    1. <jolla> Any open PRs to discuss? (flypig, 08:49:08)

  7. General discussion (15 min) (flypig, 08:53:15)
    1. https://forum.sailfishos.org/t/add-vpnc-patches-to-ease-usage-of-vpn-for-fritz-box-users/3955 (Thaodan, 08:57:09)
    2. Concerning log capture, pherjung highlighted the following forum topic for discussing it: (flypig, 08:58:51)
    3. https://forum.sailfishos.org/t/easily-catch-logs/12018 (flypig, 08:58:54)
    4. : The Community Bug Coordination Team will start to highlight feature requests as well as bugs. They will devise a suitable process for this. (flypig, 09:17:12)
    5. : all candy to improve the process and bribe the team is welcome (thilo[m], 09:18:21)
    6. https://forum.sailfishos.org/t/wiki-collecting-debug-information/12751 (thilo[m], 09:23:11)
    7. https://github.com/ProgVal/Limnoria is the bot I'm reffering to (Thaodan, 09:23:29)
    8. <Thaodan> "I want to create a repo for common answers and questions. Do you we have a sailfish community org somewhere, would anyone want to contribute?" (flypig, 09:25:34)

  8. Next meeting time and date (5 min) (flypig, 09:27:03)
    1. Next meeting will be held on Thursday 8th December 2022 at 08:00am UTC: 2022-12-08T0800Z (flypig, 09:29:07)


Meeting ended at 09:29:33 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. flypig (140)
  2. thilo[m] (51)
  3. Thaodan (39)
  4. pherjung (15)
  5. ExTechOp (11)
  6. Solrac[m] (10)
  7. Nico (7)
  8. ViGe (6)
  9. dcaliste (4)
  10. sailbot (2)
  11. sledges (1)
  12. daneos (1)
  13. fridl (1)


Generated by MeetBot 0.1.4.