#sailfishos-meeting: Sailfish OS, open source, collaboration -- 29th Feb 2024

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

Meeting summary

    1. Meeting information and agenda can be found here: (rainemak, 08:00:00)
    2. https://forum.sailfishos.org/t/community-meeting-on-29th-february-2024/18036/3 (rainemak, 08:00:00)

  2. Brief introduction (5 min). Please prefix your name/handle with #info (rainemak, 08:00:12)
    1. Otto Mäkelä, community (ExTechOp, 08:00:17)
    2. Adam Pigg, community (piggz[m], 08:01:08)
    3. Raine Mäkeläinen, sailor @ Jolla, chairperson today (rainemak, 08:01:16)
    4. David Llewellyn-Jones, community (flypig, 08:01:30)
    5. Simonas Leleiva -- privateer for wotsits:) (sledges, 08:01:59)
    6. Crabster - lurker (Crabster, 08:02:02)
    7. Andrew Branson, sailing by (abr, 08:02:06)
    8. Damien Caliste, community (dcaliste, 08:02:32)
    9. Pekka Vuorela, Jolla (pvuorela, 08:03:11)

  3. Jolla’s retraction of ~ 15 open sourced components in October 2023 (15mins -- asked by olf) (rainemak, 08:05:17)
    1. <olf> Is Jolla planning the re-release the source code of the ~ 15 (rainemak, 08:05:17)
    2. <olf> software components, which had been released BSD-licensed each in (rainemak, 08:05:17)
    3. <olf> an own GitHub repository in September to Oktober 2023? (rainemak, 08:05:17)
    4. <olf> If so, … (rainemak, 08:05:17)
    5. <olf> When? (rainemak, 08:05:19)
    6. <olf> all fifteen of them, less, or even more? (rainemak, 08:05:21)
    7. <olf> using the same BSD license as the first time? (rainemak, 08:05:23)
    8. <olf> (rainemak, 08:05:25)
    9. <olf> Background: (rainemak, 08:05:27)
    10. <olf> (rainemak, 08:05:29)
    11. <olf> The source code of some of these software components was really (rainemak, 08:05:31)
    12. <olf> helpful as a documentation how things really work, plus how to build (rainemak, 08:05:33)
    13. <olf> software using them and how to extend them. (rainemak, 08:05:35)
    14. <olf> (rainemak, 08:05:39)
    15. <olf> Furthermore, having the source code of these components accessible at (rainemak, 08:05:41)
    16. <olf> GitHub allows for writing proper bug reports or even bug fixes for (rainemak, 08:05:43)
    17. <olf> contributors. (rainemak, 08:05:45)
    18. <Jolla> Open sourcing more components in general is in our roadmap. Timing (rainemak, 08:05:59)
    19. <Jolla> is an open question. Please keep following these meetings and (rainemak, 08:05:59)
    20. <Jolla> fortnight newsletters. You’ll hear about this. At the end you (rainemak, 08:05:59)
    21. <Jolla> likely (should) see more components available. License selection (rainemak, 08:05:59)
    22. <Jolla> happens case by case. There can be cases were dynamic linking/ (rainemak, 08:05:59)
    23. <Jolla> static linking/IPC (details matter) affects to what license can be (rainemak, 08:06:01)
    24. <Jolla> chosen. (rainemak, 08:06:03)
    25. <Jolla> (rainemak, 08:06:05)
    26. <Jolla> Your background thinking is spot on! Documenting, use them (goes (rainemak, 08:06:09)
    27. <Jolla> hand in hand with documentation), extend them, better bug reports, (rainemak, 08:06:11)
    28. <Jolla> and even contributing fixes are very much in the core of our (rainemak, 08:06:13)
    29. <Jolla> thinking as well. (rainemak, 08:06:15)
    30. Björn Bidar - Sailor @ Jolla (Thaodan, 08:06:59)

  4. eSIM support in Sailfish OS (5mins -- asked by cquence) (rainemak, 08:27:12)
    1. <cquence> Can you clarify what is the situation with eSIM support? Is the (rainemak, 08:27:12)
    2. <cquence> eSIM transparent to the OS and can be used as a regular SIM card (rainemak, 08:27:12)
    3. <cquence> or does it need work? If additional work is required is it (rainemak, 08:27:12)
    4. <cquence> something that can then be used across all devices or is work (rainemak, 08:27:13)
    5. <cquence> required for each supported device to enable eSIM for it? (rainemak, 08:27:13)
    6. <Jolla> Certainly, we’ll try to clarify. The eSIM support needs development (rainemak, 08:27:25)
    7. <Jolla> effort so it’s not that transparent. We have not been looking eSIM #info <Jolla> too deeply, but we’d not be surprised if the implementation would (rainemak, 08:27:25)
    8. <Jolla> be hardware specific. Based on initial investigation, changes are (rainemak, 08:27:25)
    9. <Jolla> probably needed at a higher level to add support for handling the (rainemak, 08:27:25)
    10. <Jolla> QR-codes specific to downloading the eSIM profile, and then more (rainemak, 08:27:25)
    11. <Jolla> code would be needed to process the profile, and finally oFono (rainemak, 08:27:27)
    12. <Jolla> would need additions to support the eSIM profile for setting up the (rainemak, 08:27:29)
    13. <Jolla> mobile network. So not a trivial piece of work. (rainemak, 08:27:31)

  5. Open PR discussion (5 mins -- asked by Jolla) (rainemak, 08:34:39)
    1. <Jolla> Any open PRs to discuss? (rainemak, 08:34:39)

  6. General discussion (10 min) (rainemak, 08:40:10)
    1. Wanted to share this crazy workaround to fix voice echo during calls to Xperia 10 III: (sledges, 08:42:27)
    2. https://github.com/sonyxperiadev/bug_tracker/issues/771#issuecomment-1969923419 (sledges, 08:42:28)
    3. https://github.com/SailfishOS-SonyXperia/cosupdateservice (Thaodan, 08:44:02)
    4. https://github.com/SailfishOS-SonyXperia/bugs/issues/46 (Thaodan, 08:52:14)

  7. Next meeting time and date (5 mins) (rainemak, 08:55:11)
    1. Next meeting will be held on Thursday 14th March 2024 at 08:00am UTC: 2024-03-14T0800Z (rainemak, 08:59:55)


Meeting ended at 09:02:21 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. rainemak (97)
  2. Thaodan (31)
  3. sledges (21)
  4. flypig (18)
  5. dcaliste (14)
  6. ExTechOp (9)
  7. abr (3)
  8. sailbot (2)
  9. pvuorela (2)
  10. piggz[m] (1)
  11. Crabster (1)


Generated by MeetBot 0.1.4.