List of problems with Plasma Active on Mer

[martin brook]

Marco Hi,

Carsten has been working on some architecture pages on the wiki which may
help here,

http://wiki.merproject.org/wiki/Architecture

BR

vgrade


On Thu, May 31, 2012 at 11:07 AM, Marco Martin <notmart at gmail.com> wrote:

> On Thursday 31 May 2012, Aaron J. Seigo wrote:
> > On Thursday, May 31, 2012 10:13:30 martin brook wrote:
> > > Just a reminder that Mer does not include hardware adaptations, so
> kernel
> > > and graphics drivers are out of scope of that project.
> > >
> > > Nemo does aim to support an x86 adaptation.
> >
> > imho, this highlights a scoping error for mer. here's why:
> >
> > * mer doesn't do hardware adaptation.
> > * projects on top of mer do
> > * there are multiple projects on top of mer, all of which need
> adaptations
> > * there is a finite number of common hardware targets
> >
> > this leads to multiple projects working on the same hardware adaptations
> > without a good place to collaborate.
>
> on top of that, add the fact that everybody is quite confused where mer
> stops
> and nemo begins also tells something (i still didn't understood it 100%)
>
> if something becomes very difficult to communicate correctly, maybe there
> is
> some underlying problem in how things are structured...
>
> --
> Marco Martin
> _______________________________________________
> Active mailing list
> Active at kde.org
> https://mail.kde.org/mailman/listinfo/active
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/active/attachments/20120531/476d0bf6/attachment.html>