On Friday 08 June 2012, Dario Freddi wrote:
> > there will be enough on the agenda without adding marketing to it, and
> > there are many people not there who ought to be if marketing was part of
> > the mix.
>
> I partly disagree here. In the first frameworks sprint we also created
> a plan whic
On Friday 08 June 2012, Aleix Pol wrote:
> >
> > same thing for names of tecnologies (there should be advertized as
> > developer tools but never to the end user) so in the ui should never
> > ever appear nepomuk, phonon or akonadi for instance.
> >
> > different discourse for products that are d
On Fri, Jun 8, 2012 at 4:23 PM, Marco Martin wrote:
> On Friday 08 June 2012, Tomaz Canabrava wrote:
>> 'Plasma' and 'Nepomuk - whatever this means' ? those namings are
>> confusing, and if you guys really want a broader audience, you should
>> really make it easy for people that are not on your f
2012/6/7 Aaron J. Seigo :
>> but it occurred to
>> me we have indeed a serious naming problem (which I believe was the
>> main source of misunderstanding over the last days) on all of this. In
>> my opinion the diagram makes more sense when s/Workspace/Desktop. I
>> see more the concept of "workspa
2012/6/8 Aurélien Gâteau :
>> > Perhaps the "KDE Workspace" box should be named " KDE SC Plasma
>> > Workspaces".
>> how is this difference useful? (serious question, not rhetorical.)
>
> I suggested "SC" to avoid people thinking I consider Active not to be a KDE
> Workspace. It is a KDE workspace
On Friday 08 June 2012, Tomaz Canabrava wrote:
> 'Plasma' and 'Nepomuk - whatever this means' ? those namings are
> confusing, and if you guys really want a broader audience, you should
> really make it easy for people that are not on your field to use your
> software. I understand that technologie
Le vendredi 8 juin 2012 05:49:00 Tomaz Canabrava a écrit :
> On Fri, Jun 8, 2012 at 5:37 AM, Aurélien Gâteau wrote:
> > Perhaps the "KDE Workspace" box should be named " KDE SC Plasma
> > Workspaces".
> As one of the most active Talkers about KDE on universities that are
> not on the IT field, I s
Le vendredi 8 juin 2012 15:11:57 Aaron J. Seigo a écrit :
> On Friday, June 8, 2012 14:37:09 Aurélien Gâteau wrote:
> > just means it is released using a different schedule
>
> in what way does the release schedule matter? what does it change that is
> important to understand when asking "what is
Le vendredi 8 juin 2012 15:07:17 Aaron J. Seigo a écrit :
> ok.. let's try to define that then. i'll offer what i see as a product, as
> then perhaps you can do the same and we can compare and hopefully
> understand each other better.
>
> Product: a finished whole that is presented in a form that
On Friday, June 08, 2012 12:35:46 Martin Klapetek wrote:
> On Fri, Jun 8, 2012 at 12:01 PM, Sebastian Kügler wrote:
> > Food for thought: How many Linux kernel developers do you know that try to
> > divide the Linux kernel in subprojects for servers, desktops, embedded
> > systems? Here, just like
On Friday, June 08, 2012 14:37:09 Aurélien Gâteau wrote:
> Perhaps the "KDE Workspace" box should be named " KDE SC Plasma Workspaces".
Read this: http://community.kde.org/Promo/Branding/Map#KDE_Workspaces
in short: ("KDE Workspaces", in principle can include other workspaces,
"Plasma Workspaces
On Friday, June 8, 2012 14:37:09 Aurélien Gâteau wrote:
> just means it is released using a different schedule
in what way does the release schedule matter? what does it change that is
important to understand when asking "what is plasma, how is put together and
how can we move it forward"?
> Perh
On Friday, June 8, 2012 14:31:14 Aurélien Gâteau wrote:
> Le vendredi 8 juin 2012 14:22:37 Aaron J. Seigo a écrit :
> > another fun tidbit: did you know that the search & launch (aka SAL)
> > containment was designed for Netbook, but is also used for the Plasma
> > KPart
> > now and is very popular
On Friday 08 June 2012 14:39:37 Aaron J. Seigo wrote:
> ~15kLOC current delta, 10K LOC of "real" delta once workspace and kdelibs
> branches get merged, and 250k LOC total (well, closer to 300K depending on
> what you count; but i'm being a little conservative in what i included
> there)
>
> the 25
On Fri, Jun 8, 2012 at 5:37 AM, Aurélien Gâteau wrote:
> [Damn. Just when I say I am out of this discussion, a message arrives I feel
> the urge to answer.]
>
> Le vendredi 8 juin 2012 14:31:08 Aaron J. Seigo a écrit :
>> it would be like saying that Calligra, Amarok and Digikam are somehow of a
>
On Friday 08 June 2012 14:22:37 Aaron J. Seigo wrote:
> On Friday, June 8, 2012 13:47:18 Aurélien Gâteau wrote:
> > My goal with this diagram was to illustrate end-user products and how they
> > are grouped under umbrella terms, rather than teams.
>
> then it isn't an architecture diagram, and it s
On Friday, June 8, 2012 14:30:18 Kevin Ottens wrote:
> On Friday 08 June 2012 14:09:36 Aaron J. Seigo wrote:
> > the design of Plasma lets us take the overwhelming majority of code and
> > re-use it across workspace shells. that's the entire point. i've
> > calculated
> > that the current delta bet
[Damn. Just when I say I am out of this discussion, a message arrives I feel
the urge to answer.]
Le vendredi 8 juin 2012 14:31:08 Aaron J. Seigo a écrit :
> it would be like saying that Calligra, Amarok and Digikam are somehow of a
> different class compared to KMail because KMail is in the SC.
Le vendredi 8 juin 2012 14:22:37 Aaron J. Seigo a écrit :
> On Friday, June 8, 2012 13:47:18 Aurélien Gâteau wrote:
> > My goal with this diagram was to illustrate end-user products and how they
> > are grouped under umbrella terms, rather than teams.
>
> then it isn't an architecture diagram, and
esign.
>
> As I answered to Sebas, I was not aiming at charting technical design, but
ah, then i was confused by the title "KDE Architecture Diagram" and the
inclusion of things like kdelibs.
> rather at identifying products and how they are grouped.
why is this important?
On Friday 08 June 2012 14:09:36 Aaron J. Seigo wrote:
> the design of Plasma lets us take the overwhelming majority of code and
> re-use it across workspace shells. that's the entire point. i've calculated
> that the current delta between Active and Desktop is ~15000 LOC, and that
> once we merge s
On Friday, June 8, 2012 13:47:18 Aurélien Gâteau wrote:
> My goal with this diagram was to illustrate end-user products and how they
> are grouped under umbrella terms, rather than teams.
then it isn't an architecture diagram, and it shouldn't include things like
kdelibs.
how products are present
On Friday, June 8, 2012 12:35:46 Martin Klapetek wrote:
> While I share your idea of Plasma Workspaces, I would imagine that
> different parts of the kernel are maintained/developed by different people.
and they don't whinge at each about it ;)
> Sure, the core is the same, but the platform-speci
Le vendredi 8 juin 2012 12:20:43 Aaron J. Seigo a écrit :
> > If I am not mistaken, kde workspace and plasma active are developed in
> > different repositories,
>
> kde-runtime is also developed in a different repository. so is folderview,
> which is definitely part of KDE Workspaces; it's also in
Le vendredi 8 juin 2012 12:01:39 Sebastian Kügler a écrit :
> On Thursday, June 07, 2012 22:16:13 Aurélien Gâteau wrote:
> > Le jeudi 7 juin 2012 21:11:09 Aaron J. Seigo a écrit :
> > > there's an artificial spliting between "kde workspace" and "plasma
> > > active"
> > > that does not exist. those
Am Freitag 08 Juni 2012, 12.35:46 schrieb Martin Klapetek:
Morning
> On Fri, Jun 8, 2012 at 12:01 PM, Sebastian Kügler wrote:
> > Food for thought: How many Linux kernel developers do you know that try
> > to divide the Linux kernel in subprojects for servers, desktops,
> > embedded systems? Her
On Fri, Jun 8, 2012 at 12:01 PM, Sebastian Kügler wrote:
>
> Food for thought: How many Linux kernel developers do you know that try to
> divide the Linux kernel in subprojects for servers, desktops, embedded
> systems? Here, just like in Plasma, there are a few codepathes that differ
> per
> dev
On Friday, June 8, 2012 12:01:39 Sebastian Kügler wrote:
> Food for thought: How many Linux kernel developers do you know that try to
> divide the Linux kernel in subprojects for servers, desktops, embedded
> systems?
thanks for bringing up this example Sebastian :) it's one that we've used for
ye
On Thursday, June 7, 2012 22:16:13 Aurélien Gâteau wrote:
> Le jeudi 7 juin 2012 21:11:09 Aaron J. Seigo a écrit :
> > there's an artificial spliting between "kde workspace" and "plasma active"
> > that does not exist. those of us working on these things keep saying that
> > but nobody seems to eit
On Thursday, June 07, 2012 22:16:13 Aurélien Gâteau wrote:
> Le jeudi 7 juin 2012 21:11:09 Aaron J. Seigo a écrit :
> > there's an artificial spliting between "kde workspace" and "plasma active"
> > that does not exist. those of us working on these things keep saying that
> > but nobody seems to ei
Le jeudi 7 juin 2012 21:11:09 Aaron J. Seigo a écrit :
> there's an artificial spliting between "kde workspace" and "plasma active"
> that does not exist. those of us working on these things keep saying that
> but nobody seems to either be listening to or believing us :)
If I am not mistaken, kde
On Thursday 07 June 2012 21:11:09 Aaron J. Seigo wrote:
> there's an artificial spliting between "kde workspace" and "plasma active"
> that does not exist. those of us working on these things keep saying that
> but nobody seems to either be listening to or believing us :)
and I think here we have f
On Thursday, June 7, 2012 09:31:08 Aurélien Gâteau wrote:
> Spent some time yesterday evening on drawing a diagram of KDE architecture,
> as I proposed in an other thread. Please have a look and tell me what's
> wrong in it.
thanks for taking the time to do this.
it certainly helps me understand
On Thursday, June 7, 2012 13:47:06 Dario Freddi wrote:
> Well it looks quite close to the status quo imho,
i think it reflects the understanding many have, yes.
> but it occurred to
> me we have indeed a serious naming problem (which I believe was the
> main source of misunderstanding over the la
Hey, first of all thanks for caring :)
Well it looks quite close to the status quo imho, but it occurred to
me we have indeed a serious naming problem (which I believe was the
main source of misunderstanding over the last days) on all of this. In
my opinion the diagram makes more sense when s/Work
35 matches
Mail list logo
