Meeting Date:
6/30/06 11:00 a.m. EDT
Attendees:
Andrew Eberbach
Joel Hawkins
Dan Jemiolo
Jervis Liu
Dennis O'Flynn
Balan Subramanian
Mark Weitzel
Topics:
1. Define a milestone schedule and deadlines for future
features/bugs in JIRA.
2. Microsoft/OASIS reconcilation specs and how this affects the
Muse roadmap.
3. Relationship between Muse, Tuscany, and Eclipse Corona
News & Decisions:
1. The team has agreed to the following milestones and content:
a. Milestone #2 (M2) - Friday, 8/4/06
i. OSGi support
ii. Error message cleanup/accuracy
iii. Persistence API
iv. More! - see JIRA
b. Release 2.0 (R2) - Friday, 9/1/06
i. Just bug fixes and documentation improvements
from M2.
2. The team agreed that all requests and bugs must have their own
entry in JIRA, where they will be assigned to developers working on the
project. Anyone can have a JIRA account, so this is not an issue.
a. All requests/fixes that are to be considered for M2
must be in JIRA by EOD Thursday, 7/13/06.
b. Any code or artifacts that contributors have for M2
requests/fixes can be put in JIRA before 7/13/06.
c. The team will prioritize any incomplete
features/requests during its 7/13/06 meeting.
3. Microsoft/HP/IBM/Intel are trying to reconcile the WSDM vs
WS-Management war by drafting a new set of merged specifications and then
putting them through ratification (the standards body is not yet known).
We do not know exactly when the specs will be published, but we do know
that they will build heavily on the current specs; we can start to discuss
plans for implementing them using the Muse programming model and propose a
roadmap based on Date X (where X = whenever the first drafts are
published).
Dan will send out an initial proposal on this, and the team will
debate/modify it until it comes to a plan everyone agrees on. We hope to
have most of this plan agreed on for 7/13/06.
4. Joel, Jervis, and Mark led a discussion on implementing
manageability capabilities for Tuscany using Muse/OSGi. It was decided
that most of this work should be done in Tuscany, using Muse's core
conceptual programming model as the basis for the non-web-services-based
manageability features. Joel and Jervis will work together to create
working PoC of Tuscany manageability by 7/21/06; the manageability
capability will include start/stop operations and status properties (may
map to MUWS State or OperationalStatus).
5. Mark reviewed how the tooling story would work given a
WSDL-to-Java-like code generation tool in Apache: how this would be used
by an Eclipse IDE, how we would import/export units of manageability, how
it could be extended to support less common use cases w/o rewriting a lot
of model/generation code. This was brought up in the context of the
Tuscany PoC discussion when trying to determine how much web services
spec/plumbing code would need to be included to do non-web-services
manipultation of the manageability components.
6. With many people on vacation, next week's call is cancelled.
Action Items:
1. Dan will post the milestone schedule on the web site. For now,
we will include a link to JIRA as a reference to content; as we get closer
to the end of July, we will provide the final list of M2 content.
2. Dan, Andrew, and Joel will post their known features/bugs into
JIRA, along with any code they have supporting the requests.
2a. Other Muse contributors should add their requests to JIRA as
well.
3. Dan will send out the initial reconcilation roadmap proposal
for the team to revise.
4. Joel and Jervis will start work on the Tuscany/Muse PoC and
update us on progress on 7/13/06.
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]
