Hi guys,
what should we do the next? Do you think there is a synergy between ODE
and Shark and if ODE could be a sponsor? Should we discuss some other
things?
What would be the next step that should be taken from our side?
Greetings,
Sasa.
Sasa Bojanic wrote:
Well, Shark also has well designed core...in general we can also
support something that is not XPDL since core is based on API.
However, Shark implementation is XPDL based and Shark interprets XPDL.
We have the complete XPDL object model that we also use in our JaWE
editor which supports XPDL 100%. I doubt BPEL's core can fit into XPDL.
By re-writing the core I basically mean extending XPDL object model
and adding more functionality to Shark as defined by XPDL 2.1 spec.
Thanks for the link about licenses...I think we will not have too much
problems here.
Regarding diversity, we plan to ask current Shark community as well as
the previous contributors to get more involved into the project. We
also expect some interest from the Apache community.
Greetings,
Sasa.
Matthieu Riou wrote:
Same question here, especially given that you mention planning to
rewrite
the Shark core. ODE has a fairly well designed core which we're already
reusing for something that's not BPEL, would be reusing it as well an
option?
For the licensing questions, regarding which license are allowed or not,
this could help:
http://www.apache.org/legal/3party.html
I'm also curious about the strong ties to Together Teamlösungen. You
mention
the possibility of orphanage in the proposal, which is good, but how
do you
plan to address diversity? One of the conditions of graduation from the
Apache incubator is sufficient diversity.
Thanks,
Matthieu
On Wed, Mar 4, 2009 at 10:59 AM, Alex Boisvert <[email protected]>
wrote:
Sasa,
Where do you see the synergies between Shark and Ode? i.e., How
would the
respective communities benefit?
alex
On Wed, Mar 4, 2009 at 5:00 AM, Sasa Bojanic <[email protected]
wrote:
Dear All,
I've already posted an email to incubator's list asking for a
champion/sponsor for moving Shark project to Apache.
I communicated with Matthieu Riou and he suggested ODE could be a
sponsor
for this project and told me the best way would be to start
discussion on
this list.
Let me repeat what I already posted to incubator list:
Enhydra Shark workflow engine is a project currently hosted on
ObjectWeb
(
http://shark.objectweb.org/)
It is the most popular open-source java workflow engine completely
based
on
WfMC standards.
It uses XPDL1.0 as its native workflow process definition language.
It can be embedded into other Java applications (Swing, Console,
...) or
can be used as a server through WebService, EJB, CORBA, ...
Shark's modular, plug-in architecture makes shark suitable for
integration
into different kind of projects.
It is a mature project started 5years ago, has a significant community
and
more than 100000 downloads on ObjectWeb and almost 10000 posts on
mailing
list. It is widely used all around the world in production, typically
integrated into different kind of applications, from
DocumentManagement
and
government applications up to applications for special purposes
like bank
services, HR, Help desk, ... and in many, many others
Our goal is to move the core shark components to Apache. We should
have
no
problems with CLAs since these components are developed only by our
core
developers.
We would like to continue with Shark development on Apache by
re-factoring
Shark kernel's code and other major components to support XPDL2.1
specification.
Attached is an initial version of SharkProposal....Please feel free to
ask
any question.
Greetings,
Sasa.
