naming the next major release

[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 system in 
favor of the tablet thingy. For many users Active is just the tablet shell.

I fear that this could end up being seen in exactly the opposite way as we 
want to achieve with the one device shell approach. If you want to get it 
wrong, you'll get it wrong and lately I have the feeling that the media is 
getting it wrong on purpose just to have more clicks.
> 
> the most minimalist thing would be to just call it all “Plasma” and be done
> with it and not try at all to differentiate the new release from the old by
> the product name.
> 
> another approach would be to shift weight to “Active” and drop “Plasma” from
> the name, though “KDE Active” is  not as google-able and we lose whatever
> value we’ve put into Plasma as a brand.
I agree that we should somehow keep Plasma in it.
> 
> *sigh* this needs more thought :/
> 
> > 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 to communicate that although being
> > part of Plasma not being part of Plasma.
> 
> i suppose it comes down to the following two things:
> 
> * do we feel we can communicate clearly, developer to developer, what Plasma
> is, and how components like KWin fit within that
> * do we expect LXDE / Razor developers to be intelligent people who will
> understand technical communication
> 
> my experience with both of those things is “yes”
I'm also not concerned with devs. I'm quite sure that this will be not of an 
issue. I'm more concerned about the users as they will have to choose OpenBox 
or KWin. If they think that with KWin they get the full "bloat" of Plasma on a 
lightweight desktop they will not use it out of principle. We already see that 
LXDE has to fight against the bloat perspective since they started using Qt - 
which is a pity.

Cheers
Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20130820/22747868/attachment.sig>