#sailfishos-meeting: Sailfish OS, open source, collaboration -- 23rd April 2026
Meeting started by rainemak at 16:00:09 UTC
(full logs).
Meeting summary
-
- Meeting information and agenda can be found
here: (rainemak,
16:00:09)
- https://forum.sailfishos.org/t/29030/3
(rainemak,
16:00:09)
- Brief introduction (5 min). Please prefix your name/handle with #info (rainemak, 16:00:09)
- Otto Mäkelä, community (extechop[m],
16:00:16)
- Raine Mäkeläinen, Jolla (rainemak,
16:00:22)
- Nico, community (Nico,
16:00:27)
- Andrea Scarpino, community (Guest6720,
16:00:35)
- Matti Viljanen, Jolla (direc85[m],
16:01:03)
- mal, Jolla (mal,
16:04:41)
- Niels, Community (fingus,
16:04:48)
- frankps, Community (frankps,
16:05:03)
- Keyboard and predictive text (5 mins -- Kanthal) (rainemak, 16:05:06)
- <Kanthal> Hello! (rainemak,
16:05:06)
- <Kanthal> I am curious if there are any
plans to modernize the whole (rainemak,
16:05:06)
- <Kanthal> keyboard experience, especially
since there will be a lot of new (rainemak,
16:05:06)
- <Kanthal> users with J2. (rainemak,
16:05:06)
- <Kanthal> As an example I struggle to
type on a keyboard that doesn’t have (rainemak,
16:05:07)
- <Kanthal> borders around the letters,
suggestions, autocorrect (didn’t have (rainemak,
16:05:09)
- <Kanthal> that in my language even with
XT9). (rainemak,
16:05:11)
- <Kanthal> Features like OTP codes being
shown as a autofill suggestion when (rainemak,
16:05:13)
- <Kanthal> you receive them in sms/email
are also very helpful and pretty (rainemak,
16:05:15)
- <Kanthal> much standard on other
platforms. (rainemak,
16:05:17)
- <Kanthal> (rainemak,
16:05:19)
- <Kanthal> So I would like to know if
reworking the keyboard is on the (rainemak,
16:05:21)
- <Kanthal> horizon. (rainemak,
16:05:23)
- <Kanthal> Thanks in advance! (rainemak,
16:05:27)
- <Jolla> Thank you for your question.
Prediction is something that we're (rainemak,
16:05:29)
- <Jolla> thinking about. Earlier we
mentioned presage as an option. We (rainemak,
16:05:31)
- <Jolla> should investigate if we could do
something with hunspell. Let's (rainemak,
16:05:33)
- <Jolla> see what can we make for Sailfish
OS 5.2. (rainemak,
16:05:35)
- Community Tasks Board (10 mins -- nephros) (rainemak, 16:11:51)
- https://forum.sailfishos.org/t/community-meeting-on-23rd-april-2026/29030/3
(rainemak,
16:11:51)
- <Jolla> What an excellent topic. We have
been steering this all towards (rainemak,
16:13:01)
- <Jolla> GitHub Sailfish OS issues. Same
time we are opening issues from the (rainemak,
16:13:01)
- <Jolla> internal issue tracker to public
-- let us do it in our own phase. (rainemak,
16:13:01)
- <Jolla> It'll take time. Espacially
regarding components that are already (rainemak,
16:13:01)
- <Jolla> open sourced. (rainemak,
16:13:01)
- <Jolla> (rainemak,
16:13:03)
- <Jolla> We're open to new plugins for
GitHub, let's avoid intoducting (rainemak,
16:13:04)
- <Jolla> something completely new.
(rainemak,
16:13:06)
- ACTION: We need to
improve / figure community task board (rainemak,
16:21:01)
- Tracking of non-resolved Community Meeting topics (10 mins -- nephros) (rainemak, 16:22:05)
- <nephros> While these meetings offer a
nice and welcome opportunity for the (rainemak,
16:22:05)
- <nephros> Community to discuss topics,
the results of the meetings tend to (rainemak,
16:22:05)
- <nephros> be very
non-committal/consequential. Words like “later”, “we will
(rainemak,
16:22:05)
- <nephros> come back to this” etc.
(rainemak,
16:22:05)
- <nephros> This is fine - however, often
things that should have received an (rainemak,
16:22:07)
- <nephros> answer “later” are lost in
time/memory/the meeting logs. (rainemak,
16:22:08)
- <nephros> As the Meeting bot has the
capability of creating "action items’, (rainemak,
16:22:10)
- <nephros> I propose using that to record
things that should be revisited (rainemak,
16:22:12)
- <nephros> “later”. (rainemak,
16:22:14)
- <nephros> (rainemak,
16:22:16)
- <nephros> At the start of each subsequent
meeting, if there were updates to (rainemak,
16:22:18)
- <nephros> a previous Action Item, this
should be presented briefly. (rainemak,
16:22:20)
- <nephros> (rainemak,
16:22:22)
- <nephros> Action Items should only be
added if they have some resemblance (rainemak,
16:22:26)
- <nephros> of importance. Not every
unresolved topic needs to be an action (rainemak,
16:22:28)
- <nephros> item. (rainemak,
16:22:30)
- <nephros> Whether something is an Action
Item or not is decided by the (rainemak,
16:22:32)
- <nephros> Meeting Chair Person
only. (rainemak,
16:22:34)
- <Jolla> This we should tackle the
soonest. Proposal would be that Meeting (rainemak,
16:22:41)
- <Jolla> Chair Person keeps track on the
action items. We could repeat open (rainemak,
16:22:41)
- <Jolla> actions as a first item after
intro. That's in itself is an (rainemak,
16:22:42)
- <Jolla> action point for rainemak. Like
requested, let's focus on the how (rainemak,
16:22:44)
- <Jolla> part. (rainemak,
16:22:46)
- <Jolla> Meeting Chair should flag actions
as suggested. (rainemak,
16:23:21)
- ACTION: Actions to be
followed up meeting by meeting (rainemak,
16:24:31)
- ACTION: Jolla to
adjust meeting template (rainemak,
16:33:07)
- user-replaceable battery on the Jolla J2 site (5 mins -- PolatBirdal) (rainemak, 16:33:55)
- <PolatBirdal> Hello, there is a statement
on your site saying “user- (rainemak,
16:33:55)
- <PolatBirdal> replaceable battery,” but
recently when we examined the (rainemak,
16:33:55)
- <PolatBirdal> phones with friends in the
group, the phone’s battery was (rainemak,
16:33:55)
- <PolatBirdal> under a protective plate,
and the protective plate was (rainemak,
16:33:55)
- <PolatBirdal> screwed to the case.
Logically, how can it be replaced by the (rainemak,
16:33:56)
- <PolatBirdal> user? (rainemak,
16:33:58)
- <Jolla> Yes, you need to open the screws
to replace battery. The battery #info <Jolla> won't be glued
so no need for heater. (rainemak,
16:34:00)
- details of the return conditions regarding the product (5 mins -- PolatBirdal) (rainemak, 16:40:06)
- <PolatBirdal> Hello, I asked before as
well, yes, but I forgot to ask for (rainemak,
16:40:06)
- <PolatBirdal> the details, so you
answered according to the situation I (rainemak,
16:40:06)
- <PolatBirdal> asked about. I could not
fully explain the situation in the (rainemak,
16:40:06)
- <PolatBirdal> community chat. The exact
issue is this: of course, we also (rainemak,
16:40:06)
- <PolatBirdal> know this device is a
European device, meaning it is expected (rainemak,
16:40:07)
- <PolatBirdal> to be marketed within
Europe, but as people who like Jolla, (rainemak,
16:40:08)
- <PolatBirdal> we accepted this difficulty
and prepared shipping companies (rainemak,
16:40:10)
- <PolatBirdal> like forward2me. In this
sense, what kinds of problems that (rainemak,
16:40:12)
- <PolatBirdal> may arise from handing it
over to a shipping company are we (rainemak,
16:40:14)
- <PolatBirdal> responsible for? If a
problem comes up during the shipping (rainemak,
16:40:16)
- <PolatBirdal> process and the shipping
company has the product but is not (rainemak,
16:40:18)
- <PolatBirdal> sending it, are we free to
use our return option at that (rainemak,
16:40:20)
- <PolatBirdal> moment, or since we have
already given this product to the (rainemak,
16:40:22)
- <PolatBirdal> shipping company, do we no
longer have any return right at (rainemak,
16:40:26)
- <PolatBirdal> all under any
circumstances? (rainemak,
16:40:28)
- <Jolla> This should be covered in forum
already. Anything missing? (rainemak,
16:40:30)
- https://forum.sailfishos.org/t/community-meeting-on-23rd-april-2026/29030/9
(rainemak,
16:40:32)
- Some love for Harbour (5 mins -- ilpianista) (rainemak, 16:44:14)
- <ilpianista> I read several topics about
what API are missing in Harbour so (rainemak,
16:44:14)
- <ilpianista> that we get more apps into
it, however none is talking about (rainemak,
16:44:15)
- <ilpianista> the Harbour “dev
experience”. I’m sorry, but from my point of (rainemak,
16:44:15)
- <ilpianista> view: it s*cks. We are
waiting for a wave of new users, but (rainemak,
16:44:15)
- <ilpianista> there could be developers
among them as well. I would like to (rainemak,
16:44:16)
- <ilpianista> see these things implemented
in harbour ASAP: 1) notifications (rainemak,
16:44:18)
- <ilpianista> for approved/rejected apps,
2) notifications for comments and (rainemak,
16:44:20)
- <ilpianista> 3) two factor
authentication, as I’m concerned about supply (rainemak,
16:44:22)
- <ilpianista> chain attacks which are
quite popular and successful. (rainemak,
16:44:26)
- <Jolla> Good points. Let's have open
discussion on the topic. (rainemak,
16:44:28)
- Batterys for Jolla C2 and more (5 mins -- asked by fingus) (rainemak, 16:55:24)
- <fingus> The first shipped Jolla C2 units
(including mine) are now about (rainemak,
16:55:24)
- <fingus> 1,5 years old, and I think this
is a good time to start (rainemak,
16:55:24)
- <fingus> considering the supply of spare
batteries for them. The (rainemak,
16:55:25)
- <fingus> possibility of getting Reeder
S19 Max Pro S batteries in Europe (rainemak,
16:55:26)
- <fingus> looks bad, so this seems to be
an important issue to resolve. I (rainemak,
16:55:28)
- <fingus> also contacted our spare-parts
distributor (https://www.aswo.de, (rainemak,
16:55:30)
- <fingus> they are reliable, fast, have
been on the market for a long time (rainemak,
16:55:32)
- <fingus> and have a good reputation.),
from whom we purchase a large number (rainemak,
16:55:34)
- <fingus> of spare parts for the
notebooks, tablets, and smartphones we sell (rainemak,
16:55:36)
- <fingus> at the company where I work. We
have been working with them for (rainemak,
16:55:38)
- <fingus> the last 24 years and they
provide a good service. I explained the (rainemak,
16:55:40)
- <fingus> situation with the new Jolla
phones and gave them (german parent (rainemak,
16:55:42)
- <fingus> company) your contact
information, so you (or reeder) might be (rainemak,
16:55:44)
- <fingus> able to form a joint venture for
spare parts. The goals of this (rainemak,
16:55:46)
- <fingus> idea are availability,
lower-cost and faster shipping and leave (rainemak,
16:55:48)
- <fingus> out this kind of work for your
employees. I also offered to stay (rainemak,
16:55:50)
- <fingus> in contact with them about this
matter to provide further (rainemak,
16:55:52)
- <fingus> information as a German native
speaker with a technical background (rainemak,
16:55:56)
- <fingus> and as a community
spokesperson. (rainemak,
16:55:58)
- <fingus> (rainemak,
16:56:00)
- <fingus> I’ll try to attend, but no
promises (when stuck in traffic jam), (rainemak,
16:56:02)
- <fingus> maybe shift this topic to latest
slot. (rainemak,
16:56:04)
- <Jolla> Currently we are lacking spare
batteries for Jolla C2. We do have (rainemak,
16:56:06)
- <Jolla> replacement units though.
Further, swapping battery on Jolla C2 is (rainemak,
16:56:08)
- <Jolla> not straight-forward as you need
in practice heat the back plate to (rainemak,
16:56:10)
- <Jolla> get it properly detached (without
breaking it). It's not (rainemak,
16:56:12)
- <Jolla> recommended to try to swap Jolla
C2 battery yourself. (rainemak,
16:56:14)
- Open Pull Requests (PRs) to discussion (5 mins -- asked by Jolla) (rainemak, 17:05:20)
- General discussion (10 mins) (rainemak, 17:14:45)
- Next meeting time and date (2 mins) (rainemak, 17:26:45)
- Next meeting will be held on Thursday 7th May
2026 at 04:00pm UTC: 2026-05-07T1600Z (rainemak,
17:28:55)
Meeting ended at 17:29:29 UTC
(full logs).
Action items
- We need to improve / figure community task board
- Actions to be followed up meeting by meeting
- Jolla to adjust meeting template
People present (lines said)
- rainemak (237)
- fingus (36)
- Nico (30)
- Guest6720 (15)
- Polatbirdal (13)
- extechop[m] (7)
- direc85[m] (6)
- frankps (4)
- poetaster (4)
- sailbot (2)
- mal (2)
- Keto (2)
- tuplasuhveli[m] (1)
Generated by MeetBot 0.1.4.