Just to show I'm not taking sides :) eZpublisher just went to a dual licensing system too. For more info check out:
http://developer.ez.no/home/licence/ Regards T. ----- Original Message ----- From: "Tim Sellar" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 02, 2001 6:44 PM Subject: RE: GPL or not? > > > proVSD will be based on freeVSD... in what way ? Will proVSD use > > the same code, > > but simply extend it ? If that's the case, proVSD has to be > > released as GPL as > > well. > > > > Actually this is incorrect. For an example of how dual-licensing of software > can lead to better software for everyone follow this: > http://www.winterspeak.com/columns/102901.html > > > People who discovered freeVSD through some kind of link were > > always able to > > download it and try it. But when you start pulling everything > > away from people > > who 'may be interested', they will immediately back off. They > > want to try the > > software before they spend money, even if it's very cheap. And I > > don't think you > > can blame them, can you ? > > People are still free to try the software. Everything save for the latest > release is available in easily installable packages. Only the latest > release, for the time being, requires the additional overhead of fetching > and building. > > > > > Personally, I'm very interested in deploying freeVSD on a large > > scale, but it > > needs a lot more work before I can get that done. I'm willing to > > implement these > > features : > > - Load balancing for Apache, Qmail and MySQL (all 3 tested so far > > and working > > fine outside freeVSD) > > - Failover system guaranteeing 100% uptime for Apache, Qmail and > > MySQL with > > shared disk array (MySQL is tough on shared disk array though, > > still working on > > that) > > - Use of a distributed file system with replication, again adding to the > > redundancy of the solution > > These are the reasons why I was asking for a clear layout of how > > freeVSD was > > designed last week. I had the intention to begin development as > > soon as possible. > > But seeing how things are evolving now, I might as well throw all > > those ideas > > away and start building a new virtual server system, specifically > > designed for > > 100% availability. > > > > As I have previously said, freeVSD is not going away. If you were intending > to contribute code you would have to be using CVS in any event, and you > still can. > > ------------------------- The freeVSD Support List -------------------------- > Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support > Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support > Archives: http://freevsd.org/support/mail-archives/freevsd-support > -------------------------------------------------------------------------- --- > ------------------------- The freeVSD Support List -------------------------- Subscribe: mailto:[EMAIL PROTECTED]?body=subscribe%20freevsd-support Unsubscribe: mailto:[EMAIL PROTECTED]?body=unsubscribe%20freevsd-support Archives: http://freevsd.org/support/mail-archives/freevsd-support -----------------------------------------------------------------------------
