Hi everyone,

can we please stop the ad hominem= s and stick to constructive suggestions to improve things please? this is b= ecoming disgusting and is a poor display of community dynamics

Thank you.

2018-02-05 16:36 GMT+01:00 Morten Welinder <mortenw@gnome.org><= /span>:

> Your behavi= our on this mailing list, and on Bugzilla, has been
> consistently rude, inconsiderate, and plain abusive of the patience > and effort that volunteers put in the platform you're consuming.
You have absolutely no respect for the work of other volunteers to t= he gtk+
project or for people whose opinions aren't aligned with you.=C2=A0 You= put a high
value on your own disruptive work, and a value of zero on anyone else.

So, yeah, I don't like you.=C2=A0 And you probably don't like me.
Morten

On Mon, Feb 5, 2018 at 9:15 AM, Emmanuele Bassi <ebassi@gmail.com> wrote:
> On 5 February 2018 at 13:19, Morten Welinder <mortenw@gnome.org> wrote:
>>> Considering that you usually stop short of the first step I ha= ve to
>>> ask you: what kind of "busywork" have you ever exper= ienced?
>>
>> Here's a sample:
>> https://bugzilla.gnome.org/show_= bug.cgi?id=3D694627#c7
>>
>> Yes, that was you.=C2=A0 What did you really gain from asking that=
>> question, other than verifying that I read my email?
>
> I gained the fact that you read your email and if you're still
> experiencing the issue, or if it was accidentally fixed in the ~4
> years between your original report and me going through the open bugs<= br> > of gobject-introspection. That's why it was marked as NEEDINFO. >
> As soon as you replied, the bug was reinstated as NEW and will be
> migrated to the gobject-introspection repository on gitlab.gnome.org= .
>
>> The more typical sample -- not recently practiced by gtk+ -- is ma= ss
>> moving of bugs into NEEDINFO with a note saying something like
>> "This bug was reported for version x.y. Please test if it sti= ll applies.=C2=A0 If
>> we get no response, this bug will be closed in 30 days."
>
> Which is what Matthias has said we're going to do in the email you=
> replied to =E2=80=94 and it's also implied in the NEEDINFO state a= s it's used
> by GNOME projects.
>
>> The reason I call that busywork is that you can actually do as ask= ed
>> only to repeat the whole thing in a year when no-one has looked at=
>> in the meantime.=C2=A0 And repeat it a year after that.=C2=A0 And = multiply all that
>> by the number of open bugs you have.
>
> Oh, I'm sorry you're *so* inconvenienced by volunteers trying = to get
> the bug count under control, and cannot replicate every single set up<= br> > from 5 years ago.
>
>> Quite frankly, the rational response to such periodic requests is = to
>> simply answer "the bug is still there" without going thr= ough the work
>> of checking.
>
> So, you're basically just making shit up?
>
> That's *really* great to know, because now I won't feel compel= led at
> all to act on bug reports coming from you.
>
> Next time, either don't bother, or just be a decent human being, a= nd
> answer "I don't know".
>
>>=C2=A0 That's rational for the bug reporter because it preserve= s
>> the investment of time that was put into reporting the bug without=
>> spending more maintaining an large portfolio of open bugs.
>
> That's the "rational" thing to do if you're just abu= sing the ecosystem
> you're taking advantage of.
>
> Again, that's a great thing to know.
>
>>> Of course it is, that's why we generally don't do that= =E2=80=94 except,
>>> maybe, for rude bug reporters.
>>
>> You really don't like to be called out, do you?=C2=A0 (And, ye= s, I know I am
>> occasionally and deliberately rude.=C2=A0 The email you responded = to was
>> not rude; it's just that you don't take criticism well, if= at all.)
>
> Your behaviour on this mailing list, and on Bugzilla, has been
> consistently rude, inconsiderate, and plain abusive of the patience > and effort that volunteers put in the platform you're consuming. >
> You've been called out before, multiple times, about this.
>
> Of course, you can now spin it the way you want it, and say it's m= e
> that doesn't like being called out. I'll just remember it for = the next
> time you open a bug, explaining what *I* have to do, without even
> bothering to attach a patch. Or reply "this bug still exists"= ; without
> testing it, because you're too busy with your own stuff.
>
> Ciao,
>=C2=A0 Emmanuele.
>
>> On Mon, Feb 5, 2018 at 5:37 AM, Emmanuele Bassi <ebassi@gmail.com> wrote:
>>> On 4 February 2018 at 20:52, Morten Welinder <mortenw@gnome.org> wrote:
>>>> As a general principle, you should only ask bug reporters = to do work if you
>>>> intend to do something with the answer.=C2=A0 Or, with oth= er words, it really is
>>>> not nice to keep asking "is that bug still there?&quo= t; until they get tired of the
>>>> busywork and leave in disgust.
>>>
>>> The busywork meaning "attaching a patch and iterating ove= r it"?
>>> Considering that you usually stop short of the first step I ha= ve to
>>> ask you: what kind of "busywork" have you ever exper= ienced?
>>>
>>> Of course if we get a positive response that the bug is still = there
>>> we're going to migrate it and keep track of it.
>>>
>>>> With that in mind, I believe it is much nicer to just leav= e the old bugs there.
>>>
>>> The old bugs will be left there, but closed, so we don't n= eed to check
>>> two bug lists, and split the maintenance resources even more.<= br> >>>
>>>> We never got around to solving the reporter's problem,= but at least we did
>>>> not add to the pain by asking them to do work and report b= ack, only to
>>>> ignore the result of that.=C2=A0 Doing that is quite rude.=
>>>
>>> Of course it is, that's why we generally don't do that= =E2=80=94 except,
>>> maybe, for rude bug reporters.
>>>
>>> Ciao,
>>>=C2=A0 Emmanuele.
>
>
>
> --
> = https://www.bassi.io
> [@] ebassi [@gmail.com]
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/g= tk-devel-list

Cheers,
Alberto = Ruiz

--001a113d362e174a05056478eaca-- --===============3063150076354960318== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list --===============3063150076354960318==--