Re: [Soaplite-devel] SOAP::Lite maintenance

[David B. <Dav...@qm...>]

+5 to Martin.  :-)
an extra +5 when I see patches!  :-)

+10 to Byrne if you give him the acccess he requires.   (like passing PAU=
SE primary maintainer status to martin, or at least giving martin co-main=
tainer status).

Buzz.

-----Original Message-----
From: soa...@li...
[mailto:soa...@li...]On Behalf Of Martin
Kutter
Sent: Friday, 28 September 2007 12:15 AM
To: by...@ma...
Cc: soa...@li...
Subject: [Soaplite-devel] SOAP::Lite maintenance


Hi Byrne,

as far as I can see, SOAP::Lite is currently not being maintained.=20

In my opinion, this is a quite undesirable state, as SOAP and XMLRPC appl=
ications
become more and more widespread, and other languages like python already =
provide
support for them in there standard library.

I hereby offer to take over maintenance of the SOAP::Lite module.

My plans for SOAP::Lite maintenance are:

1) Work down the list of bug reports on CPAN & sourceforge
2) Split the SOAP/Lite.pm into separate files, while completely preservin=
g SOAP::Lite's
API
   In my opinion, the BIG SOAP/Lite.pm is one of the most serious design=20
   flaws in SOAP::Lite. This can easily be changed by moving to a=20
   one package/one file stragey.
   Separating packages into different files eases maintenance, and makes=20
   SOAP::Lite more "lightweight"
3) Factor out the seldomly used parts into separate packages.
   In my opinion, there's no need for Jabber or MQ support in SOAP-Lite -=
=20
   they could easily be factored out into SOAP-Lite-Jabber and SOAP-Lite-=
MQ

   distributions.
   I bet there's more to come...
4) Centralize contact.
   - move the yahoo groups user support forum to a user mailing list=20
     on sourceforge
   - move soaplite.com to soap-lite.sourceforge.net

To introduce myself: I'm known on CPAN as MKUTTER. I'm the author of SOAP=
::WSDL,
a WSDL-based frontend for SOAP::Lite. I'm currently doing a complete rewr=
ite
of SOAP::WSDL, and have learned - the hard way - that I can't use too muc=
h of
SOAP::Lite as a base for SOAP::WSDL - actually, the only usable part is t=
he
transport backends.

I'm also receiving user comments suggesting improvements which cannot be =
done
without modifying SOAP::Lite, too.

I consider this a very bad situation, which could be fixed easily - provi=
ded
SOAP::Lite would be actively maintained.=20

As there seems no one there to do the task, I'd just offer to do it mysel=
f.


Regards,

Martin
* Gesendet mit / Sent by: FEN-Webmail * http://www.fen-net.de *

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Soaplite-devel mailing list
Soa...@li...
https://lists.sourceforge.net/lists/listinfo/soaplite-devel


The message and any attachment is confidential and may be privileged or o=
therwise protected from disclosure. If you have received it by mistake pl=
ease let us know by reply and then delete it from your system; you should=
 not copy the message or disclose its contents to anyone.