#sailfishos-meeting: Sailfish OS, open source, collaboration -- 30th May 2024

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

Meeting summary

    1. Meeting information and agenda can be found here: (rainemak, 07:00:24)
    2. https://forum.sailfishos.org/t/community-meeting-on-30th-may-2024/18640/ (rainemak, 07:00:24)

  2. Brief introduction (5 min). Please prefix your name/handle with #info (rainemak, 07:00:24)
    1. Otto Mäkelä, community (ExTechOp, 07:00:42)
    2. Raine Mäkeläinen, sailor @ Jolla, chairperson today (rainemak, 07:01:05)
    3. Matti Viljanen, community (direc85[m], 07:02:45)
    4. Andrea Scarpino, SailfishOS user, maintainer of some app (ilpianista, 07:03:04)
    5. Pami Ketolainen, sailor @ Jolla (Keto, 07:04:59)
    6. Ruben De Smet, rubdos (rubdos[m], 07:05:10)

  3. Sony Xperia 10 IV and V base firmware for Sailfish installation (5mins -- asked by ExTechOp) (rainemak, 07:05:59)
    1. <ExTechOp> Please let us know at your earliest convenient time what version (rainemak, 07:06:05)
    2. <ExTechOp> of the Sony Xperia 10 IV and V base firmware you want to have at (rainemak, 07:06:05)
    3. <ExTechOp> Sailfish install time. Once we get our phones and run them a while (rainemak, 07:06:05)
    4. <ExTechOp> on Android (to verify they are functioning normally, as you (rainemak, 07:06:05)
    5. <ExTechOp> recommend), the system may want to update itself to beyond what (rainemak, 07:06:05)
    6. <ExTechOp> the Sailfish installer expects, and this of course could be (rainemak, 07:06:07)
    7. <ExTechOp> problematic. (rainemak, 07:06:08)
    8. <Jolla> Yes, thank you. Yes, do inform you as soon as possible. Currently (rainemak, 07:06:21)
    9. <Jolla> it’s Android 13 based. (rainemak, 07:06:21)

  4. The Jolla Mind2 (5mins -- asked by jojomen) (rainemak, 07:10:42)
    1. <Jolla> Long list of questions. Hence, a link to forum. (rainemak, 07:10:49)
    2. https://forum.sailfishos.org/t/community-meeting-on-30th-may-2024/18640/3 (rainemak, 07:10:49)
    3. <Jolla> Thank you jojomen & throwaway69 for the Jolla Mind 2 questions. (rainemak, 07:11:03)
    4. <Jolla> Anything related to the Jolla Mind 2 please join to the established (rainemak, 07:11:03)
    5. <Jolla> Jolla Mind 2 discord server 10 there’s a mind2 channel. There are (rainemak, 07:11:03)
    6. <Jolla> technical people to give you answers. (rainemak, 07:11:03)
    7. <Jolla> (rainemak, 07:11:03)
    8. <Jolla> We’ll pass these questions to Mind 2 team. Thanks. (rainemak, 07:11:05)
    9. https://discord.gg/K3BaqkuK (rainemak, 07:11:06)

  5. Jolla Community Phone 2 (5mins -- asked by jojomen) (rainemak, 07:15:50)
    1. <jojomen> 1) How long will it last on a battery charge? (Say, compared to the XA2 or 10III.) (rainemak, 07:15:57)
    2. <jojomen> 2) Does it run a mainline kernel? (rainemak, 07:15:57)
    3. <jojomen> 2.1) If not, for how long is the SoC supported by its (rainemak, 07:15:57)
    4. <jojomen> 2.1) manufacturer? (rainemak, 07:15:57)
    5. <jojomen> 3) Which periferals use mainline drivers? (rainemak, 07:15:57)
    6. <jojomen> 3.1) For those that do not, for how long are drivers supported by (rainemak, 07:15:59)
    7. <jojomen> 3.1) the manufacturer? (rainemak, 07:16:01)
    8. <Jolla> Thank you for your questions! (rainemak, 07:16:27)
    9. <Jolla> 1) Seems to be lasting long but unfortunately, I do not have (rainemak, 07:16:27)
    10. <Jolla> comparison numbers. (rainemak, 07:16:27)
    11. <Jolla> 2) No, it doesn’t run mainline kernel. (rainemak, 07:16:27)
    12. <Jolla> 3) No, it doesn't use mainline drivers. (rainemak, 07:16:27)

  6. Licence subscriptions (5mins -- asked by jojomen) (rainemak, 07:19:58)
    1. <jojomen> What developer subscription options will there be? (rainemak, 07:19:58)
    2. <jojomen> (rainemak, 07:19:58)
    3. <jojomen> The SFOS app ecosystem relies on individual efforts, with no (rainemak, 07:19:58)
    4. <jojomen> feasible way to recuperate costs. Making sure an app works and (rainemak, 07:19:58)
    5. <jojomen> looks ok means testing on many devices, which would make (rainemak, 07:19:59)
    6. <jojomen> subscription costs high for the developer. As a result, developers (rainemak, 07:20:01)
    7. <jojomen> will be incentivized to limit testing. (rainemak, 07:20:03)
    8. <Jolla> What kind of models would you like to see? Calling proposals from (rainemak, 07:20:08)
    9. <Jolla> those who feel it concerns them. (rainemak, 07:20:08)

  7. Some details on few topics I care (5mins -- asked by ilpianista) (rainemak, 07:27:34)
    1. <ilpianista> Is there any plan to implement these features? If not, could (rainemak, 07:27:42)
    2. <ilpianista> you please opensource the components? (rainemak, 07:27:42)
    3. <ilpianista> (rainemak, 07:27:42)
    4. <ilpianista> 1) Automatically mount *encrypted* sd-card (rainemak, 07:27:42)
    5. <ilpianista> 2) ICE (In Case Of Emergency) field on lock screen 1 (rainemak, 07:27:42)
    6. <ilpianista> Option to scramble PIN layout when unlocking device 1 (rainemak, 07:27:43)
    7. <ilpianista> (rainemak, 07:27:47)
    8. <ilpianista> EDIT: using patchmanager to solve those isn’t a viable solution (rainemak, 07:27:49)
    9. <ilpianista> as I don’t want to mess with hacky workarounds. (rainemak, 07:27:51)
    10. https://forum.sailfishos.org/t/automatically-mount-encrypted-sd-card/12023 (rainemak, 07:28:02)
    11. https://forum.sailfishos.org/t/ice-in-case-of-emergency-field-on-lock-screen/6726 (rainemak, 07:28:02)
    12. https://forum.sailfishos.org/t/option-to-scramble-pin-layout-when-unlocking-device/6944 (rainemak, 07:28:02)
    13. <Jolla> Currently these are not in the roadmap. First two would be nice and (rainemak, 07:28:10)
    14. <Jolla> valuable (surely 3rd one as well). Scrambling the PIN layout needs (rainemak, 07:28:10)
    15. <Jolla> more thinking. Very valuable input, we’ll consider these to the (rainemak, 07:28:10)
    16. <Jolla> roadmap. (rainemak, 07:28:10)

  8. Software licences (5mins -- asked by jojomen) (rainemak, 07:32:43)
    1. <jojomen> Please elaborate a bit on the good news about the GPL v3 “not (rainemak, 07:32:43)
    2. <jojomen> being a problem” (announced during Love Day) and the possibility (rainemak, 07:32:43)
    3. <jojomen> to open source parts (like happened briefly in October last year) (rainemak, 07:32:43)
    4. <Jolla> Let’s clarify. We did not announce that GPLv3 is good. Sami talked (rainemak, 07:33:05)
    5. <Jolla> about former limitation that we had. Let’s see what future (rainemak, 07:33:05)
    6. <Jolla> brings :). (rainemak, 07:33:05)
    7. https://www.youtube.com/watch?v=1nEC3sVExAU&t=5365s (rainemak, 07:33:05)

  9. Catching Ctrl-Enter in QML (5mins -- asked by direc85) (rainemak, 07:37:24)
    1. <Jolla> Requested 10mins, giving you 5mins. (rainemak, 07:37:24)
    2. <direc85> Many desktop chat applications can be configured so that while (rainemak, 07:37:34)
    3. <direc85> typing a message, Enter on the keyboard makes a new line and (rainemak, 07:37:34)
    4. <direc85> Ctrl-Enter or Shift-Enter sends the message. Using a Bluetooth or (rainemak, 07:37:34)
    5. <direc85> USB keyboard with Sailfish OS, it doesn’t seem to be possible to (rainemak, 07:37:34)
    6. <direc85> catch the modifier keys in QML TextArea item to replicate the (rainemak, 07:37:34)
    7. <direc85> behaviour. Is it possible to catch the modifiers, and if so, how (rainemak, 07:37:35)
    8. <direc85> could it be done? If not, would it be possible to have this (rainemak, 07:37:37)
    9. <direc85> feature in a future release? (rainemak, 07:37:39)
    10. <direc85> (rainemak, 07:37:41)
    11. <direc85> PS. Yes, the context is Whisperfish here, but this should apply to (rainemak, 07:37:43)
    12. <direc85> Messages and other messaging applications too - if they choose to (rainemak, 07:37:47)
    13. <direc85> implement it. There are plenty of other keyboard-navigation ideas (rainemak, 07:37:49)
    14. <direc85> I have, but let’s start with this first. (rainemak, 07:37:51)
    15. <Jolla> Sorry Direc85, we just didn’t have time try to sort out this for (rainemak, 07:37:53)
    16. <Jolla> you. (rainemak, 07:37:55)
    17. <Jolla> (rainemak, 07:37:57)
    18. <Jolla> That said, we’ll get back to you on the matter. (rainemak, 07:37:59)
    19. Please ping me if don’t hear from us. (rainemak, 07:38:01)

  10. Delete email action for events view (10mins -- asked by direc85) (rainemak, 07:41:38)
    1. <direc85> As I receive quite a lot of update notifications via email, and (rainemak, 07:41:38)
    2. <direc85> just reading the title is enough, it would be handy if there was a (rainemak, 07:41:38)
    3. <direc85> third action for the email in events view - deleting the email. (rainemak, 07:41:38)
    4. <direc85> I’m sure others users too would find good use of the feature. Some (rainemak, 07:41:38)
    5. <direc85> applications already provide more than two actions, for example (rainemak, 07:41:39)
    6. <direc85> WhatsApp messages offer three actions, so that shouldn’t be an (rainemak, 07:41:41)
    7. <direc85> issue. Could this feature be added to to Email in a future (rainemak, 07:41:43)
    8. <direc85> release? (rainemak, 07:41:47)
    9. <Jolla> While could fit some uses, we need to be cautious on deleting (rainemak, 07:42:12)
    10. <Jolla> content which cannot be (easily) returned. Commonly that’s protected (rainemak, 07:42:12)
    11. <Jolla> by remorse items, and notification actions can be even more easy to (rainemak, 07:42:12)
    12. <Jolla> trigger by accident. However, the remorse from client side does not (rainemak, 07:42:12)
    13. <Jolla> necessarily fit the notification system that well. Also, while we (rainemak, 07:42:12)
    14. <Jolla> cannot control how many notification actions Android apps use, there (rainemak, 07:42:13)
    15. <Jolla> should probably be some threshold of going over the two. (rainemak, 07:42:17)
    16. <Jolla> (rainemak, 07:42:19)
    17. <Jolla> That said, we see and hear your point of view. (rainemak, 07:42:21)

  11. Ruby dropped from repos (2mins -- asked by rubdos) (rainemak, 07:53:23)
    1. <rubdos> The changelog of 4.6.0.11 1 mentioned the removal of Ruby from the (rainemak, 07:53:31)
    2. <rubdos> SailfishOS repositories. I’m probably the only one using it (the (rainemak, 07:53:31)
    3. <rubdos> university restaurant menu gets pushed to my Pebble over DBUS with (rainemak, 07:53:31)
    4. <rubdos> that script), but I’d love to know the reasoning behind this. (rainemak, 07:53:31)
    5. https://forum.sailfishos.org/t/changelog-sauna-4-6-0/18531 (rainemak, 07:53:39)
    6. <Jolla> We do not have anything requiring Ruby in the stack anymore. For a (rainemak, 07:53:46)
    7. <Jolla> long time, it was only a build requirement for some component, but (rainemak, 07:53:46)
    8. <Jolla> as that is no longer the case, we decided to drop Ruby to cut down (rainemak, 07:53:46)
    9. <Jolla> the maintenance burden, build cycles, etc. (rainemak, 07:53:46)

  12. Open PR discussion (5 mins -- asked by Jolla) (rainemak, 07:56:18)
    1. <Jolla> Any open PRs to discuss? (rainemak, 07:56:18)

  13. General discussion (5 min) (rainemak, 07:58:53)
  14. Next meeting time and date (2 mins) (rainemak, 08:01:28)
    1. Next meeting will be held on Thursday 13th June 2024 at 07:00am UTC: 2024-06-13T0700Z (rainemak, 08:02:38)


Meeting ended at 08:02:54 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. rainemak (175)
  2. direc85[m] (21)
  3. rubdos[m] (11)
  4. ilpianista (10)
  5. abr (8)
  6. ExTechOp (6)
  7. dcaliste (6)
  8. sailbot (2)
  9. Keto (1)


Generated by MeetBot 0.1.4.