Please note new time slot
Schedule: Thursday 2026-04-23T16: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.
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:
2 Likes
The idea would be something akin to a (or maybe actual) “Kanban” board Backlog column published by Jolla, that aspiring community contributors can look at and pick up tasks from.
Kind of a “reverse channel” from Jolla to the community (as opposed to bug reports, feature requests etc. whic go the other way)
A possibility for the Jolla team to potentially get work done externally, with some control over what is deemed “important”, or “important, but not now”, or “meh, one-banana-problem, lets find some monkey”.
Things that come to mind:
- “Janitorial” work on the Sailfish OS · GitHub repos: cleaning up .spec files, fixing packaging things, retiring old repos/packages that may not be used any more
- updating base open source packages
- other things which are on the Jolla Team’s backlog but do not necessarily need to be performed by the Jolla team
Also important: It should be understood that nothing about publishing such a list would be interpreted as a commitment or non-commitment of Jolla to anything, not as a road map, or anything else that reflects internal workings at Jolla.
It is simply a list of things staff thinks community could help with.
Personal note: in the discussion about this, please do not focus on potential tools, or actual tasks - instead focus on the “process” - on the how, not the what.
Be aware of how bikeshedding works.
11 Likes
- Name/IRC nick: nephros
- Topic: Tracking of non-resolved Community Meeting topics
- Approx. time needed: 5min
- Substitute (optional):
- Some details about the topic:
While these meetings offer a nice and welcome opportunity for the Community to discuss topics, the results of the meetings tend to be very non-committal/consequential. Words like “later”, “we will come back to this” etc.
This is fine - however, often things that should have received an answer “later” are lost in time/memory/the meeting logs.
As the Meeting bot has the capability of creating "action items’, I propose using that to record things that should be revisited “later”.
At the start of each subsequent meeting, if there were updates to a previous Action Item, this should be presented briefly.
Action Items should only be added if they have some resemblance of importance. Not every unresolved topic needs to be an action item.
Whether something is an Action Item or not is decided by the Meeting Chair Person only.
8 Likes
- Name/IRC nick:Polatbirdal
- **Topic:**details of the return conditions regarding the product
- **Some details about the topic:**Hello, I asked before as well, yes, but I forgot to ask for the details, so you answered according to the situation I asked about. I could not fully explain the situation in the community chat. The exact issue is this: of course, we also know this device is a European device, meaning it is expected to be marketed within Europe, but as people who like Jolla, we accepted this difficulty and prepared shipping companies like forward2me. In this sense, what kinds of problems that may arise from handing it over to a shipping company are we responsible for? If a problem comes up during the shipping process and the shipping company has the product but is not sending it, are we free to use our return option at that moment, or since we have already given this product to the shipping company, do we no longer have any return right at all under any circumstances?
- Approx. time needed: If I am in the meeting, 10 minutes; if not, 5 minutes.
5 Substitute: The reason I am asking about this issue in detail is that I will be going abroad. Since I am going to a foreign country, they want me to come to our country and collect the tax ID. Because of this, I am asking these questions while considering possibilities such as not being able to receive it.
I would like to add to PolatBirdals Post:
Sliding release exist, so there normally shouldn’t be a need for screws.
But i understand why they choose a metal plate for battery cover. It’s a strong physical protection against punctures and it also transmits/distribute heat better while charging, acting like a passive cooling system.
2 Likes
