Well, I hope someone comes along & actively maintains a Mir-based MeR
distro, just so the wider community has it "bets hedged" so-to-speak.
I fear though that this will never happen, or too little too late... :-(
On 13/03/13 5:23 PM, Carsten Munk wrote:
2013/3/12 Nathan <[email protected]>:
Anyone else on all this?
Surely MeR team has been seriously assessing it & not immediately dismissing
on ideological grounds?
(stuff around governance isn't even completely defined yet anyway)
The important thing to remember is that Mer isn't a one-size-fits-all.
Before Wayland+Qt5 was integrated, it was successfully maintained
outside the Core even if it affects core components. Mer's meant to be
modified by vendors to fit what they need to do. Busybox instead of
Coreutils, Qt5 instead of Qt4, Mir instead of Wayland.
Since there's been no contribution of Mir in any kind of working form,
it's hard to properly evaluate consequences of it being there.
That said, from what I recall, the license is GPLv3 and the general
rule is that build-time, GPLv3 is OK, it being needed for a sane
run-time experience of Mer itself is not.
Like with the coreutils discussions, if you want to do something
different, different license policies, you're free to do your own
build of Mer and take advantage of the 99% other components you're not
modifying. Mer's about sharing effort and load of maintaining a
complex set of interlinked components so you (as a vendor) can easily
take it and build products on top.
BR
Carsten Munk
On 12/03/13 3:51 AM, Hillel Lubman wrote:
I don't consider their move with Mir good, but if they attempt to make the
drivers sharable with Wayland and actually push Nvidia and others to produce
these drives - it will be a positive outcome.
Regards,
Hillel.
On 12/03/13 3:17 AM, Hillel Lubman wrote:
This looks like a positive development:
https://plus.google.com/116812394236590806058/posts/SwC1CheXX65
Hopefully we'll contribute back not just an awesome display server in
the
form of Mir and an awesome desktop environment in the form of Unity, but
also low-level improvements that can be used by Wayland compositors. I'm
particularly excited about our engagements with NVIDIA and AMD; although
it's early days, I'm hopeful we can get a solution for “but what about
proprietary drivers?” not just for Mir, but for everyone.
If that will be true, things can turn out good for Wayland as well.
Regards,
Hillel.
On Mon, Mar 11, 2013 at 12:30 PM, Nathan <[email protected]> wrote:
So no one else concerned about this? Where do you think the community can
go from here?
Can Sailfish Alliance (or someone else) really beat Canonical to the
punch w/a Wayland based smartphone (or similar form-factor) next yr?*
I have my worries/concerns/doubts....
*And with a Wayland implementation that's fully competitive with Mir?
On 8/03/13 8:22 AM, Nathan wrote:
Hey, I'd love to know what folks here think about this, got some thoughts
on the matter?
Phoronix has been covering it all heavily, a recent article by them:
http://www.phoronix.com/scan.php?page=news_item&px=MTMyMDk
On 6/03/13 4:34 AM, Jukka Eklund wrote:
Hi,
I think you might catch Mer folks better via Mer mailing list.
-Jukka
On Tue, Mar 5, 2013 at 7:43 PM, Nathan <[email protected]> wrote:
So no thoughts on this from MeR/Nemo/Sailfish folk? Would really love to
hear them...
On 5/03/13 4:52 AM, Nathan wrote:
This is pretty big: https://wiki.ubuntu.com/MirSpec
I thought Canonical were "basically" just using tweaked Cyanogenmod +
libhybris + a QML shell on top (boring/non-innovative).
But it appears they're moving more & more towards their own complete OS
stack (much more akin to Sailfish)...
I really hope they intend to work with Wayland/Weston, & perhaps even
merge (where practical) efforts longer-term into one truly F/OSS project.
But I have my doubts/concerns... If they do, MeR/Nemo/Sailfish could
stand to benefit a lot, & conversely so could Canonical.
Cheers,
Nath
_______________________________________________
SailfishOS.org Devel mailing list
