You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2006/06/15 06:32:09 UTC
REMINDER: Incubator Quarterly Board Reports Are Due
It is that time again. Please have your reports posted to
http://wiki.apache.org/incubator/June2006
by Sunday afternoon AT THE LATEST. Please do not be late. I will not be
able to handle last minute additions.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Matthias Wessendorf <ma...@apache.org>.
sure,
we all should take care :)
I am just looking for a nice status file template.
On 6/14/06, Adam Winer <aw...@gmail.com> wrote:
> Matthias,
>
> Thanks for the update; I can take care of this, right?
>
> -- Adam
>
>
> On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > FYI...
> >
> > ---------- Forwarded message ----------
> > From: Noel J. Bergman <no...@devtech.com>
> > Date: Jun 14, 2006 9:32 PM
> > Subject: REMINDER: Incubator Quarterly Board Reports Are Due
> > To: general@incubator.apache.org
> >
> >
> > It is that time again. Please have your reports posted to
> >
> > http://wiki.apache.org/incubator/June2006
> >
> > by Sunday afternoon AT THE LATEST. Please do not be late. I will not be
> > able to handle last minute additions.
> >
> > --- Noel
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
> >
> > --
> > Matthias Wessendorf
> > Aechterhoek 18
> > 48282 Emsdetten
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
>
--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Matthias Wessendorf <ma...@apache.org>.
Any open tasks ?!?
I did a bit wiki
a bit status file
and patch for the incubator side.
What's missing?
On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> Again me :)
>
> I committed a first version of a STATUS file to the incubator
> subversion (see [1]).
> This guy should grow and grow and grow during the next days/weeks ;)
>
> -Matthias
>
> [1] http://svn.apache.org/viewvc/incubator/adffaces/trunk/STATUS
>
> On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > Adam,
> >
> > I didn't add Omar to this file. But Jonas. Jonas is listed at [1]. Omar not.
> > But I guess that this fact won't be changed, right.
> >
> > -Matthias
> >
> > [1] http://people.apache.org/~jim/committers.html
> >
> > On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > > Craig-
> > >
> > > I changed some doc for [1]. Patch attached.
> > >
> > > -Matthias
> > >
> > > [1] http://incubator.apache.org/projects/adffaces.html
> > >
> > > On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > Craig,
> > > >
> > > > I did an upload for the "mvn site" build during this week (see [1]).
> > > > I think it should be available under http://incubator.apache.org/adffaces
> > > > Or should we use the *new* name?
> > > > To me the new name is much more important, to get out of the
> > > > incubator, since this code is donated by Oralce
> > > >
> > > > -Matthias
> > > >
> > > > [1] http://people.apache.org/~matzew/trinidad_doc/
> > > >
> > > > On 6/14/06, Craig McClanahan <cr...@apache.org> wrote:
> > > > > On 6/14/06, Adam Winer <aw...@gmail.com> wrote:
> > > > > >
> > > > > > Matthias,
> > > > > >
> > > > > > Thanks for the update; I can take care of this, right?
> > > > >
> > > > >
> > > > > Within the incubator, it is normally the mentor's job to do the actual
> > > > > reporting (as well as updating the status page). But, obviously, you guys
> > > > > are the ones that can feed me highlights we'd like to mention since last
> > > > > month.
> > > > >
> > > > > After graduation, reponsibility for reporting to the Board belongs to the
> > > > > PMC chair for the appropriate top level project.
> > > > >
> > > > > -- Adam
> > > > >
> > > > >
> > > > > Craig
> > > > >
> > > > > On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > > > > FYI...
> > > > > > >
> > > > > > > ---------- Forwarded message ----------
> > > > > > > From: Noel J. Bergman <no...@devtech.com>
> > > > > > > Date: Jun 14, 2006 9:32 PM
> > > > > > > Subject: REMINDER: Incubator Quarterly Board Reports Are Due
> > > > > > > To: general@incubator.apache.org
> > > > > > >
> > > > > > >
> > > > > > > It is that time again. Please have your reports posted to
> > > > > > >
> > > > > > > http://wiki.apache.org/incubator/June2006
> > > > > > >
> > > > > > > by Sunday afternoon AT THE LATEST. Please do not be late. I will not
> > > > > > be
> > > > > > > able to handle last minute additions.
> > > > > > >
> > > > > > > --- Noel
> > > > > > >
> > > > > > >
> > > > > > > ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Matthias Wessendorf
> > > > > > > Aechterhoek 18
> > > > > > > 48282 Emsdetten
> > > > > > > blog: http://jroller.com/page/mwessendorf
> > > > > > > mail: mwessendorf-at-gmail-dot-com
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > > Aechterhoek 18
> > > > 48282 Emsdetten
> > > > blog: http://jroller.com/page/mwessendorf
> > > > mail: mwessendorf-at-gmail-dot-com
> > > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > > Aechterhoek 18
> > > 48282 Emsdetten
> > > blog: http://jroller.com/page/mwessendorf
> > > mail: mwessendorf-at-gmail-dot-com
> > >
> > >
> > >
> >
> >
> > --
> > Matthias Wessendorf
> > Aechterhoek 18
> > 48282 Emsdetten
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
>
>
> --
> Matthias Wessendorf
> Aechterhoek 18
> 48282 Emsdetten
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Matthias Wessendorf <ma...@apache.org>.
Again me :)
I committed a first version of a STATUS file to the incubator
subversion (see [1]).
This guy should grow and grow and grow during the next days/weeks ;)
-Matthias
[1] http://svn.apache.org/viewvc/incubator/adffaces/trunk/STATUS
On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> Adam,
>
> I didn't add Omar to this file. But Jonas. Jonas is listed at [1]. Omar not.
> But I guess that this fact won't be changed, right.
>
> -Matthias
>
> [1] http://people.apache.org/~jim/committers.html
>
> On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > Craig-
> >
> > I changed some doc for [1]. Patch attached.
> >
> > -Matthias
> >
> > [1] http://incubator.apache.org/projects/adffaces.html
> >
> > On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > > Craig,
> > >
> > > I did an upload for the "mvn site" build during this week (see [1]).
> > > I think it should be available under http://incubator.apache.org/adffaces
> > > Or should we use the *new* name?
> > > To me the new name is much more important, to get out of the
> > > incubator, since this code is donated by Oralce
> > >
> > > -Matthias
> > >
> > > [1] http://people.apache.org/~matzew/trinidad_doc/
> > >
> > > On 6/14/06, Craig McClanahan <cr...@apache.org> wrote:
> > > > On 6/14/06, Adam Winer <aw...@gmail.com> wrote:
> > > > >
> > > > > Matthias,
> > > > >
> > > > > Thanks for the update; I can take care of this, right?
> > > >
> > > >
> > > > Within the incubator, it is normally the mentor's job to do the actual
> > > > reporting (as well as updating the status page). But, obviously, you guys
> > > > are the ones that can feed me highlights we'd like to mention since last
> > > > month.
> > > >
> > > > After graduation, reponsibility for reporting to the Board belongs to the
> > > > PMC chair for the appropriate top level project.
> > > >
> > > > -- Adam
> > > >
> > > >
> > > > Craig
> > > >
> > > > On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > > > FYI...
> > > > > >
> > > > > > ---------- Forwarded message ----------
> > > > > > From: Noel J. Bergman <no...@devtech.com>
> > > > > > Date: Jun 14, 2006 9:32 PM
> > > > > > Subject: REMINDER: Incubator Quarterly Board Reports Are Due
> > > > > > To: general@incubator.apache.org
> > > > > >
> > > > > >
> > > > > > It is that time again. Please have your reports posted to
> > > > > >
> > > > > > http://wiki.apache.org/incubator/June2006
> > > > > >
> > > > > > by Sunday afternoon AT THE LATEST. Please do not be late. I will not
> > > > > be
> > > > > > able to handle last minute additions.
> > > > > >
> > > > > > --- Noel
> > > > > >
> > > > > >
> > > > > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Matthias Wessendorf
> > > > > > Aechterhoek 18
> > > > > > 48282 Emsdetten
> > > > > > blog: http://jroller.com/page/mwessendorf
> > > > > > mail: mwessendorf-at-gmail-dot-com
> > > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > > Aechterhoek 18
> > > 48282 Emsdetten
> > > blog: http://jroller.com/page/mwessendorf
> > > mail: mwessendorf-at-gmail-dot-com
> > >
> >
> >
> > --
> > Matthias Wessendorf
> > Aechterhoek 18
> > 48282 Emsdetten
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
> >
> >
>
>
> --
> Matthias Wessendorf
> Aechterhoek 18
> 48282 Emsdetten
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Matthias Wessendorf <ma...@apache.org>.
Adam,
I didn't add Omar to this file. But Jonas. Jonas is listed at [1]. Omar not.
But I guess that this fact won't be changed, right.
-Matthias
[1] http://people.apache.org/~jim/committers.html
On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> Craig-
>
> I changed some doc for [1]. Patch attached.
>
> -Matthias
>
> [1] http://incubator.apache.org/projects/adffaces.html
>
> On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > Craig,
> >
> > I did an upload for the "mvn site" build during this week (see [1]).
> > I think it should be available under http://incubator.apache.org/adffaces
> > Or should we use the *new* name?
> > To me the new name is much more important, to get out of the
> > incubator, since this code is donated by Oralce
> >
> > -Matthias
> >
> > [1] http://people.apache.org/~matzew/trinidad_doc/
> >
> > On 6/14/06, Craig McClanahan <cr...@apache.org> wrote:
> > > On 6/14/06, Adam Winer <aw...@gmail.com> wrote:
> > > >
> > > > Matthias,
> > > >
> > > > Thanks for the update; I can take care of this, right?
> > >
> > >
> > > Within the incubator, it is normally the mentor's job to do the actual
> > > reporting (as well as updating the status page). But, obviously, you guys
> > > are the ones that can feed me highlights we'd like to mention since last
> > > month.
> > >
> > > After graduation, reponsibility for reporting to the Board belongs to the
> > > PMC chair for the appropriate top level project.
> > >
> > > -- Adam
> > >
> > >
> > > Craig
> > >
> > > On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > > FYI...
> > > > >
> > > > > ---------- Forwarded message ----------
> > > > > From: Noel J. Bergman <no...@devtech.com>
> > > > > Date: Jun 14, 2006 9:32 PM
> > > > > Subject: REMINDER: Incubator Quarterly Board Reports Are Due
> > > > > To: general@incubator.apache.org
> > > > >
> > > > >
> > > > > It is that time again. Please have your reports posted to
> > > > >
> > > > > http://wiki.apache.org/incubator/June2006
> > > > >
> > > > > by Sunday afternoon AT THE LATEST. Please do not be late. I will not
> > > > be
> > > > > able to handle last minute additions.
> > > > >
> > > > > --- Noel
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Matthias Wessendorf
> > > > > Aechterhoek 18
> > > > > 48282 Emsdetten
> > > > > blog: http://jroller.com/page/mwessendorf
> > > > > mail: mwessendorf-at-gmail-dot-com
> > > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Matthias Wessendorf
> > Aechterhoek 18
> > 48282 Emsdetten
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
>
>
> --
> Matthias Wessendorf
> Aechterhoek 18
> 48282 Emsdetten
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
>
>
--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Matthias Wessendorf <ma...@apache.org>.
Craig-
I changed some doc for [1]. Patch attached.
-Matthias
[1] http://incubator.apache.org/projects/adffaces.html
On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> Craig,
>
> I did an upload for the "mvn site" build during this week (see [1]).
> I think it should be available under http://incubator.apache.org/adffaces
> Or should we use the *new* name?
> To me the new name is much more important, to get out of the
> incubator, since this code is donated by Oralce
>
> -Matthias
>
> [1] http://people.apache.org/~matzew/trinidad_doc/
>
> On 6/14/06, Craig McClanahan <cr...@apache.org> wrote:
> > On 6/14/06, Adam Winer <aw...@gmail.com> wrote:
> > >
> > > Matthias,
> > >
> > > Thanks for the update; I can take care of this, right?
> >
> >
> > Within the incubator, it is normally the mentor's job to do the actual
> > reporting (as well as updating the status page). But, obviously, you guys
> > are the ones that can feed me highlights we'd like to mention since last
> > month.
> >
> > After graduation, reponsibility for reporting to the Board belongs to the
> > PMC chair for the appropriate top level project.
> >
> > -- Adam
> >
> >
> > Craig
> >
> > On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > > > FYI...
> > > >
> > > > ---------- Forwarded message ----------
> > > > From: Noel J. Bergman <no...@devtech.com>
> > > > Date: Jun 14, 2006 9:32 PM
> > > > Subject: REMINDER: Incubator Quarterly Board Reports Are Due
> > > > To: general@incubator.apache.org
> > > >
> > > >
> > > > It is that time again. Please have your reports posted to
> > > >
> > > > http://wiki.apache.org/incubator/June2006
> > > >
> > > > by Sunday afternoon AT THE LATEST. Please do not be late. I will not
> > > be
> > > > able to handle last minute additions.
> > > >
> > > > --- Noel
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > > For additional commands, e-mail: general-help@incubator.apache.org
> > > >
> > > >
> > > >
> > > > --
> > > > Matthias Wessendorf
> > > > Aechterhoek 18
> > > > 48282 Emsdetten
> > > > blog: http://jroller.com/page/mwessendorf
> > > > mail: mwessendorf-at-gmail-dot-com
> > > >
> > >
> >
> >
>
>
> --
> Matthias Wessendorf
> Aechterhoek 18
> 48282 Emsdetten
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Matthias Wessendorf <ma...@apache.org>.
Craig,
I did an upload for the "mvn site" build during this week (see [1]).
I think it should be available under http://incubator.apache.org/adffaces
Or should we use the *new* name?
To me the new name is much more important, to get out of the
incubator, since this code is donated by Oralce
-Matthias
[1] http://people.apache.org/~matzew/trinidad_doc/
On 6/14/06, Craig McClanahan <cr...@apache.org> wrote:
> On 6/14/06, Adam Winer <aw...@gmail.com> wrote:
> >
> > Matthias,
> >
> > Thanks for the update; I can take care of this, right?
>
>
> Within the incubator, it is normally the mentor's job to do the actual
> reporting (as well as updating the status page). But, obviously, you guys
> are the ones that can feed me highlights we'd like to mention since last
> month.
>
> After graduation, reponsibility for reporting to the Board belongs to the
> PMC chair for the appropriate top level project.
>
> -- Adam
>
>
> Craig
>
> On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > > FYI...
> > >
> > > ---------- Forwarded message ----------
> > > From: Noel J. Bergman <no...@devtech.com>
> > > Date: Jun 14, 2006 9:32 PM
> > > Subject: REMINDER: Incubator Quarterly Board Reports Are Due
> > > To: general@incubator.apache.org
> > >
> > >
> > > It is that time again. Please have your reports posted to
> > >
> > > http://wiki.apache.org/incubator/June2006
> > >
> > > by Sunday afternoon AT THE LATEST. Please do not be late. I will not
> > be
> > > able to handle last minute additions.
> > >
> > > --- Noel
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> > >
> > >
> > > --
> > > Matthias Wessendorf
> > > Aechterhoek 18
> > > 48282 Emsdetten
> > > blog: http://jroller.com/page/mwessendorf
> > > mail: mwessendorf-at-gmail-dot-com
> > >
> >
>
>
--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Craig McClanahan <cr...@apache.org>.
On 6/14/06, Adam Winer <aw...@gmail.com> wrote:
>
> Matthias,
>
> Thanks for the update; I can take care of this, right?
Within the incubator, it is normally the mentor's job to do the actual
reporting (as well as updating the status page). But, obviously, you guys
are the ones that can feed me highlights we'd like to mention since last
month.
After graduation, reponsibility for reporting to the Board belongs to the
PMC chair for the appropriate top level project.
-- Adam
Craig
On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> > FYI...
> >
> > ---------- Forwarded message ----------
> > From: Noel J. Bergman <no...@devtech.com>
> > Date: Jun 14, 2006 9:32 PM
> > Subject: REMINDER: Incubator Quarterly Board Reports Are Due
> > To: general@incubator.apache.org
> >
> >
> > It is that time again. Please have your reports posted to
> >
> > http://wiki.apache.org/incubator/June2006
> >
> > by Sunday afternoon AT THE LATEST. Please do not be late. I will not
> be
> > able to handle last minute additions.
> >
> > --- Noel
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
> >
> > --
> > Matthias Wessendorf
> > Aechterhoek 18
> > 48282 Emsdetten
> > blog: http://jroller.com/page/mwessendorf
> > mail: mwessendorf-at-gmail-dot-com
> >
>
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Adam Winer <aw...@gmail.com>.
Matthias,
Thanks for the update; I can take care of this, right?
-- Adam
On 6/14/06, Matthias Wessendorf <ma...@apache.org> wrote:
> FYI...
>
> ---------- Forwarded message ----------
> From: Noel J. Bergman <no...@devtech.com>
> Date: Jun 14, 2006 9:32 PM
> Subject: REMINDER: Incubator Quarterly Board Reports Are Due
> To: general@incubator.apache.org
>
>
> It is that time again. Please have your reports posted to
>
> http://wiki.apache.org/incubator/June2006
>
> by Sunday afternoon AT THE LATEST. Please do not be late. I will not be
> able to handle last minute additions.
>
> --- Noel
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
>
> --
> Matthias Wessendorf
> Aechterhoek 18
> 48282 Emsdetten
> blog: http://jroller.com/page/mwessendorf
> mail: mwessendorf-at-gmail-dot-com
>
Fwd: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Matthias Wessendorf <ma...@apache.org>.
FYI...
---------- Forwarded message ----------
From: Noel J. Bergman <no...@devtech.com>
Date: Jun 14, 2006 9:32 PM
Subject: REMINDER: Incubator Quarterly Board Reports Are Due
To: general@incubator.apache.org
It is that time again. Please have your reports posted to
http://wiki.apache.org/incubator/June2006
by Sunday afternoon AT THE LATEST. Please do not be late. I will not be
able to handle last minute additions.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
--
Matthias Wessendorf
Aechterhoek 18
48282 Emsdetten
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Lance Waterman <la...@gmail.com>.
Thanks Alex,
I think this is accurate with one addition. Cory is working on the "Context"
API and should have something to post by next week.
Lance
On 6/15/06, Alex Boisvert <bo...@intalio.com> wrote:
>
>
> Speaking of status, here's my understanding of ongoing work:
>
> 1) Maciej is working on providing detailed description for the scenarios
> identified by Cory. This is a necessary step to continue the discussion
> on the Jacob module.
>
> 2) Lance, Paul and Zubin are working on the Deployment API and
> relationship to the proposed Integration API.
>
> 3) There's ongoing work for retooling PXE with the proposed Integration
> API, which provides validation of its semantics and real-world use, as
> well as tangible progress towards our roadmap. This has happened
> outside of the incubator initially because of access rights issue which
> I think are now resolved. So I'd like to know if there's interest for
> moving this into the incubator now.
>
> Anything else that I'm missing? It would be good to hear from people to
> know what's going on on a more regular basis <nudge! nudge!>
>
> It think we should have our next IRC session as soon as we have #1 from
> Maciej above.
>
> alex
>
>
> Matthieu Riou wrote:
> > Perfect! I've just added a short sentence to reflect the undergoing
> > effort
> > from Maciej and others to document PXE.
> >
> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
> >>
> >>
> >> > Can someone please step up and help?
> >>
> >> Either I stepped up or everyone else stepped back... I put a couple
> >> of lines into the wiki about the work with the integration and
> >> deployment APIs.
> >>
> >> ---
> >> Paul R Brown
> >> paulrbrown@gmail.com
> >> http://mult.ifario.us/
> >>
> >>
> >>
> >>
> >
>
>
Re: Jacob documentation
Posted by Davanum Srinivas <da...@gmail.com>.
Lance,
FYI, i raised a support request with root and cc'ed you.
-- dims
On 6/29/06, Lance Waterman <la...@gmail.com> wrote:
> Thanks Matthieu,
>
> To the best of my knowledge I have not received an email with my apache
> account information. The only email I have is from Dims ...
>
> >>FYI, accounts were created for the following:
> >>bflood,paulrbrown,lwaterman >>,charper,assaf,boisvert
>
> >>thanks,
> >>dims
>
> Lance
>
>
> On 6/29/06, Matthieu Riou < matthieu.riou@gmail.com> wrote:
> >
> > Lance,
> >
> > You don't need any password for the wiki, it's open to regsitration. Just
> > register using your full name and any password you like. For SVN I think
> > you'll have to login to people.apache.org to setup your password but I
> > think
> > that's explained in the e-mail you received with your apache account
> > information.
> >
> > Cheers,
> >
> > Matthieu.
> >
> > On 6/29/06, Lance Waterman < lance.waterman@gmail.com> wrote:
> > >
> > > Yes, I found the the documentation very helpful. I would like to ask a
> > > couple of detail questions around persistence.
> > >
> > > 1) I would like to understand the purpose of the following method found
> > in
> > > the "BpelAbstraction" class:
> > >
> > > protected BpelRuntimeContext getBpelRuntimeContext() {
> > > BpelRuntimeContext nativeApi = (BpelRuntimeContext)
> > > JacobVPU.activeJacobThread().getExtension( BpelRuntimeContext.class);
> > > assert nativeApi != null;
> > > return nativeApi;
> > > }
> > >
> > > and then from the JacobThread interface ...
> > >
> > > /**
> > > * DOCUMENTME
> > > *
> > > * @param extensionClass DOCUMENTME
> > > *
> > > * @return DOCUMENTME
> > > */
> > > public Object getExtension(Class extensionClass);
> > >
> > > Does registering the process context with the VPU tie the process
> > context
> > > to
> > > the Soup frame ( i.e. FastSoupImpl.ChannelFrame ) in some way or is this
> > > just utilizing the JacobVPU singleton?
> > >
> > > 2) For a BPEL process, will there ever be a case where reactions remain
> > in
> > > the Soup queue at the time Soup.write() is called? If I am thinking
> > about
> > > this correctly there should only be objects in the channel frame and
> > > object
> > > frame?
> > >
> > > 3) Why are outstanding BPEL requests persisted into the Soup ( i.e.
> > > soup.setGlobalData(_outstandingRequests); )? These seem to be BPEL
> > > correlation specific artifacts and I don't understand why they need to
> > be
> > > part of the VPU?
> > >
> > > Alex - I would like to walk through the code that hooks the JACOB engine
> >
> > > into the iapi and then after that perhaps we can have an IRC around what
> > > the
> > > build should look like for the ODE trunk? On a side note - I'd like to
> > > post
> > > some deployment documents to the Wiki and check in some code to the
> > > scratch
> > > area. I believe I have an Apache user account but I have not seen
> > anything
> > > about a password - do you know how to acquire a password?
> > >
> > > Thanks,
> > >
> > > Lance
> > >
> > >
> > >
> > >
> > > On 6/28/06, Alex Boisvert <bo...@intalio.com> wrote:
> > > >
> > > >
> > > > Oh and by the way, was the Jacob documentation helpful? What's the
> > next
> > > > step there?
> > > >
> > > > alex
> > > >
> > > >
> > > > Lance Waterman wrote:
> > > > > Alex,
> > > > >
> > > > > I have been reading through the JACOB documentation on the Wiki and
> > I
> > > > > think
> > > > > I'm at the point where #3 would be helpful. Could you move this into
> > > the
> > > > > scratch area where we can begin to walk through it?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Lance
> > > > >
> > > > > On 6/15/06, Alex Boisvert <bo...@intalio.com> wrote:
> > > > >>
> > > > >>
> > > > >> Speaking of status, here's my understanding of ongoing work:
> > > > >>
> > > > >> 1) Maciej is working on providing detailed description for the
> > > > scenarios
> > > > >> identified by Cory. This is a necessary step to continue the
> > > > discussion
> > > > >> on the Jacob module.
> > > > >>
> > > > >> 2) Lance, Paul and Zubin are working on the Deployment API and
> > > > >> relationship to the proposed Integration API.
> > > > >>
> > > > >> 3) There's ongoing work for retooling PXE with the proposed
> > > Integration
> > > > >> API, which provides validation of its semantics and real-world use,
> > > as
> > > > >> well as tangible progress towards our roadmap. This has happened
> > > > >> outside of the incubator initially because of access rights issue
> > > which
> > > > >> I think are now resolved. So I'd like to know if there's interest
> > > for
> > > > >> moving this into the incubator now.
> > > > >>
> > > > >> Anything else that I'm missing? It would be good to hear from
> > people
> > > > to
> > > > >> know what's going on on a more regular basis <nudge! nudge!>
> > > > >>
> > > > >> It think we should have our next IRC session as soon as we have #1
> > > from
> > > > >> Maciej above.
> > > > >>
> > > > >> alex
> > > > >>
> > > > >>
> > > > >> Matthieu Riou wrote:
> > > > >> > Perfect! I've just added a short sentence to reflect the
> > undergoing
> > > > >> > effort
> > > > >> > from Maciej and others to document PXE.
> > > > >> >
> > > > >> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
> > > > >> >>
> > > > >> >>
> > > > >> >> > Can someone please step up and help?
> > > > >> >>
> > > > >> >> Either I stepped up or everyone else stepped back... I put a
> > > couple
> > > > >> >> of lines into the wiki about the work with the integration and
> > > > >> >> deployment APIs.
> > > > >> >>
> > > > >> >> ---
> > > > >> >> Paul R Brown
> > > > >> >> paulrbrown@gmail.com
> > > > >> >> http://mult.ifario.us/
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > > >> >
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > > > --
> > > > Intalio :: The Business Process Management Company
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
--
Davanum Srinivas : http://people.apache.org/~dims/
Re: Jacob documentation
Posted by Matthieu Riou <ma...@gmail.com>.
Then you'll have to go through the doc:
http://apache.org/dev/new-committers-guide.html
http://apache.org/dev/
Matt.
On 6/29/06, Lance Waterman <la...@gmail.com> wrote:
>
> Thanks Matthieu,
>
> To the best of my knowledge I have not received an email with my apache
> account information. The only email I have is from Dims ...
>
> >>FYI, accounts were created for the following:
> >>bflood,paulrbrown,lwaterman >>,charper,assaf,boisvert
>
> >>thanks,
> >>dims
>
> Lance
>
>
> On 6/29/06, Matthieu Riou < matthieu.riou@gmail.com> wrote:
> >
> > Lance,
> >
> > You don't need any password for the wiki, it's open to regsitration.
> > Just
> > register using your full name and any password you like. For SVN I think
> > you'll have to login to people.apache.org to setup your password but I
> > think
> > that's explained in the e-mail you received with your apache account
> > information.
> >
> > Cheers,
> >
> > Matthieu.
> >
> > On 6/29/06, Lance Waterman < lance.waterman@gmail.com> wrote:
> > >
> > > Yes, I found the the documentation very helpful. I would like to ask a
> > > couple of detail questions around persistence.
> > >
> > > 1) I would like to understand the purpose of the following method
> > found in
> > > the "BpelAbstraction" class:
> > >
> > > protected BpelRuntimeContext getBpelRuntimeContext() {
> > > BpelRuntimeContext nativeApi = (BpelRuntimeContext)
> > > JacobVPU.activeJacobThread().getExtension( BpelRuntimeContext.class);
> > > assert nativeApi != null;
> > > return nativeApi;
> > > }
> > >
> > > and then from the JacobThread interface ...
> > >
> > > /**
> > > * DOCUMENTME
> > > *
> > > * @param extensionClass DOCUMENTME
> > > *
> > > * @return DOCUMENTME
> > > */
> > > public Object getExtension(Class extensionClass);
> > >
> > > Does registering the process context with the VPU tie the process
> > context
> > > to
> > > the Soup frame ( i.e. FastSoupImpl.ChannelFrame ) in some way or is
> > this
> > > just utilizing the JacobVPU singleton?
> > >
> > > 2) For a BPEL process, will there ever be a case where reactions
> > remain in
> > > the Soup queue at the time Soup.write() is called? If I am thinking
> > about
> > > this correctly there should only be objects in the channel frame and
> > > object
> > > frame?
> > >
> > > 3) Why are outstanding BPEL requests persisted into the Soup ( i.e.
> > > soup.setGlobalData(_outstandingRequests); )? These seem to be BPEL
> > > correlation specific artifacts and I don't understand why they need to
> > be
> > > part of the VPU?
> > >
> > > Alex - I would like to walk through the code that hooks the JACOB
> > engine
> > > into the iapi and then after that perhaps we can have an IRC around
> > what
> > > the
> > > build should look like for the ODE trunk? On a side note - I'd like to
> > > post
> > > some deployment documents to the Wiki and check in some code to the
> > > scratch
> > > area. I believe I have an Apache user account but I have not seen
> > anything
> > > about a password - do you know how to acquire a password?
> > >
> > > Thanks,
> > >
> > > Lance
> > >
> > >
> > >
> > >
> > > On 6/28/06, Alex Boisvert <bo...@intalio.com> wrote:
> > > >
> > > >
> > > > Oh and by the way, was the Jacob documentation helpful? What's the
> > next
> > > > step there?
> > > >
> > > > alex
> > > >
> > > >
> > > > Lance Waterman wrote:
> > > > > Alex,
> > > > >
> > > > > I have been reading through the JACOB documentation on the Wiki
> > and I
> > > > > think
> > > > > I'm at the point where #3 would be helpful. Could you move this
> > into
> > > the
> > > > > scratch area where we can begin to walk through it?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Lance
> > > > >
> > > > > On 6/15/06, Alex Boisvert <boisvert@intalio.com > wrote:
> > > > >>
> > > > >>
> > > > >> Speaking of status, here's my understanding of ongoing work:
> > > > >>
> > > > >> 1) Maciej is working on providing detailed description for the
> > > > scenarios
> > > > >> identified by Cory. This is a necessary step to continue the
> > > > discussion
> > > > >> on the Jacob module.
> > > > >>
> > > > >> 2) Lance, Paul and Zubin are working on the Deployment API and
> > > > >> relationship to the proposed Integration API.
> > > > >>
> > > > >> 3) There's ongoing work for retooling PXE with the proposed
> > > Integration
> > > > >> API, which provides validation of its semantics and real-world
> > use,
> > > as
> > > > >> well as tangible progress towards our roadmap. This has happened
> > > > >> outside of the incubator initially because of access rights issue
> > > which
> > > > >> I think are now resolved. So I'd like to know if there's
> > interest
> > > for
> > > > >> moving this into the incubator now.
> > > > >>
> > > > >> Anything else that I'm missing? It would be good to hear from
> > people
> > > > to
> > > > >> know what's going on on a more regular basis <nudge! nudge!>
> > > > >>
> > > > >> It think we should have our next IRC session as soon as we have
> > #1
> > > from
> > > > >> Maciej above.
> > > > >>
> > > > >> alex
> > > > >>
> > > > >>
> > > > >> Matthieu Riou wrote:
> > > > >> > Perfect! I've just added a short sentence to reflect the
> > undergoing
> > > > >> > effort
> > > > >> > from Maciej and others to document PXE.
> > > > >> >
> > > > >> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
> > > > >> >>
> > > > >> >>
> > > > >> >> > Can someone please step up and help?
> > > > >> >>
> > > > >> >> Either I stepped up or everyone else stepped back... I put a
> > > couple
> > > > >> >> of lines into the wiki about the work with the integration and
> >
> > > > >> >> deployment APIs.
> > > > >> >>
> > > > >> >> ---
> > > > >> >> Paul R Brown
> > > > >> >> paulrbrown@gmail.com
> > > > >> >> http://mult.ifario.us/
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > > >> >>
> > > > >> >
> > > > >>
> > > > >>
> > > > >
> > > >
> > > >
> > > > --
> > > > Intalio :: The Business Process Management Company
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
Re: Jacob documentation
Posted by Lance Waterman <la...@gmail.com>.
Thanks Matthieu,
To the best of my knowledge I have not received an email with my apache
account information. The only email I have is from Dims ...
>>FYI, accounts were created for the following:
>>bflood,paulrbrown,lwaterman >>,charper,assaf,boisvert
>>thanks,
>>dims
Lance
On 6/29/06, Matthieu Riou < matthieu.riou@gmail.com> wrote:
>
> Lance,
>
> You don't need any password for the wiki, it's open to regsitration. Just
> register using your full name and any password you like. For SVN I think
> you'll have to login to people.apache.org to setup your password but I
> think
> that's explained in the e-mail you received with your apache account
> information.
>
> Cheers,
>
> Matthieu.
>
> On 6/29/06, Lance Waterman < lance.waterman@gmail.com> wrote:
> >
> > Yes, I found the the documentation very helpful. I would like to ask a
> > couple of detail questions around persistence.
> >
> > 1) I would like to understand the purpose of the following method found
> in
> > the "BpelAbstraction" class:
> >
> > protected BpelRuntimeContext getBpelRuntimeContext() {
> > BpelRuntimeContext nativeApi = (BpelRuntimeContext)
> > JacobVPU.activeJacobThread().getExtension( BpelRuntimeContext.class);
> > assert nativeApi != null;
> > return nativeApi;
> > }
> >
> > and then from the JacobThread interface ...
> >
> > /**
> > * DOCUMENTME
> > *
> > * @param extensionClass DOCUMENTME
> > *
> > * @return DOCUMENTME
> > */
> > public Object getExtension(Class extensionClass);
> >
> > Does registering the process context with the VPU tie the process
> context
> > to
> > the Soup frame ( i.e. FastSoupImpl.ChannelFrame ) in some way or is this
> > just utilizing the JacobVPU singleton?
> >
> > 2) For a BPEL process, will there ever be a case where reactions remain
> in
> > the Soup queue at the time Soup.write() is called? If I am thinking
> about
> > this correctly there should only be objects in the channel frame and
> > object
> > frame?
> >
> > 3) Why are outstanding BPEL requests persisted into the Soup ( i.e.
> > soup.setGlobalData(_outstandingRequests); )? These seem to be BPEL
> > correlation specific artifacts and I don't understand why they need to
> be
> > part of the VPU?
> >
> > Alex - I would like to walk through the code that hooks the JACOB engine
>
> > into the iapi and then after that perhaps we can have an IRC around what
> > the
> > build should look like for the ODE trunk? On a side note - I'd like to
> > post
> > some deployment documents to the Wiki and check in some code to the
> > scratch
> > area. I believe I have an Apache user account but I have not seen
> anything
> > about a password - do you know how to acquire a password?
> >
> > Thanks,
> >
> > Lance
> >
> >
> >
> >
> > On 6/28/06, Alex Boisvert <bo...@intalio.com> wrote:
> > >
> > >
> > > Oh and by the way, was the Jacob documentation helpful? What's the
> next
> > > step there?
> > >
> > > alex
> > >
> > >
> > > Lance Waterman wrote:
> > > > Alex,
> > > >
> > > > I have been reading through the JACOB documentation on the Wiki and
> I
> > > > think
> > > > I'm at the point where #3 would be helpful. Could you move this into
> > the
> > > > scratch area where we can begin to walk through it?
> > > >
> > > > Thanks,
> > > >
> > > > Lance
> > > >
> > > > On 6/15/06, Alex Boisvert <bo...@intalio.com> wrote:
> > > >>
> > > >>
> > > >> Speaking of status, here's my understanding of ongoing work:
> > > >>
> > > >> 1) Maciej is working on providing detailed description for the
> > > scenarios
> > > >> identified by Cory. This is a necessary step to continue the
> > > discussion
> > > >> on the Jacob module.
> > > >>
> > > >> 2) Lance, Paul and Zubin are working on the Deployment API and
> > > >> relationship to the proposed Integration API.
> > > >>
> > > >> 3) There's ongoing work for retooling PXE with the proposed
> > Integration
> > > >> API, which provides validation of its semantics and real-world use,
> > as
> > > >> well as tangible progress towards our roadmap. This has happened
> > > >> outside of the incubator initially because of access rights issue
> > which
> > > >> I think are now resolved. So I'd like to know if there's interest
> > for
> > > >> moving this into the incubator now.
> > > >>
> > > >> Anything else that I'm missing? It would be good to hear from
> people
> > > to
> > > >> know what's going on on a more regular basis <nudge! nudge!>
> > > >>
> > > >> It think we should have our next IRC session as soon as we have #1
> > from
> > > >> Maciej above.
> > > >>
> > > >> alex
> > > >>
> > > >>
> > > >> Matthieu Riou wrote:
> > > >> > Perfect! I've just added a short sentence to reflect the
> undergoing
> > > >> > effort
> > > >> > from Maciej and others to document PXE.
> > > >> >
> > > >> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
> > > >> >>
> > > >> >>
> > > >> >> > Can someone please step up and help?
> > > >> >>
> > > >> >> Either I stepped up or everyone else stepped back... I put a
> > couple
> > > >> >> of lines into the wiki about the work with the integration and
> > > >> >> deployment APIs.
> > > >> >>
> > > >> >> ---
> > > >> >> Paul R Brown
> > > >> >> paulrbrown@gmail.com
> > > >> >> http://mult.ifario.us/
> > > >> >>
> > > >> >>
> > > >> >>
> > > >> >>
> > > >> >
> > > >>
> > > >>
> > > >
> > >
> > >
> > > --
> > > Intalio :: The Business Process Management Company
> > >
> > >
> > >
> >
> >
>
>
Re: Jacob documentation
Posted by Matthieu Riou <ma...@gmail.com>.
Lance,
You don't need any password for the wiki, it's open to regsitration. Just
register using your full name and any password you like. For SVN I think
you'll have to login to people.apache.org to setup your password but I think
that's explained in the e-mail you received with your apache account
information.
Cheers,
Matthieu.
On 6/29/06, Lance Waterman <la...@gmail.com> wrote:
>
> Yes, I found the the documentation very helpful. I would like to ask a
> couple of detail questions around persistence.
>
> 1) I would like to understand the purpose of the following method found in
> the "BpelAbstraction" class:
>
> protected BpelRuntimeContext getBpelRuntimeContext() {
> BpelRuntimeContext nativeApi = (BpelRuntimeContext)
> JacobVPU.activeJacobThread().getExtension(BpelRuntimeContext.class);
> assert nativeApi != null;
> return nativeApi;
> }
>
> and then from the JacobThread interface ...
>
> /**
> * DOCUMENTME
> *
> * @param extensionClass DOCUMENTME
> *
> * @return DOCUMENTME
> */
> public Object getExtension(Class extensionClass);
>
> Does registering the process context with the VPU tie the process context
> to
> the Soup frame ( i.e. FastSoupImpl.ChannelFrame ) in some way or is this
> just utilizing the JacobVPU singleton?
>
> 2) For a BPEL process, will there ever be a case where reactions remain in
> the Soup queue at the time Soup.write() is called? If I am thinking about
> this correctly there should only be objects in the channel frame and
> object
> frame?
>
> 3) Why are outstanding BPEL requests persisted into the Soup ( i.e.
> soup.setGlobalData(_outstandingRequests); )? These seem to be BPEL
> correlation specific artifacts and I don't understand why they need to be
> part of the VPU?
>
> Alex - I would like to walk through the code that hooks the JACOB engine
> into the iapi and then after that perhaps we can have an IRC around what
> the
> build should look like for the ODE trunk? On a side note - I'd like to
> post
> some deployment documents to the Wiki and check in some code to the
> scratch
> area. I believe I have an Apache user account but I have not seen anything
> about a password - do you know how to acquire a password?
>
> Thanks,
>
> Lance
>
>
>
>
> On 6/28/06, Alex Boisvert <bo...@intalio.com> wrote:
> >
> >
> > Oh and by the way, was the Jacob documentation helpful? What's the next
> > step there?
> >
> > alex
> >
> >
> > Lance Waterman wrote:
> > > Alex,
> > >
> > > I have been reading through the JACOB documentation on the Wiki and I
> > > think
> > > I'm at the point where #3 would be helpful. Could you move this into
> the
> > > scratch area where we can begin to walk through it?
> > >
> > > Thanks,
> > >
> > > Lance
> > >
> > > On 6/15/06, Alex Boisvert <bo...@intalio.com> wrote:
> > >>
> > >>
> > >> Speaking of status, here's my understanding of ongoing work:
> > >>
> > >> 1) Maciej is working on providing detailed description for the
> > scenarios
> > >> identified by Cory. This is a necessary step to continue the
> > discussion
> > >> on the Jacob module.
> > >>
> > >> 2) Lance, Paul and Zubin are working on the Deployment API and
> > >> relationship to the proposed Integration API.
> > >>
> > >> 3) There's ongoing work for retooling PXE with the proposed
> Integration
> > >> API, which provides validation of its semantics and real-world use,
> as
> > >> well as tangible progress towards our roadmap. This has happened
> > >> outside of the incubator initially because of access rights issue
> which
> > >> I think are now resolved. So I'd like to know if there's interest
> for
> > >> moving this into the incubator now.
> > >>
> > >> Anything else that I'm missing? It would be good to hear from people
> > to
> > >> know what's going on on a more regular basis <nudge! nudge!>
> > >>
> > >> It think we should have our next IRC session as soon as we have #1
> from
> > >> Maciej above.
> > >>
> > >> alex
> > >>
> > >>
> > >> Matthieu Riou wrote:
> > >> > Perfect! I've just added a short sentence to reflect the undergoing
> > >> > effort
> > >> > from Maciej and others to document PXE.
> > >> >
> > >> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
> > >> >>
> > >> >>
> > >> >> > Can someone please step up and help?
> > >> >>
> > >> >> Either I stepped up or everyone else stepped back... I put a
> couple
> > >> >> of lines into the wiki about the work with the integration and
> > >> >> deployment APIs.
> > >> >>
> > >> >> ---
> > >> >> Paul R Brown
> > >> >> paulrbrown@gmail.com
> > >> >> http://mult.ifario.us/
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >
> > >>
> > >>
> > >
> >
> >
> > --
> > Intalio :: The Business Process Management Company
> >
> >
> >
>
>
Re: Jacob documentation
Posted by Lance Waterman <la...@gmail.com>.
Maciej,
Thanks for clearing things up however, I'm still a bit confused by #1. Let
me ask the question in another way. Looking at the following method in
BpelRuntimeContextImpl ...
private void initVPU() {
vpu = new JacobVPU();
vpu.registerExtension(BpelRuntimeContext.class, this);
soup = new FastSoupImpl(null);
soup.setReplacementMap(_bpelProcess._replacementMap);
vpu.setContext(soup);
}
Why does the BpelRuntimeContext need to register itself with the VPU ( "
vpu.registerExtension(BpelRuntimeContext.class, this);")?
Lance
On 6/29/06, Maciej Szefler <mb...@intalio.com> wrote:
>
> On Thu, 2006-06-29 at 09:07 -0600, Lance Waterman wrote:
> > Yes, I found the the documentation very helpful. I would like to ask a
> > couple of detail questions around persistence.
> >
> > 1) I would like to understand the purpose of the following method found
> in
> > the "BpelAbstraction" class:
> >
> > protected BpelRuntimeContext getBpelRuntimeContext() {
> > BpelRuntimeContext nativeApi = (BpelRuntimeContext)
> > JacobVPU.activeJacobThread().getExtension(BpelRuntimeContext.class);
> > assert nativeApi != null;
> > return nativeApi;
> > }
> >
> Jacob knows nothing about BPEL. This is a mechanism to obtain an
> interface that allows the instance to interact with the BPEL engine
> facilities (such as external communication and data access).
>
> > and then from the JacobThread interface ...
> >
> > /**
> > * DOCUMENTME
> > *
> > * @param extensionClass DOCUMENTME
> > *
> > * @return DOCUMENTME
> > */
> > public Object getExtension(Class extensionClass);
> >
> > Does registering the process context with the VPU tie the process
> context to
> > the Soup frame ( i.e. FastSoupImpl.ChannelFrame ) in some way or is this
> > just utilizing the JacobVPU singleton?
>
> > 2) For a BPEL process, will there ever be a case where reactions remain
> in
> > the Soup queue at the time Soup.write() is called? If I am thinking
> about
> > this correctly there should only be objects in the channel frame and
> object
> > frame?
> Your understanding is mostly correct. The only time this happens in the
> PXE engine right now is if the processing of an instance takes
> inordinately long. This will happen if the process has an endless loop
> in it (typically a <While> with a bad condition).
>
> >
> > 3) Why are outstanding BPEL requests persisted into the Soup ( i.e.
> > soup.setGlobalData(_outstandingRequests); )? These seem to be BPEL
> > correlation specific artifacts and I don't understand why they need to
> be
> > part of the VPU?
> This is a bit of hack to allow global instance-level data to be stored
> without extending the DAO layer. The VPU does not actually interpret the
> outstandingRequest object it just stores it along with the rest of the
> execution state.
>
> > Alex - I would like to walk through the code that hooks the JACOB engine
> > into the iapi and then after that perhaps we can have an IRC around what
> the
> > build should look like for the ODE trunk? On a side note - I'd like to
> post
> > some deployment documents to the Wiki and check in some code to the
> scratch
> > area. I believe I have an Apache user account but I have not seen
> anything
> > about a password - do you know how to acquire a password?
> >
> > Thanks,
> >
> > Lance
> >
> >
> >
> >
> > On 6/28/06, Alex Boisvert <bo...@intalio.com> wrote:
> > >
> > >
> > > Oh and by the way, was the Jacob documentation helpful? What's the
> next
> > > step there?
> > >
> > > alex
> > >
> > >
> > > Lance Waterman wrote:
> > > > Alex,
> > > >
> > > > I have been reading through the JACOB documentation on the Wiki and
> I
> > > > think
> > > > I'm at the point where #3 would be helpful. Could you move this into
> the
> > > > scratch area where we can begin to walk through it?
> > > >
> > > > Thanks,
> > > >
> > > > Lance
> > > >
> > > > On 6/15/06, Alex Boisvert <bo...@intalio.com> wrote:
> > > >>
> > > >>
> > > >> Speaking of status, here's my understanding of ongoing work:
> > > >>
> > > >> 1) Maciej is working on providing detailed description for the
> > > scenarios
> > > >> identified by Cory. This is a necessary step to continue the
> > > discussion
> > > >> on the Jacob module.
> > > >>
> > > >> 2) Lance, Paul and Zubin are working on the Deployment API and
> > > >> relationship to the proposed Integration API.
> > > >>
> > > >> 3) There's ongoing work for retooling PXE with the proposed
> Integration
> > > >> API, which provides validation of its semantics and real-world use,
> as
> > > >> well as tangible progress towards our roadmap. This has happened
> > > >> outside of the incubator initially because of access rights issue
> which
> > > >> I think are now resolved. So I'd like to know if there's interest
> for
> > > >> moving this into the incubator now.
> > > >>
> > > >> Anything else that I'm missing? It would be good to hear from
> people
> > > to
> > > >> know what's going on on a more regular basis <nudge! nudge!>
> > > >>
> > > >> It think we should have our next IRC session as soon as we have #1
> from
> > > >> Maciej above.
> > > >>
> > > >> alex
> > > >>
> > > >>
> > > >> Matthieu Riou wrote:
> > > >> > Perfect! I've just added a short sentence to reflect the
> undergoing
> > > >> > effort
> > > >> > from Maciej and others to document PXE.
> > > >> >
> > > >> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
> > > >> >>
> > > >> >>
> > > >> >> > Can someone please step up and help?
> > > >> >>
> > > >> >> Either I stepped up or everyone else stepped back... I put a
> couple
> > > >> >> of lines into the wiki about the work with the integration and
> > > >> >> deployment APIs.
> > > >> >>
> > > >> >> ---
> > > >> >> Paul R Brown
> > > >> >> paulrbrown@gmail.com
> > > >> >> http://mult.ifario.us/
> > > >> >>
> > > >> >>
> > > >> >>
> > > >> >>
> > > >> >
> > > >>
> > > >>
> > > >
> > >
> > >
> > > --
> > > Intalio :: The Business Process Management Company
> > >
> > >
> > >
>
>
Re: Jacob documentation
Posted by Maciej Szefler <mb...@intalio.com>.
On Thu, 2006-06-29 at 09:07 -0600, Lance Waterman wrote:
> Yes, I found the the documentation very helpful. I would like to ask a
> couple of detail questions around persistence.
>
> 1) I would like to understand the purpose of the following method found in
> the "BpelAbstraction" class:
>
> protected BpelRuntimeContext getBpelRuntimeContext() {
> BpelRuntimeContext nativeApi = (BpelRuntimeContext)
> JacobVPU.activeJacobThread().getExtension(BpelRuntimeContext.class);
> assert nativeApi != null;
> return nativeApi;
> }
>
Jacob knows nothing about BPEL. This is a mechanism to obtain an
interface that allows the instance to interact with the BPEL engine
facilities (such as external communication and data access).
> and then from the JacobThread interface ...
>
> /**
> * DOCUMENTME
> *
> * @param extensionClass DOCUMENTME
> *
> * @return DOCUMENTME
> */
> public Object getExtension(Class extensionClass);
>
> Does registering the process context with the VPU tie the process context to
> the Soup frame ( i.e. FastSoupImpl.ChannelFrame ) in some way or is this
> just utilizing the JacobVPU singleton?
> 2) For a BPEL process, will there ever be a case where reactions remain in
> the Soup queue at the time Soup.write() is called? If I am thinking about
> this correctly there should only be objects in the channel frame and object
> frame?
Your understanding is mostly correct. The only time this happens in the
PXE engine right now is if the processing of an instance takes
inordinately long. This will happen if the process has an endless loop
in it (typically a <While> with a bad condition).
>
> 3) Why are outstanding BPEL requests persisted into the Soup ( i.e.
> soup.setGlobalData(_outstandingRequests); )? These seem to be BPEL
> correlation specific artifacts and I don't understand why they need to be
> part of the VPU?
This is a bit of hack to allow global instance-level data to be stored
without extending the DAO layer. The VPU does not actually interpret the
outstandingRequest object it just stores it along with the rest of the
execution state.
> Alex - I would like to walk through the code that hooks the JACOB engine
> into the iapi and then after that perhaps we can have an IRC around what the
> build should look like for the ODE trunk? On a side note - I'd like to post
> some deployment documents to the Wiki and check in some code to the scratch
> area. I believe I have an Apache user account but I have not seen anything
> about a password - do you know how to acquire a password?
>
> Thanks,
>
> Lance
>
>
>
>
> On 6/28/06, Alex Boisvert <bo...@intalio.com> wrote:
> >
> >
> > Oh and by the way, was the Jacob documentation helpful? What's the next
> > step there?
> >
> > alex
> >
> >
> > Lance Waterman wrote:
> > > Alex,
> > >
> > > I have been reading through the JACOB documentation on the Wiki and I
> > > think
> > > I'm at the point where #3 would be helpful. Could you move this into the
> > > scratch area where we can begin to walk through it?
> > >
> > > Thanks,
> > >
> > > Lance
> > >
> > > On 6/15/06, Alex Boisvert <bo...@intalio.com> wrote:
> > >>
> > >>
> > >> Speaking of status, here's my understanding of ongoing work:
> > >>
> > >> 1) Maciej is working on providing detailed description for the
> > scenarios
> > >> identified by Cory. This is a necessary step to continue the
> > discussion
> > >> on the Jacob module.
> > >>
> > >> 2) Lance, Paul and Zubin are working on the Deployment API and
> > >> relationship to the proposed Integration API.
> > >>
> > >> 3) There's ongoing work for retooling PXE with the proposed Integration
> > >> API, which provides validation of its semantics and real-world use, as
> > >> well as tangible progress towards our roadmap. This has happened
> > >> outside of the incubator initially because of access rights issue which
> > >> I think are now resolved. So I'd like to know if there's interest for
> > >> moving this into the incubator now.
> > >>
> > >> Anything else that I'm missing? It would be good to hear from people
> > to
> > >> know what's going on on a more regular basis <nudge! nudge!>
> > >>
> > >> It think we should have our next IRC session as soon as we have #1 from
> > >> Maciej above.
> > >>
> > >> alex
> > >>
> > >>
> > >> Matthieu Riou wrote:
> > >> > Perfect! I've just added a short sentence to reflect the undergoing
> > >> > effort
> > >> > from Maciej and others to document PXE.
> > >> >
> > >> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
> > >> >>
> > >> >>
> > >> >> > Can someone please step up and help?
> > >> >>
> > >> >> Either I stepped up or everyone else stepped back... I put a couple
> > >> >> of lines into the wiki about the work with the integration and
> > >> >> deployment APIs.
> > >> >>
> > >> >> ---
> > >> >> Paul R Brown
> > >> >> paulrbrown@gmail.com
> > >> >> http://mult.ifario.us/
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >
> > >>
> > >>
> > >
> >
> >
> > --
> > Intalio :: The Business Process Management Company
> >
> >
> >
Re: SVN
Posted by Davanum Srinivas <da...@gmail.com>.
please try now.
thanks,
dims
On 6/30/06, Maciej Szefler <mb...@intalio.com> wrote:
> So.. I'm getting a 403 FORBIDDEN error checking stuff into SVN. Perhaps
> someone with the right authority could fix that (account is mszefler).
> -maciej
>
>
--
Davanum Srinivas : http://people.apache.org/~dims/
SVN
Posted by Maciej Szefler <mb...@intalio.com>.
So.. I'm getting a 403 FORBIDDEN error checking stuff into SVN. Perhaps
someone with the right authority could fix that (account is mszefler).
-maciej
Re: Jacob documentation
Posted by cory <co...@gmail.com>.
I found the documentation to be helpful as well. Do you have any
information about the performance of the engine? Have you seen
performance problem with it at all?
Thanks.
-cory
On 6/29/06, Lance Waterman <la...@gmail.com> wrote:
> Yes, I found the the documentation very helpful. I would like to ask a
> couple of detail questions around persistence.
>
> 1) I would like to understand the purpose of the following method found in
> the "BpelAbstraction" class:
>
> protected BpelRuntimeContext getBpelRuntimeContext() {
> BpelRuntimeContext nativeApi = (BpelRuntimeContext)
> JacobVPU.activeJacobThread().getExtension(BpelRuntimeContext.class);
> assert nativeApi != null;
> return nativeApi;
> }
>
> and then from the JacobThread interface ...
>
> /**
> * DOCUMENTME
> *
> * @param extensionClass DOCUMENTME
> *
> * @return DOCUMENTME
> */
> public Object getExtension(Class extensionClass);
>
> Does registering the process context with the VPU tie the process context to
> the Soup frame ( i.e. FastSoupImpl.ChannelFrame ) in some way or is this
> just utilizing the JacobVPU singleton?
>
> 2) For a BPEL process, will there ever be a case where reactions remain in
> the Soup queue at the time Soup.write() is called? If I am thinking about
> this correctly there should only be objects in the channel frame and object
> frame?
>
> 3) Why are outstanding BPEL requests persisted into the Soup ( i.e.
> soup.setGlobalData(_outstandingRequests); )? These seem to be BPEL
> correlation specific artifacts and I don't understand why they need to be
> part of the VPU?
>
> Alex - I would like to walk through the code that hooks the JACOB engine
> into the iapi and then after that perhaps we can have an IRC around what the
> build should look like for the ODE trunk? On a side note - I'd like to post
> some deployment documents to the Wiki and check in some code to the scratch
> area. I believe I have an Apache user account but I have not seen anything
> about a password - do you know how to acquire a password?
>
> Thanks,
>
> Lance
>
>
>
>
> On 6/28/06, Alex Boisvert <bo...@intalio.com> wrote:
> >
> >
> > Oh and by the way, was the Jacob documentation helpful? What's the next
> > step there?
> >
> > alex
> >
> >
> > Lance Waterman wrote:
> > > Alex,
> > >
> > > I have been reading through the JACOB documentation on the Wiki and I
> > > think
> > > I'm at the point where #3 would be helpful. Could you move this into the
> > > scratch area where we can begin to walk through it?
> > >
> > > Thanks,
> > >
> > > Lance
> > >
> > > On 6/15/06, Alex Boisvert <bo...@intalio.com> wrote:
> > >>
> > >>
> > >> Speaking of status, here's my understanding of ongoing work:
> > >>
> > >> 1) Maciej is working on providing detailed description for the
> > scenarios
> > >> identified by Cory. This is a necessary step to continue the
> > discussion
> > >> on the Jacob module.
> > >>
> > >> 2) Lance, Paul and Zubin are working on the Deployment API and
> > >> relationship to the proposed Integration API.
> > >>
> > >> 3) There's ongoing work for retooling PXE with the proposed Integration
> > >> API, which provides validation of its semantics and real-world use, as
> > >> well as tangible progress towards our roadmap. This has happened
> > >> outside of the incubator initially because of access rights issue which
> > >> I think are now resolved. So I'd like to know if there's interest for
> > >> moving this into the incubator now.
> > >>
> > >> Anything else that I'm missing? It would be good to hear from people
> > to
> > >> know what's going on on a more regular basis <nudge! nudge!>
> > >>
> > >> It think we should have our next IRC session as soon as we have #1 from
> > >> Maciej above.
> > >>
> > >> alex
> > >>
> > >>
> > >> Matthieu Riou wrote:
> > >> > Perfect! I've just added a short sentence to reflect the undergoing
> > >> > effort
> > >> > from Maciej and others to document PXE.
> > >> >
> > >> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
> > >> >>
> > >> >>
> > >> >> > Can someone please step up and help?
> > >> >>
> > >> >> Either I stepped up or everyone else stepped back... I put a couple
> > >> >> of lines into the wiki about the work with the integration and
> > >> >> deployment APIs.
> > >> >>
> > >> >> ---
> > >> >> Paul R Brown
> > >> >> paulrbrown@gmail.com
> > >> >> http://mult.ifario.us/
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >
> > >>
> > >>
> > >
> >
> >
> > --
> > Intalio :: The Business Process Management Company
> >
> >
> >
>
>
Re: Jacob documentation
Posted by Lance Waterman <la...@gmail.com>.
Yes, I found the the documentation very helpful. I would like to ask a
couple of detail questions around persistence.
1) I would like to understand the purpose of the following method found in
the "BpelAbstraction" class:
protected BpelRuntimeContext getBpelRuntimeContext() {
BpelRuntimeContext nativeApi = (BpelRuntimeContext)
JacobVPU.activeJacobThread().getExtension(BpelRuntimeContext.class);
assert nativeApi != null;
return nativeApi;
}
and then from the JacobThread interface ...
/**
* DOCUMENTME
*
* @param extensionClass DOCUMENTME
*
* @return DOCUMENTME
*/
public Object getExtension(Class extensionClass);
Does registering the process context with the VPU tie the process context to
the Soup frame ( i.e. FastSoupImpl.ChannelFrame ) in some way or is this
just utilizing the JacobVPU singleton?
2) For a BPEL process, will there ever be a case where reactions remain in
the Soup queue at the time Soup.write() is called? If I am thinking about
this correctly there should only be objects in the channel frame and object
frame?
3) Why are outstanding BPEL requests persisted into the Soup ( i.e.
soup.setGlobalData(_outstandingRequests); )? These seem to be BPEL
correlation specific artifacts and I don't understand why they need to be
part of the VPU?
Alex - I would like to walk through the code that hooks the JACOB engine
into the iapi and then after that perhaps we can have an IRC around what the
build should look like for the ODE trunk? On a side note - I'd like to post
some deployment documents to the Wiki and check in some code to the scratch
area. I believe I have an Apache user account but I have not seen anything
about a password - do you know how to acquire a password?
Thanks,
Lance
On 6/28/06, Alex Boisvert <bo...@intalio.com> wrote:
>
>
> Oh and by the way, was the Jacob documentation helpful? What's the next
> step there?
>
> alex
>
>
> Lance Waterman wrote:
> > Alex,
> >
> > I have been reading through the JACOB documentation on the Wiki and I
> > think
> > I'm at the point where #3 would be helpful. Could you move this into the
> > scratch area where we can begin to walk through it?
> >
> > Thanks,
> >
> > Lance
> >
> > On 6/15/06, Alex Boisvert <bo...@intalio.com> wrote:
> >>
> >>
> >> Speaking of status, here's my understanding of ongoing work:
> >>
> >> 1) Maciej is working on providing detailed description for the
> scenarios
> >> identified by Cory. This is a necessary step to continue the
> discussion
> >> on the Jacob module.
> >>
> >> 2) Lance, Paul and Zubin are working on the Deployment API and
> >> relationship to the proposed Integration API.
> >>
> >> 3) There's ongoing work for retooling PXE with the proposed Integration
> >> API, which provides validation of its semantics and real-world use, as
> >> well as tangible progress towards our roadmap. This has happened
> >> outside of the incubator initially because of access rights issue which
> >> I think are now resolved. So I'd like to know if there's interest for
> >> moving this into the incubator now.
> >>
> >> Anything else that I'm missing? It would be good to hear from people
> to
> >> know what's going on on a more regular basis <nudge! nudge!>
> >>
> >> It think we should have our next IRC session as soon as we have #1 from
> >> Maciej above.
> >>
> >> alex
> >>
> >>
> >> Matthieu Riou wrote:
> >> > Perfect! I've just added a short sentence to reflect the undergoing
> >> > effort
> >> > from Maciej and others to document PXE.
> >> >
> >> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
> >> >>
> >> >>
> >> >> > Can someone please step up and help?
> >> >>
> >> >> Either I stepped up or everyone else stepped back... I put a couple
> >> >> of lines into the wiki about the work with the integration and
> >> >> deployment APIs.
> >> >>
> >> >> ---
> >> >> Paul R Brown
> >> >> paulrbrown@gmail.com
> >> >> http://mult.ifario.us/
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >>
> >>
> >
>
>
> --
> Intalio :: The Business Process Management Company
>
>
>
Re: Jacob documentation
Posted by Alex Boisvert <bo...@intalio.com>.
Oh and by the way, was the Jacob documentation helpful? What's the next
step there?
alex
Lance Waterman wrote:
> Alex,
>
> I have been reading through the JACOB documentation on the Wiki and I
> think
> I'm at the point where #3 would be helpful. Could you move this into the
> scratch area where we can begin to walk through it?
>
> Thanks,
>
> Lance
>
> On 6/15/06, Alex Boisvert <bo...@intalio.com> wrote:
>>
>>
>> Speaking of status, here's my understanding of ongoing work:
>>
>> 1) Maciej is working on providing detailed description for the scenarios
>> identified by Cory. This is a necessary step to continue the discussion
>> on the Jacob module.
>>
>> 2) Lance, Paul and Zubin are working on the Deployment API and
>> relationship to the proposed Integration API.
>>
>> 3) There's ongoing work for retooling PXE with the proposed Integration
>> API, which provides validation of its semantics and real-world use, as
>> well as tangible progress towards our roadmap. This has happened
>> outside of the incubator initially because of access rights issue which
>> I think are now resolved. So I'd like to know if there's interest for
>> moving this into the incubator now.
>>
>> Anything else that I'm missing? It would be good to hear from people to
>> know what's going on on a more regular basis <nudge! nudge!>
>>
>> It think we should have our next IRC session as soon as we have #1 from
>> Maciej above.
>>
>> alex
>>
>>
>> Matthieu Riou wrote:
>> > Perfect! I've just added a short sentence to reflect the undergoing
>> > effort
>> > from Maciej and others to document PXE.
>> >
>> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
>> >>
>> >>
>> >> > Can someone please step up and help?
>> >>
>> >> Either I stepped up or everyone else stepped back... I put a couple
>> >> of lines into the wiki about the work with the integration and
>> >> deployment APIs.
>> >>
>> >> ---
>> >> Paul R Brown
>> >> paulrbrown@gmail.com
>> >> http://mult.ifario.us/
>> >>
>> >>
>> >>
>> >>
>> >
>>
>>
>
--
Intalio :: The Business Process Management Company
Re: iapi
Posted by Alex Boisvert <bo...@intalio.com>.
Yes, we'll import the iapi implementation into the scratch area.
alex
Lance Waterman wrote:
> Alex,
>
> I have been reading through the JACOB documentation on the Wiki and I
> think
> I'm at the point where #3 would be helpful. Could you move this into the
> scratch area where we can begin to walk through it?
>
> Thanks,
>
> Lance
>
> On 6/15/06, Alex Boisvert <bo...@intalio.com> wrote:
>>
>>
>> Speaking of status, here's my understanding of ongoing work:
>>
>> 1) Maciej is working on providing detailed description for the scenarios
>> identified by Cory. This is a necessary step to continue the discussion
>> on the Jacob module.
>>
>> 2) Lance, Paul and Zubin are working on the Deployment API and
>> relationship to the proposed Integration API.
>>
>> 3) There's ongoing work for retooling PXE with the proposed Integration
>> API, which provides validation of its semantics and real-world use, as
>> well as tangible progress towards our roadmap. This has happened
>> outside of the incubator initially because of access rights issue which
>> I think are now resolved. So I'd like to know if there's interest for
>> moving this into the incubator now.
>>
>> Anything else that I'm missing? It would be good to hear from people to
>> know what's going on on a more regular basis <nudge! nudge!>
>>
>> It think we should have our next IRC session as soon as we have #1 from
>> Maciej above.
>>
>> alex
>>
>>
>> Matthieu Riou wrote:
>> > Perfect! I've just added a short sentence to reflect the undergoing
>> > effort
>> > from Maciej and others to document PXE.
>> >
>> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
>> >>
>> >>
>> >> > Can someone please step up and help?
>> >>
>> >> Either I stepped up or everyone else stepped back... I put a couple
>> >> of lines into the wiki about the work with the integration and
>> >> deployment APIs.
>> >>
>> >> ---
>> >> Paul R Brown
>> >> paulrbrown@gmail.com
>> >> http://mult.ifario.us/
>> >>
>> >>
>> >>
>> >>
>> >
>>
>>
>
--
Intalio :: The Business Process Management Company
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Lance Waterman <la...@gmail.com>.
Alex,
I have been reading through the JACOB documentation on the Wiki and I think
I'm at the point where #3 would be helpful. Could you move this into the
scratch area where we can begin to walk through it?
Thanks,
Lance
On 6/15/06, Alex Boisvert <bo...@intalio.com> wrote:
>
>
> Speaking of status, here's my understanding of ongoing work:
>
> 1) Maciej is working on providing detailed description for the scenarios
> identified by Cory. This is a necessary step to continue the discussion
> on the Jacob module.
>
> 2) Lance, Paul and Zubin are working on the Deployment API and
> relationship to the proposed Integration API.
>
> 3) There's ongoing work for retooling PXE with the proposed Integration
> API, which provides validation of its semantics and real-world use, as
> well as tangible progress towards our roadmap. This has happened
> outside of the incubator initially because of access rights issue which
> I think are now resolved. So I'd like to know if there's interest for
> moving this into the incubator now.
>
> Anything else that I'm missing? It would be good to hear from people to
> know what's going on on a more regular basis <nudge! nudge!>
>
> It think we should have our next IRC session as soon as we have #1 from
> Maciej above.
>
> alex
>
>
> Matthieu Riou wrote:
> > Perfect! I've just added a short sentence to reflect the undergoing
> > effort
> > from Maciej and others to document PXE.
> >
> > On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
> >>
> >>
> >> > Can someone please step up and help?
> >>
> >> Either I stepped up or everyone else stepped back... I put a couple
> >> of lines into the wiki about the work with the integration and
> >> deployment APIs.
> >>
> >> ---
> >> Paul R Brown
> >> paulrbrown@gmail.com
> >> http://mult.ifario.us/
> >>
> >>
> >>
> >>
> >
>
>
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Alex Boisvert <bo...@intalio.com>.
Speaking of status, here's my understanding of ongoing work:
1) Maciej is working on providing detailed description for the scenarios
identified by Cory. This is a necessary step to continue the discussion
on the Jacob module.
2) Lance, Paul and Zubin are working on the Deployment API and
relationship to the proposed Integration API.
3) There's ongoing work for retooling PXE with the proposed Integration
API, which provides validation of its semantics and real-world use, as
well as tangible progress towards our roadmap. This has happened
outside of the incubator initially because of access rights issue which
I think are now resolved. So I'd like to know if there's interest for
moving this into the incubator now.
Anything else that I'm missing? It would be good to hear from people to
know what's going on on a more regular basis <nudge! nudge!>
It think we should have our next IRC session as soon as we have #1 from
Maciej above.
alex
Matthieu Riou wrote:
> Perfect! I've just added a short sentence to reflect the undergoing
> effort
> from Maciej and others to document PXE.
>
> On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
>>
>>
>> > Can someone please step up and help?
>>
>> Either I stepped up or everyone else stepped back... I put a couple
>> of lines into the wiki about the work with the integration and
>> deployment APIs.
>>
>> ---
>> Paul R Brown
>> paulrbrown@gmail.com
>> http://mult.ifario.us/
>>
>>
>>
>>
>
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Matthieu Riou <ma...@gmail.com>.
Perfect! I've just added a short sentence to reflect the undergoing effort
from Maciej and others to document PXE.
On 6/14/06, Paul R Brown <pa...@gmail.com> wrote:
>
>
> > Can someone please step up and help?
>
> Either I stepped up or everyone else stepped back... I put a couple
> of lines into the wiki about the work with the integration and
> deployment APIs.
>
> ---
> Paul R Brown
> paulrbrown@gmail.com
> http://mult.ifario.us/
>
>
>
>
Re: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Paul R Brown <pa...@gmail.com>.
> Can someone please step up and help?
Either I stepped up or everyone else stepped back... I put a couple
of lines into the wiki about the work with the integration and
deployment APIs.
---
Paul R Brown
paulrbrown@gmail.com
http://mult.ifario.us/
Fwd: REMINDER: Incubator Quarterly Board Reports Are Due
Posted by Davanum Srinivas <da...@gmail.com>.
Can someone please step up and help?
thanks,
dms
---------- Forwarded message ----------
From: Noel J. Bergman <no...@devtech.com>
Date: Jun 15, 2006 12:32 AM
Subject: REMINDER: Incubator Quarterly Board Reports Are Due
To: general@incubator.apache.org
It is that time again. Please have your reports posted to
http://wiki.apache.org/incubator/June2006
by Sunday afternoon AT THE LATEST. Please do not be late. I will not be
able to handle last minute additions.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
--
Davanum Srinivas : http://wso2.com/blogs/