#mer-meeting: Sailfish OS, open source, collaboration – 14th November 2019

Meeting started by Jaymzz at 09:00:04 UTC (full logs).

Meeting summary

  1. Brief introduction (5 min). Please prefix your name/handle with # info (Jaymzz, 09:00:30)
    1. James Noori - sailor @ Jolla (Jaymzz, 09:00:38)
    2. Jonatan Walck - community lurker:) (jwalck, 09:00:56)
    3. Ville Nummela - sailor @ Jolla (ViGe, 09:01:12)
    4. Meeting information and agenda can be found here: https://lists.sailfishos.org/pipermail/devel/2019-November/008910.html (Jaymzz, 09:01:17)
    5. Otto Mäkelä - community (ExTechOp, 09:01:36)
    6. Nico - community (Nico[m], 09:02:19)
    7. Damien Caliste, community (dcaliste, 09:02:23)
    8. David Llewellyn-Jones - sailor @ Jolla (flypig, 09:02:23)
    9. Mister_Magister - community (Mister_Magister, 09:02:34)
    10. Simonas Leleiva - privateer for Jolla (sledges, 09:02:39)
    11. KeeperoftheKeys - community dev (KeeperoftheKeys, 09:03:00)
    12. Björn Bidar - community dev (Thaodan, 09:03:10)

  2. SSH connectivity (Asked by KeeperoftheKeys – 10 min) (Jaymzz, 09:06:49)
    1. It is not clear to me how exposed SSH is on the phone, netstat tells me SSH is listening on all interfaces, and though I recall that there was some mention of SSH being locked down a bit in some previous release I haven't been able to find it. SSH is reachable over both USB and wireless which is OK (though for wireless maybe a 'trusted network' flag would be nice) however it may actually also be reachable over the cellular con (Jaymzz, 09:07:02)
    2. Restricting access to SSH from cellular network was released in 3.0.2 using a firewall. Even though you see sshd listening on all interfaces it's only connectable from Wifi or USB. You can find the rules for this in /etc/connman/firewall.conf and its associated firewall.d directory (though USB is configured separately). There's currently no way to lock SSH down to only 'trusted' WiFi networks; it's a nice idea. There are the s (Jaymzz, 09:07:46)
    3. https://debian-administration.org/article/685/Restricting_SSH_logins_to_particular_IP_addresses (Jaymzz, 09:07:57)
    4. 5 extra minutes added to this topic (Jaymzz, 09:19:07)

  3. Design elements of SFOS that started to show their age and UX/UI issues. (Asked by ApBBB – 20 min) (Jaymzz, 09:22:56)
    1. SFOS is some years old now and certain elements (ie app icons, indicators etc) have started to show their age. Is there going to be a redesign anytime soon??? Also there have been consistency issues (small and most likely easily fixable) i the UI/UX noted by the community for quite a while now that haven't been addressed. Anything jolla plans to do? (Jaymzz, 09:23:09)
    2. We are gradually upgrading our asset. We appreciate all the feedback to identify existing problems. Helping the development team with a detailed list of the known occurrences of the problem is always invaluable. (Jaymzz, 09:23:49)

  4. Enable/fix bluetooth 4 for Android wearable apps (asked by minodesign79 – 5 min) (Jaymzz, 09:31:06)
    1. It seem that Android wearable apps are not able to connect with their related devices. An example are the MI Bands: the MI Fit app, is downloadable and working, but can't pair with Mi band 3 on XA2 because of a 'no BT 4 error'. If it's not a security breach it would be nice open the access for Android apps, or check/update BT drivers on Android side. (There are some duplicated request on TJC) (Jaymzz, 09:31:17)
    2. It is not supported at the moment and there is no ETA to when it will be. Unfortunately giving Android Apps access to Bluetooth is not as simple as allowing it to access the hardware directly since then Sailfish OS and AlienDalvik would interfere with each other, what complicates the situation is that android APIs (bluedroid/fluoride) and Sailfish OS APIs (bluez5) differ quite a lot so a direct translation is also not easy to (Jaymzz, 09:31:54)

  5. UI topic: Bold/accessible mode (asked by minodesign79 – 5 min) (Jaymzz, 09:39:55)
    1. I noticed the absence of 'boldness' on SF OS UI typography. This topic is not about a graphic discussion, it's more about accessibility: it would be nice an Option like "Make test bolder" that modifies All the fonts on UI with the source pro Bold (or the bold variant of font used). (Jaymzz, 09:40:05)
    2. We have also identified the need to improve legibility on Sailfish OS. Some enhancements have already been introduced in the current Sailfish version, for example light ambiences have slightly thicker fonts to improve legibility. Improving accessibility options to have different typefaces is a possibility we are considering. While we have ongoing tasks to improve this area, it may be good to share some light on the complexity (Jaymzz, 09:40:29)
    3. ideas: create differentiation in the fonts for an easier understanding based on the user's disability. (Jaymzz, 09:45:37)
    4. ideas: Maybe change the font in a accesabity menu depending of the type of the disability that the user selects. (Jaymzz, 09:45:49)
    5. ideas: a high contrast ambiance (Jaymzz, 09:46:51)
    6. idea suggestion from ApBBB: a black and white ambience (Jaymzz, 09:48:45)

  6. "Swipe Down" gesture behavior (asked by minodesign79 – 5 min) (Jaymzz, 09:55:33)
    1. Adding an option under 'Gestures' where the user can activate the old school "Swipe down to close". A lazy solution could be to place an option to chose from: "Available also on apps", and "Only from home view". (Jaymzz, 09:55:47)
    2. We are very much aware of the topic, and for this reason we have also studied the behaviour. In addition we should not forget that we have repeated feedback that many users struggled with the old swipe down to close gesture. Creating an option is something that we prefer to avoid. Options can increase the complexity of the software and result to higher maintenance effort. As a reminder, the Sailfish 3 has a "Swipe down to clos (Jaymzz, 09:56:04)
    3. 10 min over time - adding 5 more minutes due to hot discussion (Jaymzz, 10:10:47)

  7. Refining the Ambiences, Ambiences as file (asked by minodesign – 10 min) (Jaymzz, 10:14:38)
    1. Ambiences were a very nice, idea at beginning. What about making possible to export, and share own Ambience through a file? In this old Tjc thread I mentioned an Ambience free store, but there are copyright flaws. The ability to export and send privately an ambience to another SF phone can remain... (Jaymzz, 10:14:46)
    2. https://together.jolla.com/question/181188/make-ambiences-great-again-feature-request/ (Jaymzz, 10:14:52)
    3. Cool idea. Since an ambience is mostly about content (wallpaper, ringtones) shouldn't require coding skills to share and upload ambiences out of the device. Polished ambiences need more control than device UI currently provides. (Jaymzz, 10:15:06)

  8. Developer forum (by ViGe – 10 min) (Jaymzz, 10:28:59)
  9. general discussion (10 min) (Jaymzz, 10:43:26)
    1. If you still have more ideas about the mentioned forum, please send them to me via email: ville.nummela@jolla.com (Jaymzz, 10:44:00)

  10. next meeting time and date (5 min) (Jaymzz, 10:54:08)
    1. Next meeting will be held on December 12th 2019 at 09:00 UTC (Jaymzz, 10:54:51)

Meeting ended at 10:57:10 UTC (full logs).

Action items

  1. (none)

People present (lines said)

  1. Jaymzz (101)
  2. minodesign79 (55)
  3. Thaodan (42)
  4. KeeperoftheKeys (36)
  5. Mister_Magister (33)
  6. elfio (25)
  7. ViGe (21)
  8. schmittlauch[m] (20)
  9. Kaffeine (19)
  10. jpetrell (14)
  11. Nico[m] (13)
  12. sledges (10)
  13. dcaliste (6)
  14. abranson (6)
  15. flypig (6)
  16. ExTechOp (6)
  17. adantes (5)
  18. Venemo (4)
  19. r0kk3rz (4)
  20. Hummer12007 (4)
  21. jlaakkonen (4)
  22. lbt (2)
  23. merbot (2)
  24. mal (2)
  25. jwalck (1)
  26. minodesign (1)
  27. ljo (1)

Generated by MeetBot 0.1.4.