Re: naming the next major release
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 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 using Qt people call it a Qt app, when you use KDE > >> FW it becomes a KDE app. So what should I call the software I write when > >> using KDE FW? > > > > Just to chime in here, this is clearly wrong. A KDE App (or project, if > > you > > will) is not defined by its technical dependencies, but by the people who > > write it, see manifesto.kde.org. > > 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 software > but KDE projects are mostly software no? This is too controversial, > I know the idea is the we KDE are a community, but it's a community > that have projects and software hence why am wrong in saying > KDE software? It's software made by KDE people. Look for example at your rant about switches. It's always saying "KDE 4.11", which is just wrong. That's what I meant. Just by scrolling down your blog I see two posts with "KDE 4.11" in the title. This is working against the rebranding. How are we supposed to have the media get it right, if even the developers continue to use the old wording. Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 about a such an important conversation happening. It's really true that names matter, and thus that branding matters. Thanks so much for starting the discussion. Valorie On Mon, Aug 19, 2013 at 12:56 PM, 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 all been around a million times, but i will > cover > again for completeness: > > Do we need a single name for all the bits that go into our desktop > shell? > > yes, we do. > :: giant snip:: > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 task of everyone more difficult who tries to work on the >> > repositioning of the brand. >> >> Well if I write an app using Qt people call it a Qt app, when you use KDE FW >> it becomes a KDE app. So what should I call the software I write when using >> KDE FW? > > Just to chime in here, this is clearly wrong. A KDE App (or project, if you > will) is not defined by its technical dependencies, but by the people who > write it, see manifesto.kde.org. 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 software but KDE projects are mostly software no? This is too controversial, I know the idea is the we KDE are a community, but it's a community that have projects and software hence why am wrong in saying KDE software? It's software made by KDE people. > Daniel, I think you've gone a few years back in time, stuck your fingers > firmly into your ears as to the reasoning of the whole rebranding, and are now > trying to turn back the clocks for no good reason. I never intended to question the rebranding thing, I really don't care about it, KDE has always been a community just like Gnome and Linux are, making sure KDE isn't more just a desktop isn't the point I'm making. What I'm saying is that people still install distros choosing the "KDE desktop", and not the Plasma desktop, and this is one of the reasons why I believe Plasma 2, is the right name, this way people can know what plasma shell is and use this. In short don't you think the whole new 5 cycle needs more coordinating between all parts, will it be an SC, will there be an official shell of course if this is really going to happen? As you said the rebranding happened years ago but somehow I'm only seeing it affect software (as in releases) now. > Would you mind giving the rebranding another try to actually understand it, > and not work against what has been years of work, and not an easy, but very > much necessary endeavour? Then we could actually move forward, instead of one > step ahead, two steps back. Just forget I mentioned KDE and SC, just take my +1 on Plasma 2, this is becoming an endless and unnecessary discussion, already regret for giving my 2c please give them back :P ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 different discussion? a bit OT.. how to call the desktop doesn't really affect the release cycle Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 multiple packages as a combined unit -- but if we off-load the definition of such packages to the Distros, I'm afraid that we might see a huge increase in Distro-specific Bugs - and they'd be bugs which we can't reproduce, because we've (possibly) made the definition of KDE contents too flexible, and don't have all of those configurations available to run ourselves. IMO, it would be a Very-Bad-Thing(tm) if our first response to many bugs becomes a request to "clean up their package selection, and see if the probelm is still reproducible". A number of such requests to "elinimate weirdness", from bug triage persons, would basically be like the definition of an SC anyway. (But after the fact, and all of the misdirected packaging work, and aggravation of end Users). If we consider it a Good-Thing(tm) to avoid defining co-requisite KDE libraries at Release Time, does our own Release process (and that of all our "K" Softwares) have the time and facilities to test a large number of possible combinations? Or, is my worry resolved by already-in-progress refactoring? 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? On 08/21/2013 12:35 PM, Martin Graesslin wrote: <> 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/LXDE joining the KDE umbrella. What then? From one day to another it would be obvious that using "the KDE desktop" is not working any more. << big snip of stuff not relevant to my questions >> Who said there will be a software compilation in the KF 5 world or that the Plasma Workspaces will be part of such a maybe existing software compilation? Please note that this has not yet been discussed, but I know that a few people in the Plasma team (me included) would favor to not have the SC anymore. The reasons you mention are a part of it. In fact the whole discussion highlights it. We would not need to think about a version number if Plasma would be part of the software compilation. Cheers Martin -- GPG fingerprint: 597E 4CE5 6D56 A7C2 DA3A 26FF F21F F828 0C86 165A ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 tries to work on the > > repositioning of the brand. > > Well if I write an app using Qt people call it a Qt app, when you use KDE FW > it becomes a KDE app. So what should I call the software I write when using > KDE FW? Just to chime in here, this is clearly wrong. A KDE App (or project, if you will) is not defined by its technical dependencies, but by the people who write it, see manifesto.kde.org. Daniel, I think you've gone a few years back in time, stuck your fingers firmly into your ears as to the reasoning of the whole rebranding, and are now trying to turn back the clocks for no good reason. Would you mind giving the rebranding another try to actually understand it, and not work against what has been years of work, and not an easy, but very much necessary endeavour? Then we could actually move forward, instead of one step ahead, two steps back. Thanks, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 using Qt people call it a Qt app, when you use KDE FW it becomes a KDE app. So what should I call the software I write when using KDE FW? > It is important. If people from the outside think it's one coherent thing we > wouldn't need efforts like frameworks to make it more attractive for 3rd party > developers and it also makes any attempts to get KWin as the window manager > for all Qt based shells much more difficult. Which is a reason why I do care > about it. Well re-branding is really hard, it's for a reason companies fight for names... Clearly I'm not alone in not know how to properly brand things now. >> The KDE community has to decide which will be the included, since plasma >> got there first there isn't much chance for a replacement, then better >> do like Razor. > does the KDE community have to decide? Yes, look at the old Oyranos vs colord-kde thread, in the end colord-kde probably has more usage where KWin color correction only works with Oyranos (I don't plan to fix this before we have wayland). And Kolor-manager ended up in extragear... > Did the community ever decide that > there can only be one file manager in the SC? The fact that Konqueror is also a file manager could be tagged as historical reason imho. > Also does software have to be in > the SC? Or is software more blessed by being in the SC? Sure it is, most distros have meta packages which installing kde-utils brings a bunch of "utils" stuff, if your app is in there it gets more attention. > Large part of the > release announcement for 4.11 is about KScreen - to my knowledge it's not even > released as part of the SC. Right, it got good promoting due to being an important thing to many users, would a new clock applet (not part of the SC) get on the announcement page? > What do you think is the more prominent music > player by KDE? Amarok which is not part of the SC or juk which is part of the > SC? Same for IM - kopete vs kpt. I do agree with you it's not needed to be in the SC, but notice the core apps vs regular apps difference, if I write another window manager that happens to replace kwin in the SC would people still want to install KWin? Sure if you promote it better (or have more quality) downstream might use it as default. > Who said there will be a software compilation in the KF 5 world or that the > Plasma Workspaces will be part of such a maybe existing software compilation? Nobody (afaik) said the opposite either :) > Please note that this has not yet been discussed, but I know that a few people > in the Plasma team (me included) would favor to not have the SC anymore. The > reasons you mention are a part of it. In fact the whole discussion highlights > it. OK, then imho we could have modules SC ie kde utils/edu... SC, the SC is good because it help with the coordination of small modules that doesn't have to worry when to release their stuff. > We would not need to think about a version number if Plasma would be part > of the software compilation. Well if that's the reason shouldn't the discussion about having/being part of SC take place first? ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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/LXDE joining the KDE umbrella. What > >> > then? > >> > From one day to another it would be obvious that using "the KDE > >> > desktop" > >> > is > >> > not working any more. > >> > >> In that case what we will end up is with just KDE libraries? I mean > >> people are used to "install/use KDE" which means the SC. > > > > no?!? I fail to see what you want to tell us, I cannot follow your > > thought. I guess it's based on you still think that KDE is not the > > community but all the software we tend to release once half a year. > > Sorry if it's hard to understand, so I'll try to put it into another way: > * First I just wanted to say that I prefer Plasma 2 instead of 5, because it > helps understanding the age and we have lots of other KDE components with > different versions than 5. > > * Second I'm saying that KDE is also the software because we do release a >KDE Software Compilation which has the KDE name. ok, that I did not get at all :-) I personally also don't like 5 for the .0 reason. > > * I know we don't market the KDE desktop anymore, all the blog posts >around KDE still talk about it as a DE. Lots of friends that use KDE SC >don't even know what is plasma-desktop because for them it's KDE. 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. It is important. If people from the outside think it's one coherent thing we wouldn't need efforts like frameworks to make it more attractive for 3rd party developers and it also makes any attempts to get KWin as the window manager for all Qt based shells much more difficult. Which is a reason why I do care about it. > > For example what happens if I want my own shell (no I didn't write one :P ) > on the KDE SC? > > The KDE community has to decide which will be the included, since plasma > got there first there isn't much chance for a replacement, then better > do like Razor. does the KDE community have to decide? Did the community ever decide that there can only be one file manager in the SC? Also does software have to be in the SC? Or is software more blessed by being in the SC? Large part of the release announcement for 4.11 is about KScreen - to my knowledge it's not even released as part of the SC. What do you think is the more prominent music player by KDE? Amarok which is not part of the SC or juk which is part of the SC? Same for IM - kopete vs kpt. > > I'm not against the KDE renaming, but I think we are getting > to a point that having an Software Compilation becomes a > problem. If Razor is now a KDE project they why only plasma > is included? Who said there will be a software compilation in the KF 5 world or that the Plasma Workspaces will be part of such a maybe existing software compilation? Please note that this has not yet been discussed, but I know that a few people in the Plasma team (me included) would favor to not have the SC anymore. The reasons you mention are a part of it. In fact the whole discussion highlights it. We would not need to think about a version number if Plasma would be part of the software compilation. Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 another it would be obvious that using "the KDE desktop" >> > is >> > not working any more. >> >> In that case what we will end up is with just KDE libraries? I mean >> people are used to "install/use KDE" which means the SC. > no?!? I fail to see what you want to tell us, I cannot follow your thought. I > guess it's based on you still think that KDE is not the community but all the > software we tend to release once half a year. Sorry if it's hard to understand, so I'll try to put it into another way: * First I just wanted to say that I prefer Plasma 2 instead of 5, because it helps understanding the age and we have lots of other KDE components with different versions than 5. * Second I'm saying that KDE is also the software because we do release a KDE Software Compilation which has the KDE name. * I know we don't market the KDE desktop anymore, all the blog posts around KDE still talk about it as a DE. Lots of friends that use KDE SC don't even know what is plasma-desktop because for them it's KDE. For example what happens if I want my own shell (no I didn't write one :P ) on the KDE SC? The KDE community has to decide which will be the included, since plasma got there first there isn't much chance for a replacement, then better do like Razor. I'm not against the KDE renaming, but I think we are getting to a point that having an Software Compilation becomes a problem. If Razor is now a KDE project they why only plasma is included? About print-manager the user can see it's version using the about module of system-settings, but since KDE does the branching/tagging it's easier to just rely on the KDE version, the 0.3 vesion is something useless when on SC. But to me as a developer tells me how much I change it, and since it's mostly complete 4.10 has 0.3 and 4.11 has 0.3 because most commits where just bugfixes. Also dpkg -l print-manager shows the KDE SC version (so it does for dolphin). PS I don't care much what plasma does as I'm mostly a user of plasma shell and API, but as a user I just felt that jumping into 5 just because the KDE FW is at 5 seems wrong, as after all KDE is just the community. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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, libs, etc.). Got that idea while reading a news that Cryengine 3 got renamed to Cryengine Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 another > >> KDE option). > > > > this might change. Consider Razor/LXDE joining the KDE umbrella. What > > then? > > From one day to another it would be obvious that using "the KDE desktop" > > is > > not working any more. > > In that case what we will end up is with just KDE libraries? I mean > people are used to "install/use KDE" which means the SC. no?!? I fail to see what you want to tell us, I cannot follow your thought. I guess it's based on you still think that KDE is not the community but all the software we tend to release once half a year. > > If we are going to drop the "KDE desktop" then imho it should > be better to put some marketing on the "Plasma desktop" > which uses KDE technology. We haven't marketed a "KDE desktop" for years now. > > The same imho happens to Razor/LXDE, they will keep being > Razor/LXDE maybe using KDE pieces. At some point KDE > might vanish completely as the more things from the > frameworks are upstreamed (not that this is bad!). Why should KDE vanish if Razor uses frameworks? I fail to follow your reasoning. > > This of course end up being completely ok with the new > KDE = comunity branding which to me is a shame that > the shell looses it's identity. I somehow imagine in the > future people talking about plasma people or lxde people > and the KDE name being left only for frameworks. Why should they only talk about Plasma? > > Of course I'm just supposing. > > > I'm in fact aware of at least three desktop shells by the KDE community. > > The only thing those three share is the window manager. > > But at some level "the" KDE shell is plasma, and if these others want > to be known > the have to do the promoting themselves. Just for the record: one of the three desktop shells I meant is Plasma :-) As far as I know the other shells don't want to be promoted, but they would get obviously the same level of promotion. The dot is open to every KDE project. > > > Given that we know that we want to open us for more projects and that we > > want to get our technologies into other Qt based desktops, it would be a > > really bad idea to ignore this fact when we do the planning for the next > > version. > No, I'm not saying to ignore this fact. It's just that imho > the idea of pushing Plasma to version 5 is bad for the > reasons I mentioned. If plasma will keep being included > into KDE SC the SC version is what users see. I really have problems understanding your arguments. They seem to be centered around "I don't like the renaming of KDE, thus I do not like this". I think the renaming was a good step and reflects much better what we as a community do. I can only recommend to open up on it and see the positive aspects of it. > > An example is that when someone fill a bug against > say print-manager I care which KDE version they have > and not if p-m is at version 0.3, because I know which > version was included in that SC. then you should fix this. In KWin we include also information about kdelibs version (compilation, runtime) and Qt. It helps a lot. Personal remark: I sometimes have problems following your arguments and recently I had the feeling that you jump to wrong conclusions based on incorrect and incomplete data. I think this is also here the case. You jump directly to the conclusion but seem to miss the reasons and the good advantages of the renaming of KDE. Just look at the manifesto - without the renaming that would not have happened. As you have not been at Akademy I recommend to watch the recordings of Kevin's keynote. Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request 112128: Fix plasmapkg -t theme -r ThemeName to actually uninstall the theme.
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/112128/#review38288 --- This review has been submitted with commit 64505f15b9725d3d213990c5fce7f1fc2e41acc7 by Jeremy Whiting to branch KDE/4.11. - Commit Hook On Aug. 21, 2013, 4:50 p.m., Jeremy Paul Whiting wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://git.reviewboard.kde.org/r/112128/ > --- > > (Updated Aug. 21, 2013, 4:50 p.m.) > > > Review request for kde-workspace, Plasma, Aaron J. Seigo, Marco Martin, and > Sebastian Kügler. > > > Description > --- > > Currently uninstallation of plasma themes is very broken for a couple of > reasons. One reason is that the tar packages downloaded from kde-look and > other kns services contain a subfolder with the theme name, that then > contains the metadata.desktop file that plasma::PackageStructure looks for in > order to uninstall or install a plugin. The other problem is that themes > aren't really plugins, so plasmapkg -t theme -r blah fails. This patch fixes > the second issue. I'll upload another patch for review that fixes the first > issue. > > > Diffs > - > > plasma/tools/plasmapkg/main.cpp 6a2982b292ec9736710f4b41dcaa0cbff3986c46 > > Diff: http://git.reviewboard.kde.org/r/112128/diff/ > > > Testing > --- > > Plasma themes correctly uninstall here with this and my other patch. > > > Thanks, > > Jeremy Paul Whiting > > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 KDE umbrella. What then? > From one day to another it would be obvious that using "the KDE desktop" is > not working any more. In that case what we will end up is with just KDE libraries? I mean people are used to "install/use KDE" which means the SC. If we are going to drop the "KDE desktop" then imho it should be better to put some marketing on the "Plasma desktop" which uses KDE technology. The same imho happens to Razor/LXDE, they will keep being Razor/LXDE maybe using KDE pieces. At some point KDE might vanish completely as the more things from the frameworks are upstreamed (not that this is bad!). This of course end up being completely ok with the new KDE = comunity branding which to me is a shame that the shell looses it's identity. I somehow imagine in the future people talking about plasma people or lxde people and the KDE name being left only for frameworks. Of course I'm just supposing. > I'm in fact aware of at least three desktop shells by the KDE community. The > only thing those three share is the window manager. But at some level "the" KDE shell is plasma, and if these others want to be known the have to do the promoting themselves. > Given that we know that we want to open us for more projects and that we want > to get our technologies into other Qt based desktops, it would be a really bad > idea to ignore this fact when we do the planning for the next version. No, I'm not saying to ignore this fact. It's just that imho the idea of pushing Plasma to version 5 is bad for the reasons I mentioned. If plasma will keep being included into KDE SC the SC version is what users see. An example is that when someone fill a bug against say print-manager I care which KDE version they have and not if p-m is at version 0.3, because I know which version was included in that SC. Best ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request 112128: Fix plasmapkg -t theme -r ThemeName to actually uninstall the theme.
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/112128/ --- (Updated Aug. 21, 2013, 4:50 p.m.) Status -- This change has been marked as submitted. Review request for kde-workspace, Plasma, Aaron J. Seigo, Marco Martin, and Sebastian Kügler. Description --- Currently uninstallation of plasma themes is very broken for a couple of reasons. One reason is that the tar packages downloaded from kde-look and other kns services contain a subfolder with the theme name, that then contains the metadata.desktop file that plasma::PackageStructure looks for in order to uninstall or install a plugin. The other problem is that themes aren't really plugins, so plasmapkg -t theme -r blah fails. This patch fixes the second issue. I'll upload another patch for review that fixes the first issue. Diffs - plasma/tools/plasmapkg/main.cpp 6a2982b292ec9736710f4b41dcaa0cbff3986c46 Diff: http://git.reviewboard.kde.org/r/112128/diff/ Testing --- Plasma themes correctly uninstall here with this and my other patch. Thanks, Jeremy Paul Whiting ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request 112128: Fix plasmapkg -t theme -r ThemeName to actually uninstall the theme.
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/112128/#review38287 --- This review has been submitted with commit ab7b64e3a9c788814bda5c2dd2fce1a676c8e1ea by Jeremy Whiting to branch master. - Commit Hook On Aug. 17, 2013, 3:03 a.m., Jeremy Paul Whiting wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://git.reviewboard.kde.org/r/112128/ > --- > > (Updated Aug. 17, 2013, 3:03 a.m.) > > > Review request for kde-workspace, Plasma, Aaron J. Seigo, Marco Martin, and > Sebastian Kügler. > > > Description > --- > > Currently uninstallation of plasma themes is very broken for a couple of > reasons. One reason is that the tar packages downloaded from kde-look and > other kns services contain a subfolder with the theme name, that then > contains the metadata.desktop file that plasma::PackageStructure looks for in > order to uninstall or install a plugin. The other problem is that themes > aren't really plugins, so plasmapkg -t theme -r blah fails. This patch fixes > the second issue. I'll upload another patch for review that fixes the first > issue. > > > Diffs > - > > plasma/tools/plasmapkg/main.cpp 6a2982b292ec9736710f4b41dcaa0cbff3986c46 > > Diff: http://git.reviewboard.kde.org/r/112128/diff/ > > > Testing > --- > > Plasma themes correctly uninstall here with this and my other patch. > > > Thanks, > > Jeremy Paul Whiting > > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Review Request 112128: Fix plasmapkg -t theme -r ThemeName to actually uninstall the theme.
--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/112128/#review38285 --- Ship it! looks good to me - Marco Martin On Aug. 17, 2013, 3:03 a.m., Jeremy Paul Whiting wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > http://git.reviewboard.kde.org/r/112128/ > --- > > (Updated Aug. 17, 2013, 3:03 a.m.) > > > Review request for kde-workspace, Plasma, Aaron J. Seigo, Marco Martin, and > Sebastian Kügler. > > > Description > --- > > Currently uninstallation of plasma themes is very broken for a couple of > reasons. One reason is that the tar packages downloaded from kde-look and > other kns services contain a subfolder with the theme name, that then > contains the metadata.desktop file that plasma::PackageStructure looks for in > order to uninstall or install a plugin. The other problem is that themes > aren't really plugins, so plasmapkg -t theme -r blah fails. This patch fixes > the second issue. I'll upload another patch for review that fixes the first > issue. > > > Diffs > - > > plasma/tools/plasmapkg/main.cpp 6a2982b292ec9736710f4b41dcaa0cbff3986c46 > > Diff: http://git.reviewboard.kde.org/r/112128/diff/ > > > Testing > --- > > Plasma themes correctly uninstall here with this and my other patch. > > > Thanks, > > Jeremy Paul Whiting > > ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 day to another it would be obvious that using "the KDE desktop" is not working any more. I'm in fact aware of at least three desktop shells by the KDE community. The only thing those three share is the window manager. Given that we know that we want to open us for more projects and that we want to get our technologies into other Qt based desktops, it would be a really bad idea to ignore this fact when we do the planning for the next version. > some components happen to have survived since > KDE 1 (kwin/konqueror maybe?), Just for the record: both KWin and Konqueror got introduced in KDE (SC) 2. The oldest to my knowledge still being developed application is KMail. Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 marketing and public > communication, but it ended up that way, and sure enough press reaction to SC > was overwhelmingly negative. Sure, just to clarify what I was trying to state is that most users know the KDE version not the components of it. For the SC maybe in 5 we could go back to "we are KDE and KDE is also the software" I think people can tell the difference without an "SC" :P but whatever that's another (endless) discussion and off topic... ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 it ended up that way, and sure enough press reaction to SC was overwhelmingly negative. -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 single components, for example I go to dolphin look at it's version and I have 2.2 but my KDE is 4.10.5, when the user report bugs most of the time they specify the whole KDE version and not the component one. Having KDE as just as people (bad thing imho) brings these issues, do we install KDE software? Or would I install KDE people? IMHO the core of the KDE is it's libraries/frameworks which will be named at 5. One can write another KDE shell (iirc there is kor) (and don't make it in SC) but that will still be a KDE shell. enough talking to summarize I'd say we should go for KDE SC 5 which includes 2nd gen of Plasma, 3rd gen of dolphin and so on, some components happen to have survived since KDE 1 (kwin/konqueror maybe?), naming Plasma as 5 doesn't reflect it's real age. Regards, -- Daniel Nicoletti - http://dantti.wordpress.com ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: naming the next major release
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 about it for a while, just few considerations * we want to maintain the "kde is the community, not the software" mantra * so a name for "the product workspace" is needed * any descriptive name, sich as "workspace" "shell" "desktop" risks to be too narrow, nerdy and cold * a name that sounds cool but doesn't really describe something is better, "plasma" or "plasma active" are (as the term "firefox" per se doesn't have anything to do with browser) * Plasma has quite some luggage already, that may be an advantage or a disadvantage, i don't know (but we have years of climbing the googlability of the term already, that's quite an investment) * Plasma Active may indeed cause a problem in perception and bogus articles like "kde is dropping the desktop for tablets". Paradoxically I think the place where instead would have a good effect is the internal developer community (for applications developers there is still a bit of "the active version is not my problem, i care only about desktop" feeling * I'm not sure thinking about a completely different new name would come up with something that would work, but if someone can think about any, please speak ;) My vote would go for Plasma. hell, i would even go as far as changing the kickoff icon (no, not with the cashew, with something better :p) About numbers, 2 or 5 i don't know, they may risk to dilute the catchiness? Cheers, Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Add custom first week support to KDE digital clock.
Hi! https://git.reviewboard.kde.org/r/111849/ is updated, another patch is there, which use custom config file! Thanks everyone! 2013/8/4 Sebastian Kügler > Hi Hu Zheng, > > On Saturday, August 03, 2013 11:42:22 Hu Zheng wrote: > > Done! See: > > https://git.reviewboard.kde.org/r/111849/ > > Please submit the patch as patch on reviewboard, not as attachment. That > way, > it can be read easily from the web interface. > > Please also attach screenshots of any UI that has been changed. > > Thanks, > -- > sebas > > http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 > -- http://www.huzheng.org ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
