gotze
Site administrator
/ Moderator
Apr 28, 2003, 1:49 PM
Post #1 of 1
(4946 views)
Shortcut
|
|
Going open source
|
Can't Post
|
|
I've decided to make the plugin open source. Now I need to study the various licensing schemes. Ironically, I've worked with open source policy for the Danish government, and know a number of the open source gurus around, but never thought I myself had to dig into all the questions one needs to ask oneself when going open source with a particular project.
My main concern is whether I will be able to maintain the code base, and keep the code alive. I can only do so with help from others. Now I know that "living code" is not really a requirement for, say, GPL. But maybe it should be, because there is nothing worse than an open source project that "dies".
I had a number of people look into the code, and here is a summary of my findings: - The current code does not have the same high quality as LSQL (but is still pretty good), and would benefit from a revision by someone like Alex.
- The usage of RPC-bindings is the de facto way of doing web services, but document/literal style bindings are the future, my WS/XML-friends say. I am not sure how involved it would be to offer both styles (think it's a matter of using a valid XML schema in the WSDL)
- The usage of SOAP::Lite will cause a lot of people problems. It is not an easy Perl module to install. Maybe a PHP solution should be considered? NuSOAP is pretty good.
- Documentation and code examples will be needed. A first "killer app" using the web service should be developed. I'm visiting Google API and Amazon WS often these days ...
- There is a good business case for consulting services related to this plugin. Users will typically be high-end LSQL users.
(This post was edited by gotze on Apr 29, 2003, 3:16 PM)
|
MAIN
SEARCH
WHO'S 
LOG 
Dansk