[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Allow money donations for precise bugs
From: Waldo Bastian <bastian () kde ! org>
Date: 2005-03-14 0:51:33
Message-ID: 200503140151.37449.bastian () kde ! org
[Download RAW message or body]
[Attachment #2 (multipart/signed)]
On Monday 14 March 2005 00:34, Mathias Homann wrote:
> > > who was that again, suse?
> >
> > Well, it's good that you mention my employer. My employer actually
> > cares about its paying (!) customers.
>
> well, if you imply that i did not buy the suse which i run on several
> computers, i could send you pictures of all the suse boxes i have
> somewhere over there *points at shelf* ;) but that's beyond the scope
> of kde-devel ;)
>
> > And when my employer gets the
> > impression that a significant part of its paying customers would
> > like to have a certain feature, it will direct paid developers
> > (like me) to implement those features. It does that in the hope to
> > get that investment repaid in the form of increased product sales.
>
> too bad that suse (note that i assume that you still work for them and
> not for someone else, based on an interview on kde-people which is a
> few years old by now) doesnt check the votes for the wishlist entry
> which i was orginally referring to...
That's a good point indeed, I will see if I can improve suse's performance
there.
> anyhow, i had the impression that assigning a bug/wish to a certain
> developer means that that person HAS to do it in a certain timeframe
> unless he's too busy with more important stuff...
If the developer assigns it himself it usually indicates an intention on
his/her part to work on it.
> given the fact that you cannot vote higher than 20 for any given bug
> or feature on the kde bugzilla, at least 200 people DO care for that
> specific one, it has 2150 votes.
> So, here's the point again: it seems that some developers do not care
> about other opinions about features/bugs than their own. which makes
> giving feedback a bit of a moot point...
No, giving feedback is not moot, but just because you voice your opinion will
not mean that developers always follow that opinion. It's like voting on
election day, it's important to do, but at the same time it doesn't mean that
your party always wins.
> > You seem to care, you have the ability to pay the kmail developer to
> > get it done, yet you don't do so.
>
> who said that? I never said that i wouldnt want to pay for a
> feature... But i would really like to be SURE that it gets
> implemented in a reasonable time frame, before i donate whatever i
> can spare (which is not that much). Besides, there are some cases
> where i noticed that the fact that any given bug or feature is marked
> as "fixed" ("implemented", respectively) in the kde bugzilla, does
> not mean that this feature appears in the next released KDE...
It typically means that it is fixed for the next major release (x.y) if the
fix is simple it may get backported for the next bugfix release (x.y.z)
> as i already said, i do know that point.
> MY point is, that more often than not, it _FEELS_ like the developers
> happily ignore the feedback they get, for whatever reasons.
I don't think I can change the feeling, but if you look at
http://bugs.kde.org/weekly-bug-summary.cgi then I think KDE developers are
fairly responsive. At the same time you will notice that almost every week we
get more new bugreports than that we are able to process in that week.
> > It's a bit like the fairy tale about the goose that laid
> > golden eggs, you need to keep the goose healthy and happy to
> > benefit from the eggs. Throwing euros at it doesn't help if all it
> > wants is love and care.
>
> to stick with the picture: its hard to love and care for a goose that
> keeps hissing at you and snapping at your fingers ;)
Lets hope then that this thread in the end improved the mutual understanding a
bit more.
> bye,
> MH
>
> on a totally unrelated sidenote, how do i get my selfmade kde
> screensaver into kde3-extragear or whereever it belongs?
Send a mail to kde-core-devel@kde.org about it, if the concensus is that it
should go into KDE CVS (or at least if there is no strong objection after two
days or so), you can mail sysadmin@kde.org for CVS access [1] and
the sysadmins can import your code into the kdereview CVS module and after it
has received a bit of review and works ok with the KDE build system it can
move to the module where it belongs to based on the consensus on
kde-core-devel.
Cheers,
Waldo
[1] http://developer.kde.org/documentation/other/developer-faq.html#q1.8
[Attachment #5 (application/pgp-signature)]
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]