From: David Edelsohn <dje.gcc@gmail.com>
To: "Carlos O'Donell" <carlos@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
"Frank Ch. Eigler" <fche@elastic.org>,
Overseers <overseers@sourceware.org>
Subject: Re: GCC Bugzilla accounts
Date: Mon, 05 Jun 2017 15:39:00 -0000 [thread overview]
Message-ID: <CAGWvnyky=SGcioY6MrO4xhVPUr-hYEx1_yfXcB03wa9tXA_Bpg@mail.gmail.com> (raw)
In-Reply-To: <20170601195649.GA6416@ednor.casa.cgf.cx>
On Thu, Jun 1, 2017 at 3:56 PM, Christopher Faylor
<cgf-use-the-mailinglist-please@sourceware.org> wrote:
> On Thu, Jun 01, 2017 at 10:53:24AM -0400, David Edelsohn wrote:
>>If we solicited new volunteers from the GCC community to review GCC
>>Bugzilla account requests, can we easily and conveniently provide those
>>volunteers with privileges to create / approve GCC Bugzilla accounts?
>>This could be an opportunity to grow the GNU Toolchain developer
>>community with important but non-programming tasks.
>
> Frédéric Buclin created a program called "bugzilla-createuser" that
> is used on sourceware when a new account is created that needs
> bugzilla access. We could add a "create-bugzilla-account" command
> to the limited shell that source-control-only users get so that
> anyone with access to gcc's svn could create a bugzilla account.
>
> So, you'd do something like:
>
> ssh gcc.gnu.org create-bugzilla-user user password
I could ask for a volunteer to review GCC Bugzilla account requests on
the GCC Mailing List. That seems like a reasonable start if a user
can be authorized with restricted privileges to create GCC BZ
accounts.
Thanks, David
next prev parent reply other threads:[~2017-06-05 15:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 16:07 David Edelsohn
2017-05-25 16:26 ` Joseph Myers
2017-05-25 16:37 ` Carlos O'Donell
2017-05-25 16:41 ` Joseph Myers
2017-05-25 20:16 ` Ian Lance Taylor
2017-05-25 20:35 ` Gerald Pfeifer
2017-05-25 21:36 ` Frédéric Buclin via overseers
2017-05-31 11:54 ` David Edelsohn
2017-05-31 12:38 ` Carlos O'Donell
2017-05-31 12:41 ` David Edelsohn
2017-05-31 13:14 ` Frank Ch. Eigler
2017-05-31 13:22 ` David Edelsohn
2017-05-31 14:39 ` Christopher Faylor
2017-05-31 14:49 ` David Edelsohn
2017-06-01 14:19 ` Joseph Myers
2017-06-01 14:44 ` Christopher Faylor
2017-06-01 14:53 ` David Edelsohn
2017-06-01 19:56 ` Christopher Faylor
2017-06-05 15:39 ` David Edelsohn [this message]
2017-06-05 15:49 ` Frank Ch. Eigler
2017-06-16 22:02 ` Frank Ch. Eigler
2017-06-17 12:07 ` David Edelsohn
2017-06-20 22:40 ` David Edelsohn
2017-06-21 22:02 ` Frank Ch. Eigler
2017-06-23 13:39 ` David Edelsohn
2017-07-13 18:29 ` David Edelsohn
-- strict thread matches above, loose matches on Subject: below --
2014-12-12 15:53 gcc bugzilla accounts Damien Ruscoe
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='CAGWvnyky=SGcioY6MrO4xhVPUr-hYEx1_yfXcB03wa9tXA_Bpg@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=carlos@redhat.com \
--cc=fche@elastic.org \
--cc=joseph@codesourcery.com \
--cc=overseers@sourceware.org \
/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).