![]() |
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
@wicket: You are free to discuss this problem with Mer developers on the mailing list or the IRC channel. I think there are good solutions for that - to make some metapackages with bundles - default with some packages restricted to GPLv2, and optional ones where those packages will be replaced with updated versions even if they are GPLv3. So if vendors care - they'll use GPLv2 bundles. And if not - they'll use unrestricted ones. And users will be able to simply replace default ones with optional if they need to.
|
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
Quote:
Quote:
If you get further feedback from the mail-lists, IRC channels, or elsewhere that offers a workaround/sol'n to your concerns, please do refine the answer in the doc, or share it here. |
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
Some very revealing stuff about Ubuntu for Mobile...
https://twitter.com/stroughtonsmith/...59604455600128 In that thread there's a link to a Phoronix article, it's worthwhile reading that & it's corresponding thread. Personally I'm quite disappointed they've gone this route, Ubuntu's moved further down my interest list. I still wish them well, but Sailfish's success is now even more crucial/important. |
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
Quote:
|
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
Sailfish won't prevent you from installing other packages (they don't support DRM and any such junk). The only potential concern can be incompatibilities between these bundles. But nobody will stop you from choosing.
|
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
Quote:
|
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
@wicket
I think we need to be careful about how we define sailfish in the context of jolla handsets and vendor handsets. Certainly it has been implied, if not stated categorically that Jolla intend to license Sailfish OS to device vendors, in which case, you could expect tivoisation for the whole stack with these builds. That does not imply or suggest that Jolla devices (non vendor specific devices) will not be open to support installation of other core components. I would assume that if this is the case, then it is up to the individual who is hacking on the device to fix anything that such mods might break in the rest of the stack, by installing new builds of Mer core components. just my .02c (relevent state or federal taxes may apply) |
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
We really need one of the mer/sailfish folk to pop in & clear some things up, sadly they're almost completely averse to having anything to do with TMO :-/
stskeeps was going to, but has now said he's too busy & trying to avoid paces like TMO, which can be a distraction (he's been sick, so lots of time was lost). |
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
They are simply unlike, What can I say. They should put Stskeeps in charge of everything!
|
Re: Sailfish(Jolla): Ideas/Qns & Concerns/Criticisms
Quote:
I would think (and hope) that Jolla would have something in store for when the SDK is released, be it a forum or some other channel for communication to ensure tight comms with the developer community who will work on application development. I would also think that we will get all the info we need, as we need it and on their terms. That's common sense and good business practice. As a small enterprise with everything to lose, they are playing their cards very close to their chest. On a brighter note, I'm very happy to see that they're working with Creoir as these guys have some of Nokia's greatest hardware, design and mechanical talent on board. Think, some of Nokia's most iconic design concepts and the team at Creoir were probably behind it....... in another life :) |
| All times are GMT. The time now is 03:11. |
vBulletin® Version 3.8.8