View Single Post
Stskeeps's Avatar
Posts: 1,671 | Thanked: 11,478 times | Joined on Jun 2008 @ Warsaw, Poland
#1677
Originally Posted by shmerl View Post
Here Sailfish will be using Mer, but will pose as a metadistro. Since Mer is already a metadistro for vendors - that's confusing. Unless Sailfish is intended as a higher level metadistro, with additional components which Mer lacks, which it intends to standardize (not sure what those are). If those will be open - it'll be OK I guess. If they'll be closed but still posed as meta components - that's very much not OK.
Think:

* If you need to improve something on core level in Sailfish, you contribute to Mer and follow their processes
* If you need to improve something on handset middleware and toolkits layer in Sailfish, you contribute to Nemo and follow their processes, or if you want to work on one or more community UIs based on those.
* If you need to improve something on productized layer (codecs, translations, productized UI, as examples), you go into Sailfish specific stuff - that part is more hazy but intent is on community participation and you follow their processes there.

Does that make more sense?

The hope, at least from my side is that by keeping things separate like this, we achieve the most openness and innovation ability.

Last edited by Stskeeps; 2012-10-07 at 05:25.