#mer-meeting: Sailfish OS, Open Source, Collaboration 1st of July 2016

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

Meeting summary

    1. meeting information and agenda can be found here: https://lists.sailfishos.org/pipermail/devel/2016-June/007150.html (Jaymzz, 09:01:01)

  2. Brief introduction (5 minutes) . Please prefix your name/handle with # info (Jaymzz, 09:01:20)
    1. James Noori, Community Manager, at your service (Jaymzz, 09:01:31)
    2. Joona Petrell, UI Chief Engineer (jpetrell, 09:01:48)
    3. Martin Kolman, community member & modRana developer (M4rtinK_phone_, 09:02:12)
    4. Lewis Rockliffe, community developer (r0kk3rz, 09:02:19)
    5. Martin Ebnöther, community member (Venty, 09:02:40)
    6. Simonas Leleiva, jolla pootle & hw (sledges, 09:02:41)
    7. Christophe Chapuis, community member (Tofe, 09:02:53)
    8. Damien Caliste, community, developping sometime (dcaliste, 09:03:06)
    9. correct link : meeting information and agenda can be found here: https://lists.sailfishos.org/pipermail/devel/2016-June/007223.html (Jaymzz, 09:04:36)

  3. UI interaction slowness (10 minutes, asked by: ApB) (Jaymzz, 09:07:13)
    1. : The introduction of SF2.0 brought a new -and in many cases improved- UI but also made some actions significantly slower than what it was with SF1.0 (ie locking the phone by gestures requires two motions instead of one). So are there any plans to address issues related to the above. (Jaymzz, 09:07:23)
    2. jpetrell: we did a lot of user studies with sailfish 2.0, built dozen prototypes, while there are many useful power user gestures they often consume other users (Jaymzz, 09:10:28)
    3. gerture customisation adds combinations that we have to test, e.g. if you request that old implementation should still be optional it means we have to maintain two features: the old and the new (Jaymzz, 09:14:13)
    4. "Options are often easy to add but the more there are and the more obscure and unlikely to be actively used by developers they are the more likely they are to break and stay that way unnoticed. Complexity increases exponentially with options, after all a simple binary option can double the number of scenarios that can play out for an interaction. " (Jaymzz, 09:17:28)

  4. Requesting things to be added to mer-tools repo (5 minutes, asked by: toxip) (Jaymzz, 09:19:21)
    1. : Noticed that some basic tools like wget are not included in the mer-tools repo. How could we request things to be added to the repository? (Jaymzz, 09:19:29)
    2. related to previous topic: please give feedback, when we hear from multiple fronts about an UX issue we do try to address it, but we cannot make a toolbox UI for all (Jaymzz, 09:20:00)

  5. Requesting things to be added to mer-tools repo (5 minutes, asked by: toxip) (Jaymzz, 09:21:38)
    1. : Noticed that some basic tools like wget are not included in the mer-tools repo. How could we request things to be added to the repository? (Jaymzz, 09:21:51)
    2. < lbt> mer-tools is open for new tools (and updates to existing tools) (Jaymzz, 09:23:01)
    3. tools are not in official releases so GPLv3 is fine (Jaymzz, 09:24:46)

  6. Qt future (10 minutes, asked by: nh1402) (Jaymzz, 09:26:45)
    1. from QT 5.7 onwards it is no longer licensed under LGPL 2.1 does that affect us? (Jaymzz, 09:26:53)
    2. Qt 5.6 is long term release so the license change is not acute problem (Jaymzz, 09:28:19)
    3. more and more open source world is moving to LGPLv3 so we need to revisit our license policy (Jaymzz, 09:29:03)
    4. we are working on upgrading to Qt 5.6 (Jaymzz, 09:30:23)

  7. Update outdated packages (10 minutes, asked by OhDaeto) (Jaymzz, 09:35:32)
    1. Sailfish OS (Nemo) contains a lot of outdated and officialy unsupported packages in repos. For example, there is Perl package version 5.16.1 while Cent OS 7 / RHEL supports 5.16.3. So I would like to know how the community can help you to update your packages and projects to latest actual versions, and which parts you think are the most weakest. Thanks in advance and sorry for my poor English. Hope you understood what I want to ask (Jaymzz, 09:35:39)
    2. create pull requests in mer-core for the packages, test on your jolla 1/c/tablet, fix bugs in related mw (Jaymzz, 09:37:18)

  8. General discussion (15 minutes) (Jaymzz, 09:43:30)
  9. Next meeting's date and time (Jaymzz, 09:53:52)
    1. Next meeting will be held on Friday August 5th 2016 at 09:00 UTC (Jaymzz, 10:01:47)


Meeting ended at 10:03:35 UTC (full logs).

Action items

  1. (none)


People present (lines said)

  1. Jaymzz (72)
  2. jpetrell (46)
  3. ApBBB (21)
  4. r0kk3rz (19)
  5. sledges (19)
  6. M4rtinK_phone_ (14)
  7. nh1402_work (9)
  8. urjaman (5)
  9. lbt (3)
  10. Tofe (3)
  11. eekkelund (3)
  12. andrewalker (2)
  13. merbot (2)
  14. Venty (2)
  15. kimmoli (2)
  16. LarstiQ (2)
  17. Yaniel (1)
  18. ballock_ (1)
  19. dcaliste (1)
  20. tathhu (1)


Generated by MeetBot 0.1.4.