From: Jonathan Nieder <jrnieder@gmail.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org, Jeff King <peff@peff.net>
Subject: Re: Contributing messages to an archive
Date: Tue, 3 Jul 2018 13:44:00 -0700 [thread overview]
Message-ID: <20180703204400.GC51821@aiede.svl.corp.google.com> (raw)
In-Reply-To: <20180703195444.c2oa4svg6azsaop3@dcvr>
Hi,
Eric Wong wrote:
> Jonathan Nieder <jrnieder@gmail.com> wrote:
>> 1. When vger has a bad day, some messages might not reach
>> public-inbox but they still reach any other developers that were
>> cc-ed
>
> In that case, the notifying the admin(s) privately with an mbox
> or whatever which I can drop into my Maildir watched by
> public-inbox-watch should work fine[1].
Thanks, good to know.
>> 2. (My motivation) The git-security@googlegroups.com list receives
>> messages about embargoed issues that should not be made public
>> right away. We would like to switch to a model where after the
>> embargo expires, the discussion is made public.
>
> I suspect that is best suited for a second archive.
>
> It's simpler for readers using NNTP and Atom feeds to not get
> out-of-date messages, and filtering rules[1] would be different,
> as I suspect googlegroups allows HTML :<
Hm, I was looking forward to having it in the main archive since
that's where people look for context on a patch.
Is there a way to configure the search to look at multiple archives?
> Since I'm not a part of git-security, it might be best for you
> and/or Jeff to run that yourselves[2]. I can help out, of
> course. I'd use public-inbox-watch setup to watch that a
> particular Maildir, and you'd move unembargoed messages into
> that.
Would you be interested in helping with Git security bug reports and
reviewing the patches that address them? If so, we'd be happy to add
you to the list.
Thanks,
Jonathan
next prev parent reply other threads:[~2018-07-03 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 16:09 Contributing messages to an archive Jonathan Nieder
2018-07-03 16:39 ` Jeff King
2018-07-03 19:54 ` Eric Wong
2018-07-03 20:44 ` Jonathan Nieder [this message]
2018-07-03 21:00 ` Jeff King
2018-07-03 21:08 ` Eric Wong
2018-07-03 21:03 ` Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180703204400.GC51821@aiede.svl.corp.google.com \
--to=jrnieder@gmail.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=peff@peff.net \
/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).