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: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 8D63D1F6AC for ; Tue, 3 Jul 2018 20:44:03 +0000 (UTC) Received: by mail-pf0-x22d.google.com with SMTP id u16-v6so1555261pfh.3 for ; Tue, 03 Jul 2018 13:44:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=OJgRdPhWWoMMo0EzjPp6lNwlqJxducK7UuKL7DNq2Ro=; b=ldXI0MQt0lFp1MtNDdopsbesoSNa2X9Cbwwk3klWibZe+TMBgL+HcvHHU9xKD/YwfP p63+/J1n94tQqwE3r1TPAHFQ/7aHQMkpgr5XbafZH8hQ6CiimqdD+uFabNLxAByC89i9 NcrXcbQwOOli7FUi7vyI0hV2W9qA038GIzQTW5JXN48et8r/Hd3LhkjBUup3WoAL78sL 2CZYUsF6NGF7Mnj7tgD8crOHvkgoel5aCU3XMQAAshywJ8g2YGhSvvt2JUPtpNdrxZwh vtd8sdypO47r1mRHxQDOOMPgjQuxbp/DFweUGugQ8t01B+kxKcZvKuEOQ8qGy9RtI7mc ujIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=OJgRdPhWWoMMo0EzjPp6lNwlqJxducK7UuKL7DNq2Ro=; b=RUHQB5EHtyI1+o3AWYkeOfu8W9KQqsZ4QxpQxs4uhvX8/t7RuSqj9GnGQj4v0u35Ym MliFDvIzRcB0OOKPPXecp4X0M33a0ZchYYusF8AhvzGBEXXgOF7wDYmaWbSV9mdrXU1g 9NidfMzN4tDAyYk7B6ryt8qrGtJ/+83B3YkVQts1UrtT03NRfXKTVaREJvzp9PkDaw+b MnUxlm3Gd00rnXEaH6S/FHDvLTII4WTp7osQoSH/f5cY4Y7fcqPI7zpZIjJKVp73LCUg +Q9DYn7LbvbkHTmvAaOR4hfSuM4CSFIDs6qQPX7rWpa02Pwd7lbFcfoUsVlq4FLpAOS5 aSww== X-Gm-Message-State: APt69E292tHyRlYnVLDRXt1dBZnYtWuijcOReBACOfxBsNxu2nmzpSfe T6/lZVP85/b2iri+vbxSlDoHILUg X-Google-Smtp-Source: AAOMgpcVo5U6Tr4kh2OrYN4KAKebBFE3eSNUVW9tykL5D2nllhVSZyLgXS48I0oekrYicHu1GIEwaw== X-Received: by 2002:a62:3b89:: with SMTP id w9-v6mr23751971pfj.80.1530650642353; Tue, 03 Jul 2018 13:44:02 -0700 (PDT) Received: from aiede.svl.corp.google.com ([2620:0:100e:422:4187:1d6c:d3d6:9ce6]) by smtp.gmail.com with ESMTPSA id 8-v6sm4225296pfk.132.2018.07.03.13.44.01 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 03 Jul 2018 13:44:01 -0700 (PDT) Date: Tue, 3 Jul 2018 13:44:00 -0700 From: Jonathan Nieder To: Eric Wong Cc: meta@public-inbox.org, Jeff King Subject: Re: Contributing messages to an archive Message-ID: <20180703204400.GC51821@aiede.svl.corp.google.com> References: <20180703160910.GB51821@aiede.svl.corp.google.com> <20180703195444.c2oa4svg6azsaop3@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180703195444.c2oa4svg6azsaop3@dcvr> User-Agent: Mutt/1.9.2 (2017-12-15) List-Id: Hi, Eric Wong wrote: > Jonathan Nieder 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