RE: Bug#88623: Should not suggest manipulating others' bugs
Ah, but in that case, the bugs were YOUR bugs, even if they were assigned
against other people's packages, so you had every right to close them for
the other maintainers. I think that falls into the "don't mess with stuff
you don't understand" bit. You obviously understood the bug cause you
created it. The only thing I would have done differently is maybe reassign
the bugs to libpam-modules before you closed them, so the other maints
didn't notice the closed bugs and say "hey, I didn't fix that". But that's
a bit more work.. <shrug>
I don't think this sort of thing should be policy at all, I just think there
should be some very clear guidelines posted publicly, so that people can be
helpful (that's really a big part of Debian, in my opinion) without being
... Adam Conrad
> -----Original Message-----
> From: Ben Collins [mailto:email@example.com]On Behalf Of Ben Collins
> Sent: Monday, March 05, 2001 3:28 PM
> To: Adam Conrad
> Cc: 'Colin Watson'; firstname.lastname@example.org;
> email@example.com; 'Ben Harris'
> Subject: Re: Bug#88623: Should not suggest manipulating others' bugs
> On Mon, Mar 05, 2001 at 01:20:58PM -0700, Adam Conrad wrote:
> > In closing: Organizing bugs good. Helps people out.
> Screwing with stuff
> > you don't understand bad. Closing other people's bugs bad.
> Not always true. For instance, PAM was recently broken (by me, as the
> maintainer of PAM). SSH and cron are getting a lot of bugs reported
> against them because of that breakage. I, being subscribed to
> -bugs-dist, have been trying to catch all of them and close
> them with an
> informative message, so that my breakage does not have to
> cause too much
> work for those maintainers.
> If I followed some sort of policy such as this, I would not be able to
> do so (and I would be willing to bet that the cron and ssh maintainers
> appreciate me doing this).
> I don't think we need to enforce some sort of policy here.
> IMO, we would
> be better off with guide lines and etiquette suggestions. If
> we are too
> restrictive then we will only create bad situations.
> / Ben Collins -- ...on that fantastic voyage... --
> Debian GNU/Linux \
> ` firstname.lastname@example.org -- email@example.com --
> firstname.lastname@example.org '