On 2013-04-06, Filipus Klutiero wrote:
> It's not a /good/ way in absolute terms, but it's pretty much the only
> way for now, so I guess it's currently the best way (see
> https://lists.debian.org/debian-project/2011/11/msg00030.html ).
My experience with contacting owner@bugs, listmaster, wik
On Saturday, April 06, 2013 19:55:08, Filipus Klutiero wrote:
> Hi Chris,
> thanks for being faithful to our project and bringing up this topic :-S
>
> Chris Knadle wrote:
> > From the point of view of the bug reporter, the message the DD has sent
> > (whether intended or not) is "I'm not even go
On Sunday, April 07, 2013 03:40:02, Andrei POPESCU wrote:
> On Ma, 02 apr 13, 17:34:28, Russ Allbery wrote:
> > > Starting off with a maintainer that closes my bug report with no
> > > explanation at all? How do I join the team, when the team refuses to
> > > communicate? Why would I make another
On Ma, 02 apr 13, 17:34:28, Russ Allbery wrote:
>
> > Starting off with a maintainer that closes my bug report with no
> > explanation at all? How do I join the team, when the team refuses to
> > communicate? Why would I make another bigger offer my time, when the
> > team doesn't offer theirs e
Ian Jackson wrote:
If you and your allies have enough time and knowledge to help with the
package, then yes, you can certainly help with this.
You could write to the maintainers:
I notice you closed my bug without comment, so I went to take a look
at the rest of the bugs for gnomovision.
Ian Jackson wrote:
[...] Of course we do need bug reports to be able to tell what's wrong so
that we know what to fix. But many packages have so many bug reports
that there is already not enough time to deal with them all
thoroughly. In that case it is better to cherry-pick the ones which
seem
Hi Ian,
Ian Jackson wrote:
[...] To reiterate: the purpose of bug reports is to help improve the
software. In Debian, the maintainer(s) are in charge of deciding (in
the first instance) what counts as an improvement, and which
improvements are most important. But they are also in charge of
dec
Hi Chris,
thanks for being faithful to our project and bringing up this topic :-S
Chris Knadle wrote:
From the point of view of the bug reporter, the message the DD has sent
(whether intended or not) is "I'm not even going to dignify this with a
response. *click* " It's not /only/ this rudene
[Moving this to -project]
Stefano Zacchiroli wrote:
On Thu, Mar 28, 2013 at 05:37:18PM -0400, Chris Knadle wrote:
> Technically the DAM has the ability to act to remove a DD (per Debian
> Constitution 8.1 item 2), but the information I can gather so far seems to
> indicate that the DAM won't
On Wed 03 Apr 2013 23:50:10 Russ Allbery escribió:
[snip]
> I do think that debian-mentors helps a great deal here, not just in
> helping people with their problems but in modeling a social interaction
> style for people who are new to the project. It is, by and large, quite
> polite and construc
:
> > Chris Knadle writes ("Re: [all candidates] Removing or limiting DD
> rights?"):
> > > On Tuesday, April 02, 2013 13:53:24, Ian Jackson wrote:
[…]
> > > > Of course if a maintainer inappropriately adopts such an aggressive
> > > > approach to bug t
I'm going to move this fully onto -project, since we're into the voting
phase and I think this is more of a general project discussion at this
point. Hope that doesn't lose anyone.
Chris Knadle writes:
> Good question.
> I can say this: Debian's BTS is the only bug tracker in which I've ever
>
On Wednesday, April 03, 2013 09:40:50, Ian Jackson wrote:
> Chris Knadle writes ("Re: [all candidates] Removing or limiting DD
rights?"):
> > On Tuesday, April 02, 2013 13:53:24, Ian Jackson wrote:
> > > The purpose of a bug report is not to help solve t
Ian Jackson writes:
>> From the point of view of the bug reporter, the message the DD has
>> sent (whether intended or not) is "I'm not even going to dignify
>> this with a response. *click* " It's not /only/ this rudeness
>> that's the problem, though; the bug reporter has now been handed a
>> p
Chris Knadle writes ("Re: [all candidates] Removing or limiting DD rights?"):
> On Tuesday, April 02, 2013 13:53:24, Ian Jackson wrote:
> > The purpose of a bug report is not to help solve the submitter's
> > problem.
>
> ... No, I don't agree with this.
On 03.04.2013 06:09, Chris Knadle wrote:
On Tuesday, April 02, 2013 20:34:28, Russ Allbery wrote:
Note that we already did do something about it by deprecating close
in the
BTS in favor of sending a real email message to -done that is copied
to
the submitter. The Debian BTS now nags the mainta
Tollef Fog Heen writes:
> ]] Russ Allbery
> (Cc to owner@bugs, M-F-T to -project.)
>> Note that we already did do something about it by deprecating close in the
>> BTS in favor of sending a real email message to -done that is copied to
>> the submitter. The Debian BTS now nags the maintainer a
]] Russ Allbery
(Cc to owner@bugs, M-F-T to -project.)
> Note that we already did do something about it by deprecating close in the
> BTS in favor of sending a real email message to -done that is copied to
> the submitter. The Debian BTS now nags the maintainer about telling the
> submitter som
On Tuesday, April 02, 2013 20:34:28, Russ Allbery wrote:
> Chris Knadle writes:
> > Seriously, what I'm trying to do is lower the number of cases which
> > cause frustration and which don't get any traction. Between the "
> > *close* " problem, the maintainers that are MIA without the package
> >
Chris Knadle writes:
> Seriously, what I'm trying to do is lower the number of cases which
> cause frustration and which don't get any traction. Between the "
> *close* " problem, the maintainers that are MIA without the package
> being orphaned, maintainers dropping working on a particular pack
I'm on the -project list, so no need to CC me directly. (Fine if you do,
though.)
On Tuesday, April 02, 2013 13:53:24, Ian Jackson wrote:
> Chris Knadle writes ("Re: [all candidates] Removing or limiting DD
rights?"):
> > The #1 kind of bug reports that become proble
On 02-04-13 19:53, Ian Jackson wrote:
> Chris Knadle writes ("Re: [all candidates] Removing or limiting DD rights?"):
>> The #1 kind of bug reports that become problems are ones that go like this:
>>
>> - bug reporter: writes polite and detailed bug report
&g
Ian Jackson writes ("Re: [all candidates] Removing or limiting DD rights?"):
...
> If in this situation there is a possibility of the submitter's
> experience being turned into an improvement in the software, it could
> arise if the submitter
... can investigate further
Chris Knadle writes ("Re: [all candidates] Removing or limiting DD rights?"):
> The #1 kind of bug reports that become problems are ones that go like this:
>
> - bug reporter: writes polite and detailed bug report
> - maintainer : *cloeses bug* without discussion
>
On Fri, 29 Mar 2013, Moray Allan wrote:
> On 2013-03-28 16:35, Don Armstrong wrote:
> >ow...@bugs.debian.org is an appropriate place to report abusive
> >behavior by anyone (maintainers, users, etc) on the BTS.
>
> But how broad a definition of abusive behaviour are you taking here?
>
> I would h
On Thursday, March 28, 2013 18:35:40, Don Armstrong wrote:
> On Thu, 28 Mar 2013, Chris Knadle wrote:
> > As a bug reporter dealing with a misbehaving maintainer, this is
> >
> > what I would want:
> > 1. A clear place to report the misbehavior
>
> ow...@bugs.debian.org is an appropriate place
Stefano Zacchiroli wrote:
> Well, I certainly didn't mean to imply that bug report handling is not
> something we should look into improving. It's the causation relationship
> between that and the decreasing number of bug reports which seems
> unlikely to me.
I think it is likely a real factor, t
Don -- my apologies for not responding to this earlier; somehow I missed this
message, and figured out I had missed it via reading Moray's resonse to it.
On Thursday, March 28, 2013 18:35:40, Don Armstrong wrote:
> This message appears to be more appropriate for -project,
> non-candidate response
On 2013-03-28 16:35, Don Armstrong wrote:
ow...@bugs.debian.org is an appropriate place to report abusive
behavior by anyone (maintainers, users, etc) on the BTS.
But how broad a definition of abusive behaviour are you taking here?
I would have thought of contacting ow...@bugs.debian.org in re
This message appears to be more appropriate for -project,
non-candidate responses, please follow up there.
On Thu, 28 Mar 2013, Chris Knadle wrote:
> As a bug reporter dealing with a misbehaving maintainer, this is
> what I would want:
>
> 1. A clear place to report the misbehavior
ow...@bugs
30 matches
Mail list logo
