Community meeting on 21st May 2026

[rainemak]

Please note new time slot

Schedule: Thursday 2026-05-21T16:00:00Z

Sailfish OS Community Calendar (ICS format)

Even if you do not participate, topics tend to generate discussion. I want to see discussion happening. Thus, I’m proposing that we’d use 10mins as minimum topic duration. Maximum 6 topics a week. We’ll continue with the extended 90 mins meeting duration.

Jolla to check action points from the previous meeting. We agreed today that we’ll start to follow up action points on each meeting.

• The meeting will be held on oftc.net IRC #sailfishos-meeting .
• You can also join on Matrix or read-only on Telegram .
• Logs of previous meetings: 2026, 2025, 2024, 2023, 2022, 2021, 2020, earlier.

Topic proposals for the meeting:

• Add your name/nick using the template below to suggest a topic.
• Indicate how much time you’ll need so we can time-box the meeting accordingly.
• Please be as thorough as you can with your question/topic.
• If you can’t make the meeting please ask and name a substitute.

It is expected that you show up and present your topic, or name a substitute and make sure they attend in your absence. These IRC meetings are for real time participation and live discussions, otherwise you can post the topic on here and get responses that way.

We need you to be present to clarify details in the topic, and to ensure the discussion is leading to the answers you are looking for! If you do not participate or your question/topic isn’t clear enough it will be postponed. Also: always ask for more time than you anticipate your topic needs!

Please have your topics ready at least 3 days before the meeting so we can prepare good answers. Topics announced afterwards will be postponed to the next meeting.

Template for topic proposal: (post your topic proposals as comments to this forum topic).

• Name/IRC nick:
• Topic:
• Some details about the topic:
• Approx. time needed:
• Substitute (optional):

Open Pull Requests:
If you have, or know of, a pull request that’s been open for at least 3 weeks, but which you think deserves attention, please add a comment using the template below and we’ll consider it during the next meeting.

• Name/IRC nick:
• Open PR URL:

[nephros]

Open Pull Requests:

• Name/IRC nick: nephros, (Thaodan?)
• Open PR URL:
  • packaging: Avoid linker script libterminfo.so by Thaodan · Pull Request #3 · sailfishos/ncurses · GitHub
  • Update configure flags and update by Thaodan · Pull Request #3 · sailfishos/readline · GitHub

These have stalled a bit, but the issues lead to failure when building against pkgconfig(readline).

Example log (from nfs-utils):

[   17s] checking pkg-config is at least version 0.9.0... yes
[   17s] checking for mount... yes
[   17s] checking for libnl-3.0 >= 3.1... yes
[   17s] checking for libnl-genl-3.0 >= 3.1... yes
[   17s] checking for readline... no
[   17s] configure: error: Package requirements (readline) were not met:
[   17s] 
[   17s] Package 'termcap', required by 'readline', not found
[   17s] 
[   17s] Consider adjusting the PKG_CONFIG_PATH environment variable if you
[   17s] installed software in a non-standard prefix.

[jollus]

@jollus

@jojomen

I have made two (or more) orders. Will I have to pay for shipping twice?

No, Jolla will combine your orders and refund any excess shipping you have paid.

I am concerned this may be an issue when we are using a forwarding address company that is expecting two or more orders. Will a new receipt be emailed showing all products in one package?

That would help because I could delete the multiple receipts currently uploaded on their site and re-upload a new receipt, if sent.

I hate to see an employee receiving the package that has 2 or more phones in it, be tempted to keep them. He/she may think the sender made a mistake in sending extra phones whilst the receipt uploaded says 1 phone.

Per jojomen direction re:…..

@jojomen

I don’t remember seeing this discussed. The only official comment AFAIK is that Jolla’s responsibility ends when the parcel is delivered, in your case to the forwarding agent.

You could ask in the next Community Meeting, but do note that the deadline for new questions has just passed. If you’re lucky, there will be an answer anyway, otherwise you should check that your question is moved and appears below the announcement of the next meeting.

Finally, please update the FAQ with your Q+A

[CLMA31]

1. Name/IRC nick: CLMA31
2. Topic: General question regarding the timeline of 5.1 and AAS bluetooth support
3. Some details about the topic: Firstly, sorry for very late topic, but I thought that maybe this subject could be answered even without preparation. I don’t want to rush things, but I’m interested to know what does the timelines of 5.1 and AAS bluetooth releases look like? 5.1 has sounded like it will land soon, but can the bluetooth support for AAS side also be released at the same time?
4. Approx. time needed: 5min, probably written answer is enough
5. Substitute (optional): I try to attend, but written answer is also enough for this

[ThijssjihT]

Sorry, I am way too late, disregard this post if the timeframe causes any issues, and I will repost it for the next meeting.

1. Name: ThijssjihT
2. Topic: SFOS merch
3. Some details about the topic: The community wants merch. It will be good for brand recognition, and you will get some small profits as well. Questions:

• Are there plans to do merch?
• If not, and if the community will make designs and find a partner for printing, sales and distribution, would you do merch? Promotion of Sailfish OS / Jolla - #41 by ThijssjihT

4. Approx. time needed: 10 min.
5. Substitute: I probably won’t be able to attend, but I read every meeting text.

[rainemak]

I’m having a bit of tech difficulties on joining. Trying again in a moment. Trying to start meeting 15mins past.

[filip.k]

Minutes: #sailfishos-meeting: Sailfish OS, open source, collaboration -- 21st May 2026
Minutes (text): https://irclogs.sailfishos.org/meetings/sailfishos-meeting/2026/sailfishos-meeting.2026-05-21-16.08.txt
Log: #sailfishos-meeting log

Updated by Raine. Thanks @filip.k adding this.