From: "Carlos O'Donell" <carlos@redhat.com>
To: Frank <fche@redhat.com>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
Florian Weimer <fweimer@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
overseers@sourceware.org
Subject: Re: Overseers list should not be public
Date: Fri, 22 Sep 2017 17:34:00 -0000 [thread overview]
Message-ID: <CAEMqeSqDa=+ddsxa8X4RnmJvo2n41-ut9gi32a2RemChU2Bd8g@mail.gmail.com> (raw)
In-Reply-To: <20170922171445.GE12339@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Sep 22, 2017 11:14, "Frank Ch. Eigler" <fche@redhat.com> wrote:
Hi -
> > (I agree we could use much better status / infrastructure-related
> [...]
> I would see the following as next steps:
>
> * Add overseers to lists.html and describe what the list is for.
> * Remove robots.txt entry for overseers mailing list.
This is a separate matter ...
> * Create a wiki for base sourceware infrastructure.
> * Enforce ACL via EditorsGroup to the wiki.
> * Add a Status page in the wiki showing sourceware status.
> * Update news.html to mention latest breakage.
... from this. This latter bit has been on our todo list for
some time, but will get to it shortly.
Can I help with that?
Do you agree with all the bullet points after the first two?
c.
next prev parent reply other threads:[~2017-09-22 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 8:14 Florian Weimer
2017-09-15 12:56 ` Frank Ch. Eigler
2017-09-22 14:32 ` Carlos O'Donell
2017-09-22 14:40 ` Joseph Myers
2017-09-22 15:06 ` Martin Sebor
2017-09-22 16:37 ` Carlos O'Donell
2017-09-22 16:41 ` Frank Ch. Eigler
2017-09-22 16:56 ` Carlos O'Donell
2017-09-22 17:14 ` Frank Ch. Eigler
2017-09-22 17:34 ` Carlos O'Donell [this message]
2017-10-31 16:03 ` Frank Ch. Eigler
2017-09-22 17:06 ` Joseph Myers
2017-09-22 14:47 ` Frank Ch. Eigler
2017-09-22 14:56 ` Carlos O'Donell
2017-09-22 17:15 ` Florian Weimer
2017-09-22 17:24 ` Joseph Myers
2017-09-22 17:32 ` Carlos O'Donell
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='CAEMqeSqDa=+ddsxa8X4RnmJvo2n41-ut9gi32a2RemChU2Bd8g@mail.gmail.com' \
--to=carlos@redhat.com \
--cc=fche@elastic.org \
--cc=fche@redhat.com \
--cc=fweimer@redhat.com \
--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).