Thread: About Sailfish community
View Single Post
w00t's Avatar
w00t is offline w00t
2013-12-06 , 18:14
Posts: 1,055 | Thanked: 4,107 times | Joined on Oct 2009 @ Norway
#120
Originally Posted by shmerl View Post
w00t: Do you get the feeling that it's a preferred approach (segment out what to engage a community in, while keeping the rest behind the wall), or just a current status quo?
(these are my personal views, not everyone at Jolla will agree with me)

The very way open source works is through segmentation. Different projects with different ways of working & aims cooperating together at the fringes to make something bigger - be it a desktop or in our case a phone. I think that the model works pretty well.

Not perfectly, there are some aspects of things I dislike: like the traditional role of distributions being rather separate from the software they are distributing. I think our model (of the software being packaged & turned into a distribution by the people doing the majority of the top end software) makes a lot more sense. I suppose this shouldn't come as a surprise, given where I work.

So, to get back to answer: I think that segmentation makes sense. A core, middleware for a mobile device, and a UI/services on top.

Originally Posted by shmerl View Post
Since this really sounds more relevant to the Nemo community, not to the Sailfish one. I once asked in the past, may be there were some plans to merge Nemo and Sailfish into one open system, but that's not the case from what I've heard, and they are intended to be separate.
I don't think merging a UI and a lower end stack makes sense. That's something that harmed MeeGo quite a bit, and they were even working on trying multiple UX stacks. As a result of not having a clear seperation, you ended up with a massively unwieldy core as a result of everything being shoved into one location. Unclean architecture and increased maintenence & build burden.

Originally Posted by shmerl View Post
But what makes Sailfish - Sailifish and not Nemo is precisely what's closed (as of now). So in the context of the Sailfish community this looks somewhat strange. Does it mean that community should rather lean towards being Nemo community?
Depends where you want to work and what your goals are. Right now, if you want to work on mobile *UI*, your options are limited: Sailfish UI is not open, and Nemo's is. If you're happy contributing to anything underneath that last mile, then the field is a lot more open for collaboration and cross-pollination.
__________________
i'm a Qt expert and former Jolla sailor (forever sailing, in spirit).
if you like, read more about me.
if you find me entertaining, or useful, thank me. if you don't, then tell me why.
 

The Following 14 Users Say Thank You to w00t For This Useful Post: