Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Subject: Re: [DISCUSS] [POLICY] IP tracking for OSGi APIs
To: dev@felix.apache.org, dev@aries.apache.org
References: <CAA66TpqYemBX_kD83uvKz2Y_BwfZKKDsac8VCTbh13Hkio=cXA@mail.gmail.com>
 <15f097f8-57b4-f467-041f-ca81ca7dbbd4@apache.org>
 <CAA66TpqvOvvReGUsmLH7dhmK6S6_4HBByRuxt-yzxOf74_64Tw@mail.gmail.com>
 <8f85b872-902a-b1a5-8913-37218590b7d8@apache.org>
 <CAA66TpoGYBbBJVbA-KBK+qaKVW2sgO2mhEqQgWAsyabQ-V-0Wg@mail.gmail.com>
 <1611dfe1-73dd-f245-6691-4763a0a5b173@apache.org>
 <CAA66TpogQyOzKGhLOCpq=f0iGr_pPo=AwUAr86uqv1t1rum=5Q@mail.gmail.com>
 <0e97aded-c9bb-fbf8-fb3b-a3472b4699b3@apache.org>
 <CAA66TpooGSFXM0e+Q3BQgeGz9G2ACQ1EQ26YKiia79BRXpRybw@mail.gmail.com>
From: Carsten Ziegeler <cziegeler@apache.org>
Message-ID: <55192d4f-fd9e-4b61-10cc-ac0b6f204c48@apache.org>
Date: Tue, 24 Jan 2017 04:24:57 -0800
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; de; rv:1.8.1.23)
 Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
In-Reply-To: <CAA66TpooGSFXM0e+Q3BQgeGz9G2ACQ1EQ26YKiia79BRXpRybw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 24 Jan 2017 12:25:00 -0000

Guillaume Nodet wrote
> My point is that there is a source identified, preferably public if
> possible, private if not.
> 
> Of course if the API is not public, we can refer to the private commit so
> that  PMC members which are not OSGi members can be confident about the IP
> tracking.
> I think it depends on what stage the API is.  For example, consider the
> work Ray is working on for CDI, I don't think the API is in the OSGi git
> repo yet, so either the API is committed there first, or the commit can
> refer to Ray's github repo directly.  If a spec has been published
> officially by the OSGi Alliance, we can refer to a public source too.
> Given the API code becomes public at the time it's given to the ASF, I
> didn't thought that would be a problem to have it in a public repo in the
> first place, but if you're saying it is... I'm fine with that.
> 
> So what about:
>   "All commits that includes API code from the OSGi Alliance are done in
> separate commit and include a reference to the public (preferably) or
> private (if not public) source  where the code comes from."
> 
> Does that look better to you ?
> 
Absolutely

 Carsten

-- 
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org