[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-active
Subject:    Re: List of problems with Plasma Active on Mer
From:       martin brook <martin.brook100 () googlemail ! com>
Date:       2012-05-31 10:23:30
Message-ID: CA+uP_P5V7gO+gKuBjjxCa-j9-GQViz-Hf86A9C9sEuC0xY8Kqw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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@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@kde.org
> https://mail.kde.org/mailman/listinfo/active
>

[Attachment #5 (text/html)]

Marco Hi,<div><br></div><div>Carsten has been working on some architecture pages on \
the wiki which may help here,</div><div><br></div><div><a \
href="http://wiki.merproject.org/wiki/Architecture">http://wiki.merproject.org/wiki/Architecture</a> \
</div> <div><br></div><div>BR</div><div><br></div><div>vgrade</div><div><br><br><div \
class="gmail_quote">On Thu, May 31, 2012 at 11:07 AM, Marco Martin <span \
dir="ltr">&lt;<a href="mailto:notmart@gmail.com" \
target="_blank">notmart@gmail.com</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div class="im">On Thursday 31 May 2012, Aaron J. Seigo \
wrote:<br> &gt; On Thursday, May 31, 2012 10:13:30 martin brook wrote:<br>
&gt; &gt; Just a reminder that Mer does not include hardware adaptations, so \
kernel<br> &gt; &gt; and graphics drivers are out of scope of that project.<br>
&gt; &gt;<br>
&gt; &gt; Nemo does aim to support an x86 adaptation.<br>
&gt;<br>
&gt; imho, this highlights a scoping error for mer. here&#39;s why:<br>
&gt;<br>
&gt; * mer doesn&#39;t do hardware adaptation.<br>
&gt; * projects on top of mer do<br>
&gt; * there are multiple projects on top of mer, all of which need adaptations<br>
&gt; * there is a finite number of common hardware targets<br>
&gt;<br>
&gt; this leads to multiple projects working on the same hardware adaptations<br>
&gt; without a good place to collaborate.<br>
<br>
</div>on top of that, add the fact that everybody is quite confused where mer \
stops<br> and nemo begins also tells something (i still didn&#39;t understood it \
100%)<br> <br>
if something becomes very difficult to communicate correctly, maybe there is<br>
some underlying problem in how things are structured...<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Marco Martin<br>
_______________________________________________<br>
Active mailing list<br>
<a href="mailto:Active@kde.org">Active@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/active" \
target="_blank">https://mail.kde.org/mailman/listinfo/active</a><br> \
</div></div></blockquote></div><br></div>



_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active


[prev in list] [next in list] [prev in thread] [next in thread]