Project status and become ...

[Arnaud Quiblier]

What about the incubating project Apache Ode (Orchestration Director Engine)
?
Here what one could read from the Wiki [
http://wiki.apache.org/incubator/OdeProposal] :

"We are proposing an orchestration service that implements the WS-BPEL
specification. The implementation will also support Message/Event to process
correlation.
The project proposal includes development of an orchestration engine
abstraction to standard externally defined interfaces/bindings. The
interface implementations and/or bindings will enable the orchestration
service to be plugged into various service bus or component architectures."



--
</arnaud>

[Arnaud Quiblier]

Hi,

Sorry my last post was not complete ... and was acciddently sent !!!

I'm wondering what is the futur of the incubating Agila.
Is there a real willing to become a Apache TLP ? It seems thats both dev &
user community are quite small.

And what about the integration of Agila BPM and BPEL modules ?

If Agila BPEL is replaced by Ode (if this is not a non-sense, I'm not really
sure of my thoughts), is there an interest to developp Agila BPM to be a
settle for an Apache Workflow complete solution ?

I'm waiting your point of view ...
Cheers,

--
</arnaud>

[Matthieu Riou-2]

Hi Arnaud,

Good questions. Actually the plan is to have Agila BPEL merged into
Ode. I'm already in the list of commiters on Ode and will actively
participate. I also plan to get Agila's client API working on Ode so
that Agila BPEL users can migrate easily.

Agila BPM will continue its life in the Agila project and will perhaps
benefit from other contributions or donations. And I'll keep on
dedicating time for it.

Hope this answers to your questions...

Matthieu.

On 3/22/06, Arnaud Quiblier <aquiblier@...> wrote:

> Hi,
>
> Sorry my last post was not complete ... and was acciddently sent !!!
>
> I'm wondering what is the futur of the incubating Agila.
> Is there a real willing to become a Apache TLP ? It seems thats both dev &
> user community are quite small.
>
> And what about the integration of Agila BPM and BPEL modules ?
>
> If Agila BPEL is replaced by Ode (if this is not a non-sense, I'm not really
> sure of my thoughts), is there an interest to developp Agila BPM to be a
> settle for an Apache Workflow complete solution ?
>
> I'm waiting your point of view ...
> Cheers,
>
> --
> </arnaud>
>
>

[Arnaud Quiblier]

Thanks Matthieu.

Just after having sent my first two posts, I saw the mailing-list
general@..., which I read whith interest.
And I found the ref to the ODE mailing list too !!!

I hope that all the work done on Twister/Agila BPEL will be appriciate
during ODE development.

Same hope for Agila BPM.
Asap, I will look at Intalio|WorkFlow, which could be added to Agila ...

> Christopher : How do you feel the futur of Agila BPM. I think you write
somewhere that Italio Worflow has already all the features planned to be
released in Agila BPM. So, what next ?

I'm sure that Agila will change a lot in the next weeks / months.
But the governance decisions seems to be hard to take (one or two projects,
unique or multiple implementations, etc)
What do you think about ?

--
</arnaud>

[Christopher Lim]

Hi Arnaud,

> > Christopher : How do you feel the futur of Agila BPM. I think you write
> somewhere that Italio Worflow has already all the features planned to be
> released in Agila BPM.

I took a look at Intalio's web site at that time and they have the
designer, engine, and
web interface. Basically that is the roadmap for Agila BPM. However, I
misinterpreted things. I was thinking that Intalio will be donating
the whole stuff where in fact they've only mentioned the BPEL part and
that is for ODE.


> So, what next ?

Agila BPM needs more developers to work on the code. Your help is very
welcome. ;) Let's build a great open source BPM impl.


> I'm sure that Agila will change a lot in the next weeks / months.
> But the governance decisions seems to be hard to take (one or two projects,
> unique or multiple implementations, etc)
> What do you think about ?

Well, I think it is like that with open source. Let the community decide.


Cheers!

Chris




On 3/23/06, Arnaud Quiblier <aquiblier@...> wrote:

> Thanks Matthieu.
>
> Just after having sent my first two posts, I saw the mailing-list
> general@..., which I read whith interest.
> And I found the ref to the ODE mailing list too !!!
>
> I hope that all the work done on Twister/Agila BPEL will be appriciate
> during ODE development.
>
> Same hope for Agila BPM.
> Asap, I will look at Intalio|WorkFlow, which could be added to Agila ...
>
> > Christopher : How do you feel the futur of Agila BPM. I think you write
> somewhere that Italio Worflow has already all the features planned to be
> released in Agila BPM. So, what next ?
>
> I'm sure that Agila will change a lot in the next weeks / months.
> But the governance decisions seems to be hard to take (one or two projects,
> unique or multiple implementations, etc)
> What do you think about ?
>
> --
> </arnaud>
>
>

[M G-4]

Hi,

Please tell me what we need to do to participate in the developement of
Agila or Ode.

I am a java developer with nearly 6 yrs of experience. I have experience
with web services, workflow (BPEL) , web technologies, Swings, multithreaded
programming and various open source projects.

