Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: pass (athena.apache.org: domain of heavy@ungoverned.org
 designates 67.222.54.6 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=ungoverned.org;
	h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User;
	b=BdCT9HDzTlai0R6kuJurC4m3Q3+3A93C5lBh43GIX9/qXTVbG6rORRc1uTuB+Gw+kfDOm/i4URKlv4Xf4NcWqkbm4b+mZsn3Ba5fFgf8O6jvw+hj7aBbENKWlYVvjqXi;
Message-ID: <4C93BD48.2080006@ungoverned.org>
Date: Fri, 17 Sep 2010 12:11:04 -0700
From: "Richard S. Hall" <heavy@ungoverned.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: dev@felix.apache.org
Subject: Re: Handling of provisional OSGi API
References: <4C9398BF.1040700@ungoverned.org>
 <4DAB06BA-C229-4525-8082-8D3D46F2E002@luminis.nl>
In-Reply-To: <4DAB06BA-C229-4525-8082-8D3D46F2E002@luminis.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

  On 9/17/10 11:36, Marcel Offermans wrote:
> On 17 Sep 2010, at 18:35 , Richard S. Hall wrote:
>
>>  From my point of view, approach (1) might not be awesome, but it results in a simpler process than (2). So, I'd recommend (1). If the majority prefers (2), then we can do that (although I think we'll have to run the decision by the board first).
> I prefer (1) too.
>
> I could see us combine (1) with (2), releasing implementations with both our own APIs which gives us the freedom to experiment with a new API whilst still "supporting what's provided by public releases of draft specs.

However, this doesn't avoid the IP grey of releasing "unofficial" APIs 
in our "official" releases. Effectively, option (2) is a hybrid 
approach, since we couldn't make modifications in the provisional API 
unless it were available in a public spec snapshot, so any modifications 
would have to be done in felix package namespace. Which sort of makes 
(2) the worst of both worlds.

-> richard

> In the end, we are an open source project, so we should stick to what's available out in the open.
>
> Greetings, Marcel
>