Help fixing Lokalize & generic development questions
Greetings,
The company I work for is trying to provide our clients with a mechanism to
translate a website using .xliff and of all the translation software we looked
at, lokalize was deemed to be the best for our use case.
We ran across a few minor issues. We tried to contact the lead developer a
while back to offer to pay for these changes to be made but for whatever
reason we did not receive a response. Fair enough, people move on etc..
So I was hoping to fix these and contribute back the changes, however after 6
hours I'm still unable to get any of the changes i am making to appear in my
build of lokalize following the guide
here:http://userbase.kde.org/Lokalize#Compiling_Lokalize_from_KDE_trunk
It turns out that aside from the kdelibs-dev package mentioned on the website
you need 2 of the strigi dev libraries, something called hunspell, and a
couple of other libraries which i forget the names of now, before it will even
build. Not to mention the optional libxml, libxslt libraries . I wanted to
update this at the time when i worked out how to do it but despite being
labeled a wiki it doesn't seem that it is editable.
So eventually i have it all compiled and it installs to ~/kde43/bin.. it all
executes fine.
So then i thought ok, i'll make a simple change
src/project/projectmodel.cpp
I changed a string on line 527 from
case SourceDate:return i18nc("@title:column","Last Revision");
to:
case SourceDate:return i18nc("@title:column","Revision");
i ran make clean; make; make install loaded up the ~/kde43/bin version of
lokalize. No change. So i'm either making the change in the wrong file or
there is some sort of cache going on. I tried returning just a string and
doing the same thing... it also didn't change. So can anyone tell me if there
is some sort of cache i need to get rid of or is it just that i'm in the wrong
place ?
The actual change i wanted to make was to list .xlf files in the catalogue
manager as well as .po files. I thought perhaps adding a .xlf to the string
on line :73
m_potModel.dirLister()->setNameFilter("*.pot *.xlf");
would achieve this but i'm unsure if i'm doing some thing wrong or if this is
just not the place.
More generically is there somewhere a business like ours can go where we can
pay for either consultation to guide us in making changes or actual changes
to be made to kde related projects. We are trying to participate in the eco
system as the advantages are there in the long run but at the moment we are
finding it hard to do so. We have developers and we are willing to learn but
none of us are KDE developers and we have hard deadlines that prevent us from
spending large amounts of time learning the code in one go. However paying
for someone to answer questions or make changes is probably cost effective.
Many thanks
Andrew
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Building kde-workspace with latest checkout
Adding kde-core-devel, which is better suited for these kind of emails.
Seems to me that trunk is actually not up to date for kdelibs, and that
accessor to
resizeMethodHint is missing from plasma/wallpaper.h / .cpp
See patch attached. (can someone fix/commit this ?)
At least it made things compile again for me.
Hugo
Hi guys,
I keep getting this error while trying to build kde-workspace module:
[ 57%] Building CXX object
plasma/generic/wallpapers/image/CMakeFiles/plasma_wallpaper_image.dir/backgroundlistmodel.o
/home/ggorosito/kde/kdesrc/kde/kde-workspace/plasma/generic/wallpapers/image/image.cpp:
In member function ‘virtual void Image::save(KConfigGroup&)’:
/home/ggorosito/kde/kdesrc/kde/kde-workspace/plasma/generic/wallpapers/image/image.cpp:130:66:
error: ‘resizeMethodHint’ was not declared in this scope
/home/ggorosito/kde/kdesrc/kde/kde-workspace/plasma/generic/wallpapers/image/image.cpp:
In member function ‘virtual QWidget*
Image::createConfigurationInterface(QWidget*)’:
/home/ggorosito/kde/kdesrc/kde/kde-workspace/plasma/generic/wallpapers/image/image.cpp:152:51:
error: ‘resizeMethodHint’ was not declared in this scope
/home/ggorosito/kde/kdesrc/kde/kde-workspace/plasma/generic/wallpapers/image/image.cpp:241:34:
error: ‘resizeMethodHint’ was not declared in this scope
/home/ggorosito/kde/kdesrc/kde/kde-workspace/plasma/generic/wallpapers/image/image.cpp:251:60:
error: ‘resizeMethodHint’ was not declared in this scope
/home/ggorosito/kde/kdesrc/kde/kde-workspace/plasma/generic/wallpapers/image/image.cpp:
In member function ‘void Image::positioningChanged(int)’:
/home/ggorosito/kde/kdesrc/kde/kde-workspace/plasma/generic/wallpapers/image/image.cpp:630:47:
error: ‘resizeMethodHint’ was not declared in this scope
/home/ggorosito/kde/kdesrc/kde/kde-workspace/plasma/generic/wallpapers/image/image.cpp:
In member function ‘void Image::renderWallpaper(const QString&)’:
/home/ggorosito/kde/kdesrc/kde/kde-workspace/plasma/generic/wallpapers/image/image.cpp:783:44:
error: ‘resizeMethodHint’ was not declared in this scope
make[2]: ***
[plasma/generic/wallpapers/image/CMakeFiles/plasma_wallpaper_image.dir/image.o]
Error 1
Full log: http://pastebin.com/UnE2m3Am
Today I talked with Aaron about this, he told me to make sure that
kdelibs is up to date and is setted up to branch KDE/4.7.. and it is:
ggorosito@glaptop:~/kde/kdesrc/kde/kdelibs$ git config --get-all
remote.origin.url
http://anongit.kde.org/kdelibs.git
ggorosito@glaptop:~/kde/kdesrc/kde/kdelibs$ git branch
* KDE/4.7
master
Any ideas!?
###
# Gonzalo Gorosito
# Programador&& sysadmin
#
# http://www.tutorialesdebian.com - Tutoriales para debianeros,
scripts, info, notícias y mucho mas.
# http://www.ggorosito.com.ar - Website personal
###
Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe<<
diff --git a/plasma/wallpaper.cpp b/plasma/wallpaper.cpp
index 97ec7e8..16cf3a7 100644
--- a/plasma/wallpaper.cpp
+++ b/plasma/wallpaper.cpp
@@ -421,6 +421,9 @@ void Wallpaper::setResizeMethodHint(Wallpaper::ResizeMethod
resizeMethod)
emit renderHintsChanged();
}
+Wallpaper::ResizeMethod Wallpaper::resizeMethodHint( void ) const
+{ return d->lastResizeMethod; }
+
void Wallpaper::setTargetSizeHint(const QSizeF &targetSize)
{
d->targetSize = targetSize;
diff --git a/plasma/wallpaper.h b/plasma/wallpaper.h
index e1e9891..3086517 100644
--- a/plasma/wallpaper.h
+++ b/plasma/wallpaper.h
@@ -416,12 +416,17 @@ class PLASMA_EXPORT Wallpaper : public QObject
/**
* This method is invoked by setUrls(KUrl::List)
* Can be Overriden by Plugins which want to support setting Image URLs
- * Will be changed to virtual method in libplasma2/KDE5
+ * Will be changed to virtual method in libplasma2/KDE5
* @since 4.7
*/
void addUrls(const KUrl::List &urls);
protected:
+
+
+Wallpaper::ResizeMethod resizeMethodHint( void ) const;
+
+
/**
* This constructor is to be used with the plugin loading systems
* found in KPluginInfo and KService. The argument list is expected
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
why are bugs ignored over months?
https://bugs.kde.org/show_bug.cgi?id=270414 why in the world does nobody care about bugs like basic-operations (and rename a file is really one since many years) for half a year? does nobody upstream use the folder-view? -- Mit besten Grüßen, Reindl Harald the lounge interactive design GmbH A-1060 Vienna, Hofmühlgasse 17 CTO / software-development / cms-solutions p: +43 (1) 595 3999 33, m: +43 (676) 40 221 40 icq: 154546673, http://www.thelounge.net/ http://www.thelounge.net/signature.asc.what.htm signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
On Wed, 21 Sep 2011 08:11:43 PM Reindl Harald wrote: > https://bugs.kde.org/show_bug.cgi?id=270414 > > why in the world does nobody care about bugs like > basic-operations (and rename a file is really one > since many years) for half a year? I see lots of comments, so many people care. However there are a lot of negative comments, so working on such a bug is pretty disheartening for a developer. When I read stuff that is nasty, mean or abusive, I often find something else to do. Remember that this is a hobby for almost all developers. Another way to look at this is "why haven't you fixed it in the last six months". If you don't know how, why haven't you learned? Brad >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Am 21.09.2011 12:17, schrieb Brad Hards: > On Wed, 21 Sep 2011 08:11:43 PM Reindl Harald wrote: >> https://bugs.kde.org/show_bug.cgi?id=270414 >> >> why in the world does nobody care about bugs like >> basic-operations (and rename a file is really one >> since many years) for half a year? > I see lots of comments, so many people care. However there are a lot of > negative comments, so working on such a bug is pretty disheartening for a > developer. > > When I read stuff that is nasty, mean or abusive, I often find something else > to > do. Remember that this is a hobby for almost all developers. > > Another way to look at this is "why haven't you fixed it in the last six > months". If you don't know how, why haven't you learned? because i am no kde-developer? because i am not introduced the bug? because i have not the knowledge and time to learn fix kde-bugs? because there are users out there which are not developers? because i did first not thing that even a bugreport is needed for such a bug jumping in everybodys face multiple times each day? signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
On Wed, Sep 21, 2011 at 10:21 PM, Reindl Harald wrote: > > > Am 21.09.2011 12:17, schrieb Brad Hards: >> On Wed, 21 Sep 2011 08:11:43 PM Reindl Harald wrote: >>> https://bugs.kde.org/show_bug.cgi?id=270414 >>> >>> why in the world does nobody care about bugs like >>> basic-operations (and rename a file is really one >>> since many years) for half a year? >> I see lots of comments, so many people care. However there are a lot of >> negative comments, so working on such a bug is pretty disheartening for a >> developer. >> >> When I read stuff that is nasty, mean or abusive, I often find something >> else to >> do. Remember that this is a hobby for almost all developers. >> >> Another way to look at this is "why haven't you fixed it in the last six >> months". If you don't know how, why haven't you learned? > > because i am no kde-developer? > because i am not introduced the bug? > because i have not the knowledge and time to learn fix kde-bugs? > because there are users out there which are not developers? > > because i did first not thing that even a bugreport is needed for > such a bug jumping in everybodys face multiple times each day? Please note, that whilst you may be able to reproduce it with ease, developers may not be able to reproduce it at all. This may be due to any number of factors, including Plasma configuration, environment variables, distribution packaging, software versions (KDE, Qt, etc - and their combinations) and so forth. If a developer or triager cannot reproduce it, they cannot fix it. > > > >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << > > Regards, Ben >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
On Wed, 21 Sep 2011 08:21:39 PM Reindl Harald wrote: > because i have not the knowledge and time to learn fix kde-bugs? I think this is basically the same as saying that this bug is not important to you (i.e. you have other things to spend your time on). Yet you think someone else should spend their time. I'm not saying that this should not be fixed. However if it is really important to you, you should be willing to pay to fix it, or learn to fix it. If it isn't, then you should be willing to wait for it to be fixed. Brad >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Hi, On Wed, Sep 21, 2011 at 3:47 PM, Brad Hards wrote: > On Wed, 21 Sep 2011 08:11:43 PM Reindl Harald wrote: > > https://bugs.kde.org/show_bug.cgi?id=270414 > > > > why in the world does nobody care about bugs like > > basic-operations (and rename a file is really one > > since many years) for half a year? > I see lots of comments, so many people care. However there are a lot of > negative comments, so working on such a bug is pretty disheartening for a > developer. > > When I read stuff that is nasty, mean or abusive, I often find something > else to > do. Remember that this is a hobby for almost all developers. > > Another way to look at this is "why haven't you fixed it in the last six > months". If you don't know how, why haven't you learned? > Well though I agree with the points before it, this is actually not nice, not everyone can do development and/or fix bugs. > Brad > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to > unsubscribe << > Shantanu Tushar(UTC +0530) http://www.shantanutushar.com >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Am 21.09.2011 12:30, schrieb Brad Hards: > On Wed, 21 Sep 2011 08:21:39 PM Reindl Harald wrote: >> because i have not the knowledge and time to learn fix kde-bugs? > I think this is basically the same as saying that this bug is not important > to > you (i.e. you have other things to spend your time on). Yet you think someone > else should spend their time. this is a poor argument how do you imagine a php-developer fixing a bug in KDE/Plasma? are you developer or only user, if you are only user i can understand this naive answer of you a little bit, if you are developer you must be crazy think somebody can learn how to develop/debug kde/plsama-code in a reasonable time these "why are you not fixing it on your own" are simply dumb arguments as also "they do this in their free time" because if they do this without getting paied they should be interestet in a good reputation and errors in basic-operation are the worst ever can happen signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
On Wed, 21 Sep 2011 09:15:43 PM Reindl Harald wrote: > Am 21.09.2011 12:30, schrieb Brad Hards: > > On Wed, 21 Sep 2011 08:21:39 PM Reindl Harald wrote: > >> because i have not the knowledge and time to learn fix kde-bugs? > > > > I think this is basically the same as saying that this bug is not > > important to you (i.e. you have other things to spend your time on). Yet > > you think someone else should spend their time. > > this is a poor argument > > how do you imagine a php-developer fixing a bug in KDE/Plasma? > are you developer or only user, if you are only user i can > understand this naive answer of you a little bit, if you are > developer you must be crazy think somebody can learn how > to develop/debug kde/plsama-code in a reasonable time > > these "why are you not fixing it on your own" are simply dumb > arguments as also "they do this in their free time" because > if they do this without getting paied they should be interestet > in a good reputation and errors in basic-operation are the worst > ever can happen OK. Thanks for your continuing support for KDE. Brad >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Am 21.09.2011 13:19, schrieb Brad Hards: > On Wed, 21 Sep 2011 09:15:43 PM Reindl Harald wrote: >> Am 21.09.2011 12:30, schrieb Brad Hards: >>> On Wed, 21 Sep 2011 08:21:39 PM Reindl Harald wrote: because i have not the knowledge and time to learn fix kde-bugs? >>> >>> I think this is basically the same as saying that this bug is not >>> important to you (i.e. you have other things to spend your time on). Yet >>> you think someone else should spend their time. >> >> this is a poor argument >> >> how do you imagine a php-developer fixing a bug in KDE/Plasma? >> are you developer or only user, if you are only user i can >> understand this naive answer of you a little bit, if you are >> developer you must be crazy think somebody can learn how >> to develop/debug kde/plsama-code in a reasonable time >> >> these "why are you not fixing it on your own" are simply dumb >> arguments as also "they do this in their free time" because >> if they do this without getting paied they should be interestet >> in a good reputation and errors in basic-operation are the worst >> ever can happen > > OK. Thanks for your continuing support for KDE what exactly are you missing in the difference between developers / users my user-support is writing bug-reports, this is what i can do and this bugreport is the best sample that nobody is interested in the help of users - so the developers have two options: test their code or reply to bugreports who do you think you are tell everybody he has to shut up if the if he is no kde-developer and can not fix bugs on his own? signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
On Wednesday 21 September 2011 Sep, Reindl Harald wrote: > what exactly are you missing in the difference between developers / users > > my user-support is writing bug-reports, this is what i can do > and this bugreport is the best sample that nobody is interested in the > help of users - so the developers have two options: test their code > or reply to bugreports > > who do you think you are tell everybody he has to shut up if the > if he is no kde-developer and can not fix bugs on his own? Well, Brad is one of the kde core developers... He's got a right to tell people they need to start considering helping out. For this bug, it seems that the author of the code has disappeared in October 2010, before the report was opened. At least, I cannot find any commits by him to the folderview code anymore. Which sort of explains why nothing happened. An organisation like KDE cannot hire developers if people develop other interests and stop working on their code. It might even take quite a bit of time before anyone notices someone isn't around anymore. And then there's no guarantee anyone will pick up on the slack. What KDE needs is a constant stream of new volunteers who are prepared to take over existing code. Personally, and speaking as a KDE developer, I never have noticed this bug myself because I don't use a folderview on my desktop. Had I used folderview, I might still not have noticed because I might not have used it for renaming files. Had I used folderview and I had I tried to rename files, I still might not have noticed the bug because I might have used the mouse to leave the text entry field. But I'm not using folderview, and besides, my own project takes all my time and I have bugs dating back to 2006 that still need fixing... Getting nasty and impatient helps nobody, is not constructive, is not polite, doesn't teach anyone a lesson or makes anyone eager to please you. It's counter-productive. -- Boudewijn Rempt http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
> > OK. Thanks for your continuing support for KDE > > what exactly are you missing in the difference between developers / users > > my user-support is writing bug-reports, this is what i can do > and this bugreport is the best sample that nobody is interested in the > help of users - so the developers have two options: test their code > or reply to bugreports As far as as I can see your only contribution to the bug report is to rant at developers who are doing this in their free time. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Re: why are bugs ignored over months?
A Dimecres, 21 de setembre de 2011, Reindl Harald vàreu escriure: > Am 21.09.2011 13:19, schrieb Brad Hards: > > On Wed, 21 Sep 2011 09:15:43 PM Reindl Harald wrote: > >> Am 21.09.2011 12:30, schrieb Brad Hards: > >>> On Wed, 21 Sep 2011 08:21:39 PM Reindl Harald wrote: > because i have not the knowledge and time to learn fix kde-bugs? > >>> > >>> I think this is basically the same as saying that this bug is not > >>> important to you (i.e. you have other things to spend your time on). > >>> Yet you think someone else should spend their time. > >> > >> this is a poor argument > >> > >> how do you imagine a php-developer fixing a bug in KDE/Plasma? > >> are you developer or only user, if you are only user i can > >> understand this naive answer of you a little bit, if you are > >> developer you must be crazy think somebody can learn how > >> to develop/debug kde/plsama-code in a reasonable time > >> > >> these "why are you not fixing it on your own" are simply dumb > >> arguments as also "they do this in their free time" because > >> if they do this without getting paied they should be interestet > >> in a good reputation and errors in basic-operation are the worst > >> ever can happen > > > > OK. Thanks for your continuing support for KDE > > what exactly are you missing in the difference between developers / users > > my user-support is writing bug-reports, this is what i can do > and this bugreport is the best sample that nobody is interested in the > help of users - so the developers have two options: test their code > or reply to bugreports > > who do you think you are tell everybody he has to shut up if the > if he is no kde-developer and can not fix bugs on his own? who do you think you are to demand a bug to be fixed? Albert >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Am Mittwoch, 21. September 2011, 13:35:17 schrieb Reindl Harald: > Am 21.09.2011 13:19, schrieb Brad Hards: > > On Wed, 21 Sep 2011 09:15:43 PM Reindl Harald wrote: > >> Am 21.09.2011 12:30, schrieb Brad Hards: > >>> On Wed, 21 Sep 2011 08:21:39 PM Reindl Harald wrote: > because i have not the knowledge and time to learn fix kde-bugs? > >>> > >>> I think this is basically the same as saying that this bug is not > >>> important to you (i.e. you have other things to spend your time on). > >>> Yet you think someone else should spend their time. > >> > >> this is a poor argument > >> > >> how do you imagine a php-developer fixing a bug in KDE/Plasma? > >> are you developer or only user, if you are only user i can > >> understand this naive answer of you a little bit, if you are > >> developer you must be crazy think somebody can learn how > >> to develop/debug kde/plsama-code in a reasonable time > >> > >> these "why are you not fixing it on your own" are simply dumb > >> arguments as also "they do this in their free time" because > >> if they do this without getting paied they should be interestet > >> in a good reputation and errors in basic-operation are the worst > >> ever can happen > > > > OK. Thanks for your continuing support for KDE > > what exactly are you missing in the difference between developers / users > > my user-support is writing bug-reports, this is what i can do > and this bugreport is the best sample that nobody is interested in the > help of users - so the developers have two options: test their code > or reply to bugreports > > who do you think you are tell everybody he has to shut up if the > if he is no kde-developer and can not fix bugs on his own? Your writings make me very sad. For what reasons do you think free software developers are working in the case when it is not to make a living. It's just for fun. Do you think you increase the fun of kde developers the way you continue this conversation? Please make them not stop working at all! ;) You cannot claim anything. There is no guarantee to receive 100% bug-free software. (Maybe you remember these statements like "This program is free software. It comes without any warranty"). If you are not content, you should pay for professional support or kindly ask the people to catch up with your bug. There are only these two options. So who are you, to ignore all these rules when dealing with FOSS? So please think again about your opinions and statements and consider, that your reputation in the FOSS community might be not as good as before when you dont start to backpedal soon. Robert >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Building kde-workspace with latest checkout
On Wednesday, September 21, 2011 12:07:36 Hugo Pereira Da Costa wrote: > Adding kde-core-devel, which is better suited for these kind of emails. > > Seems to me that trunk is actually not up to date for kdelibs, and that > accessor to master is dead. do not use it. use the KDE/4.7 branch for building other KDE software, or frameworks for development of kdleibs.. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
On Wed, 21 Sep 2011 09:35:17 PM Reindl Harald wrote: > what exactly are you missing in the difference between developers / users > > my user-support is writing bug-reports, this is what i can do > and this bugreport is the best sample that nobody is interested in the > help of users - so the developers have two options: test their code > or reply to bugreports > > who do you think you are tell everybody he has to shut up if the > if he is no kde-developer and can not fix bugs on his own? Thanks for your kind words and insights. I will give them appropriate consideration. Brad >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Help fixing Lokalize & generic development questions
A Dimecres, 21 de setembre de 2011, Andrew Mason vàreu escriure:
> Greetings,
> The company I work for is trying to provide our clients with a mechanism to
> translate a website using .xliff and of all the translation software we
> looked at, lokalize was deemed to be the best for our use case.
>
> We ran across a few minor issues. We tried to contact the lead developer a
> while back to offer to pay for these changes to be made but for whatever
> reason we did not receive a response. Fair enough, people move on etc..
Nick is still around, it might be worth contacting him again.
> So I was hoping to fix these and contribute back the changes, however after
> 6 hours I'm still unable to get any of the changes i am making to appear in
> my build of lokalize following the guide
> here:http://userbase.kde.org/Lokalize#Compiling_Lokalize_from_KDE_trunk
>
> It turns out that aside from the kdelibs-dev package mentioned on the
> website you need 2 of the strigi dev libraries, something called hunspell,
> and a couple of other libraries which i forget the names of now, before it
> will even build. Not to mention the optional libxml, libxslt libraries . I
> wanted to update this at the time when i worked out how to do it but
> despite being labeled a wiki it doesn't seem that it is editable.
>
> So eventually i have it all compiled and it installs to ~/kde43/bin.. it all
> executes fine.
>
> So then i thought ok, i'll make a simple change
>
> src/project/projectmodel.cpp
>
> I changed a string on line 527 from
> case SourceDate:return i18nc("@title:column","Last Revision");
> to:
> case SourceDate:return i18nc("@title:column","Revision");
>
> i ran make clean; make; make install loaded up the ~/kde43/bin version of
> lokalize. No change. So i'm either making the change in the wrong file or
> there is some sort of cache going on. I tried returning just a string and
> doing the same thing... it also didn't change. So can anyone tell me if
> there is some sort of cache i need to get rid of or is it just that i'm in
> the wrong place ?
I'd say you are changing the wrong, file have you tried something simpler,
like making it crash in the main.cpp file?
> More generically is there somewhere a business like ours can go where we
> can pay for either consultation to guide us in making changes or actual
> changes to be made to kde related projects. We are trying to participate in
> the eco system as the advantages are there in the long run but at the
> moment we are finding it hard to do so. We have developers and we are
> willing to learn but none of us are KDE developers and we have hard
> deadlines that prevent us from spending large amounts of time learning the
> code in one go. However paying for someone to answer questions or make
> changes is probably cost effective.
At the moment I am unemployed so if you are really interested drop me a mail
in private and we can have a chat.
Thanks,
Albert
>
> Many thanks
> Andrew
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Am 21.09.2011 13:47, schrieb Boudewijn Rempt: > On Wednesday 21 September 2011 Sep, Reindl Harald wrote: > >> what exactly are you missing in the difference between developers / users >> >> my user-support is writing bug-reports, this is what i can do >> and this bugreport is the best sample that nobody is interested in the >> help of users - so the developers have two options: test their code >> or reply to bugreports >> >> who do you think you are tell everybody he has to shut up if the >> if he is no kde-developer and can not fix bugs on his own? > Well, Brad is one of the kde core developers... He's got a right to tell > people they need to start considering helping out. well, since he is not using @kde.org address how sould i know if he is a core developer or one of the way too much peopole crying "it's free software, use it as it is or stop using it" the whole day? > For this bug, it seems that the author of the code has disappeared in October > 2010, before the report was opened. At least, I cannot find any commits by > him to the folderview code anymore. Which sort of explains why nothing > happened there is someshting terrible broken if bugs from a 4.6 major release are not reviewed before 4.7/4.7.1 > An organisation like KDE cannot hire developers if people develop other > interests and stop working on their code. It might even take quite a bit of > time before anyone notices someone isn't around anymore. And then there's no > guarantee anyone will pick up on the slack. What KDE needs is a constant > stream of new volunteers who are prepared to take over existing code. i know but try to understand users who was affected hardly be the 4.0 release because upstream communicated WAY TOO LATE that 4.0 is not for endusers and the time where this was communicated where too late for fedora as example because they changed the whole packaging for 4.0 since in the whole software-world 4.0 means "final version" and not "developers only" so after that and living for years with hughe troubles especially on systems with nvidia-graphics it is frustrating seeing such bugs introduced and feeling nobody cares, the same for the whole sftp-kio rewrite last year which was a) not finished/buggy as hell and b) pushed to a stable 4.x-release to spit in the users face instead testing/finishing the replacement BEFORE push it to the users > Personally, and speaking as a KDE developer, I never have noticed this bug > myself because I don't use a folderview on my desktop. Had I used folderview, > I might still not have noticed because I might not have used it for renaming > files. Had I used folderview and I had I tried to rename files, I still might > not have noticed the bug because I might have used the mouse to leave the > text entry field. how will you use the mouse for that? since the last invasive change there are no popups for file-rename this happens currently inline and you have to press enter or on some special places directly by the file to rename, if you click somewhere the folderview or on the desktop you will not leave this dialog this is the next bug in the folder-view: * if konqueror/dplhin settings says "rename in popups" respect it * there is no question about DELETE a file > > Getting nasty and impatient helps nobody, is not constructive, is not polite, > doesn't teach anyone a lesson or makes anyone eager to please you. It's > counter-productive. i agree - but what should you do as user if a bug hits you multiple each hour since half a year and their is not other feedback as "me too"? signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
On Wed, Sep 21, 2011 at 2:10 PM, Reindl Harald wrote: >> Getting nasty and impatient helps nobody, is not constructive, is not >> polite, doesn't teach anyone a lesson or makes anyone eager to please you. >> It's counter-productive. > > i agree - but what should you do as user if a bug hits you multiple each hour > since half a year and their is not other feedback as "me too"? Do what everyone else does and go through the proper channels. Everyone has their own pet bugs, but you don't see many emails on the mailing lists like this. Why do you think that is? -Todd >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Am 21.09.2011 14:14, schrieb todd rme: > On Wed, Sep 21, 2011 at 2:10 PM, Reindl Harald wrote: >> i agree - but what should you do as user if a bug hits you multiple each hour >> since half a year and their is not other feedback as "me too"? > > Do what everyone else does and go through the proper channels. what are the "proper channels"? i thought bugtracker is > Everyone has their own pet bugs, but you don't see many emails on the > mailing lists like this. Why do you think that is? i can not say much about this because i subscribed to the devel-list today only because bugzilla does not interest upstream and update to 4.7.1 today with no chance made me tired signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
On Wed, Sep 21, 2011 at 2:18 PM, Reindl Harald wrote: > > > Am 21.09.2011 14:14, schrieb todd rme: >> On Wed, Sep 21, 2011 at 2:10 PM, Reindl Harald >> wrote: >>> i agree - but what should you do as user if a bug hits you multiple each >>> hour >>> since half a year and their is not other feedback as "me too"? >> >> Do what everyone else does and go through the proper channels. > > what are the "proper channels"? > i thought bugtracker is The bugtrack is, this mailing list is not. >> Everyone has their own pet bugs, but you don't see many emails on the >> mailing lists like this. Why do you think that is? > > i can not say much about this because i subscribed to the devel-list > today only because bugzilla does not interest upstream and update to > 4.7.1 today with no chance made me tired I've had bugs in the bug tracker a lot longer than that, yet you don't see me, or practically anyone else, spamming mailing lists demanding that someone fix our problem. If we did, the mailing list would be so swamped with such emails it would be impossible to use it for anything productive. We use bugs.kde.org and not the mailing lists for these sorts of discussions for a reason. You are being very inconsiderate to the large number of other people who also have bugs they want to be fixed but are trying to do the right thing by not swamping the mailing lists with these sorts of demands. -Todd >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
On Wednesday, September 21, 2011 14:10:15 Reindl Harald wrote: > on systems with nvidia-graphics it is frustrating seeing such bugs > introduced and feeling nobody cares, the same for the whole Reindl, you have chosen to engage in a non-constructive manner that is not bringing anything of use to the work being done. Since this does not seem to be changing as the thread continues, the discussion needs to cease here. Thank you to all involved for your understanding and cooperation. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Am 21.09.2011 14:31, schrieb todd rme: > Do what everyone else does and go through the proper channels. >> what are the "proper channels"? >> i thought bugtracker is > The bugtrack is, this mailing list is not well, and there was no feedback from any developer in the bugtracker now we found out that the maintainer has gone away months ago if i would not have written my mail we would sit here 2013 without knowing that the code is orhpaned - orphaned code especially in plasma can have two problems: a) security b) stability so it is the rigth thing to remind the core-developers that they ship orphaned code since many months, my anger was produced in silly answers like "why do you not fix it" since a lot of naive developers think everybody can fix everything i can not, but as php-developer i have enough knowledge that this is a two-line fix and exactly this is the reason why i will not understand what takes half a year P.S.: you can call me with my first name "Harald" signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
The bug is fixed. As Aaron said this thread will end here. Cheers Lydia -- Lydia Pintscher KDE Community Working Group member http://kde.org - http://about.me/lydia.pintscher >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Am 21.09.2011 15:08, schrieb Lydia Pintscher: > The bug is fixed. As Aaron said this thread will end here. thank you for https://bugs.kde.org/show_bug.cgi?id=270414#c43 this was the only result i have hoped with my initial mail instead all the non helpfull "fix it by yourself"-rants signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
On Wednesday, September 21, 2011 15:12:27 Reindl Harald wrote: > Am 21.09.2011 15:08, schrieb Lydia Pintscher: > > The bug is fixed. As Aaron said this thread will end here. > > thank you for https://bugs.kde.org/show_bug.cgi?id=270414#c43 > > this was the only result i have hoped with my initial mail > instead all the non helpfull "fix it by yourself"-rants i will revert the fix in the 4.7 branch tomorrow unless you do the following: a) apologize to everyone on this list for wasting their time and diminishing our community with your behaviour without any bullshit about how the results justified the means. i made the fix in spite of, not because of, you and your behaviour. despite me doing something nice, you are still squarely in the wrong. b) after you make that apology, stop posting to this mailing list. if you decide not to do the above, i will revert the change in the 4.7 branch tomorrow. i will include in the commit log your name and email address and CC it to the relevant bug report so that everyone who feels badly that they'll have to wait until 4.8 for the fix knows who to blame. see, you're not the only one who can play stupid games! -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
[ Comments below, in line ] On Wednesday, September 21, 2011 at 09:39 AM, Aaron J. Seigo penned about Re: why are bugs ignored over months? > [ snipped ] > > see, you're not the only one who can play stupid games! *sigh* Just a gentle reminder that two wrongs do not make a right. --- Pablo Sanchez - Blueoak Database Engineering, Inc Ph:819.459.1926 Fax: 760.860.5225 (US) >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Am 21.09.2011 15:39, schrieb Aaron J. Seigo: > On Wednesday, September 21, 2011 15:12:27 Reindl Harald wrote: >> Am 21.09.2011 15:08, schrieb Lydia Pintscher: >>> The bug is fixed. As Aaron said this thread will end here. >> thank you for https://bugs.kde.org/show_bug.cgi?id=270414#c43 >> >> this was the only result i have hoped with my initial mail >> instead all the non helpfull "fix it by yourself"-rants > i will revert the fix in the 4.7 branch tomorrow unless you do the following: > > a) apologize to everyone on this list for wasting their time and diminishing > our community with your behaviour without any bullshit about how the results > justified the means. i made the fix in spite of, not because of, you and your > behaviour. despite me doing something nice, you are still squarely in the > wrong. well, i apologize for some bad words from me i apologize for the not friendly-enough inital mail but i do NOT apologize for bringing a long existing bug to the mailing-list in the hope it will get fixed > > see, you're not the only one who can play stupid games! if you think i am playing games you did not understand my intention NOBODY here is playing games, there is software, there are bugs, they should be fixed and this has nothing to do with playing games my intention is only reporting bugs if they are there not more, not less my intention is to prevent new normal users giving up frustrated because of usability-problems on th emain-desktop if this is bad, yes then my intentions are bad signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Am Mittwoch, 21. September 2011, 20:17:57 schrieb Brad Hards: > I see lots of comments, so many people care. However there are a lot of > negative comments, so working on such a bug is pretty disheartening for a > developer. That's true! True as well is that most often the rate of negative comments increases with the time the bug gets no attention or stays unfixed, i.e. most reports start reasonable. After some time ~one month (one minor release) people start to not understand why there is no feedback/fix although there are potentially lots of confirmations/dups and offers to help testing patches. Especially if users try to help by testing patches (i.e. contribute what they are able to) and their attempt to help does not trigger any reaction from the devs. And don't get me wrong, I'm talking about bugs reproducible on different distros and by several users and not feature requests or "personal" bugs. If you want a "perfect" example of this check https://bugs.kde.org/show_bug.cgi?id=278891. So it is true as well that "real" bugs are not worked on although they have no negative comments for over a month and even a helpful audience. Not saying that one can demand anything – just stating that "bugs are not fixed because of the negative comments" is not a valid argument per se and of course the "conversation" within a bug report changes over time and that devs do play a role in it. To put it provocative – if you wait long enough every bug report will get a negative comment and thus can be marked as "users' fault that no dev works on it". Of course this also means that those reporting bugs and staying polite are punished because of the people that post comments weeks later. > When I read stuff that is nasty, mean or abusive, I often find something > else to do. Remember that this is a hobby for almost all developers. Very true. True as well though is that if somebody introduces a regression – it is reasonable that one expects the same person to show some interest in the issue and taking care of fixing it. It's not that easy to find that person but as a rule of thumb that's how reasonable people act in a community. If you brake something you fix it. > Another way to look at this is "why haven't you fixed it in the last six > months". If you don't know how, why haven't you learned? On its own that's really a bit of a killer argument and a bit too easy. Just apply it to every day's life and you will see that there are lots of things you criticise because you care yet do not learn in order to change them. And one should distinguish between different bits. Demanding a feature, a bug fix or a regression fix are different things. And demanding that broken things are fixed is not per se wrong – in contrary. The tone can be wrong and the style of doing so. No doubt. And of course one could contribute in other ways than learning, e.g. pay developers for bugs/features that are really annoying or important to oneself/a company but not important enough to the KDE devs to fix them. ~280 votes on the bug – x bugs for the fix. :-) To me it would not make sense to tell people that they cannot demand something because they get it for free but reject that they pay for it as well. To me the tone he used is not ok. But I do understand that if there is a bug (not feature request), reproducible on different distros and by many users with a lot of votes and hardly any attention from the devs over months – that it leads to questions regarding the commitment to fixing bugs of that bit of the KDE project. Even more so if a bug is due to a regression i.e. somebody broke code and does not care about fixing it. I'm not saying that this is the case here - but those issues exist and lead to frustration on user side – as the tone he used leads to frustration on dev side. Denying one or the other would be quite narrow minded IMO. So IMHO it would be useful to distinguish between the reasonable statements and the tone. Though I fully agree that it can be expected of adult people to skip the frustration when commenting and just stick to the facts. So for this bug the facts are that the folder view is a very prominent widget and that renaming is a basic operation. The bug seems to be reproducible by x+1 users on x+1 distros and thus seems "real". So who does he have to ask politely in order to get this fixed? And if asking politely is not what leads to a fix – what else could be done to avoid the blaming game when it comes to bugs (x+1 users on x+1 distros) that stay unfixed for weeks and months? Especially if it is a regression. Sven >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
thank you! the half-year no feedback and having this bug over major-releases and a lot of minor releases was the only reason for my tone and my tone will get harder everytime i get a useless "why do you not fix it" the whole KDE4.0 release makes me angry years later because it was a epic fail call it "4.0", wait for distributions prepare it for the next version and say later "but only for developers" Am 21.09.2011 15:52, schrieb Sven Burmeister: > Am Mittwoch, 21. September 2011, 20:17:57 schrieb Brad Hards: >> I see lots of comments, so many people care. However there are a lot of >> negative comments, so working on such a bug is pretty disheartening for a >> developer. > That's true! True as well is that most often the rate of negative comments > increases with the time the bug gets no attention or stays unfixed, i.e. most > reports start reasonable. After some time ~one month (one minor release) > people start to not understand why there is no feedback/fix although there > are > potentially lots of confirmations/dups and offers to help testing patches. > Especially if users try to help by testing patches (i.e. contribute what they > are able to) and their attempt to help does not trigger any reaction from the > devs. And don't get me wrong, I'm talking about bugs reproducible on > different > distros and by several users and not feature requests or "personal" bugs. > > If you want a "perfect" example of this check > https://bugs.kde.org/show_bug.cgi?id=278891. > > So it is true as well that "real" bugs are not worked on although they have > no > negative comments for over a month and even a helpful audience. Not saying > that one can demand anything – just stating that "bugs are not fixed because > of the negative comments" is not a valid argument per se and of course the > "conversation" within a bug report changes over time and that devs do play a > role in it. To put it provocative – if you wait long enough every bug report > will get a negative comment and thus can be marked as "users' fault that no > dev works on it". Of course this also means that those reporting bugs and > staying polite are punished because of the people that post comments weeks > later. > >> When I read stuff that is nasty, mean or abusive, I often find something >> else to do. Remember that this is a hobby for almost all developers. > Very true. True as well though is that if somebody introduces a regression – > it is reasonable that one expects the same person to show some interest in > the > issue and taking care of fixing it. It's not that easy to find that person > but > as a rule of thumb that's how reasonable people act in a community. If you > brake something you fix it. > >> Another way to look at this is "why haven't you fixed it in the last six >> months". If you don't know how, why haven't you learned? > On its own that's really a bit of a killer argument and a bit too easy. Just > apply it to every day's life and you will see that there are lots of things > you criticise because you care yet do not learn in order to change them. > > And one should distinguish between different bits. Demanding a feature, a bug > fix or a regression fix are different things. And demanding that broken > things > are fixed is not per se wrong – in contrary. The tone can be wrong and the > style of doing so. No doubt. > > And of course one could contribute in other ways than learning, e.g. pay > developers for bugs/features that are really annoying or important to > oneself/a company but not important enough to the KDE devs to fix them. ~280 > votes on the bug – x bugs for the fix. :-) To me it would not make sense to > tell people that they cannot demand something because they get it for free > but > reject that they pay for it as well. > > To me the tone he used is not ok. But I do understand that if there is a bug > (not feature request), reproducible on different distros and by many users > with a lot of votes and hardly any attention from the devs over months – that > it leads to questions regarding the commitment to fixing bugs of that bit of > the KDE project. Even more so if a bug is due to a regression i.e. somebody > broke code and does not care about fixing it. I'm not saying that this is the > case here - but those issues exist and lead to frustration on user side – as > the tone he used leads to frustration on dev side. Denying one or the other > would be quite narrow minded IMO. > > So IMHO it would be useful to distinguish between the reasonable statements > and the tone. Though I fully agree that it can be expected of adult people to > skip the frustration when commenting and just stick to the facts. > > So for this bug the facts are that the folder view is a very prominent widget > and that renaming is a basic operation. The bug seems to be reproducible by > x+1 users on x+1 distros and thus seems "real". > > So who does he have to ask politely in order to get this f
Re: why are bugs ignored over months?
[ Comments below, in line ] On Wednesday, September 21, 2011 at 10:01 AM, Reindl Harald penned about Re: why are bugs ignored over months? > the whole KDE4.0 release makes me angry years later because it was a > epic fail call it "4.0", wait for distributions prepare it for the > next version and say later "but only for developers" I think such passion is productive and shouldn't be penalized. If the language isn't to your liking, it could be because English is not Reindl's native tongue. I'm finally on KDE 4.6 because previous versions of KDE 4.X didn't suit my requirements. I stuck it out with KDE 3.5.x for a long while. Longer than I wanted. :) On the other hand, I'm /very/ happy with KDE 4.6 and I've goof'd around with 4.7.x a bit and filed one or two bugs. I can't wait to continue to move foward with KDE 4.x. Furthermore, I'm happy to see the KDE Development team quickly turn .x releases. I appreciate their and people like Reindl's effort. Cheers, --- Pablo Sanchez - Blueoak Database Engineering, Inc Ph:819.459.1926 Fax: 760.860.5225 (US) >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
But who do you think you are for taking a 'tone' that is harder? Are you paying the developers and they're not doing what you ask? No. Are you a contributer with a track record of delivering valuable code? No. Are you some random guy who gets abusive in bug reports and then stamps his feet in the mailing list like a petulant 2 year old when he doesn't get his way? Bingo! People have taken great pains to explain to you over and again that KDE is in the vast majority a volunteer effort. They have explained the nature of contribution and that sometimes people walk away from code leaving it un-maintained and that without new developers it is not always possible to cover that loss quickly. To make this clear: you are not helping, you are hurting. Your contributions to bug reports do more to demotivate than any information they provide helps. You are spamming a mailing list with an off-topic temper tantrum and have frustrated people who are in a position to help to the point where they are actively deciding not to. Just stop. On Wed, Sep 21, 2011 at 10:01 AM, Reindl Harald wrote: > thank you! > > the half-year no feedback and having this bug over > major-releases and a lot of minor releases was the > only reason for my tone and my tone will get harder > everytime i get a useless "why do you not fix it" > > the whole KDE4.0 release makes me angry years later > because it was a epic fail call it "4.0", wait for > distributions prepare it for the next version and > say later "but only for developers" > > Am 21.09.2011 15:52, schrieb Sven Burmeister: > > Am Mittwoch, 21. September 2011, 20:17:57 schrieb Brad Hards: > >> I see lots of comments, so many people care. However there are a lot of > >> negative comments, so working on such a bug is pretty disheartening for > a > >> developer. > > That's true! True as well is that most often the rate of negative > comments > > increases with the time the bug gets no attention or stays unfixed, i.e. > most > > reports start reasonable. After some time ~one month (one minor release) > > people start to not understand why there is no feedback/fix although > there are > > potentially lots of confirmations/dups and offers to help testing > patches. > > Especially if users try to help by testing patches (i.e. contribute what > they > > are able to) and their attempt to help does not trigger any reaction from > the > > devs. And don't get me wrong, I'm talking about bugs reproducible on > different > > distros and by several users and not feature requests or "personal" bugs. > > > > If you want a "perfect" example of this check > > https://bugs.kde.org/show_bug.cgi?id=278891. > > > > So it is true as well that "real" bugs are not worked on although they > have no > > negative comments for over a month and even a helpful audience. Not > saying > > that one can demand anything – just stating that "bugs are not fixed > because > > of the negative comments" is not a valid argument per se and of course > the > > "conversation" within a bug report changes over time and that devs do > play a > > role in it. To put it provocative – if you wait long enough every bug > report > > will get a negative comment and thus can be marked as "users' fault that > no > > dev works on it". Of course this also means that those reporting bugs and > > staying polite are punished because of the people that post comments > weeks > > later. > > > >> When I read stuff that is nasty, mean or abusive, I often find something > >> else to do. Remember that this is a hobby for almost all developers. > > Very true. True as well though is that if somebody introduces a > regression – > > it is reasonable that one expects the same person to show some interest > in the > > issue and taking care of fixing it. It's not that easy to find that > person but > > as a rule of thumb that's how reasonable people act in a community. If > you > > brake something you fix it. > > > >> Another way to look at this is "why haven't you fixed it in the last six > >> months". If you don't know how, why haven't you learned? > > On its own that's really a bit of a killer argument and a bit too easy. > Just > > apply it to every day's life and you will see that there are lots of > things > > you criticise because you care yet do not learn in order to change them. > > > > And one should distinguish between different bits. Demanding a feature, a > bug > > fix or a regression fix are different things. And demanding that broken > things > > are fixed is not per se wrong – in contrary. The tone can be wrong and > the > > style of doing so. No doubt. > > > > And of course one could contribute in other ways than learning, e.g. pay > > developers for bugs/features that are really annoying or important to > > oneself/a company but not important enough to the KDE devs to fix them. > ~280 > > votes on the bug – x bugs for the fix. :-) To me it would not make sense > to > > tell people that they cannot demand something because they get it for > fr
Re: Building kde-workspace with latest checkout
Aaron, My kdelibs its already on KDE/4.7: ggorosito@glaptop:~/kde/kdesrc/kde/kdelibs$ git pull origin KDE/4.7 >From git://anongit.kde.org/kdelibs * branchKDE/4.7-> FETCH_HEAD Already up-to-date. Do I need to do something else? Thanks ### # Gonzalo Gorosito # Programador && sysadmin # # http://www.tutorialesdebian.com - Tutoriales para debianeros, scripts, info, notícias y mucho mas. # http://www.ggorosito.com.ar - Website personal ### On Wed, Sep 21, 2011 at 8:51 AM, Aaron J. Seigo wrote: > On Wednesday, September 21, 2011 12:07:36 Hugo Pereira Da Costa wrote: >> Adding kde-core-devel, which is better suited for these kind of emails. >> >> Seems to me that trunk is actually not up to date for kdelibs, and that >> accessor to > > master is dead. do not use it. use the KDE/4.7 branch for building other KDE > software, or frameworks for development of kdleibs.. > > -- > Aaron J. Seigo > humru othro a kohnu se > GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > > KDE core developer sponsored by Qt Development Frameworks > > >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Building kde-workspace with latest checkout
On Wednesday, September 21, 2011 11:56:59 Gorosito Gonzalo wrote: > My kdelibs its already on KDE/4.7: it was part of commit 6ef2c70949c0188f72789b924d9d88b8fb72459e -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Building kde-workspace with latest checkout
I have this one here: commit 6ef2c70949c0188f72789b924d9d88b8fb72459e Author: Aaron Seigo Date: Mon Sep 19 16:18:52 2011 +0200 only allow valid values for the resize method, and add missing getters I also rebuilt kdelibs after I pulled from this branch. ### # Gonzalo Gorosito # Programador && sysadmin # # http://www.tutorialesdebian.com - Tutoriales para debianeros, scripts, info, notícias y mucho mas. # http://www.ggorosito.com.ar - Website personal ### On Wed, Sep 21, 2011 at 12:14 PM, Aaron J. Seigo wrote: > On Wednesday, September 21, 2011 11:56:59 Gorosito Gonzalo wrote: >> My kdelibs its already on KDE/4.7: > > it was part of commit 6ef2c70949c0188f72789b924d9d88b8fb72459e > > -- > Aaron J. Seigo > humru othro a kohnu se > GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 > > KDE core developer sponsored by Qt Development Frameworks > > >>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
goodbye
https://bugs.kde.org/show_bug.cgi?id=270414#c48 after we starting to get childish and revert bugfixes for over months ignored reports in major-components because personal problems i see no reason to spend MY TIME in making bugreports nobody cares after the next epic fail like label 4.0 with a version number which usually means "stable and for general use" or replacing subsystems worked for years with a pre-alpha like https://bugs.kde.org/show_bug.cgi?id=236025 maybe you will loose a larger number of users if this is the way kde wants to go do it, but sooner or later the developers maybe are alone with their software and happy because their will no netagive feedbback for things gong wrong any longer (also no positive, but who cares...) signature.asc Description: OpenPGP digital signature >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: why are bugs ignored over months?
Am Mittwoch, 21. September 2011, 15:39:57 schrieb Aaron J. Seigo: > On Wednesday, September 21, 2011 15:12:27 Reindl Harald wrote: > > Am 21.09.2011 15:08, schrieb Lydia Pintscher: > > > The bug is fixed. As Aaron said this thread will end here. > > > > thank you for https://bugs.kde.org/show_bug.cgi?id=270414#c43 > > > > this was the only result i have hoped with my initial mail > > instead all the non helpfull "fix it by yourself"-rants > > i will revert the fix in the 4.7 branch tomorrow unless you do the > following: > > a) apologize to everyone on this list for wasting their time and diminishing > our community with your behaviour without any bullshit about how the > results justified the means. i made the fix in spite of, not because of, > you and your behaviour. despite me doing something nice, you are still > squarely in the wrong. Are you trying to blackmail him and are threatening to punish the rest of the community and users? I hope I read you wrong – otherwise your behaviour would be – silly – to say it politely. > b) after you make that apology, stop posting to this mailing list. > > if you decide not to do the above, i will revert the change in the 4.7 > branch tomorrow. i will include in the commit log your name and email > address and CC it to the relevant bug report so that everyone who feels > badly that they'll have to wait until 4.8 for the fix knows who to blame. > > see, you're not the only one who can play stupid games! Honestly, if this gets into the wild it will potentially damage the KDE project's reputation and be used against it – because of your attitude and lack of sensitivity to not post such statements – even you you meant it in an ironic/sarcastic way [I hope you did!]. You are not just some KDE developer but one of the known KDE developers who represents the project in public. No matter what somebody else did – you should know better! Sovereignty looks different. Sven >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Notice of moderation
Hello all, due to recent activities and as being requested, this mailinglist is now set to full moderation, which means anyone will get moderated. This is not to make you uncomfortable, even the opposite. But don't worry, we are taking steps to have enough moderators to be in time and you don't need to wait days before your mail really gets on this list ;) So please still enjoy this place, have fun and be nice (no, that is not incompatible). Cheerio, Ingo Malchow >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Notice of moderation
A propos moderation: Can it be seen in the list-info anywhere if a list is moderated or not? Is kde-CORE-devel also set to full moderation or am I doing something wrong because even though I've subscribed all my mails await moderation. Thanks, Thomas On Wednesday 21 September 2011 20:19:00 Ingo Malchow wrote: > Hello all, > > due to recent activities and as being requested, this mailinglist is > now set to full moderation, which means anyone will get moderated. > This is not to make you uncomfortable, even the opposite. > But don't worry, we are taking steps to have enough moderators to be > in time and you don't need to wait days before your mail really gets > on this list ;) > So please still enjoy this place, have fun and be nice (no, that is > not incompatible). > > Cheerio, > Ingo Malchow > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to > >> unsubscribe << >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Notice of moderation
Buggers. It only takes one bad apple to spoil the applesauce lol. With recent events I'd like to say a great big thank you to all the devs. I love my Kde desktop and the associated apps therein. On Sep 21, 2011 2:23 PM, "Ingo Malchow" wrote: >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Notice of moderation
2011/9/21 Thomas Gahr : > A propos moderation: > > Can it be seen in the list-info anywhere if a list is moderated or not? > Is kde-CORE-devel also set to full moderation or am I doing something wrong > because even though I've subscribed all my mails await moderation. > > Thanks, > Thomas Hey Thomas, kde-core-devel is not (yet?) moderated. so no worries so far. We just need a way to have a better interaction and am searching for it. Take care, Cheerio Ingo Malchow > > On Wednesday 21 September 2011 20:19:00 Ingo Malchow wrote: >> Hello all, >> >> due to recent activities and as being requested, this mailinglist is >> now set to full moderation, which means anyone will get moderated. >> This is not to make you uncomfortable, even the opposite. >> But don't worry, we are taking steps to have enough moderators to be >> in time and you don't need to wait days before your mail really gets >> on this list ;) >> So please still enjoy this place, have fun and be nice (no, that is >> not incompatible). >> >> Cheerio, >> Ingo Malchow >> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Notice of moderation
On Wed, Sep 21, 2011 at 20:39, Thomas Gahr wrote: > A propos moderation: > > Can it be seen in the list-info anywhere if a list is moderated or not? I don't think so. > Is kde-CORE-devel also set to full moderation or am I doing something wrong > because even though I've subscribed all my mails await moderation. Yes everyone is moderated there until they're explicitly set to not moderated. We're usually pretty quick with moderating so that is hopefully not a problem. If someone could patch listadmin (a commandline moderation tool for mailman) to do this so I don't have to go to the webinterface that would increase setting this bit more often dramatically for me. At the moment it only allows approving, rejecting, discarding and skipping mails. Since I have a lot of lists to moderate I use listadmin instead of going to the webinterface for each of them. Cheers Lydia -- Lydia Pintscher KDE Community Working Group member http://kde.org - http://about.me/lydia.pintscher >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Notice of moderation
Oh yeah, let's say somthing nice about devs for a change, they really deserve it! I think it's hard to appreciate the effort they're investing. As a Linux user I know a few different communiites and the KDE community can without any doubt be called one of the nicest. Having contributed my first teeny tiny patch a few days ago I was quite nervous to approach "the devs" and really thrilled about the kindness & patience of people. So: great big thank you from me, too! I love KDE and this includes the community and the people behind it for making it happen! On Wednesday 21 September 2011 14:30:33 Dale Trombley wrote: > Buggers. It only takes one bad apple to spoil the applesauce lol. With > recent events I'd like to say a great big thank you to all the devs. I love > my Kde desktop and the associated apps therein. > On Sep 21, 2011 2:23 PM, "Ingo Malchow" wrote: >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
(documentation) I'm pissed off! ... so I'm going to do something about it ... :)
Howdy, Please accept my Subject as an attempt to lighten the recent activity on the list. :) What I'd like to do is contribute to writing documentation for the `Window-Specific Settings' I don't have a clear understanding of how some of the features work and what better way to figure it out than to write some documentation. Ha! My plan would be to write something which I can weave in my day to day work. I think it'll take me a while because like everyone else, I'm super busy. Sooo, whom should I contact? At some point I'll need a technical contact who can explain certain buttons, etc. But that's later. Thanks a lot! --- Pablo Sanchez - Blueoak Database Engineering, Inc Ph:819.459.1926 Fax: 760.860.5225 (US) >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: (documentation) I'm pissed off! ... so I'm going to do something about it ... :)
Hi Pablo, great to hear you want to help. On Wed, Sep 21, 2011 at 21:37, Pablo Sanchez wrote: > Howdy, > > Please accept my Subject as an attempt to lighten the recent activity > on the list. :) > > What I'd like to do is contribute to writing documentation for the > `Window-Specific Settings' > > I don't have a clear understanding of how some of the features work > and what better way to figure it out than to write some > documentation. Ha! > > My plan would be to write something which I can weave in my day to day > work. I think it'll take me a while because like everyone else, I'm > super busy. > > Sooo, whom should I contact? At some point I'll need a > technical contact who can explain certain buttons, etc. But that's > later. For documentation on userbase.kde.org I'd recommend talking to Anne Wilson. For KWin-specific stuff Martin Gräßlin can help you. They're CC'd. Cheers Lydia -- Lydia Pintscher KDE Community Working Group member http://kde.org - http://about.me/lydia.pintscher >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: (documentation) I'm pissed off! ... so I'm going to do something about it ... :)
[ Comments below, in line ] On Wednesday, September 21, 2011 at 03:53 PM, Lydia Pintscher penned about Re: (documentation) I'm pissed off! ... so I'm going to do something about it ... :) > Hi Pablo, > > great to hear you want to help. Hi Lydia, As I tell my wife, there is no `they' nor `someone' (as in `_someone_ should do something about that ...'), only `us' :) > For documentation on userbase.kde.org I'd recommend talking to Anne > Wilson. For KWin-specific stuff Martin Gräßlin can help you. They're > CC'd. I'll ping Anne directly to get any templates, standards, etc set up on my end. After, I'll pester^H^H^H^H^Hing Martin with questions. :) Cheers, --- Pablo Sanchez - Blueoak Database Engineering, Inc Ph:819.459.1926 Fax: 760.860.5225 (US) >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: (documentation) I'm pissed off! ... so I'm going to do something about it ... :)
Am Wed, 21 Sep 2011 15:37:48 -0400 schrieb Pablo Sanchez : > I don't have a clear understanding of how some of the features work > and what better way to figure it out than to write some > documentation. Ha! Since the the UI revamp goes onto my account and i hoped to have clarified some things - what's in particular remaining uncertain? (Not diminishing your efforts, but i'd preferably have a solution that does not invoke reading a manpage for a GUI ;-) Cheers, Thomas >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Building kde-workspace with latest checkout
ggorosito@glaptop:~/kde$ ./kdesrc-build kdelibs kde-workspace * Downloading projects.kde.org project database... Script started processing at Wed Sep 21 12:52:53 2011 <<< Build Process >>> Building kdelibs (1/2) Waiting for source code update. Running cmake... Compiling... Build succeeded after 5 minutes, and 48 seconds. Installing kdelibs. Overall time for kdelibs was 6 minutes, and 6 seconds. Building kde-workspace (2/2) Waiting for source code update. Source update complete for kde-workspace: 207 files affected. Running cmake... Compiling... Build succeeded after 8 minutes, and 6 seconds. Installing kde-workspace. Overall time for kde-workspace was 8 minutes, and 29 seconds. <<< Build Done >>> <<< PACKAGES SUCCESSFULLY BUILT >>> kdelibs kde-workspace all done!! ### # Gonzalo Gorosito # Programador && sysadmin # # http://www.tutorialesdebian.com - Tutoriales para debianeros, scripts, info, notícias y mucho mas. # http://www.ggorosito.com.ar - Website personal ### On Wed, Sep 21, 2011 at 12:20 PM, Gorosito Gonzalo wrote: > I have this one here: > > commit 6ef2c70949c0188f72789b924d9d88b8fb72459e > Author: Aaron Seigo > Date: Mon Sep 19 16:18:52 2011 +0200 > > only allow valid values for the resize method, and add missing getters > > I also rebuilt kdelibs after I pulled from this branch. > > ### > # Gonzalo Gorosito > # Programador && sysadmin > # > # http://www.tutorialesdebian.com - Tutoriales para debianeros, > scripts, info, notícias y mucho mas. > # http://www.ggorosito.com.ar - Website personal > ### > > > > On Wed, Sep 21, 2011 at 12:14 PM, Aaron J. Seigo wrote: >> On Wednesday, September 21, 2011 11:56:59 Gorosito Gonzalo wrote: >>> My kdelibs its already on KDE/4.7: >> >> it was part of commit 6ef2c70949c0188f72789b924d9d88b8fb72459e >> >> -- >> Aaron J. Seigo >> humru othro a kohnu se >> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 >> >> KDE core developer sponsored by Qt Development Frameworks >> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << >> >> > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: goodbye
Reindl, Sorry to see you go. I don't know why Aseigo is being childish - I think this is all just taking its toll on him. This is one of the advantages that companies have and we don't have - we can't pay people to fix the essential things that are boring to do. I would really like to see bounties being raised for bugs. There are a lot of problems with having bounties, and in the past such an idea has been shot down, but maybe it's worth revisiting. If users care about a bug being fixed, perhaps they would be willing to put up a small amount of money towards it being fixed. If enough users do that, it entices developers to fix the bug. John >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: (documentation) I'm pissed off! ... so I'm going to do something about it ... :)
[ Comments below, in line ] On Wednesday, September 21, 2011 at 04:24 PM, Thomas Lübking penned about Re: (documentation) I'm pissed off! ... so I'm going to do something about it ... :) > Am Wed, 21 Sep 2011 15:37:48 -0400 > schrieb Pablo Sanchez : > > > I don't have a clear understanding of how some of the features > > work and what better way to figure it out than to write some > > documentation. Ha! > > Since the the UI revamp goes onto my account and i hoped to have > clarified some things - what's in particular remaining uncertain? > (Not diminishing your efforts, but i'd preferably have a solution > that does not invoke reading a manpage for a GUI ;-) Hi Thomas, I hope this message isn't too detailed. I'm only going to mention what is unclear rather than what's clear. The specific settings are in the `Edit Window-Specific Settings - KDE Control Module' window. Window Tab == o Substring - I'm going to guess this is equivalent to performing an `fgrep' In other words, no RE support, just see if the string is found. o Regular Expression - I understand RE's. However there are different implementations so what would be interesting is to know and document which RE types we're using. Best by example. Hmmm, is this equivalent to a `grep'? :) Also, I'd like to know if `123*' is defined as `12' + potentially `3'. If someone wanted to specify `123' followed by zero or more characters, they'd need to specify `123.*' rather than `123*' Window Extra I believe `Window Extra' implies additional criteria to identify a window. What's not clear to me is how `Window types:' comes into play. Does each `Window type' get its own criteria specified in the bottom half of the window? o Window title: o Extra role: o Machine (hostname): Geometry We have different attributes such as: `Maximum horizontally', `Fullscreen', etc. For each attribute, we have the following options: o Do Not Affect o Apply Initially o Remember o Force o Apply Now o Force Temporarily Specifically, what do the above attributes do and when are they applied? Does an application need to be restarted before they're applied? Do we need to log out of our session and log back in before they're effective? (Sorry for such silly questions ... :\) Furthermore, some attributes, such as `Maximized horizontally' have a checkbox after their option. What's the purpose of the checkbox? Workarounds === o `Focus stealing prevention' - I believe if I had an application which started up and stole the focus, I'd use this setting. Cool. o `Window type' - I'm unclear on the purpose of this attribute. I see when I select `Force', I have an additional set of tweaks: `Normal Window', `Dialog Window', etc. How is this attribute used in relationship to a Workaround? Thanks a lot! And again, I apologize if these questions are silly. I did try and google a while ago and recently and I couldn't find any clear documentation. Which is why I thought I'd volunteer to write it. :) Cheers, --- Pablo Sanchez - Blueoak Database Engineering, Inc Ph:819.459.1926 Fax: 760.860.5225 (US) >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Building kde-workspace with latest checkout
Hi, I just cloned kde-libs,kde-workspace,kde-baseapps with this steps: mkdir $BRANCH cd $BRANCH git init git remote add -t $BRANCH -f origin $REMOTE_REPO git checkout $BRANCH Then compile everything without problem. On 9/22/11, Gorosito Gonzalo wrote: > I have this one here: > > commit 6ef2c70949c0188f72789b924d9d88b8fb72459e > Author: Aaron Seigo > Date: Mon Sep 19 16:18:52 2011 +0200 > > only allow valid values for the resize method, and add missing getters > > I also rebuilt kdelibs after I pulled from this branch. >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
Re: Notice of moderation
On 09/21/2011 07:19 PM, Ingo Malchow wrote: Hello all, due to recent activities and as being requested, this mailinglist is now set to full moderation, which means anyone will get moderated. This is not to make you uncomfortable, even the opposite. But don't worry, we are taking steps to have enough moderators to be in time and you don't need to wait days before your mail really gets on this list;) So please still enjoy this place, have fun and be nice (no, that is not incompatible). Moderation isn't good, and I hope that this change is reverted. I understand that posts may be unhelpful and even unpleasant, but there is something fundamentally wrong with the idea that some people must waste their time censoring a communication medium and it less efficient just because some users have a hard time ignoring some posts. Rui Maciel Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
