Ask / Submit

[Translation] Sailfish Device Manager

asked 2017-03-14 11:06:11 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2017-03-14 11:06:22 +0300

I just found the new string "Sailfish Device Manager" in the new translation round strings. How should "Sailfish Device Manager" be translated into other languages? Is it a proper name, so it should be taken as-is or should it be translated correctly like 'Sailfish Gerätemanager' in German?

I think, that @sledges can answer that easily :)

edit retag flag offensive close delete


I'm not used to the translation website, but very interested in the next release, are there some other interesting strings? :D

drummer12 ( 2017-03-14 17:08:12 +0300 )edit

1 Answer

Sort by » oldest newest most voted

answered 2017-03-14 12:30:27 +0300

sledges gravatar image

updated 2017-03-14 13:00:15 +0300

Hi @ejjoman,

"Sailfish Device Manager" is a part of the MDM framework, and the string should be treated like an app name (so the first letter of each word is capitalised, however it gets localised, just like "Kamera")

edit flag offensive delete publish link more



Out of curiosity; whats MDM for?

tortoisedoc ( 2017-03-14 17:22:15 +0300 )edit

mobile device manangement in corporate environments.

@sledges please tell me you are implementing MDM with separate users and separate environments. Separate clipboards, no interaction between userworld and corporate world. Also on Filesystem level etc. Don't make us suffer the inacceptable implementation of MDM affecting USER data. It's hard to set up SFOS with two environments I guess but it is necessary.

If MDM can force me to use an unlock code just to access user apps and functionality I'll go mad forever. Also remote wipe stuff belongs to the work environment part only. The moment my company gains access to remotewipe my device SFOS is a no go for me and by extension I hope everyone else too. We're here in 2017 after all ;-)

MoritzJT ( 2017-03-14 18:00:01 +0300 )edit

@MoritzJT Given their ongoing open source pledges, I expect the MDM functionality to be based on open source methods too. Systemd is already present, IIRC systemd-nspawn, to spawn containers, has been enabled in the kernel already.

So, I'll keep the option open that actually will be a nice feature :)

Fuzzillogic ( 2017-03-14 19:25:32 +0300 )edit

MDM is ability to access and setup a mobile device remotely. It's the Sailfish OS framework (enablers for MDM) that will be shipped only in devices of customers that require such capability, and those customers will be responsible for developing actual clients.

Vanilla Sailfish OS will be free from MDM, even though enablers (API) will still be there, however connecting and manipulating them requires elevated privileges, and also, those enablers are not exposed via TCP/IP.

A process with elevated privileges can naturally damage the device even in earlier SFOS versions (without MDM present), just like on a Linux desktop.

Moreover, if no MDM client is installed, MDM library would not exist on the system, and then even enablers would have no way of triggering themselves.

sledges ( 2017-03-14 20:11:48 +0300 )edit

Well I can live with that. Two devices it is for me ;-)

MoritzJT ( 2017-03-15 02:21:52 +0300 )edit
Login/Signup to Answer

Question tools



Asked: 2017-03-14 11:06:11 +0300

Seen: 1,091 times

Last updated: Mar 14 '17