#mer-meeting: Sailfish OS, open source, collaboration – 13th June 2019
Meeting started by sledges at 08:00:02 UTC
(full logs).
Meeting summary
-
- Meeting information and agenda can be found
here:
https://lists.sailfishos.org/pipermail/devel/2019-June/008640.html
(sledges,
08:00:08)
- Brief introduction (5 min). Please prefix your name/handle with # info (sledges, 08:00:25)
- Simonas Leleiva - privateer for Jolla
(sledges,
08:00:32)
- David Greaves; mer guy and sailor (lbt,
08:00:49)
- Martin Kolman, community & modRana
development (M4rtinK,
08:01:54)
- David Llewellyn-Jones, sailor @ jolla
(flypig,
08:02:00)
- Ville Nummela - sailor @ jolla (ViGe,
08:02:08)
- Lewis Rockliffe, community (r0kk3rz,
08:02:52)
- Vincent Knecht, community (vknecht,
08:04:39)
- Wireguard (VPN) support directly in the Settings ( https://en.wikipedia.org/wiki/WireGuard ) (30min - asked by bionade24) (sledges, 08:06:06)
- https://en.wikipedia.org/wiki/WireGuard
(sledges,
08:06:42)
- "Which Userpace Implementation should we
use?" (sledges,
08:06:54)
- Apologies, we are not sure (sledges,
08:06:58)
- "Which compiler is the right for Rust or
Go?" (sledges,
08:07:03)
- Sorry, we cannot help here either (sledges,
08:07:03)
- "Could we use the QrCode feature in the
UI?" (sledges,
08:07:09)
- Currently the VPN plugins for the settings app
are implemented entirely in QML. They're essentially designed to
send a dictionary of configuration options to connman, via VpnModel
(see
https://git.merproject.org/mer-core/nemo-qml-plugin-systemsettings/blob/master/src/vpnmodel.h).
For an example, see the VPNC QML config UI elements in
/usr/share/sailfish-vpn/vpnc on your device. You can pull in
a (sledges,
08:07:13)
- ...plugin that implements what you need (i.e.
ZXing library) for scanning QrCodes by installing the shared
libraries in /usr/lib/qt5/qml/Sailfish/. This won't get past harbour
validation though. (sledges,
08:07:38)
- https://git.merproject.org/mer-core/nemo-qml-plugin-systemsettings/blob/master/src/vpnmodel.h
(sledges,
08:07:52)
- Unless we're misunderstanding your plan here,
to get all this to work seamlessly, you'll also need to create a
connman plugin for Wireguard. Here's the code for the existing
connman VPN plugins:
https://git.merproject.org/mer-core/connman/tree/master/connman/vpn/plugins
(sledges,
08:08:02)
- https://git.merproject.org/mer-core/connman/tree/master/connman/vpn/plugins
(sledges,
08:08:18)
- <r0kk3rz> the Go userspace would work i
think, rust maybe not (sledges,
08:13:39)
- Why using the kernel module is difficult:
https://together.jolla.com/question/182324/wish-wireguard/
(sledges,
08:17:05)
- https://together.jolla.com/question/182324/wish-wireguard/
(sledges,
08:17:13)
- Scratchbox2 vs glibc; or, limitations of hooking of public api's; dockerization as a solution (30 min - asked by tortoisedoc) (sledges, 08:17:56)
- What is the plan on the scratchbox2? Currently
it is part of the official SDK, but it appears it's limits are
starting to show (see for example problems with hooking "internal"
api's of glibc, which causes some libraries / api's / apps not to
work properly (spawn api, llvm amongst others); supporting those
will need carefully evaluation of the consequences as it might
require patching of glibc). (sledges,
08:20:37)
- Is docker considered a possible replacement? If
so, is there a timeframe for it to land in the SDK? (sledges,
08:20:46)
- This question needs a little more
clarification. sb2 is used to to bypass qemu emulation of certain
executables during non-native builds. Docker does not provide any
functionality comparable to sb2. sb2 works very well and we will
continue to use it in this role. (sledges,
08:21:03)
- Although it is mature, sb2 is a sophisticated
tool and does interact deeply with the system (including glibc) so a
degree of maintenance is required over time. This is by no means an
undue burden given the benefits of the tool. (sledges,
08:21:25)
- Docker is a (relatively new, complex and
constantly changing) container technology; this role is provided by
the cross-platform Virtualbox in the SDK. The community has provided
native linux solutions to contain the SDK (eg chroot) and these
offer benefits (lower overheads for parallel builds) but also
disadvantages (exposure to different kernel versions or host
security policies like selinux). (sledges,
08:21:40)
- General discussion (25min) (sledges, 08:36:43)
- action points review:
http://meetingwords.com/sailfishos-community-irc (sledges,
08:36:58)
- http://meetingwords.com/sailfishos-community-irc
(sledges,
08:37:01)
- evaluate possibility to mark apps as
experimental (sledges,
08:37:16)
- We have had some discussions about this
internally. We might implement something like this in the future,
but this is not considered a high priority as experimental apps can
always use open repos. Instead, we plan on maturizing some APIs,
which also means that it is possible for us to allow them in
harbour. (sledges,
08:37:23)
- evaluate possibility to allow systemd socket
activation. (sledges,
08:39:47)
- We are planning to create an API for this kind
of functionality, but it will take time. (sledges,
08:39:51)
- https://together.jolla.com/question/190204/pulse-audio-12x-for-sailfish-x/
(sledges,
08:57:29)
- next meeting time and date (sledges, 09:01:26)
- Next meeting will be held on 27th June 2019 at
08:00 UTC (sledges,
09:02:12)
Meeting ended at 09:02:54 UTC
(full logs).
Action items
- (none)
People present (lines said)
- sledges (65)
- lbt (25)
- r0kk3rz (22)
- M4rtinK (19)
- tortoisedoc (17)
- flypig (8)
- vknecht (7)
- ViGe (3)
- bionade24 (2)
- merbot (2)
- pketo (2)
Generated by MeetBot 0.1.4.