[stp-dev] Highlighting action items after EclipseCon

[Oisin Hurley <ohurley@xxxxxxxx>]

Hi all,
Great to meet you all at EclipseCon this year - it was a hectic week,
but very productive and enjoyable. For me the most important part of
the week was of course Wednesday evening, when we had our committers
meeting and a BOF (until 2230!) and continued discussing the WTP and
DTP connection frameworks until after midnight.

Three things came out very strongly during our meeting and require
immediate action. These are:

1. JBI
2. Architecture
3. Building

1. At our face to face last year, ObjectWeb and LogicBlaze both brought
a strong JBI interest to the table. It's time to follow that up now and
work together to see how JBI can increase the value of the STP. This
project is intended to provide value in SOA Tooling for a diverse set
of runtimes - it's not intended to exclusively concentrate on any
particular runtime. With strong initiatives in progress around the
JBI standard [0, 1] and STP membership of the originators of these
projects, it makes sense to move forward now on the exploration of how
JBI fits into STP.

2. There were a couple of questions regarding the project architecture
at our meeting (thanks Alex!) to which we didn't have a good answer.
The summary architecture diagram in the project charter does not shine
a strong light on the structure of the project overall. We have an
urgent action item to construct a clear architecture upon which we can
hang contributions to the project.

3. We have code - we don't have a build system for that code! Naci Dai
from the WTP project has very kindly volunteered to help us put
together a top-class Eclipse build system based upon the WTP build.
Not just a standard PDE build, the WTP build provides some great
added-value items, like API coverage reports and continuous builds.
STP needs you -- if you would like to be an STP buildmaster, please
do take a step forward!

regards
   Oisin



[0]  http://www.servicemix.org/Home
[1]  http://petals.objectweb.org/