Re: Contributing messages to an archive

[Jeff King <peff@peff.net>]

On Tue, Jul 03, 2018 at 09:09:10AM -0700, Jonathan Nieder wrote:

>  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.
> 
> Is there a way to inject messages into the public-inbox.org/git
> archive?  E.g.  should I provide my own public-inbox style repository
> to pull messages from, or is there an address that I can bounce
> messages to?

To give a sense of the scale here, I have a 326-message thread regarding
the recent submodules vulnerability that I'd like to make it into the
archive (now that the issue is un-embargoed). I _could_ just re-send
those messages individually to git@vger, but:

  1. It's kind of spammy to dump so many messages.

  2. The dates are now old, which means they'd likely get spam-blocked
     if used as-is.

  3. Ditto for the "From" field, which would violate things like SPF.

Points (2) and (3) could be addressed by "wrapping" the messages and
using in-body headers, like we do for patch authors/dates, but then that
would also fool tools like public-inbox.

Likewise, I could dump the whole thing as a gzipped mbox, but it would
be nice if the contents were more easily searchable.

So it would be really nice to inject directly into the archive somehow
(and then leave a single message on the list alerting people that it
happened).

-Peff