Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EF4BA1852D for ; Thu, 22 Oct 2015 01:40:23 +0000 (UTC) Received: (qmail 36935 invoked by uid 500); 22 Oct 2015 01:40:23 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 36727 invoked by uid 500); 22 Oct 2015 01:40:23 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 36715 invoked by uid 99); 22 Oct 2015 01:40:23 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Oct 2015 01:40:23 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 99E51180E80 for ; Thu, 22 Oct 2015 01:40:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.2 X-Spam-Level: ** X-Spam-Status: No, score=2.2 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id SYcG5COmn0BD for ; Thu, 22 Oct 2015 01:40:14 +0000 (UTC) Received: from mail-vk0-f44.google.com (mail-vk0-f44.google.com [209.85.213.44]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 29FF7280A6 for ; Thu, 22 Oct 2015 01:40:14 +0000 (UTC) Received: by vkfw189 with SMTP id w189so38944612vkf.2 for ; Wed, 21 Oct 2015 18:40:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=opLyR4u2HgLsgXUM2GKvPMuuBnsqXGjM82R+qdtTzeQ=; b=LavVdR5wlVzB4w1fYRX7BttTOr9hz5+A5n9n73T6RvymGLVDCCpQ49ZPHTmSoNZulp ZnHjA6kLfcv/6SvHEURXxYfJ3OdtwtDZn3qbwlz3Gw4HLrqi9LvGiRyo+Tss568j/dgI vwowfnIVNTXdThQPjVLbiNB20JMNMkEEEvIeAxcHDg/DVMegIsQwPMzAQQN5mr+3zBub UgKJ7IlCkLdAJpuCkW1QNoYuKzttfxYJv5MgPM8E/K5EzNSPUGVta/jjBnYG+libc3YW xK9ebzw8LNc3L7pQ/dsdkGpU/VkwQzf1RfKjyhJVo4b/ilptke62VVSUdrrAJgNHFAKQ a26A== MIME-Version: 1.0 X-Received: by 10.31.44.77 with SMTP id s74mr7743423vks.124.1445478007025; Wed, 21 Oct 2015 18:40:07 -0700 (PDT) Received: by 10.31.138.82 with HTTP; Wed, 21 Oct 2015 18:40:06 -0700 (PDT) In-Reply-To: References: Date: Wed, 21 Oct 2015 20:40:06 -0500 Message-ID: Subject: Re: Short form IP clearance From: Greg Stein To: general@incubator.apache.org Content-Type: multipart/alternative; boundary=001a11c075a223b5bc0522a79384 --001a11c075a223b5bc0522a79384 Content-Type: text/plain; charset=UTF-8 I believe a PMC is capable of performing IP clearance itself. They have a VP that is an Officer and can take responsibility for the Foundation in matters of that Project. The forms/recording are valid, so I haven't suggested changing that (tho I'd like to see them move under /legal/, I'm not fussed about their location). I would hope that a PMC includes a note in their report to the Board, that they filed a clearance form. That is just natural reporting. But that is quite different from one TLP being subject to another TLP's vote (whether lazy consensus or not). There could certainly be an argument that a PMC needs to be double-checked by $entity. But that kind of second-guessing means $entity needs to double-check all commits and all release artifacts. We trust PMCs to get their IP done correctly, as they work on their project and make releases. Cheers, -g On Wed, Oct 21, 2015 at 8:28 PM, John D. Ament wrote: > Greg, > > If I'm reading your email correctly, you're just saying that the Incubator > is not responsible for processing IP Clearances in a lazy way. Projects > should instead direct their IP clearance emails to <>. > > That <> is TBD. > > John > > On Wed, Oct 21, 2015 at 9:17 PM Greg Stein wrote: > > > [trimmed response right now; in favor of getting a couple other voices] > > > > On Wed, Oct 21, 2015 at 7:01 PM, Sam Ruby > wrote: > > >... > > > > > What is this, randomly propose changes to the incubator month? > > > > > > > Has nothing to do with the Incubator, but with how a PMC records its IP > > clearance. And more importantly, to clarify that a PMC is not beholden to > > the IPMC. > > > > > > > Let me repeat what I just said. I don't believe I was being obtuse, > > > but then again, you don't appear to have read what I wrote. > > > > > > > I certainly read it, you weren't being obtuse :-) > > > > > > > 1) I hope we can agree that an Officer of the corporation should be > > > subject to the direction of the Legal Affairs committee. > > > > > > > Agreed. > > > > >... > > > > > > My point is to make the document reflect the reality of our > > organization. > > > > > > Reality is what is reflected on this page: > > > http://incubator.apache.org/ip-clearance/ > > > > > > Click on any of the clearance documents. > > > > > > I don't know what you are smoking, but those documents are real. > > > > > > > Of course. I didn't say "get rid of IP clearance". Please read my > original > > email, if you think otherwise. I just want to alter the published steps > to > > reflect that our TLPs are not beholden to the IPMC. We use the Incubator > as > > a location to record these things (which I find odd, but is a separate > > discussion). > > > > >... > > > > Cheers, > > -g > > > --001a11c075a223b5bc0522a79384--