I want to participate as a developer. Please suggest!

Thanks,
Mohit.

On 23/03/06, Christopher Lim <christopher.a.lim@...> wrote:

>
> Hi Arnaud,
>
> > > Christopher : How do you feel the futur of Agila BPM. I think you
> write
> > somewhere that Italio Worflow has already all the features planned to be
> > released in Agila BPM.
>
> I took a look at Intalio's web site at that time and they have the
> designer, engine, and
> web interface. Basically that is the roadmap for Agila BPM. However, I
> misinterpreted things. I was thinking that Intalio will be donating
> the whole stuff where in fact they've only mentioned the BPEL part and
> that is for ODE.
>
>
> > So, what next ?
>
> Agila BPM needs more developers to work on the code. Your help is very
> welcome. ;) Let's build a great open source BPM impl.
>
>
> > I'm sure that Agila will change a lot in the next weeks / months.
> > But the governance decisions seems to be hard to take (one or two
> projects,
> > unique or multiple implementations, etc)
> > What do you think about ?
>
> Well, I think it is like that with open source. Let the community decide.
>
>
> Cheers!
>
> Chris
>
>
>
>
> On 3/23/06, Arnaud Quiblier <aquiblier@...> wrote:
> > Thanks Matthieu.
> >
> > Just after having sent my first two posts, I saw the mailing-list
> > general@..., which I read whith interest.
> > And I found the ref to the ODE mailing list too !!!
> >
> > I hope that all the work done on Twister/Agila BPEL will be appriciate
> > during ODE development.
> >
> > Same hope for Agila BPM.
> > Asap, I will look at Intalio|WorkFlow, which could be added to Agila ...
> >
> > > Christopher : How do you feel the futur of Agila BPM. I think you
> write
> > somewhere that Italio Worflow has already all the features planned to be
> > released in Agila BPM. So, what next ?
> >
> > I'm sure that Agila will change a lot in the next weeks / months.
> > But the governance decisions seems to be hard to take (one or two
> projects,
> > unique or multiple implementations, etc)
> > What do you think about ?
> >
> > --
> > </arnaud>
> >
> >
>

[Christopher Lim]

Please look at this link to give you an idea:
http://www.apache.org/foundation/how-it-works.html#meritocracy

I'm sure your contribution will be very welcome. :)

Chris





On 3/23/06, M G <mg.aryans@...> wrote:

> Hi,
>
> Please tell me what we need to do to participate in the developement of
> Agila or Ode.
>
> I am a java developer with nearly 6 yrs of experience. I have experience
> with web services, workflow (BPEL) , web technologies, Swings, multithreaded
> programming and various open source projects.
>
> I want to participate as a developer. Please suggest!
>
> Thanks,
> Mohit.
>
> On 23/03/06, Christopher Lim <christopher.a.lim@...> wrote:
> >
> > Hi Arnaud,
> >
> > > > Christopher : How do you feel the futur of Agila BPM. I think you
> > write
> > > somewhere that Italio Worflow has already all the features planned to be
> > > released in Agila BPM.
> >
> > I took a look at Intalio's web site at that time and they have the
> > designer, engine, and
> > web interface. Basically that is the roadmap for Agila BPM. However, I
> > misinterpreted things. I was thinking that Intalio will be donating
> > the whole stuff where in fact they've only mentioned the BPEL part and
> > that is for ODE.
> >
> >
> > > So, what next ?
> >
> > Agila BPM needs more developers to work on the code. Your help is very
> > welcome. ;) Let's build a great open source BPM impl.
> >
> >
> > > I'm sure that Agila will change a lot in the next weeks / months.
> > > But the governance decisions seems to be hard to take (one or two
> > projects,
> > > unique or multiple implementations, etc)
> > > What do you think about ?
> >
> > Well, I think it is like that with open source. Let the community decide.
> >
> >
> > Cheers!
> >
> > Chris
> >
> >
> >
> >
> > On 3/23/06, Arnaud Quiblier <aquiblier@...> wrote:
> > > Thanks Matthieu.
> > >
> > > Just after having sent my first two posts, I saw the mailing-list
> > > general@..., which I read whith interest.
> > > And I found the ref to the ODE mailing list too !!!
> > >
> > > I hope that all the work done on Twister/Agila BPEL will be appriciate
> > > during ODE development.
> > >
> > > Same hope for Agila BPM.
> > > Asap, I will look at Intalio|WorkFlow, which could be added to Agila ...
> > >
> > > > Christopher : How do you feel the futur of Agila BPM. I think you
> > write
> > > somewhere that Italio Worflow has already all the features planned to be
> > > released in Agila BPM. So, what next ?
> > >
> > > I'm sure that Agila will change a lot in the next weeks / months.
> > > But the governance decisions seems to be hard to take (one or two
> > projects,
> > > unique or multiple implementations, etc)
> > > What do you think about ?
> > >
> > > --
> > > </arnaud>
> > >
> > >
> >
>
>

[Arnaud Quiblier]

Concerning Agila, please look at JIRA page :
 http://issues.apache.org/jira/browse/AGILA

