public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Per Bothner" <per@bothner.com>
Cc: "Ulrich Drepper" <drepper@redhat.com>, overseers@sources.redhat.com
Subject: Re: bugzilla account removal
Date: Mon, 19 Feb 2007 16:05:00 -0000	[thread overview]
Message-ID: <4aca3dc20702190805g4532d782r6733ae89694a8ab1@mail.gmail.com> (raw)
In-Reply-To: <45D94845.8020302@bothner.com>

On 2/19/07, Per Bothner <per@bothner.com> wrote:
> Ulrich Drepper wrote:
> > Frank Ch. Eigler wrote:
> >> This bugzilla
> >> account can of course be removed, but another can be readded instantly
> >> at the same or a different email address.
> >
> > I understand this.  But then this is sufficient evidence to show to the
> > ISP that this person is misusing his net access.
>
> Escalating to his ISP seems a bit excessive.  When I've searched for
> his name in Gcc and glibc bugzillas his bug reports and comments seem
> generally on-topic.  In this case it seems we have two stubborn Germans
> disagreeing over the meaning of "WONTFIX" ...  However, as
> maintainer you should be allowed to interpret "WONTFIX" for your
> project - and I think your interpretation is a reasonable one.
> (There is a practical goal of being able to use BugZilla to keep
> track of what needs to be done.   It seems reasonable to me that
> wishlist items with no commitment get marked as WONTFIX, though
> tweaking priorities/severities is another approach.)
>
> I.e.  I agree you're entitled to close the bug, but I think the issue
> can be resolved with a little diplomacy.  I can send him an email
> telling he why he should desist, if you don't mind.
> --

What he said.

I do plan on upgrading our bugzilla installs to a version that does
actually allow real "banning" (Right now we can only disable
accounts).

I'm simply waiting for the promised release of 3.0 (new dev version
came out on the 12th, so hopefully not too long) which will allow
serving multiple bugzillae from the same install.

This will finally let me merge the sources and gcc bugzilla *code*
trees, without having to merge the actual bugzilla db's.

This is why sources never gets upgraded, btw.  Doing the merge work

      parent reply	other threads:[~2007-02-19 16:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19  0:56 Ulrich Drepper
2007-02-19  1:34 ` Frank Ch. Eigler
2007-02-19  2:27   ` Ulrich Drepper
2007-02-19  6:47     ` Per Bothner
2007-02-19  9:43       ` Ulrich Drepper
2007-02-19 16:05       ` Daniel Berlin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4aca3dc20702190805g4532d782r6733ae89694a8ab1@mail.gmail.com \
    --to=dberlin@dberlin.org \
    --cc=drepper@redhat.com \
    --cc=overseers@sources.redhat.com \
    --cc=per@bothner.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).