#sailfishos-meeting: Sailfish OS, open source, collaboration – June 25th 2020

Meeting started by Jaymzz at 08:00:52 UTC (full logs).

Meeting summary

    1. Meeting information and agenda can be found here: https://lists.sailfishos.org/pipermail/devel/2020-June/009213.html (Jaymzz, 08:01:01)

  1. Brief introduction (5 min). Please prefix your name/handle with # info (Jaymzz, 08:01:16)
    1. James Noori - sailor @ Jolla (Jaymzz, 08:01:23)
    2. Gabriel - community (ggabriel, 08:01:30)
    3. Adam Pigg - Community porter/dev (piggz, 08:01:39)
    4. Louis - community (louisdk, 08:01:40)
    5. David Greaves - sailor and Mer guy (lbt, 08:01:40)
    6. remote - community (remote__, 08:01:43)
    7. Andrew Branson - sailor (abranson, 08:01:55)
    8. Ville Nummela - sailor@Jolla (ViGe, 08:01:58)
    9. Joakim - Community / dev (Sefriol, 08:02:04)
    10. David Llewellyn-Jones - sailor@jolla (flypig, 08:02:10)
    11. Mister_Magister - community (Mister_Magister, 08:02:15)
    12. Damien Caliste, community (dcaliste, 08:03:04)

  2. Decouple LUKS password from PIN code (by remote – 5 min) (Jaymzz, 08:06:08)
    1. currently LUKS password is the same as PIN code for unlock (numeric). It is very easy to crack it offline. We need an option to have a separate full-keyboard option for LUKS encryption password. (Jaymzz, 08:06:30)
    2. Alphanumeric keyboard for device lock is in our plans, but we don't have clear schedule to share as of yet. (Jaymzz, 08:06:48)
    3. Thaodan Community (Thaodan, 08:10:41)

  3. Implement a hook for wrong PIN code (panic PIN) (5 min by remote) (Jaymzz, 08:13:34)
    1. create a hook for a wrong PIN code, so it checks e.g. /etc/panic-pin for the wrong PIN and if it matches, execs the script in that file, that could for example zero out 4096 sectors (luks header) of /dev/mapper/sailfish-home. For advanced users. (Jaymzz, 08:13:43)
    2. This isn't something we have immediate plans for, but the component handling the actual unlocking is systemd-cryptsetup, which is open source. Our systemd packaging is here: https://git.sailfishos.org/mer-core/systemd/. We think it would be possible for an interested community dev to create something that does this. (Jaymzz, 08:13:56)
    3. https://git.sailfishos.org/mer-core/systemd/ (Jaymzz, 08:14:03)

  4. I/O Errors on working XA2 (by LouisDK – 5 min) (Jaymzz, 08:21:47)
    1. I recently did a file system check on my XA2 with Sailfish and got I/O errors. Fearing that my hardware was broken I reached out to Jolla Care which confirmed the same result on their XA2 running Is this expected behavior due to the encrypted filesystem? TJC ticket: (Jaymzz, 08:21:58)
    2. https://together.jolla.com/question/227495/xa2-bug-io-error-doing-file-system-check-on-working-device/ (Jaymzz, 08:22:04)

  5. Official Fxtec Pro 1 port (by LouisDK – 5 min) (Jaymzz, 08:30:58)
    1. There's a pretty stable port of SailfishOS for the Fxtec Pro 1. Due to the hardware adaption the alien dalvik from the XA2 should run on this device. Are there any current plans for making an official port for this device? (Jaymzz, 08:31:08)
    2. We are very interested in all projects using Sailfish OS. We are also very eager to support these projects if there is an opportunity to do so. Nevertheless, we do not have an official plan to provide the port for FxTec Pro at this point. (Jaymzz, 08:31:28)

  6. Jolla and public communication (by LouisDK – 20 min) (Jaymzz, 08:38:38)
    1. Lately Jolla have been quite sparse regarding their public communication. This might make some people nervous about the future of the OS and might keep someone from being interested in and developing apps for the platform. Would Jolla consider keeping the community more updated (eg. by making more blog posts about OS development and insights)? (Jaymzz, 08:38:47)
    2. We love this suggestion, and we'd love to write more blog posts, but usually if there are no posts it's because we're hard at work creating new designs, code, functionality and business. But the request is noted and we'll get as much out there as we can. (Jaymzz, 08:38:57)

  7. general discussion (15 min) (Jaymzz, 08:44:04)
    1. https://doc.qt.io/archives/qtquick-components-symbian-1.1/qt-components-right-to-left.html (piggz, 08:53:12)

  8. next meeting time and date (5 min) (Jaymzz, 09:01:39)
    1. Next meeting will be held on July 9th 2020 at 08:00 UTC (Jaymzz, 09:02:01)

Meeting ended at 09:03:01 UTC (full logs).

Action items

  1. (none)

People present (lines said)

  1. Jaymzz (63)
  2. Mister_Magister (49)
  3. ggabriel (18)
  4. piggz (18)
  5. remote__ (18)
  6. flypig (17)
  7. abranson (13)
  8. Jaymzz1 (11)
  9. louisdk (9)
  10. Sefriol (8)
  11. rinigus (6)
  12. Thaodan (5)
  13. dcaliste (3)
  14. sailbot_ (2)
  15. lbt (1)
  16. ViGe (1)

Generated by MeetBot 0.1.4.