From: Mark Wielaard <mark@klomp.org>
To: Pedro Alves <palves@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
"Jose E. Marchesi" <jemarch@gnu.org>,
overseers@sourceware.org
Subject: Re: updating bugzilla entries in sourceware.org
Date: Wed, 26 Apr 2017 19:59:00 -0000 [thread overview]
Message-ID: <1493236771.31726.70.camel@klomp.org> (raw)
In-Reply-To: <0a68400b-3c1f-f82d-b674-2d6eaa7c2c99@redhat.com>
On Wed, 2017-04-26 at 19:54 +0100, Pedro Alves wrote:
> I wonder whether we have somewhere a central place that includes information
> relevant to all products that the single bugzilla instance holds, not just
> glibc and gdb. (binutils, cygwin, elfutils, systemtap, etc.)
> Then all the different projects could reference it. There's the sourceware.org
> website of course, though that's not very convenient to edit. Does sourceware.org
> have a "sourceware" wiki? Or we could create such a page in one of the project's
> wikis and bless it as "cross project page". Anyway, just an idea that crossed my
> mind, there's not really that much information that I'm off hand thinking
> we'd put there.
It would be nice to have some shared page for project admins when
referring people to:
- Bugzilla accounts
(the above editbugs discussion, spam measures, etc.)
- Commit accounts
(https://sourceware.org/cgi-bin/pdw/ps_form.cgi
ssh troubleshooting, updating ssh keys, email forwards)
- Mailinglist instructions
(https://sourceware.org/lists.html#ml-requestor
how to whitelist yourself, attachements/HTML policies, etc.)
Cheers,
Mark
prev parent reply other threads:[~2017-04-26 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 14:49 Jose E. Marchesi
2017-04-26 14:57 ` Carlos O'Donell
2017-04-26 15:14 ` Jose E. Marchesi
2017-04-26 15:54 ` Carlos O'Donell
2017-04-26 18:54 ` Pedro Alves
2017-04-26 19:59 ` Mark Wielaard [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=1493236771.31726.70.camel@klomp.org \
--to=mark@klomp.org \
--cc=carlos@redhat.com \
--cc=jemarch@gnu.org \
--cc=overseers@sourceware.org \
--cc=palves@redhat.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).