Noel, we do seem to be coming together in prinicipal but it might be best to
achieve our "fresh start" in the practical context of Ode given the support
exhibited by other folks on the submission.

In Apache projects address a certain area of concern (e.g., JAXB, BPEL,
CORBA etc.) but they do so in the context of an community based
implementation (as opposed to standards committees, which don't have
implementations).  Likewise, Agila is an implementation and having two
implementations in the same project could be confusing.

For Ode, what we have come up with to date is our contribution...there may
be something else that fits that bill as well but I have not been exposed to
those other offerings yet and we do have some approval of what we have
proposed.

I appreciate folks need to support current users of the Agila code base but
I need to lean with the critical mass of the community.  I hope you'll
support this new proposal too.

On 2/14/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
>
> Bill,
>
> From what I am reading today between you, Geir, Lance and Mattieu, it
> seems
> that there is an emerging consensus, so if you are all willing, we could
> add
> your team as committers to Agila and import the code base as soon as we
> have
> the software grant (I haven't checked to see if that is already
> filed).  We
> will have multiple engines unless/until the people working on them decide
> to
> merge them, but will look for the workflow community to come together as
> one, while managing multiple engines and supporting a variety of client
> projects.
>
> I would hope to see everyone who has been in favor of workflow, but not
> sure
> about how it was being imported, to be active in helping to build a
> healthy
> workflow community.  Personally, I look forward to seeing happy,
> enthusiastic, comments; cross-pollination; many using projects; and an
> overall advancement in solutions to the problem domain.
>
>         --- Noel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to