Sailfish OS Should Be Merged With Tizen
 

In my view due to the overwhelming similarities between Tizen OS and Sailfish OS, the project should be merged together. Both oses are Meego derivatives and share a lot of underlying components and components not shared could be incorporated into Tizen. Jolla could still offer their own user experience. Both Tizen and Sailfish share similar project goals. Merging Sailfish with Tizen would help reduce fragmentation. Fragmentation is a problem with Linux based oses in general but it is especially a problem with embedded and mobile Linux oses. Finally merging efforts would reduce extra work and duplicated effort on the part of both parties.

Re: Sailfish OS Should Be Merged With Tizen
 

And Jolla would be dependent on the goodwill of Samsung then, who might just decide to drop Tizen, if a manager feels like it one day... ;)
It has happened so often already in the ancestry of MeeGo.

Re: Sailfish OS Should Be Merged With Tizen
 

Tizen is developed by the Linux Foundation, Intel, The Tizen Association, and Samsung. Samsung is only but one member and only has so much control over it.

Re: Sailfish OS Should Be Merged With Tizen
 

There are no such similarities that I can see.

Re: Sailfish OS Should Be Merged With Tizen
 

Competitors in the same market-segment rarely find cooperation possible in terms acceptable to both parties, except when Elopcalypse happens.

Re: Sailfish OS Should Be Merged With Tizen
 

Both are Linux, both are Meego derivatives, both have Wayland as a display manager, both use RPM as a package manager, and both project support a multitude of device form factors. The real differences is a few components like Qt or GTK, which while not officially part of tizen can be used with Tizen.

Re: Sailfish OS Should Be Merged With Tizen
 

Meego itself was the result of collaboration between Nokia and Intel, Android was the result of collaboration between Android Inc. (Now Google) and the Open Handset Alliance which consists of many manufacturers and LiMo (Linux Mobile) was the result of collaboration between manufacturers. Platforms generally become most successful when they have a lot of hardware available, so collaboration to a certain degree makes a lot of sense.

Re: Sailfish OS Should Be Merged With Tizen
 

Nope.

Check for instance:
https://github.com/kumadasu/tizen-hi...y.pdf?raw=true
Note the distance between SailfishOS and Tizen, due to the fact that Tizen actually has relatively little in common with MeeGo.

The Tizen history tree is also included in this presentation from SmartDevCon 2013 about Tizen architecture, from an Samsung R&D engineer:
http://2013.smartdevcon.eu/static/up...chitecture.pdf
Quoting from slide 6:
"Tizen != MeeGo

Tizen has got few bits from MeeGo
- Connman
- oFono
- BlueZ
- RPM
- staff"

Re: Sailfish OS Should Be Merged With Tizen
 

I would rather see a switch. Jolla gets Tizen and Samsung gets Sailfish. Now just think sailfish on Note :D They can give Sail the HW it deserves. Jolla are smaller and can easly launch a tizen device since they have no expectation and can release as Beta a few years.

Re: Sailfish OS Should Be Merged With Tizen
 

... and Qt is basically all that matters. (Well, almost.)
Fragmentation is a pain for developers, yes. But developers use Qt and friends on Sailfish. So they wouldn't gain a lot from a 'merge' that doesn't include Qt on the partner's side.

A co-operation with Ubuntu would be much more useful. I think there were even talks about it between the technical teams once, but I doubt they were successful in the end.

Re: Sailfish OS Should Be Merged With Tizen
 

If you want to compare them I would suggest to have a look at Tizen:Common and Mer ...

At least both projects cooperate to same upstream packages ...

Re: Sailfish OS Should Be Merged With Tizen
 

Samsung is also funding and developing EFL inside the Linux community and they've been doing that for years now. Plus, Tizen isn't even Samsung's baby, it's a Linux baby which Samsung contributes to (maybe a bit more than others, but still not their OS).

Re: Sailfish OS Should Be Merged With Tizen
 

At least from what I've seen, things never went really well. I think there was some toolkit-level (Silica <-> Ubuntu API) wishes for collaboration, but nothing happened there at all, due to lack of time from the Jolla side in my opinion - although I was not surprised to see that not pan out honestly, given the endings of similar past efforts for cross-platform API compatibility even with teams in the same company (Symbian <-> MeeGo) also having trouble.

I would have expected to have seen more collaboration on layers below the UI, libraries, daemons, and such, but Ubuntu seem to pretty consistently have decided to do things Their Own Way, and ignoring most of Jolla's (and formerly, Nokia's) open source work on contacts/calendaring, sync, telephony, and all sorts of other areas. And then there's the more public differences (like Mir instead of Wayland).

I won't publically speculate about why they do this, but honestly, all I can see it doing is harming, and continuing to harm them. Their choices - for whatever reason they are made - are affecting their ability to ship products. One day, maybe they'll realise that.

Re: Sailfish OS Should Be Merged With Tizen
 

In terms of cooperation between Tizen and Sailfish, I don't see it as something that is realistically possible without either a lot of pain or a lot of compromise on one end or another. MeeGo was a pretty good case study in that, if you were following the technical details (there was a lot of pain and politics in which components were to be used, and which were to be thrown to the side), and the end result was quite lacking in some areas, considering it was supposed to be post-1.0 in terms of version numbering.

I also don't see it as being something that necessarily really benefits either side. I mean, changing software and distro tooling, inducing communication overhead, differing QA/integration/etc structures, etc, etc - all for what? Sharing a bunch of software packaging? I don't see the benefit, frankly.

"Sailfish OS" to me has always been about integrating a bunch of open source software projects, writing a few new ones to fill the gaps, dropping a UI on top of it - and doing all necessary integration/QA/testing gruntwork to make a consumer product out of the disparate pieces. The 'real' software work is supposed to happen outside of the distro projects themselves (in Sailfish's terms, that's Mer, Qt, etc projects).