Hi, I didn't reply to the whole list of lists to which this was posted, but I wanted to see if anyone in the XML-RPC project has a better angle on this than I do.

What does this all mean in English? This seems to be the tail end of a long thread from some other list. How is this going to affect the XML-RPC project?

For example, I would be alarmed to see XML-RPC, Axis, and XML-Security all get a mandate to become one project or leave Apache.

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net

Sam Ruby wrote:

> Separate code bases with separate communities should be separate
> projects. Independent of the size of the codebase, if the size of
> the community is only a few people, then it is not an ASF project.
> Such efforts can be pursued outside of the ASF, be pursued inside the
> Incubator, or be incorporated inside an existing community – as long
> as all participants in that larger community are treated as peers.

With respect to XML, I honestly don't know how many communities we have. But the above provides a recipe to find out. Without changing any physical layout of mailing lists or cvs repositories, we can begin to phase out the karma and voting boundaries between various subprojects. Those that don't wish to participate will be encouraged to form their own separate projects (or move into incubation).

What I like most about such a proposal is that it is completely up to the commiters to decide whether they want opt in or opt out.

What do others think?

- Sam Ruby


Reply via email to