#sailfishos-meeting: Sailfish OS, open source, collaboration -- 5th September 2024

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

Meeting summary

    1. Meeting information and agenda can be found here: (rainemak, 07:00:20)
    2. https://forum.sailfishos.org/t/community-meeting-on-5th-september-2024/19811 (rainemak, 07:00:20)

  2. Brief introduction (5 min). Please prefix your name/handle with #info (rainemak, 07:00:20)
    1. Otto Mäkelä, community (ExTechOp, 07:00:39)
    2. Raine Mäkeläinen, Jolla (rainemak, 07:00:49)
    3. Vlad G., community (b100dian[m], 07:01:22)
    4. Matti Viljanen, Sailor @ Jolla (direc85, 07:02:01)
    5. Björn Bidar, Sailor @ Jolla (Thaodan, 07:03:40)

  3. Is Jolla C2 new telephony stack going to be open source, including VoLTE/5G? (10 mins -- asked by vlagged) (rainemak, 07:05:16)
    1. <vlagged> Some details about the topic: The “Jolla C2 Community Phone (rainemak, 07:05:16)
    2. <vlagged> deliveries 3” thread starts with the mention of a new Android 13+ (rainemak, 07:05:16)
    3. <vlagged> telephony stack and the recent messages there asked for support (rainemak, 07:05:16)
    4. <vlagged> testing the VoLTE compatibility. As the previous VoLTE (rainemak, 07:05:16)
    5. <vlagged> implementation was proprietary, I would like to know if the next (rainemak, 07:05:18)
    6. <vlagged> one will have a brighter future and be open sourced. The next best (rainemak, 07:05:20)
    7. <vlagged> thing - will packages be available to community ports? Thanks! (rainemak, 07:05:22)
    8. <Jolla> Jolla C2 is a unisoc device. For VoLTE this means that ofono (rainemak, 07:06:26)
    9. <Jolla> vendor plugin will be for unisoc hardware adaptation. Similarly as (rainemak, 07:06:26)
    10. <Jolla> there is that qti plugin. Whether it is then open sourced eventually (rainemak, 07:06:26)
    11. <Jolla> or not is more complex question as there's a vendor dependency. (rainemak, 07:06:26)
    12. <Jolla> Let's make first a solid VoLTE for Jolla C2. (rainemak, 07:06:26)
    13. piggz community porter (piggz[m], 07:06:51)
    14. Damien Caliste, community (dcaliste, 07:07:02)
    15. https://forum.sailfishos.org/t/sailfish-community-news-29th-august-2024-c2-update/19793/7 (b100dian[m], 07:10:20)
    16. The answer partially covered already in the forum (rainemak, 07:10:22)
    17. https://forum.sailfishos.org/t/sailfish-community-news-29th-august-2024-c2-update/19793/7 (rainemak, 07:10:25)

  4. Replacing device lock maximum attempts with attempt delays (10 mins -- asked by pvuorela) (rainemak, 07:15:39)
    1. <pvuorela> The device lock settings has had configurable maximum attempts. (rainemak, 07:15:39)
    2. <pvuorela> When that is reached, the device is put into locked state. The (rainemak, 07:15:39)
    3. <pvuorela> setting has been vague on the UI, not fully explaining what it (rainemak, 07:15:39)
    4. <pvuorela> does, and also dangerous as unlock attempts might happen (rainemak, 07:15:39)
    5. <pvuorela> unintended in a pocket, or by a toddler, etc. It hasn’t protected (rainemak, 07:15:43)
    6. <pvuorela> the sensitive data too well either as nothing gets done to that. (rainemak, 07:15:45)
    7. <pvuorela> So instead of configurable maximum attempts, we are considering (rainemak, 07:15:47)
    8. <pvuorela> adding pauses on retries after too many failed attempts in short (rainemak, 07:15:49)
    9. <pvuorela> time. (rainemak, 07:15:51)
    10. https://forum.sailfishos.org/t/how-to-unlock-the-encryption-of-your-home-if-you-dont-know-your-lock-code-bruteforce/3004/8 (direc85, 07:27:51)
    11. No strong comments / feelings against pvuorela's proposal (rainemak, 07:31:24)

  5. Open PR discussion (5 mins -- asked by Jolla) (rainemak, 07:31:32)
  6. General discussion (10 mins) (rainemak, 07:40:25)
  7. Next meeting time and date (5 mins) (rainemak, 07:52:31)
    1. https://t.me/joinchat/AAAAAFcbasJX67Fu-aGxxQ (Thaodan, 08:00:29)
    2. Next meeting will be held on Thursday 19th September 2024 at 07:00am UTC: 2024-09-19T0700Z (rainemak, 08:00:46)


Meeting ended at 08:00:53 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. rainemak (84)
  2. Thaodan (27)
  3. b100dian[m] (10)
  4. direc85 (10)
  5. ExTechOp (8)
  6. piggz[m] (8)
  7. Brian_ (7)
  8. pvuorela (6)
  9. dcaliste (5)
  10. sailbot (2)
  11. rubdos[m] (1)


Generated by MeetBot 0.1.4.