Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of matthieu.riou@gmail.com
 designates 66.249.82.205 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Vbri4IKw9VSg0Fh/6uBfE8tkOgD8p5fEuV5kc9RKPDfyjdzf+ONA6CFHdQ7kNn7w0eTet+zixr/wbwIu6Y9rxMrZarvNx8fJvUJoS8kEJPl/hjGWljNYVqPeqvBjRfw7vAnsGNUuqQ7bRDDlAXvCBcWK+W8DkHu0nOm7uFkdpjE=
Message-ID: <fbdc6a970602030902p3846135k6ddc8395e2738ddb@mail.gmail.com>
Date: Fri, 3 Feb 2006 17:02:41 +0000
From: Matthieu Riou <matthieu.riou@gmail.com>
Reply-To: matthieu.riou@gmail.com
To: general@incubator.apache.org
Subject: Re: [VOTE] accept donation of a business process engine into the
 ServiceMix project
Cc: dev@geronimo.apache.org
In-Reply-To: <BB129BD1-71D5-4F11-9707-F62D641C7448@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <9483C48B-70D6-4C35-899A-77216E576BA1@gmail.com>
	 <8AD8D078-8CC0-4106-AC32-7C85C8B0FD29@gmail.com>
	 <19e0530f0602030502s4ee1507ob38f40e5daaa7881@mail.gmail.com>
	 <774DCCE8-CE6B-4123-9DC0-D8C50D47D2AA@gmail.com>
	 <19e0530f0602030607r444f8897i899e36e6094c71db@mail.gmail.com>
	 <43E37150.6090509@Golux.Com>
	 <9125B734-778E-4000-8966-34DC091345AE@gmail.com>
	 <19e0530f0602030737i177d234cy41a14d0468f6d57d@mail.gmail.com>
	 <43E38116.20803@Golux.Com>
	 <BB129BD1-71D5-4F11-9707-F62D641C7448@gmail.com>

I do agree with your point James, communities built around a narrow
scope are harder to grow and attracting new commiters can become
hazardous. However my feeling is that the failure of Agila in
attracting new committers (for now) is mostly due to a lack of public
exposure and not really to BPEL having a narrow scope. Besides, even
if there aren't many committers working on Agila yet, there are people
using it.

I'm not sure I have any weight at all in this discussion, however I
can't see why a BPEL implementation would be developed as part of a
JBI implementation. JBI is made to integrate nicely with many
components (rules engines, scripting, soap and jms layers, ...), does
that mean that all these components should be developed under the
ServiceMix umbrella? I don't believe so.

My 2 cents.

>On 3 Feb 2006, at 16:13, Rodent of Unusual Size wrote:>> Incidentally
its worth looking at other projects at Apache like Agila>> and various
projects on http://ws.apache.org like EWS, Mirae, Muse,>> WSRF, TSIK
etc which are kinda quiet, some near dormant. Making>> projects too
small and too granular can sometimes harm the chances of>> creating a
vibrant community. Just as the some folks in the WS PMC>> are starting
to consider collapsing projects together due to>> inactivity, I think
we should stay open to the idea of creating less>> granular projects
that can build a thriving community to start with>> then, if the
community decides, split things off later if something>> becomes so
popular it deserves its own project.>> James, bearing in mind the
*content* of Dims questions above,> rather than how he phrased them,
would you please expand on> the above to address how Dims apparently
interpreted it?The point I was trying to make above has nothing to do
with ws-folksor anyone involved in the projects - apologies if my
cold-inducedramblings caused any offence. It was more just a general
observationon project size and community growth. Its hard growing
communities;it takes a lot of time and effort. Projects can be too
broad(Jakarta) and too granular - but sometimes its easier to
buildcommunity inside a single project with one overall aim (Geronimo
forJ2EE, ServiceMix for JBI, Jakarta Commons / WS Commons for
utilitycode etc) than to have lots of smaller
projects.James-------http://radio.weblogs.com/0112098/- Show quoted
text ----------------------------------------------------------------------=
To
unsubscribe, e-mail: general-unsubscribe@incubator.apache.orgFor
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