About: About Caoyuan's Blog
Browse by time:
- April 2010 (1)
- March 2010 (1)
- January 2010 (3)
- December 2009 (3)
- November 2009 (2)
- October 2009 (2)
- September 2009 (5)
- August 2009 (4)
- July 2009 (1)
- June 2009 (3)
- May 2009 (1)
- April 2009 (2)
- March 2009 (3)
- February 2009 (15)
- January 2009 (2)
- December 2008 (4)
- November 2008 (5)
- October 2008 (6)
- September 2008 (1)
- August 2008 (1)
- July 2008 (5)
- June 2008 (1)
- May 2008 (4)
- April 2008 (5)
- March 2008 (7)
- February 2008 (5)
- January 2008 (7)
- December 2007 (8)
- November 2007 (3)
- October 2007 (8)
- September 2007 (4)
- August 2007 (6)
- July 2007 (5)
- June 2007 (1)
- May 2007 (4)
- April 2007 (8)
- March 2007 (3)
- February 2007 (3)
- January 2007 (2)
- December 2006 (2)
- November 2006 (4)
- October 2006 (1)
- September 2006 (2)
- August 2006 (1)
- July 2006 (2)
- June 2006 (5)
- May 2006 (6)
- April 2006 (7)
- March 2006 (2)
- December 2005 (4)
Switch to GPL license?
I'm thinking to switch the license of BlogTrader Platform from BSD to GPL.
Making the license under GPL will encourage the contributors (include me) to release more source code to public, and means compatible to GPLed softwares that may be integrated into this project, such as: Sleepycat's Berkeley DB.
Of course, the source code that had been released will remain under BSD license, but I will not update it any more.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/blog_logo.png)
rss
Comments
It might also help if you put the code into CVS or SubVersion? for others to work with.
It's hard to collaborate when it's not available in some type of source repository.
m.
Yes the frist thing to do is to have your code in CVS.
After you should ponder wether you want to put the GPL or LGPL.
Personnally, I prefer BSD license because it is really free (Apache license is also good) and because I fear the legal consecuences of using (L)GPL.
The subversion repository of source code has been on sourceforge.net for somedays, to check out: svn co https://svn.sourceforge.net/svnroot/humaitrader humaitrader
For the legal consecuences of using (L)GPL. I'm considering to apply some exceptions for custom indicators and drawings etc.And, if I stick on BSD, it will be difficult to integrate other GPLed code or libs in.
Are there evidence that GPL increases contributions? My modest contributions to Open Source projects have all been to BSD och Apache licensed projects.
Sometimes I use libraries in personal projects and learn to like them. Then I want to use them at work too. If the project is using GPL that makes things difficult.
LGPL is a great license for projects, and it ensures that what you produce stays open source. BSD is also a fine license, but it allows people to make non-free versions of the software. You may or may not consider that to be a good thing. (I think it is a good thing, myself)
I'll also urge you to carefully investigate things yourself. Don't fall prey to fanatics who spread FUD about "the legal consequences" of licenses that don't follow their religion or to people who clearly can't differentiate LGPL from GPL in a discussion. It goes without saying that you shouldn't take this at face value either - do your own research and make an informed choice.
Good luck. No matter what you choose, more open source is a good thing!
i'm not sure that switching to GPL is a good thing.
For instance, there are some commercial technical analysis indicators, thus switching to GPL will automatically disable making money on this.
So, if you really want to make blogtrader to be used widely, you should not switch to GPL.
How will using the GPL "automatically disable making money on this"? That's ridiculous.
I agree w/ the change to gpl. But like the 'classpath' project we'd need to allow non-gpl indicators/modules. On the data side, just have a non-gpl indicator read directly from the DB. ON the nUI side however you'd need to define a few exceptions so that a non-gpl indicator could draw on the screen.
As it stands right now. Once Blogtrader matures someone could incorporate the entire project into thier app and sell it as thier own.
Mark
I think switching to GPL and using svn could be the right step if you want other developers begin to write code for this project. But also it should be very important to improve the internal documentation. For example i'm making a simple drawing chart : i've copied and renamed a sample chart like ParallelChart?, copied and renamed HandledParallelChart?, added some lines to the xml layers file and with some coding i've my first handled drawing added to the toolbar. Unfortunatly without good documentation is very difficult to do some more complex things cause i have to go deep and deep reading the source code and this is time expensive :) I think that improving documentation is at the first place, then changing licence also is important to have more people works on this project.
Hi Matt,
I still need to think about the solution, especially how to apply the exceptions, for which part, whether a contributor agreement is neccesary etc.
If switch to GPL.
Hi Stefano,
The source code and APIs change rapidly, they are not stable enough for developers at this time.