I know that Andrew has sent in his CLAs - Oliver and Joel, can you submit 
the iCLA and cCLA forms?

http://www.apache.org/licenses/icla.txt

http://www.apache.org/licenses/cla-corporate.txt

thanks,
Dan



"Davanum Srinivas" <[EMAIL PROTECTED]> wrote on 06/16/2006 12:03:03 PM:

> There is no harm in everyone involved sending in their iCLA. Since it
> takes a while to register anyway. When uploading to JIRA there is a
> button to indicate assent to include the patch in any ASF project,
> that should take care of small patches.
> 
> thanks,
> dims
> 
> On 6/16/06, Daniel Jemiolo <[EMAIL PROTECTED]> wrote:
> > Meeting Date:
> >
> >         6/16/06 11:00 a.m. EDT
> >
> > Attendees:
> >
> >         Andrew Eberbach
> >         Joel Hawkins
> >         Dan Jemiolo
> >         Rick Rineholt
> >         Oliver Waeldrich
> >
> >
> > Topics:
> >
> >         1. Review of build process and issues that new users might 
have
> > with getting Maven to work
> >
> >         2. Alignment of Muse/OSGi work with Apache Tuscany (SCA)
> >
> >         3. Q&A and review of core concepts for non-IBM developers who 
are
> > making contributions (or want to make contributions) but are new to 
the
> > code base.
> >
> >
> > News & Decisions:
> >
> >         1. As stated in a previous email, the build is available, but 
not
> > 100% complete. The jar creation process does not yet take into account 
the
> > .properties files or the OSGi-ification that Joel has been working on.
> >
> >         2. Topic #2 was postponed until our 6/30 call because our 
Tuscany
> > rep could not join the call. Rick R. is also interested in this topic 
and
> > will join again on 6/30.
> >
> >         3. Oliver has reviewed the code and design docs, but not much 
of
> > Axis2. The programming model is constant over Axis1 and Axis2, so only
> > directory structure and jar files should change when moving to the new
> > engine. It was decided that the best way to get into the details of 
the
> > code while also moving forward on the code generation piece is for 
Andrew
> > and Oliver to post what they have (design doc, code, etc) to the 
mailing
> > list and discuss on that forum. A number of action items came from 
this.
> >
> >
> > Action Items:
> >
> >         1. Dan will add the .properties files to the build, as well as 
the
> > sample projects.
> >
> >         2. Dan and Joel will get together to modify the build to 
create
> > OSGi bundles vs. regular jar files (postponed for the following week,
> > since Joel will be on vacation). We will also need to contribute 
Joel's
> > OSGi-specific modules.
> >
> >         3. Andrew will post his initial design for code generation to 
JIRA
> > to start the design discussion. Andrew and Oliver are the current code
> > generation contributors, with Dan acting as a codebase reference.
> >
> >         4. Dan will email Sal/Dims to find out how much admin process 
is
> > necessary to accept contributions from Joel and Oliver (e.g., is a CLA
> > required).
> >
> >         5. Oliver will work with his company's legal/management to do 
what
> > is necessary to post his current code generation work as part of our
> > design discussion and development plan.
> >
> >
> > If you have any questions or clarifications about these minutes, 
please
> > send them along!
> >
> > Thanks,
> > Dan
> >
> >
> > Dan Jemiolo
> > IBM Corporation
> > Research Triangle Park, NC
> >
> >
> > +++ I'm an engineer. I make slides that people can't read. Sometimes I 
eat
> > donuts. +++
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> 
> -- 
> Davanum Srinivas : http://wso2.com/blogs/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to