Re: Re: naming the next major release

2013-09-05 Thread Martin Gräßlin
On Thursday 05 September 2013 13:25:33 Thomas Pfeiffer wrote: > On 20.08.2013 07:06, Martin Graesslin wrote: > > I do want to promote KWin for the usage in LXDE/Razor as in the next > > version we will hardly have any build-time dependencies from frameworks > > higher than tier1. I'm concerned that

Re: naming the next major release

2013-09-05 Thread Thomas Pfeiffer
On 19.08.2013 21:56, Aaron J. Seigo wrote: Hi... after seeing the Nth time that we don’t know if the next release will be called Plasma Workspaces 2 or something else, i’d like to find consensus on this point so we can move forward in communication with confidence. the first point that we’ve al

Re: naming the next major release

2013-09-05 Thread Thomas Pfeiffer
On 20.08.2013 07:06, Martin Graesslin wrote: I do want to promote KWin for the usage in LXDE/Razor as in the next version we will hardly have any build-time dependencies from frameworks higher than tier1. I'm concerned that a generic name "Plasma" would work against that as it would be difficult

Re: Re: naming the next major release

2013-09-03 Thread Martin Gräßlin
On Friday 30 August 2013 19:44:40 Aaron J. Seigo wrote: > If we say that “KDE Plasma” makes “Plasma” too much “KDE”, then we are > creating a real problem for ourselves: nothing can use “KDE” in conjunction > with its project name since that too would suggest exclusivity. There's another thing into

Re: naming the next major release

2013-09-02 Thread Sebastian Kügler
On Friday, August 30, 2013 19:44:40 Aaron J. Seigo wrote: > If we say that “KDE Plasma” makes “Plasma” too much “KDE”, then we are > creating a real problem for ourselves +1. -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 __

Re: naming the next major release

2013-09-02 Thread Aaron J. Seigo
On Saturday, August 31, 2013 13:35:27 Marco Martin wrote: > The one thing that i would really love to get away with tough is replacng > the conception of "for" KDE (and therefore unusable everywhere else as > "KDE" was a different operating system altogether) with "by" KDE This is something some o

Re: naming the next major release

2013-08-31 Thread Marco Martin
On Friday 30 August 2013, Aaron J. Seigo wrote: > > Without KDE being a brand with value, we lose one of the larger reasons to > add your project to the KDE galaxy of products. > > We need to move “KDE” into the direction of being our “Toyota” or “Sony”. > Just because there is a Toyota Camry doe

Re: naming the next major release

2013-08-30 Thread Aaron J. Seigo
On Friday, August 23, 2013 11:50:20 Marco Martin wrote: > On Thursday 22 August 2013 23:20:11 Giorgos Tsiapaliokas wrote: > > KDE, for instance the most references in plasma active are > > "Plasma Active" and not "KDE Plasma Active", but PA doesn't have any > > distance from KDE. I believe that pro

Re: naming the next major release

2013-08-23 Thread Antonis Tsiapaliokas
Hello to all, > To me is the contrary,.. what is now plasma+kwin gets seenn by people as > "the" > KDE > > if becomes just "Plasma", then become "a" desktop by KDE, not "the" KDE > desktop, would be more a normal citizen, > making room for instance Razor+Lxde to become another desktop by KDE +1

Re: naming the next major release

2013-08-23 Thread Marco Martin
On Thursday 22 August 2013 23:20:11 Giorgos Tsiapaliokas wrote: > KDE, for instance the most references in plasma active are > "Plasma Active" and not "KDE Plasma Active", but PA doesn't have any > distance from KDE. I believe that projects take some distance > from "KDE" when they stop referring t

Re: naming the next major release

2013-08-22 Thread Aaron J. Seigo
On Wednesday, August 21, 2013 20:40:09 Valorie Zimmerman wrote: > audience, such as the KDE-Community list. KDE-devel, KDE-core-devel and > KDE-Promo are some of the other possibilities to at least ping about a such > an important conversation happening. Yes, I have a purposeful habit of doing exa

Re: naming the next major release

2013-08-22 Thread Giorgos Tsiapaliokas
On 22 August 2013 21:26, David Edmundson wrote: > One thing that wasn't clear to me on the original proposals and has just > been mentioned by Giorgos is the prefix "KDE". > > KDE is not just "the community" but also "an umbrella brand for the > technology created by the KDE community" [0]. > I h

