Re: How long should it take to fix a obvious memory leak?

[Sriram Ramkrishna <sri ramkrishna me>]

This is a fruitless discussion.

Let me explain a little what people are trying to communicate to you.  You're looking at this in a very rigid manner.

In an open source community, your credentials matter.  When your positive, we're positive, if you're sour, well you're going to get a likewise reaction.  If you're ultimate goal is to get the bug fixed then you' need to social engineer to do it.  Sometimes that just means that you might have to take over maintainership.  That's how a lot of people got to become maintainers or core developers because the took something that annoyed them and fixed it.  "Open" in open source means that you have the ability to address problem directly rather than waiting on others.

Barring that, you'll have to be polite and observe the social niceties.  This should not be particularly new to you.  We do this every day not in just in a open source project but in our daily lives.  All you're doing right now is antagonizing people here and you're no closer to fixing your bug, but instead you just have people mad at you.  It's a fruitless discussion.

sri 

On Thu, Apr 4, 2013 at 9:08 AM, Ma Xiaojun <damage3025 gmail com> wrote:

On Fri, Apr 5, 2013 at 12:05 AM, Olav Vitters <olav vitters nl> wrote:
> Every software has bugs. GNOME has loads. We have Bugzilla to track
> them. Help is appreciated to fix these, but pretty much all the
> developers know that there are bugs.
>
> Sometimes bugs are forgotten and just a ping is enough to get some
> progress in a bug.

So I brought up a honest question, how long should a bug be fixed.
This should be a scientific measure of "Quality of Support".

> The entire "OMG there is a bug" thing is not impressive.

Well, what's wrong if I just said OMG?

_______________________________________________
desktop-devel-list mailing list
desktop-devel-list gnome org
https://mail.gnome.org/mailman/listinfo/desktop-devel-list