From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 07ABF1F6AC; Tue, 3 Jul 2018 19:54:45 +0000 (UTC) Date: Tue, 3 Jul 2018 19:54:44 +0000 From: Eric Wong To: Jonathan Nieder Cc: meta@public-inbox.org, Jeff King Subject: Re: Contributing messages to an archive Message-ID: <20180703195444.c2oa4svg6azsaop3@dcvr> References: <20180703160910.GB51821@aiede.svl.corp.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180703160910.GB51821@aiede.svl.corp.google.com> List-Id: Jonathan Nieder wrote: > Hi Eric et al, > > I dug through the documentation at public-inbox.org and didn't see a > clear answer to this, so thought I'd ask to see whether my idea is > crazy. > > https://public-inbox.org/git contains a copy of all messages sent to > the git mailing list, which is a useful resource for git developers. > But some messages don't reach there: > > 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]. > 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 :< 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. > 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? If you're using public-inbox-watch, then dropping messages into a Maildir being watched ought to do the trick. There's also some one-off scripts in the scripts/ directory of the git repo (e.g. scripts/import_vger_from_mbox) which can work after-the-fact. [1] If configured, PublicInbox::SaPlugin::ListMirror actually prevents bounced messages from being injected. The admin would have to edit the top Received: header. [2] The partitioned v2 layout I wrote for kernel.org scales way better than the original 2/38 layout. Cloning is a little more involved (see the bottom of ), but the only difference is in setup is passing the "-V2" switch to public-inbox-init. But yeah, remember being appalled by hosting costs of git-scm.com Peff posted, and public-inbox.org has always run on a $20/month VPS which I also hack and run test suites from.