Re: naming the next major release

2013-08-22 Thread David Edmundson
My thoughts below. - Dropping the term "workspace": Seems sensible to me. It even seems this was the original intention [0]. - Calling it version 2. This makes a lot of sense, having a software compilation of KDE Plasma 5.x and KDE Applications 5.y, where x and y are different would be very very

Re: naming the next major release

2013-08-22 Thread Djuro Drljaca
Hello, with the "chaotic" nature of (future) release cycles for individual components the "date version number" format (for example "2013.08") is probably a good idea :) If I am not mistaken it was actually you (Martin G.) who initially suggested that :) On Thu, Aug 22, 2013 at 7:50 PM, Martin

Re: naming the next major release

2013-08-22 Thread Martin Graesslin
On Wednesday 21 August 2013 20:38:05 Martin Graesslin wrote: > On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote: > > Other proposals, ideas, tweaks to the above most welcome, but let’s try to > > come to a consensus on this matter before the end of this month. > > another idea: let's drop th

Re: naming the next major release

2013-08-22 Thread Martin Graesslin
On Thursday 22 August 2013 20:36:24 Giorgos Tsiapaliokas wrote: > Hello, > > On 21 August 2013 12:49, Marco Martin wrote: > > My vote would go for Plasma. > > +1, just "Plasma" without "KDE". > > On 21 August 2013 21:38, Martin Graesslin wrote: > > another idea: let's drop the version number

Re: naming the next major release

2013-08-22 Thread Giorgos Tsiapaliokas
Hello, On 21 August 2013 12:49, Marco Martin wrote: > > My vote would go for Plasma. > +1, just "Plasma" without "KDE". On 21 August 2013 21:38, Martin Graesslin wrote: > > another idea: let's drop the version number completely and only use it > internally (bugtracker, libs, etc.) > I was t

Re: naming the next major release

2013-08-22 Thread Matthias Klumpp
2013/8/21 Martin Graesslin : > On Wednesday 21 August 2013 19:36:21 Daniel Nicoletti wrote: >> [...] >> Ok, then what am I doing wrong in calling my stuff KDE stuff? >> http://manifesto.kde.org/benefits.html lists what I do on my >> projects, I was arguing about Martin saying that I talk KDE as sof

Re: naming the next major release

2013-08-21 Thread Martin Graesslin
On Wednesday 21 August 2013 19:36:21 Daniel Nicoletti wrote: > 2013/8/21 Sebastian Kügler : > > On Wednesday, August 21, 2013 17:12:10 Daniel Nicoletti wrote: > >> 2013/8/21 Martin Graesslin : > >> > Yes I noticed that for example you still talk about KDE as software in > >> > your > >> > blog post

Re: naming the next major release

2013-08-21 Thread Valorie Zimmerman
Hi Plasma folks, This thread has been fascinating reading. I hope that after you reach a tentative conclusion, that you make a proposal to a list with a wider KDE audience, such as the KDE-Community list. KDE-devel, KDE-core-devel and KDE-Promo are some of the other possibilities to at least ping

Re: naming the next major release

2013-08-21 Thread Daniel Nicoletti
2013/8/21 Sebastian Kügler : > On Wednesday, August 21, 2013 17:12:10 Daniel Nicoletti wrote: >> 2013/8/21 Martin Graesslin : >> > Yes I noticed that for example you still talk about KDE as software in >> > your >> > blog posts. To be honest I have to cringe if I read it, because it makes >> > the

Re: naming the next major release

2013-08-21 Thread Marco Martin
On Wednesday 21 August 2013 14:39:36 Rick Stockton wrote: > > BTW, as a (mostly) end-User, I'm fine (and prefer) Plasma-2. But KDE > without "base" SC Releases will tend to fragment Distro content > selection, right? sorry, I have to be a bit tedious here :p isn't this material for a completely d

Re: naming the next major release

2013-08-21 Thread Rick Stockton
I wonder: If KDE will not define and Release an internally consistent 'SC' anymore, then how should packagers differentiate between "Minor Version" and "Point Release Updates" for their end users? I understand the use of an RPM or Deb name such as "Task-KDE-Plasma" used as a collection, defining

Re: naming the next major release

