Mailing-List: contact celix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: celix-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of pepijnnoltes@gmail.com
 designates 209.85.210.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <90CAB1CA-C6AC-4AD0-B79E-38A367BAC33E@luminis.nl>
References: 
 <CA+T-u8dom9A96KAcpuuB1XzXT7vatp3O2A+CrjCO1v3hhToFRw@mail.gmail.com>
	<90CAB1CA-C6AC-4AD0-B79E-38A367BAC33E@luminis.nl>
Date: Wed, 11 Jan 2012 09:04:31 +0100
Message-ID: 
 <CAPhv5g-rKwaNERTYCfEko2Q6NoUjb0kxaz-hos0L_rwr0_bp_A@mail.gmail.com>
Subject: Re: Poddling status
From: Pepijn Noltes <pepijnnoltes@gmail.com>
To: celix-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 11, 2012 at 7:55 AM, Marcel Offermans
<marcel.offermans@luminis.nl> wrote:
> On Jan 11, 2012, at 7:30 AM, Alexander Broekhuis wrote:
>
>> On the incubator list a discussion is going on about slow/small poddling=
s
>> and how to handle these. Celix is one of these poddlings.
>>
>> For Celix I see the following problems (at least):
>> - No community growth (or not visible..)
>> - No new committers
>> - No releases made
>>
>> I think a plan is needed to see how we can move Celix towards graduation=
,
>> how we can get a community, more committers etc.
>
> Agreed. The Incubator PMC in particular is interested in learning how the=
 community intends to address the issues that prevent a podling from gradua=
ting. They feel that, especially after being in the incubator for over a ye=
ar, a graduation plan should be drafted.

Concerning the Celix community growth, at Thales Netherlands we are
currently working on a research project in which Celix plays a big
part. We are exploring the opportunity to use Celix as a middleware
solution - replacing our propertairy solution - in our Radar
development. We strongly feel this is going to be a succes and are the
moment busy developing the OSGi Device Access Specification in Celix.
We are planning to send a patch in the coming weeks. Hopefully this
helps in supporting Celix :)

>
>> Looking at the three items, the first two will be the most difficult, an=
d
>> require the most attention. We have been working on visibility, going to
>> the EclipseCon, ApacheCon and several other smaller local community even=
ts.
>
> Again, I agree. While it is time to make a release as well, and this migh=
t actually help people who want to take a look at Celix, the main issue tha=
t needs to be addressed is the size and diversity of the community.
>
> At these events you mention, no doubt you have talked directly to a bunch=
 of people. Could you somehow summarize their feedback?
>
> What other communities can we possibly reach out to, and how?
>
>> I'd like to hear what people following this list think of these problems=
,
>> and how we can move towards a healthy community. What is holding you bac=
k?
>> What is needed to be able to adopt Celix? Feel free to express any conce=
rn
>> or opinion you have. Either technical, documentation etc.
>
> One question I've been getting occasionally is: "does Celix also work wit=
h C++?".
>
> From a use case point of view, I think we could explore the scenario wher=
e you have Java application that uses native code. Mostly, this is now done=
 using JNI which has the downside that it can take the whole JVM down if so=
mething goes wrong in the native code. From a robustness point of view, thi=
s is unacceptable, and I think Celix can be used to provide a better implem=
entation. With this use case, we can target any Java project that uses nati=
ve libraries, which in turn might help growing our community. Such use case=
s are probably interesting enough to write about on all kinds of Java sites=
.

Good idea. I also think a working scenario with Celix instead of JNI
is worth presenting to different Java user groups.

>
> Greetings, Marcel
>

Greetings,
Pepijn