Meeting Date:
8/31/06 11:00 a.m. EDT
Attendees:
Barry Atkins
Andrew Eberbach
Joel Hawkins
Dan Jemiolo
Balan Subramanian
Mark Weitzel
Topics:
1. Discuss tutorial content:
a. Decide what material is needed and prioritize it (can't
cover everything in three weeks).
b. Decide who will be responsible for each section of
material.
2. Integrating tutorial with web site - need to add content to web
site and include it in SDK package. Need to decide the best way to do
this.
3. Reminder to verify release candidate on Friday.
4. Muse on constrained devices (J2ME & OSGi).
News & Decisions:
1. Joel will handle OSGi-specific tutorial content. Andrew will
handle use of the tooling. Dan will handle Axis2 and general programming
model tasks. Andrew's sections will probably overlap with Dan's, so they
will have to come up with the tutorial flow and write some sections
together.
2. Team decided it would be easiest to just include a snapshot of
the website in the -bin download package rather than having two different
forms of the documentation/tutorial content. The non-documentation content
on the web site is pretty small and shouldn't add any overhead.
a. Dan will refactor web site in the next few days to have
1.0 and 2.0 sections.
b. Team can commit documentation to /site, under the 2.0
sections. This does not affect the web site until we refresh the site
content on minotaur.apache.org.
3. Dan will make a final build of the code on Friday at noon and
post it online. Joel/Andrew will vote to verify that they have reviewed
the JARs.
4. Barry Atkins introduced work he's done to try and build Muse
against J2ME JDK, specifically the Personal Profile.
a. Has 1/3 compiling so far - no major issues, but some
missing APIs to deal with.
b. Most significant missing API is java.net.URI.
c. Other profiles have more restrictions and may not be
feasible.
5. Joel and Barry discussed SOAP services for J2ME/OSGi,
specifically KSoap. Barry will try and get his build running on OSGi 4
(Equinox or Felix) and KSoap.
6. Team discussed how it would handle J2ME support (fork, patch,
etc.). Mark is going to investigate how other similar projects have
handled this and report back before we start adding things to the
repository. Once we've discussed these findings online, we will create the
proper structure for supporting the J2ME code.
7. Joel and Mark are unavailable next week, and we're just working
on tutorial/guide material, so we'll cancel next week's call and report
status via email.
Action Items:
1. Mark will investigate: methods for supporting J2SE and J2ME
code streams for the project, availability of code analysis tools to
expedite J2ME build efforts.
2. Joel will contact Apache Felix team about use of their OSGi
implementation on J2ME and the availability of SOAP services.
3. Dan will refactor web site to have 1.0 and 2.0 sections and
send instructions for committing tutorials docs when this is done.
4. Everyone will report their findings or status to muse-dev by
next Thursday since there is no call next week.
5. Team will review the release candidate build tomorrow and +1 or
report an error in the JAR files.
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]