2013-08-21 Thread Sebastian Kügler
On Wednesday, August 21, 2013 17:12:10 Daniel Nicoletti wrote: > 2013/8/21 Martin Graesslin : > > Yes I noticed that for example you still talk about KDE as software in > > your > > blog posts. To be honest I have to cringe if I read it, because it makes > > the task of everyone more difficult who

Re: naming the next major release

2013-08-21 Thread Daniel Nicoletti
2013/8/21 Martin Graesslin : > Yes I noticed that for example you still talk about KDE as software in your > blog posts. To be honest I have to cringe if I read it, because it makes the > task of everyone more difficult who tries to work on the repositioning of the > brand. Well if I write an app u

Re: naming the next major release

2013-08-21 Thread Martin Graesslin
On Wednesday 21 August 2013 15:58:03 Daniel Nicoletti wrote: > 2013/8/21 Martin Graesslin : > > On Wednesday 21 August 2013 13:52:06 Daniel Nicoletti wrote: > >> 2013/8/21 Martin Graesslin : > >> > On Wednesday 21 August 2013 11:29:52 Daniel Nicoletti wrote: > >> > this might change. Consider Razor

Re: naming the next major release

2013-08-21 Thread Daniel Nicoletti
2013/8/21 Martin Graesslin : > On Wednesday 21 August 2013 13:52:06 Daniel Nicoletti wrote: >> 2013/8/21 Martin Graesslin : >> > On Wednesday 21 August 2013 11:29:52 Daniel Nicoletti wrote: >> > this might change. Consider Razor/LXDE joining the KDE umbrella. What >> > then? >> > From one day to an

Re: naming the next major release

2013-08-21 Thread Martin Graesslin
On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote: > Other proposals, ideas, tweaks to the above most welcome, but let’s try to > come to a consensus on this matter before the end of this month. another idea: let's drop the version number completely and only use it internally (bugtracker, lib

Re: naming the next major release

2013-08-21 Thread Martin Graesslin
On Wednesday 21 August 2013 13:52:06 Daniel Nicoletti wrote: > 2013/8/21 Martin Graesslin : > > On Wednesday 21 August 2013 11:29:52 Daniel Nicoletti wrote: > >> My 2c, > >> > >> On KDE 4 aka KDE SC 4, plasma was always just plasma, > >> no user says I'm using the plasma shell (as there isn't anot

Re: naming the next major release

2013-08-21 Thread Daniel Nicoletti
2013/8/21 Martin Graesslin : > On Wednesday 21 August 2013 11:29:52 Daniel Nicoletti wrote: >> My 2c, >> >> On KDE 4 aka KDE SC 4, plasma was always just plasma, >> no user says I'm using the plasma shell (as there isn't another >> KDE option). > this might change. Consider Razor/LXDE joining the K

Re: naming the next major release

2013-08-21 Thread Martin Graesslin
On Wednesday 21 August 2013 11:29:52 Daniel Nicoletti wrote: > My 2c, > > On KDE 4 aka KDE SC 4, plasma was always just plasma, > no user says I'm using the plasma shell (as there isn't another > KDE option). this might change. Consider Razor/LXDE joining the KDE umbrella. What then? >From one da

Re: naming the next major release

2013-08-21 Thread Daniel Nicoletti
2013/8/21 Marco Martin : > On Wednesday 21 August 2013, Daniel Nicoletti wrote: >> My 2c, >> >> On KDE 4 aka KDE SC 4, plasma was always just plasma, >> no user says I'm using the plasma shell (as there isn't another >> KDE option). > > Incidently, the whole SC stuff, was never intended for marketi

Re: naming the next major release

2013-08-21 Thread Marco Martin
On Wednesday 21 August 2013, Daniel Nicoletti wrote: > My 2c, > > On KDE 4 aka KDE SC 4, plasma was always just plasma, > no user says I'm using the plasma shell (as there isn't another > KDE option). Incidently, the whole SC stuff, was never intended for marketing and public communication, but

Re: naming the next major release

2013-08-21 Thread Daniel Nicoletti
My 2c, On KDE 4 aka KDE SC 4, plasma was always just plasma, no user says I'm using the plasma shell (as there isn't another KDE option). I think even if Plasma is numbered after 2, users will still say they have installed KDE 5 or KDE SC 5, the marketing imo must go to the whole SC 5 and not to

Re: naming the next major release

