You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by Apache Wiki <wi...@apache.org> on 2009/05/17 21:39:39 UTC

[Ws Wiki] Update of "FrontPage/WebServicesPMCReorg" by GlenDaniels

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The following page has been changed by GlenDaniels:
http://wiki.apache.org/ws/FrontPage/WebServicesPMCReorg

New page:
= Web Services PMC Re-organization =

This page exists to capture points of discussion and proposals regarding the Web Service PMC and how we should re-organize it in order to better serve the individual projects and the broader user community.

== Points of Discussion ==

A "blackboard" for noting salient points in the discussion.

 * Transports are only ever used in an Axis2 environment.
 * Other projects (i.e. Abdera) use Axiom
 * Other projects (i.e. CXF) use XmlSchema

== Proposals ==

Concrete proposals here, with rationales.

=== Leave it alone ===

This proposal is the simplest, as it simply states "everything is ok as it is and we should leave it that way".  The implication here is that even though we are a large project and look like an "umbrella", we are still doing a good job of oversight and community management.  Also, even though it might make organizational sense to reduce the number of subprojects, the reality is that a WS developer often needs to touch multiple subprojects (i.e. an Axis2 developer may need to work on Axiom, a Neethi developer might have to fix things in Axis2 after changes, etc).  As such keeping them together might make sense.

=== Split it #1 ===

Phase 1:

 * Promote Axis2 to a TLP containing Axis2 Java + C, and the transports.
 * Promote WS-Commons to a TLP containing at least Axiom, Neethi, XmlSchema

Phase 2:

 * Decide which if any of the remaining subprojects should be promoted or retired to the Attic.

=== Split it #2 ===

There are a variety of ways we might consider splitting the project...