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 C72741857B for ; Fri, 23 Oct 2015 12:08:34 +0000 (UTC) Received: (qmail 53103 invoked by uid 500); 23 Oct 2015 12:08:34 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 52912 invoked by uid 500); 23 Oct 2015 12:08:34 -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 52901 invoked by uid 99); 23 Oct 2015 12:08:34 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Oct 2015 12:08:34 +0000 Received: from mail-yk0-f170.google.com (mail-yk0-f170.google.com [209.85.160.170]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id AF1C61A0181 for ; Fri, 23 Oct 2015 12:08:33 +0000 (UTC) Received: by ykdr3 with SMTP id r3so117296219ykd.1 for ; Fri, 23 Oct 2015 05:08:32 -0700 (PDT) X-Received: by 10.129.136.65 with SMTP id y62mr16669900ywf.69.1445602112857; Fri, 23 Oct 2015 05:08:32 -0700 (PDT) MIME-Version: 1.0 References: <01535019-06CF-4562-ADE7-797091F83989@gmail.com> <5A90207C-B89F-4039-B436-791127203E16@gmail.com> <98848498-2950-4214-B5A9-30E116594547@jaguNET.com> In-Reply-To: From: "John D. Ament" Date: Fri, 23 Oct 2015 12:08:23 +0000 Message-ID: Subject: Re: Short form IP clearance To: general@incubator.apache.org Content-Type: multipart/alternative; boundary=001a114f2d246c6cfc0522c47832 --001a114f2d246c6cfc0522c47832 Content-Type: text/plain; charset=UTF-8 On Fri, Oct 23, 2015 at 8:03 AM Sam Ruby wrote: > On Fri, Oct 23, 2015 at 7:55 AM, John D. Ament > wrote: > > So.... basically if someone attaches a patch to a JIRA, which becomes > part > > of our public mailing lists, we're good? > > If that code was all that poster's original work, not previously > published elsewhere (particularly under a different license), then > that's fine. > > If that code was previously developed elsewhere, had multiple > contributors, and made available (particularly under a different > license), then no. > > I'll also note that the goal of IP Clearance isn't to disallow such > contributions, it is merely to make sure that we capture all of the > relevant history (IP provenance) for posterity. > So then probably the more concise form is "the work was first developed as a part of the ASF and not elsewhere." A cursory read makes it sound partially like external contributions require IP Clearance, but having this note makes it clearer. > > > Would github PR's fall under the same premise, since the contents of > those > > mails become public record? > > See above. > > - Sam Ruby > > > On Fri, Oct 23, 2015 at 7:51 AM Sam Ruby wrote: > > > >> On Fri, Oct 23, 2015 at 7:41 AM, John D. Ament > >> wrote: > >> > I think probably the better question is "which contributions require > IP > >> > Clearance"? > >> > >> "Any code that was developed outside of the ASF SVN repository and our > >> public mailing lists must be processed like this, even if the external > >> developer is already an ASF committer." > >> > >> Source: http://incubator.apache.org/ip-clearance/ > >> > >> At a minimum, the word "SVN" should be removed. Any other changes > >> people feel are necessary? > >> > >> - Sam Ruby > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org > >> For additional commands, e-mail: general-help@incubator.apache.org > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org > For additional commands, e-mail: general-help@incubator.apache.org > > --001a114f2d246c6cfc0522c47832--