2013-08-21 Thread Marco Martin
On Monday 19 August 2013, Aaron J. Seigo wrote: > > Other proposals, ideas, tweaks to the above most welcome, but let’s try to > come to a consensus on this matter before the end of this month. > > then we can all move forward in confidence together, whatever it is we > decide. after thinking ab

Re: naming the next major release

2013-08-20 Thread Sebastian Kügler
On Monday, August 19, 2013 21:56:35 Aaron J. Seigo wrote: > given that we are moving to a “grand unified shell” approach where the > different user experiences flow seamlessly from one to the next, it may > make sense to drop the concept that there is such huge differentiation that > they are the “

Re: naming the next major release

2013-08-20 Thread Sebastian Kügler
On Monday, August 19, 2013 21:56:35 Aaron J. Seigo wrote: [ snipperdeesnip ] > “KDE’s Plasma workspaces come in Desktop, Netbook, Tablet and > Mediacenter > flavours...” > > “KDE’s Plasma provides user experiences for desktop, netbook, tablet, > ..” > > given that we are moving to a

Re: naming the next major release

2013-08-20 Thread Sebastian Kügler
On Tuesday, August 20, 2013 10:56:41 Marco Martin wrote: > On Tuesday 20 August 2013, Aaron J. Seigo wrote: > > > > That’s also what I see in the openSuse packages. > > > > So, yes, I got the # wrong .. it’s 3, not 5 currently .. so we’d end up > > with 4 unless we skip it go to 5. Still, the “numb

Re: naming the next major release

2013-08-20 Thread Marco Martin
On Tuesday 20 August 2013, Aaron J. Seigo wrote: > > That’s also what I see in the openSuse packages. > > So, yes, I got the # wrong .. it’s 3, not 5 currently .. so we’d end up > with 4 unless we skip it go to 5. Still, the “number used in the name > doesn’t match the version number of ” commen

Re: naming the next major release

2013-08-20 Thread Martin Graesslin
On Tuesday 20 August 2013 09:56:59 Aaron J. Seigo wrote: > one tempting idea is to promote “Plasma Active” up as the name used for all > the workspaces ... I would vote against "Plasma Active" as that might end up at the users (and media and they can get it wrong big times) as we drop the desktop

Re: naming the next major release

2013-08-20 Thread Aaron J. Seigo
On Tuesday, August 20, 2013 07:06:10 Martin Graesslin wrote: > On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote: > > 3. ‘2’ ... why “two” if this is version 5? well, libplasma is actually > > going to be version 6 iirc, so it isn’t the library. i also am not a big > > believer in b

Re: naming the next major release

2013-08-19 Thread Martin Graesslin
On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote: > 3. ‘2’ ... why “two” if this is version 5? well, libplasma is actually going > to be version 6 iirc, so it isn’t the library. i also am not a big believer > in branding after version numbers. neither are any of our proprietary > competitors

Re: naming the next major release

2013-08-19 Thread Aaron J. Seigo
On Monday, August 19, 2013 23:08:15 Marco Martin wrote: > On Monday 19 August 2013, Kevin Ottens wrote: > > On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote: > > > 3. ‘2’ ... why “two” if this is version 5? well, libplasma is actually > > > going to be version 6 iirc, so it isn’t the library.

Re: naming the next major release

2013-08-19 Thread Kevin Ottens
On Monday 19 August 2013 23:08:15 Marco Martin wrote: > On Monday 19 August 2013, Kevin Ottens wrote: > > On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote: > > > 3. ‘2’ ... why “two” if this is version 5? well, libplasma is actually > > > going to be version 6 iirc, so it isn’t the library. >

Re: naming the next major release

2013-08-19 Thread Marco Martin
On Monday 19 August 2013, Kevin Ottens wrote: > On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote: > > 3. ‘2’ ... why “two” if this is version 5? well, libplasma is actually > > going to be version 6 iirc, so it isn’t the library. > > Not that its relevant for the rest of the discussion, but

Re: naming the next major release

2013-08-19 Thread Kevin Ottens
On Monday 19 August 2013 21:56:35 Aaron J. Seigo wrote: > 3. ‘2’ ... why “two” if this is version 5? well, libplasma is actually going > to be version 6 iirc, so it isn’t the library. Not that its relevant for the rest of the discussion, but as the library number itself is concerned you can make