Take a look at an e-mail thread "Is this list active?" from last
November 16th.
What I took away is: that Jeff Ortel (maintainer) needs help triaging
tickets, Jeff committed to giving priority to tickets where users
submitted patches.
From someone that knows more about SOAP than myself, how about having
a
troubleshooting page and problem submission guideline listing what is
needed for someone to fix the problem (trace back, WSDL, ...) to speed
things along.
As far as the "correct" answer, unless there are several committed
developers, forking the code will the same problem - barely maintained
code.
(and ditto: Jeremy, sorry to temporary hijack your thread but Jeremy try
contacting Jeff via IRC has he mentioned in e-mail thread above)
From: suds-bounces(a)lists.fedoraproject.org
[mailto:suds-bounces@lists.fedoraproject.org] On Behalf Of Chris Sears
Sent: Wednesday, March 09, 2011 4:32 PM
To: suds(a)lists.fedoraproject.org
Subject: Re: [Fedora-suds-list] suds not building complex types
correctly
Hi Jeremy,
I don't have an immediate answer to your question, but I wanted to use
this opportunity to ask the list a broader question: How can we improve
community support for Suds?
I want to help Jeremy. I've been using Suds with varying degrees of
success for a couple years. I could probably help him go through the
WSDL, trace the Suds code and figure out the issue. Maybe it could be
fixed with a doctor or it might require a patch. If the Suds maintainers
were actively accepting patches and responding to bugs, I would feel
like doing the troubleshooting with Jeremy would be a good investment of
time. But they don't appear to be, so I'm somewhat conflicted.
I know the "correct" answer is to fork the code, fix it, and let the
gears of open source do their thing, but I don't see myself being a very
good maintainer, which makes it rather hypocritical of me to fault the
current Suds maintainers.
Thoughts anyone?
(Jeremy, sorry to temporary hijack your thread)
- Chris