Hi Julian,
Quote:
If you're reading Andy, I'd love to hear your thoughts.
I was just reading your response to my Plone questions in another thread, and researching your past posts when I found this reference to me. LOL! You should have just PM'ed me.
When I read your post I thought "wow, this guy's business looks similar to mine" and then I nearly jumped out of my skin when I read the last line ;) Anyway, I totally share your point of view, and share the issues that you face.
As you may know, I rely totally on XOOPS to make a living - my business depends on it. As well as myself, I currently employ one full-time developer who works 100% on XOOPS systems. My wife will also join the business shortly, and we have two small children to support. I'm also bringing some other developers on board. So this is real life serious stuff, and not just a hobby.
As you describe, we normally do sell software as a service, rather than "development hours" or "lines of code". But the Event Manager module project was totally different. This development was commissioned by a client that wanted to run the code on their own in-house server. So I have no control of how the code is released under GPL.
Normally, we sell XOOPS as a service running on our own servers (just like you) and so we decide whether to release the code or not. Obviously we want to give the code away, but we have to balance this against keeping our competitive edge. We also have a desire to give back to the community that has helped our business start in the first place. So how does this work in practice....
Well, I've recently joined the wf-projects module development team, so that they can use any code that might be useful, as I use wf-sections as the CMS module for my sites. (In reality though, most code is for very specific purposes, and needs a lot of work to be useful to the OSS community). Hopefully, this move will help give back to the community.
Secondly, I plan to release two new GPL modules shortly. One will be a multi-purpose directory module, and the other will be a member profile manager, so that members can have more sophisticated personal profiles, and integrate XOOPS registration with credit card payment gateways.
As for the issue of how we keep our competitive edge, whilst releasing our code as OSS, then you will have to PM me about that, or sign a non-disclosure agreement! ;)
Andy