Re: [Soaplite-devel] State of the SOAP

[Robert L. <rla...@ao...>]

Mike South wrote:
> Right now there is a patch waiting which will let you generate stub
> code for a service that publishes a wsdl.  I think that the first
> order of business would be to apply (or reject with reasons) the
> outstanding patches.  

Maintenance should be separate from this process, at least initially. 
Combining the two into a single "project" will only create confusion for 
developers/maintainers.

> If the current maintainer doesn't have time to
> maintain it, he should be passing it off.

Agreed.  Has anyone stepped forward to take the torch?  From what I've 
read, SOAP::Lite is maintained only so that maintainer's current SOAP 
implementation isn't broken.  And that's the level of commitment most of 
us would be willing to provide too.  Finding someone willing to go the 
extra mile to make it right, to maintain it properly, is the challenge.

> Writing a new module is
> also a good idea, but imho we need to get maintenance of the current
> code running in parallel.  Right now that is stalled.
> 

Maintenance is a tricky thing.  Adding patches creates instability, 
which can lead to more maintenance.  I can understand why it's been slow 
in coming.

Rob