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.

Notes on XML Schema

While CXF (and and presumably Axis) depend on XmlSchema, the committer community is tiny. The combination of it with the other commons items doesn't help very much in achieving critical mass, since the subject matter is so disparate. Given the apparent push toward taking release votes more seriously, this is a matter of real concern. Maybe it can be addressed in the proposal(s) below by actively recruiting more interested parties to the relevant PMC. Or, maybe CXF would make a better home, insofar as there is active work at CXF that depends on ongoing maintenance and improvement of Xml Schema. Another possibility is Xerces. After all, W3C XML Schema is not uniquely, or even primarily, a web service technology. I had a recent discussion with the Xerces-dev community. Initially, the reaction was to express distress that XmlSchema had ever been invented, insofar as it was 'just another' package that solved problems addressed elsewhere. However, further exploration revealed that the code inside Xerces (not to mention stuff over at dev.java.net) doesn't address the same use cases as XmlSchema does. Thus, more discussion might come up with a plan to push XmlSchema in with the rest of ASF's XML universe.

Proposals

Concrete proposals here, with rationales. If you favor a particular proposal, add your name to the list next to it - and feel free to change your opinions as the discussion moves forward, this is NOT an official vote.

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.

Supporters: * ant (with the changes in my comment above)

Split it #1

(NOTE: I edited this to reflect Dan's comment and also adding Rampart/Sandesha/Kandula to the Axis2 TLP --Glen)

Phase 1:

Phase 2:

Comments:

Supporters:

Split it #2

Reasoning:

Supporters:

Split it #3

Phase 1:

Phase 2:

Supporters:

Split it #4

Phase 1:

Phase 2:

Rationale:

Open questions:

needs is a single library that combines some of what is inside Xerces with the unique functionality of XmlSchema, and has the momentum to evolve to 1.1 and all of that. Absent anyone to do this, leaving it in WS-Commons seems sensible to me. It does the Xml-Schema-tic work needed for web services. A better name would be ws-xml-schema, come to think of it. Given the report here about the future of XML as an Apache umbrella, I'm anxious to see what Dan and others think of this alternative.

Supporters:

Split it #5

(please feel free to add other proposals)

FrontPage/WebServicesPMCReorg (last edited 2009-09-20 22:49:07 by localhost)