Now I’m thinking of rewriting the last parts of my tagboard plugin that are held over from the original one that I based it on, so that I can release it under the GPL instead of the license it has now, but then again I’ve got so many other side projects on the backburner that I’m not sure that it’s worth it.
Categories
-
More Feeds
External Links
Archives
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
8 Comments
i’m not sure how licensing works, but in copyright land, i think that would still qualify as a “work after another work,” me thinks. excused in art, but requires “permission” in business.
I don’t think that would apply here. Anyone can write (and completely own the rights to) their own tagboard (or pretty much any other kind of software) from scratch, even if they’ve used (or modified) a similar program from someone else in the past.
The only hangup could be if that original product was so unique that any similar program would be considered a direct copy of that original, which definitely isn’t the case here. I’ll probably just go back and take the pieces from the original one I released a long time ago and make it functionally similar to the one I’ve got now. Since it would be 100% my own code, the original author would have no more of an issue with me than they would with anyone else who writes any tagboard software.
As far as licensing goes, the main issue is that since what I’m distributing actually contains some code originally released by someone else, I have to abide by their licensing terms, which include redistributing under the same license.
yeah, i think i was just typing for the sake of typing. sorry to not contribute anything.
So I can copy someones code as long as I type it out again? JK
Anyways, why?
No, if you copy their code word for word that is copying, which is different than making something similar totally on your own. I know you know that, but just to clarify…
The “why” I explained above: I don’t want to distribute my plugin under the CC Attribution -noncommercial-ShareAlike license, which I have to right now if I include code that was distributed under it. I want to distribute my plugin under the GPL, like I do with the other plugins.
Yeah, but why?
The GPL is more in line with the terms that I’d prefer to license my software under.
For a simple example, I think I mentioned to you the other day that I had offered my tagboard plugin for use on the wordpress.com site. Well, wp.com is run by Automattic, which is Matt’s commercial company, so if wordpress.com is therefore considered “commercial use” (which I’m pretty sure it would be, even though it’s free), they could not use my tagboard plugin since I currently have to license it under the CC license that it’s got right now. If it were GPL, they could use it.
That’s what I wanted to know.