#sailfishos-meeting: Sailfish OS, open source, collaboration -- 15th January 2026

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

Meeting summary

    1. Meeting information and agenda can be found here: (rainemak, 16:00:45)
    2. https://forum.sailfishos.org/t/26416 (rainemak, 16:00:45)

  2. Brief introduction (5 min). Please prefix your name/handle with #info (rainemak, 16:00:45)
    1. Raine Mäkeläinen, Jolla (rainemak, 16:00:47)
    2. Otto Mäkelä, community (ExTechOp, 16:00:56)
    3. Nico, Community (Nico, 16:00:59)
    4. poetaster, community (poetaster, 16:01:10)
    5. Heng Ye, community (HengYe[m], 16:01:45)
    6. Matti Viljanen, Jolla (direc85[m], 16:02:02)
    7. Sebix, community (sebix[m], 16:02:34)
    8. mal, Jolla (mal, 16:03:02)
    9. jojomen, community (jojomen, 16:03:14)
    10. pherjung, community (pherjung, 16:04:59)

  3. Less extreme Store limitations (15 mins -- rikudou) (rainemak, 16:05:45)
    1. <rikudou> I have two apps which IMO don’t do anything extraordinary but (rainemak, 16:05:45)
    2. <rikudou> neither can be currently published to the Jolla Store. One of (rainemak, 16:05:45)
    3. <rikudou> them is BitSailor and the other is the Beginner’s Guide. The (rainemak, 16:05:45)
    4. <rikudou> Beginner’s Guide app uses DBus calls to open a store page (rainemak, 16:05:45)
    5. <rikudou> directly, while BitSailor needs node.js. Especially the DBus (rainemak, 16:05:47)
    6. <rikudou> stuff is ridiculous, that’s like disabling Intents on (rainemak, 16:05:48)
    7. <rikudou> Android. (rainemak, 16:05:50)
    8. <Jolla> Thank for your question. One can feel D-Bus limitation (rainemak, 16:05:54)
    9. <Jolla> ridiculous but this boils down to Sailjail and how sandboxing (rainemak, 16:05:54)
    10. <Jolla> has been built. Whitelisting D-Bus services or interfaces can (rainemak, 16:05:56)
    11. <Jolla> surely be done but how it should be done is another topic. (rainemak, 16:05:58)
    12. <Jolla> Allowing D-Bus services in the Store doesn’t help until the (rainemak, 16:06:00)
    13. <Jolla> sandboxing is fixed. We have been thinking an approach where (rainemak, 16:06:02)
    14. <Jolla> application developers could somehow rather easily manifest that (rainemak, 16:06:04)
    15. <Jolla> the app would like to talk to a D-Bus service xyz. Requirement (rainemak, 16:06:08)
    16. <Jolla> basically would be that end user should be able to understand (rainemak, 16:06:10)
    17. <Jolla> the needed permission. (rainemak, 16:06:12)
    18. <Jolla> (rainemak, 16:06:14)
    19. <Jolla> The Store limitations are defenitely something that we should be #info <Jolla> looking during the 1H/26. This is also somewhat related to the (rainemak, 16:06:16)
    20. <Jolla> next topic. (rainemak, 16:06:19)
    21. filip, community sorry for the delay (filip, 16:12:08)

  4. Featuring good apps from Chum or Storeman in the Jolla Store (15 mins -- asked by pherjung) (rainemak, 16:20:52)
    1. <pherjung> There will be various new users and Sailfish ecosystem may be (rainemak, 16:20:58)
    2. <pherjung> difficult to understand for beginner users. Jolla Store could (rainemak, 16:20:58)
    3. <pherjung> be a little bit modified to include featured apps from Chum (rainemak, 16:20:58)
    4. <pherjung> or Storeman. The list should be provided by trusted users and (rainemak, 16:20:58)
    5. <pherjung> any app listed in the Jolla Store would have a warning with (rainemak, 16:20:58)
    6. <pherjung> some explanation. This information could be provided by the (rainemak, 16:20:59)
    7. <pherjung> trusted users or even by the developer. See this thread for (rainemak, 16:21:01)
    8. <pherjung> further details: Merging Jolla Store, Chum and OpenRepos (rainemak, 16:21:03)
    9. <pherjung> together (rainemak, 16:21:07)
    10. https://forum.sailfishos.org/t/merging-jolla-store-chum-and-openrepos-together/26711 (rainemak, 16:21:09)
    11. <Jolla> The idea behind Chum is very good and transparent. As user you (rainemak, 16:21:11)
    12. <Jolla> have change to check in git SHA1 level what has been built and (rainemak, 16:21:13)
    13. <Jolla> also audit source code as the source code repository needs to be (rainemak, 16:21:15)
    14. <Jolla> open. (rainemak, 16:21:17)
    15. <Jolla> (rainemak, 16:21:19)
    16. <Jolla> Idea behind trusted users or developer is also interresting. (rainemak, 16:21:21)
    17. <Jolla> (rainemak, 16:21:23)
    18. <Jolla> This Jolla Store vs Chum vs Storeman thing will be messy for new (rainemak, 16:21:25)
    19. <Jolla> users as you rightfully raised. Let’s have open discussion on (rainemak, 16:21:27)
    20. <Jolla> this. (rainemak, 16:21:29)
    21. https://forum.sailfishos.org/t/sailjail-and-d-bus-interaction-between-apps (poetaster, 16:21:40)
    22. nephros, community, late-comer (nephros_, 16:26:35)

  5. xmpp system integration open sourcing (5 mins -- asked by poetaster) (rainemak, 16:36:01)
    1. <poetaster> I recall accounts was headed for opening? Is xmpp perhaps (rainemak, 16:36:19)
    2. <poetaster> possible. As it stands xmpp integration isn’t really usable (rainemak, 16:36:19)
    3. <poetaster> since both cryptography and groups features are missing. (rainemak, 16:36:19)
    4. <Jolla> Yes, absolutely xmpp account is an option. Before open sourcing (rainemak, 16:36:29)
    5. <Jolla> it, we’ll need to separate the repository so that all relevant (rainemak, 16:36:29)
    6. <Jolla> pieces would be in the same repository. Few accounts were split (rainemak, 16:36:29)
    7. <Jolla> into multiple repositories in the past in contrast for example (rainemak, 16:36:29)
    8. <Jolla> to NextCloud account where all is in place. (rainemak, 16:36:29)

  6. Clarification between shop.jolla.com and commerce.jolla.com (5 mins -- asked by pherjung) (rainemak, 16:45:00)
    1. <pherjung> Actually, it’s a bit confusing. Do you plan to replace (rainemak, 16:45:00)
    2. <pherjung> shop.jolla.com with commerce.jolla.com? See Download not (rainemak, 16:45:00)
    3. <pherjung> available after Jolla shop purchase (rainemak, 16:45:00)
    4. shop.jolla.com (rainemak, 16:45:00)
    5. commerce.jolla.com (rainemak, 16:45:02)
    6. <Jolla> Sure, we know as well. Getting rid of the old shop.jolla.com and (rainemak, 16:45:29)
    7. <Jolla> having the downloadable Sailfish OS images available somewhere (rainemak, 16:45:29)
    8. <Jolla> needs more efforts. Unfortunately, we have not had time to clean (rainemak, 16:45:29)
    9. <Jolla> this up. Frankly, not even highest priority item whilst same (rainemak, 16:45:29)
    10. <Jolla> time something that we want to fix as well. (rainemak, 16:45:29)
    11. <Jolla> (rainemak, 16:45:31)
    12. <Jolla> But yes problem is noted, acknowledged and understood. (rainemak, 16:45:32)

  7. Back cover of the upcoming J2, specifically cameras (5mins -- asked by jojomen) (rainemak, 16:50:23)
    1. <jojomen> To protect front lenses, cameras should be recessed. (rainemak, 16:50:23)
    2. <jojomen> (rainemak, 16:50:23)
    3. <jojomen> The renders on commerce.jolla.com show that, when laid down, (rainemak, 16:50:23)
    4. <jojomen> the phone will rest on the cameras. So it is quite likely the (rainemak, 16:50:23)
    5. <jojomen> front lenses will get scratched, impairing image quality. (rainemak, 16:50:25)
    6. <jojomen> (rainemak, 16:50:26)
    7. <jojomen> How final is the design? Is there any chance to change the (rainemak, 16:50:28)
    8. <jojomen> design to make cameras at least slightly recessed? (rainemak, 16:50:30)
    9. <Jolla> The design is not yet final. We just received so called (rainemak, 16:50:37)
    10. <Jolla> “appearance models” with the real dimensions, weight, materials (rainemak, 16:50:38)
    11. <Jolla> and feel as-close-as-possible to the actual device. So not to (rainemak, 16:50:40)
    12. <Jolla> confuse: the appearance model does not have functioning (rainemak, 16:50:42)
    13. <Jolla> electronics inside yet - actual functional samples are to come (rainemak, 16:50:44)
    14. <Jolla> down the road later. (rainemak, 16:50:46)
    15. <Jolla> (rainemak, 16:50:48)
    16. <Jolla> We are looking into this as well. Having cameras recessed would (rainemak, 16:50:50)
    17. <Jolla> likely not fix this. (rainemak, 16:50:52)
    18. https://forum.sailfishos.org/t/jolla-phone-update-design-appearance-models/27024 (rainemak, 16:50:54)

  8. Updated Forum rules to address AI generated posts (15 mins -- asked by jojomen) (rainemak, 16:59:01)
    1. <jojomen> Unfiltered AI posts regurgitate falsehoods, waste effort and (rainemak, 16:59:01)
    2. <jojomen> turn threads into an offtopic mess (rainemak, 16:59:01)
    3. <jojomen> (rainemak, 16:59:01)
    4. <jojomen> We are seeing an influx of new members, which is a good thing. (rainemak, 16:59:01)
    5. <jojomen> It’s probably unavoidable that newcomers post questions or (rainemak, 16:59:03)
    6. <jojomen> ideas that have already been discussed at length. Even if this (rainemak, 16:59:04)
    7. <jojomen> is a burden for forum regulars, it is something we need to (rainemak, 16:59:08)
    8. <jojomen> deal with as gracefully as possible. (rainemak, 16:59:10)
    9. <jojomen> (rainemak, 16:59:12)
    10. <jojomen> However, posting unfiltered AI content is a new trend that (rainemak, 16:59:14)
    11. <jojomen> brings a concentrate of all the normal forum challenges with (rainemak, 16:59:16)
    12. <jojomen> more harm than benefit. I would like to see the forum rules (rainemak, 16:59:18)
    13. <jojomen> updated to discourage or ban the practice. Maybe like: (rainemak, 16:59:20)
    14. <jojomen> (rainemak, 16:59:22)
    15. <jojomen> > Please avoid posting AI generated content. People will be (rainemak, 16:59:24)
    16. <jojomen> much more interested in engaging with your original ideas. (rainemak, 16:59:26)
    17. <jojomen> (rainemak, 16:59:28)
    18. <jojomen> Edit: Active moderation is better than detailed rules. Also, I (rainemak, 16:59:30)
    19. <jojomen> my allergy towards AI slop resulted in a harsher-than (rainemak, 16:59:32)
    20. <jojomen> -necessary reaction. I do think it should be mentioned in the (rainemak, 16:59:34)
    21. <jojomen> Forum Rules, but something short (like the above) would (rainemak, 16:59:38)
    22. <jojomen> suffice. (rainemak, 16:59:40)
    23. <Jolla> Like pherjung comment in the Forum, we had a discussion under (rainemak, 16:59:42)
    24. <Jolla> moderators about this as well. (rainemak, 16:59:44)
    25. <Jolla> (rainemak, 16:59:46)
    26. <Jolla> Let’s have an open discussion here as well. (rainemak, 16:59:48)

  9. Support backlog (5 mins -- asked by jojomen) (rainemak, 17:16:11)
    1. <jojomen> In mid-December, there was mention of a long list of support (rainemak, 17:16:11)
    2. <jojomen> tickets resulting in delayed replies. What is the current (rainemak, 17:16:11)
    3. <jojomen> situation? (rainemak, 17:16:11)
    4. <jojomen> (rainemak, 17:16:11)
    5. <jojomen> A month ago, there was this message asking for patience: (rainemak, 17:16:13)
    6. https://forum.sailfishos.org/t/jolla-phone-pre-order-campaign-has-started/25772/492 (rainemak, 17:16:15)
    7. <jojomen> …and since then we’ve had major holidays, so it could be that (rainemak, 17:16:17)
    8. <jojomen> you still have a long queue of tickets to deal with. What is (rainemak, 17:16:19)
    9. <jojomen> the current situation for support, what kind of delays could (rainemak, 17:16:21)
    10. <jojomen> be expected? (rainemak, 17:16:23)
    11. <jojomen> (rainemak, 17:16:25)
    12. <jojomen> Edit: removed reference to resolved issue (rainemak, 17:16:27)
    13. <Jolla> We’re dequeue it. As you understand we have of course received (rainemak, 17:16:32)
    14. <Jolla> new questions after this. In the backlog we have for example a (rainemak, 17:16:33)
    15. <Jolla> task to improve Jolla Phone (2026) FAQ based on the answered (rainemak, 17:16:33)
    16. <Jolla> frequent questions. If you haven’t noticed there’s an anchor now (rainemak, 17:16:35)
    17. <Jolla> as well. (rainemak, 17:16:39)
    18. https://jolla.com/phone#faq (rainemak, 17:16:41)
    19. <Jolla> (rainemak, 17:16:43)
    20. <Jolla> Thank you all for your help as well. (rainemak, 17:16:45)

  10. Harbour exception for File Browser (15 mins -- asked by pherjung) (rainemak, 17:23:35)
    1. <pherjung> There’s question itself. As it is rather long, please check (rainemak, 17:23:35)
    2. <pherjung> the link. (rainemak, 17:23:35)
    3. https://forum.sailfishos.org/t/community-meeting-on-15th-january-2026/26416/14 (rainemak, 17:23:37)
    4. https://forum.sailfishos.org/t/make-file-browser-official/27097/1 (rainemak, 17:23:38)
    5. <Jolla> The starting point is pretty much covered by nephros. (rainemak, 17:24:35)
    6. https://forum.sailfishos.org/t/make-file-browser-official/27097/32 (rainemak, 17:24:35)

  11. Progress in Xperia 10 IV/V ports? (5 mins -- asked by AlmuHS) (rainemak, 17:39:05)
    1. <AlmuHS> The Xperia 10 IV and V ports seems freezed from many months (rainemak, 17:39:05)
    2. <AlmuHS> ago. Some users got to use the Xperia 10 V using v4b blobs, to (rainemak, 17:39:05)
    3. <AlmuHS> fix the battery monitor, but the camera, microphone (only works (rainemak, 17:39:05)
    4. <AlmuHS> in calls) and hardware codecs doesn’t works yet. (rainemak, 17:39:07)
    5. <AlmuHS> (rainemak, 17:39:08)
    6. <AlmuHS> I want to know about the progress in these ports, especially (rainemak, 17:39:10)
    7. <AlmuHS> camera and microphone. (rainemak, 17:39:12)
    8. <Jolla> Hopefully mal is able to join and update on this if there's (rainemak, 17:39:19)
    9. <Jolla> something to update. (rainemak, 17:39:19)

  12. Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla) (rainemak, 17:43:12)
  13. General discussion (15 mins) (rainemak, 17:45:54)
  14. Next meeting time and date (2 mins) (rainemak, 18:07:10)
    1. Next meeting will be held on Thursday 29th January 2026 at 04:00pm UTC: 2026-01-29T1600Z (rainemak, 18:10:13)


Meeting ended at 18:10:56 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. rainemak (261)
  2. poetaster (69)
  3. jojomen (63)
  4. pherjung (23)
  5. ExTechOp (22)
  6. nephros_ (22)
  7. filip (12)
  8. rikudou (12)
  9. Nico (7)
  10. mal (7)
  11. direc85[m] (3)
  12. sebix[m] (3)
  13. sailbot (2)
  14. HengYe[m] (1)


Generated by MeetBot 0.1.4.