You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by ip...@apache.org on 2004/12/03 02:06:13 UTC
svn commit: r109612 - /incubator/muse/trunk/src/site/content/apollo-hermes-muse-roadmap.txt
Author: ips
Date: Thu Dec 2 17:06:12 2004
New Revision: 109612
URL: http://svn.apache.org/viewcvs?view=rev&rev=109612
Log:
updated several items
Added:
incubator/muse/trunk/src/site/content/apollo-hermes-muse-roadmap.txt
Added: incubator/muse/trunk/src/site/content/apollo-hermes-muse-roadmap.txt
Url: http://svn.apache.org/viewcvs/incubator/muse/trunk/src/site/content/apollo-hermes-muse-roadmap.txt?view=auto&rev=109612
==============================================================================
--- (empty file)
+++ incubator/muse/trunk/src/site/content/apollo-hermes-muse-roadmap.txt Thu Dec 2 17:06:12 2004
@@ -0,0 +1,157 @@
+Apache Projects Roadmap (updated 12/02/04)
+==========================================
+EXECUTIVE SUMMARY
+
+There are two main milestones that need to be achieved with the
+Apache projects. First, the new WSRF 1.2 (Apollo) and WSN 1.2
+(Hermes) projects must be built out. Second, Muse 1.0 will need
+to be developed. There are two phases to the Muse 1.0
+development. First, the code base must be rewritten to use the
+Apollo and Hermes projects rather than the embedded
+implementations of the WSRF 1.1 and WSN 1.1 specifications.
+Second, the MuWS reference implementation must be brought into
+compliance with WSDM MuWS 1.0.
+
+HP INTERNAL TASKS
+
+- Mail to internal users and dev mailing lists. Let them know about Apache
+ project and that we need their help in building out the community. Tell
+ them the ws-rp and ws-rf SEN projects are dead and that the mailing lists
+ will be deleted.
+
+- Generally announce the project to HP internal (ATO, SGBU, etc.)
+
+- Put a snapshot of the donated code into Clearcase.
+ [In Progress]
+
+
+APACHE PROJECT SETUP
+
+In addition to the project build out items, the following tasks
+will need to be executed after becoming an Incubated Apache Project:
+
+- Request Unix/CVS/SVN accounts, SVN repos, project mailing lists, JIRA projects.
+ See http://www.apache.org/dev/project-creation-form.txt
+ [SVN repos, mailing lists, and JIRA projects set up;
+ Accounts requested; setup done for Ian and Sal, but still pending
+ for Steve, Mazz, and Bill]
+
+- Checkin code to Apache SVN.
+ [Done for HP code; Globus code should be in soon]
+
+- Project web sites. In particular explaining the charter of the projects,
+ links to the specs and making visible the non-production nature of Muse
+ 0.5
+ [Muse 90% done; Apollo 50% done]
+
+- Initiate the Apache software grant process.
+ [not necessary until project is ready to graduate from incubation]
+
+
+ROADMAP ITEMS
+
+1) Build the new common WSRF and WSN projects (Apollo and Hermes), which
+ will combine the GTK4 implementation of WSRF and WSN specs with the
+ Muse implementation of these same specs.
+
+See sub-priorities - XMLBeans implementation for WS-RF
+ P1 - BaseFaults
+ - Done
+ P1 - RP (15 ED) (I1)
+ - Done except for the following tasks:
+ - Callback interface for property synchronization. (3 ED)
+ - Prop Change Notification (Needs to come after the WS-N
+ BaseNotification implementation, although it drives the interface definition). (4 ED)
+ P1 - RL (2 ED) (I1)
+ - Done
+ P2 - SG (5 ED)
+ - Is there a Globus impl for this?
+ - Let impl be driven by MuWS ServiceGroup needs.
+ - User Documentation, including architecture doc, getting started and one good example. (3 ED) (I1)
+
+P1 - WS-RF Dispatcher (3 ED) (I1)
+ - Done
+
+P1 - WS-N project build out (I1 - Spike)
+ - Need to look at how WS-Eventing will effect interface definitions.
+ - Migrate Globus interfaces
+ - Build out impl based on either Globus impl, Muse impl, or
+ combination. Main decision is whether to use XMLBeans types
+ or pre-defined types. How to abstract version issue?
+ - User Documentation, including architecture doc, getting started
+ and one good example.
+
+P2 - Code generation (could be put off if time constrained until after 2 & 3 below).
+
+P1 - Nightly Build System. Implies CVS setup, project web site setup, and setup of Maven repo. Assuming this is via Apache infrastructure. As soon as we know how to do this make it happen.
+
+P* - (Ongoing Best Practices) Robust Unit Tests, Javadocs, I18n, and Logging
+
+2) Build Muse 1.0
+ - Based on new WSRF/WSN projects
+ - MuWS 1.0 Compliance
+ P1 - MuWS Relationships
+ P2 - Support for Discovery Capability. In particular, WS-ServiceGroup interface
+ for Registry (dependent upon WS-RF ServiceGroup implementation, so may want
+ to combine the two efforts)
+ P1 - Support WSDM Event format
+ P1 - Support for latest Metrics Capability (Bryan Murray is leading this effort)
+ P1 - Support for new required Notifications (this is embedded in other Capabilities).
+ P1 - Support for Manageability Capabilities
+ P1 - Support for Configuration Capability
+ P1 - Support for latest State capability specification
+ - User Documentation, including architecture doc, getting started and one good example.
+
+3) MuWS Client API
+- The project needs a committer in this space, either from HP or from
+ the community. From the HP perspective, it is currently unstaffed.
+- Registry-independent operation.
+- An example that would help enable HP SPI developers.
+- Support for Async calls.
+- I18N Support.
+- Trailmap for Examples.
+- Support for SetResourceProperties.
+- Refactor tests to use common test classes with Muse.
+- Logging.
+- Add "invoke" to Instance implementation.
+- Are we using this API to build out any of the interop demo tools? Ideally, yes.
+
+4) MuWS 1.0 Interop Work. Once the interop demo definition is defined,
+ let it drive the work priorities.
+
+5) Presentations & Demos.
+ - ApacheCon, Nov2004.
+ [Ian and Sal attended; BOF was scheduled last minute, and nobody showed up]
+ - Globus World, Feb2005. (Latha, w/ help from Ian and Sal)
+
+6) Enablement Activities. Terry R has an expectation that the WSDM RI
+ team will assist others in ATO in their efforts to use Muse. Not
+ sure exactly what the time sink would be here, but it should be
+ accounted for.
+
+
+KEY DATES:
+
+WSDM MuWS 1.0 interop demo. Current target is late February / early March 2005.
+
+
+IMPLEMENTATION PLAN
+
+Now - Winter Holiday Break
+Apache Project Setup
+Implement WSRF 1.2 (Apollo), then WSN 1.2 (Hermes)
+
+Jan/Feb
+Implement MuWS 1.0 (Muse) on top of Apollo and Hermes
+
+Plan for Iteration 1 and 2:
+
+I1: Nov 1 - Nov 23 (ApacheCon is Nov 15 - 17)
+--------------------------------------------
+Finish WSRP capabilities, WSRF Dispatcher (23 ED)
+
+I2: Nov 29 - Dec 23
+-------------------
+WSRP PropChangeNotif abstraction layer
+WSN
+PropChangeNotif impl for WSN
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org