Perhaps can Chris point out the major issues ...

--
</arnaud>

[Arnaud Quiblier]

> Agila BPM needs more developers to work on the code. Your help is very
> welcome. ;) Let's build a great open source BPM impl.


Sure I'll try to help ... despite I'm absolutly not a WorkFlow-BPM-BPEL
specialist at all !!!
I would like to enhance worflow patterns support, as issues #28 to #37.
But I must admit I'm experience difficulties regarding the way to implement
them ...


--
</arnaud>

[Christopher Lim]

Arnaud,

1. I'd like to consider the engine functionality as the most major
issue. Specifically task split/merge capability.

AGILA-29, AGILA-31, AGILA-32, AGILA-34

2. Then, there is also the need to split up the current source code
into Engine, Web Interface, and Designer components.

Chris





On 3/23/06, Arnaud Quiblier <aquiblier@...> wrote:
> Concerning Agila, please look at JIRA page :
>  http://issues.apache.org/jira/browse/AGILA
>
> Perhaps can Chris point out the major issues ...
>
> --
> </arnaud>
>
>

[Arnaud Quiblier]

> 2. Then, there is also the need to split up the current source code
> into Engine, Web Interface, and Designer components.


I think I'll try to split source code during this WE ...

You prepared three dirs in the SVN repo : core, console & designer ...
1/ Does the web-app go into console or anything else ?
2/ What's the prupose of the designer part ?


--
</arnaud>

[Christopher Lim]

core = engine
console = web app
designer = workflow designer.
                visual representation of the workflow xml. can be used
for designing a workflow.

I'm sorry but I don't understand "> I think I'll try to split source
code during this WE ..." :)

Cheers!
Chris


On 3/25/06, Arnaud Quiblier <aquiblier@...> wrote:

> > 2. Then, there is also the need to split up the current source code
> > into Engine, Web Interface, and Designer components.
>
>
> I think I'll try to split source code during this WE ...
>
> You prepared three dirs in the SVN repo : core, console & designer ...
> 1/ Does the web-app go into console or anything else ?
> 2/ What's the prupose of the designer part ?
>
>
> --
> </arnaud>
>
>

[Zubin Wadia]

Chris, it means - Weekend.

Z.
---------- Original Message ----------------------------------
From: "Christopher Lim" <christopher.a.lim@...>
Reply-To: agila-dev@...
Date:  Sat, 25 Mar 2006 00:56:10 +0800

>core = engine
>console = web app
>designer = workflow designer.
>                visual representation of the workflow xml. can be used
>for designing a workflow.
>
>I'm sorry but I don't understand "> I think I'll try to split source
>code during this WE ..." :)
>
>Cheers!
>Chris
>
>
>On 3/25/06, Arnaud Quiblier <aquiblier@...> wrote:
>> > 2. Then, there is also the need to split up the current source code
>> > into Engine, Web Interface, and Designer components.
>>
>>
>> I think I'll try to split source code during this WE ...
>>
>> You prepared three dirs in the SVN repo : core, console & designer ...
>> 1/ Does the web-app go into console or anything else ?
>> 2/ What's the prupose of the designer part ?
>>
>>
>> --
>> </arnaud>
>>
>>
>

 




________________________________________________________________
Sent via the WebMail system at mail.imagewk.com


 
                   

[Christopher Lim]

Cool. Thanks. ;)

Chris


On 3/25/06, Zubin Wadia <zwadia@...> wrote:

> Chris, it means - Weekend.
>
> Z.
> ---------- Original Message ----------------------------------
> From: "Christopher Lim" <christopher.a.lim@...>
> Reply-To: agila-dev@...
> Date:  Sat, 25 Mar 2006 00:56:10 +0800
>
> >core = engine
> >console = web app
> >designer = workflow designer.
> >                visual representation of the workflow xml. can be used
> >for designing a workflow.
> >
> >I'm sorry but I don't understand "> I think I'll try to split source
> >code during this WE ..." :)
> >
> >Cheers!
> >Chris
> >
> >
> >On 3/25/06, Arnaud Quiblier <aquiblier@...> wrote:
> >> > 2. Then, there is also the need to split up the current source code
> >> > into Engine, Web Interface, and Designer components.
> >>
> >>
> >> I think I'll try to split source code during this WE ...
> >>
> >> You prepared three dirs in the SVN repo : core, console & designer ...
> >> 1/ Does the web-app go into console or anything else ?
> >> 2/ What's the prupose of the designer part ?
> >>
> >>
> >> --
> >> </arnaud>
> >>
> >>
> >
>
>
>
>
>
> ________________________________________________________________
> Sent via the WebMail system at mail.imagewk.com
>
>
>
>
>

[Christopher Lim]

> I think I'll try to split source code during this WE

I look forward to that.

Thanks,
Chris


...

>
> You prepared three dirs in the SVN repo : core, console & designer ...
> 1/ Does the web-app go into console or anything else ?
> 2/ What's the prupose of the designer part ?
>
>
> --
> </arnaud>
>
>