#mer-meeting: Sailfish OS, open source, collaboration – 10th January 2019

Meeting summary

1. 1. Meeting information and agenda can be found here: https://lists.sailfishos.org/pipermail/devel/2019-January/008531.html (Jaymzz, 09:00:15)
   
   
2. Brief introduction (5 min). Please prefix your name/handle with # info (Jaymzz, 09:00:38)
   1. James Noori - sailor @ Jolla (Jaymzz, 09:00:47)
   2. Leszek Lesner - Community member + Dev (leszek, 09:01:05)
   3. Dylan Van Assche - Community & app developer (DylanVanAssche, 09:02:02)
   4. David Greaves - sailor and Mer guy (lbt, 09:02:09)
   5. Martin Kolman - community & modRana development (M4rtinK_phone_, 09:02:27)
   6. Simonas Leleiva - privateer @ Jolla (sledges, 09:02:28)
   7. David Llewellyn-Jones - sailor @ Jolla (flypig_, 09:02:34)
   8. Andrew Branson - Jolla sailor (abranson, 09:02:58)
   9. Lewis Rockliffe - community hacker (r0kk3rz, 09:03:07)
   10. Richard Booth - community (richrboo, 09:03:15)
   11. Simon Brown - community (zotan, 09:05:33)
   
   
3. Harbour and it's place in the strategy of jolla (w/r to individual markets) (20 min – asked by tortiosedoc ) (Jaymzz, 09:05:39)
   1. Harbour has been since the start the only place where applications are officially distributed and, most importantly, (to a certain extent) validated. We have seen a constant rise on the openrepos, not only in terms of users, but also in terms of functionalities (download stats, origin tracking etc) but this has not been the case for harbour. How does harbour fit into the "big localized ecosystems" picture? How does it currentl (Jaymzz, 09:06:13)
   2. this topic is from the last meeting where we had to postpone it to this one, and here comes the answers: (Jaymzz, 09:06:48)
   3. Jolla Store is operational in Jolla and licensee devices in almost all countries. (Jaymzz, 09:07:05)
   4. Country ecosystem licensees have an option to include Jolla Store and Jolla distributed SW updates on their devices, or they can replace these with their own independent implementations. However, target is to keep ecosystem compatibility (so that there is only Single Sailfish API) (Jaymzz, 09:07:16)
   5. We are looking into most efficient ways of improving the developer offering and have expanded the team, but we are still very short on resources and therefore need to carefully balance needs. So far the focus has been on developing the SDK and providing more APIs with Sailfish 3 releases, but we do acknowledge that Store and its functionality is important for developers and users. (Jaymzz, 09:07:28)
   6. Sailor @ private (Robbster, 09:09:32)
   7. Damien Caliste, so late... (dcaliste, 09:16:49)
   
   
4. how can the community help to improve the state of QtWayland in Mer? (20 min – asked by dcaliste ) (Jaymzz, 09:24:18)
   1. Currently QtWayland:master is ancient and there are a lot of branches with piles of commits, current one seems to be mer-5.4. I guess the rebase on Qt5.9 is in mer-5.9. Would it make sense to use a submodule pointing to upstream (with a checkout at 5.6.3 currently), with the additional commits as git-patches, as it is done for messagingframework ? Then, all additional commits can be reviewed to be upstreamed if it make sense a (Jaymzz, 09:24:29)
   2. The current QtWayland is based on Qt 5.4 because the QtWayland API was rewritten in a non-backwards compatible fashion after 5.4 and the homescreen and other software needed significant adaptation. That has mostly been done for Qt 5.9 and because most changes were upstreamed the delta to the upstream 5.9 is small. (Jaymzz, 09:25:21)
   3. The best way to manage patches on top of an upstream branch is contentious and many methods have been tried with mer projects. A different model would have to be adopted universally across all the mer Qt forks at least and require the support of the people maintainting them. (Jaymzz, 09:25:27)
   4. https://git.merproject.org/mer-core/qtwayland (Jaymzz, 09:32:00)
   5. compile https://git.merproject.org/mer-core/wayland/merge_requests/1 and https://git.merproject.org/mer-core/libsdl/merge_requests/2 and figure out the crash in sdl. (dcaliste, 09:49:36)
   
   
5. general discussion (15 min) (Jaymzz, 09:54:24)
   1. REMINDER: new rules for these meetings for increased efficiency is that the deadline for topic announcements is 3 days before the meeting so that we can have time to discuss them internally. Any topic announced after that will be postponed to the next meeting. (Jaymzz, 09:54:39)
   
   
6. next meeting time and date (Jaymzz, 10:10:43)
   1. Next meeting will be held on Jan 24th 2019 at 09:00 UTC (Jaymzz, 10:11:58)

Action items

1. (none)

People present (lines said)

1. Jaymzz (57)
2. M4rtinK_phone_ (26)
3. dcaliste (24)
4. r0kk3rz (22)
5. sledges (17)
6. leszek (9)
7. DylanVanAssche (7)
8. mal (7)
9. chriadam (5)
10. tortoisedoc (5)
11. lbt (3)
12. zotan (2)
13. richrboo (2)
14. merbot (2)
15. pketo (2)
16. HeinrichJolla (2)
17. abranson (1)
18. Robbster (1)
19. flypig_ (1)