Hmm... Well... Maybe the first step should be to determine what
features people are actually using. We need to figure out which
features we can cut out of SOAP, and which features we need to add.
Once we have that list...
The next step would be an RFC, where we allow for anyone with a good
idea to submit a proposal, solution, or other recommendation. In
general, we would want to see plans for the redevelopment of SOAP::Lite.
With that in hand, we could separate feature requests for structural
changes, and develop a final draft plan for the layout of the module.
Community sign off would probably be appreciated.
Once a plan had been decided upon, only then would development commence
on the module itself.
Charlie Bowman wrote:
> I think a lot of people are wanting to help, I know I am. What we need
> is a little leadership to help get the ball rolling.
> On 2/16/07, *Robert Landrum* < rlandrum@...
> <mailto:rlandrum@...>> wrote:
> I just read the State of the SOAP post on soaplite.com
> <http://soaplite.com>. I couldn't
> agree more. It's pretty awful code, and slogging through it to figure
> out why it's doing something wrong is way too cumbersome.
> I just discovered an ugly little bug today with how WSDLs are converted
> into code, and how parameter handling is (to be blunt) broken. The fix
> however, is even uglier.
> If work on a rewrite is underway, I'm interested in contributing.