Community meeting on 23rd October 2025

Announcements
1

Please note new time slot

Schedule: Thursday 2025-10-23T16:00:00Z :world_map: :date:

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 agreed 9th October to extend meeting time slot to 90mins. Same time slot still.

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
2

  • Name/IRC nick: KeeperoftheKeys

  • Topic: WPA3 status update

  • Some details about the topic: I recently installed some simple Open Source IoT switches and was very surprised to find them supporting WPA3, this makes my Jolla phone the only thing preventing me from switching our home network to WPA3. I recall that there has been some work on this in the past where do things stand? Based on a little of my own testing (see below) it seems like it should be “in reach/spitting distance”.

    WPA3 is mostly a software issue, I have seen it working on Linux laptops that were built years before anyone even thought about WPA3, as far as I recall connman/wpasupplicant would need to be updated for this.

    Software versions:

    • Connman 1.41 shipped initial WPA3-SAE support based on phoronix, the current version on my phone [SFOS 5 (10ii)] is 1.38
    • Per a wpa_supplicant changelog it added WPA3 in 2.10 and on my phone I find 2.11 and I was able to manually connect using it (wpa_supplicant -i wlan0 -c local.conf) this did not set the correct IP address from my router, I need to check with another device if this is a config issue of the testing SSID or an issue with the phone but after manually setting the correct IP address (ip addr add…) I was able to “prove” that I indeed connected successfully to the WPA3 SSID.
      To do all of this I also had to do some gymnastics with enabling/disabling wireless in the GUI to allow wpa_supplicant to grab control of wlan0 from connman.

  • Approx. time needed: 2-3 minutes

  • Substitute (optional): Please discuss regardless of my presence, I will most likely not be able to attend.

5 Likes
3

  • Name/IRC nick: KeeperoftheKeys

  • Topic: Allow apps to use nextcloud client or add ability to configure folder sync

  • Some details about the topic: As documented in this topic Sailsync OwnCloud does not work out of the box with recent versions of nextcloud and due to Qt limitations this is only going to get worse, @nephros has built a newer drop in binary with Qt 5.15 but that is also a solution that will only hold so long and while those who run NC instances where they have full control can lower the minimum.supported.desktop.version they are taking a risk as per the NC devs.
    IMHO Sailsync OwnCloud provides a functionality that should just be part of the NC account settings, if that is not a possibility then it would be nice if it could leverage the builtin client (and credentials) instead of needing to ship its own.

  • Approx. time needed: 5 minutes

  • Substitute (optional): Please discuss regardless of my presence, I will most likely not be able to attend.

8 Likes
4
5 Likes