Rather than thinking of libraries vs applications, think of various
licenses as different tools to achieve different goals. You have first
to think what kind of life you'd like to give to your product. E.g.:
would you like to create a community? Would you like to have people
contributing back
+1
always consider your end goal first, then find the license that meets
your need. For example, almost all of the open source projects I work
on have the underlying goal of getting people to do more interesting
things with Java. This means I want to code shared as far and wide as
Joshua Marinacci wrote:
+1
always consider your end goal first, then find the license that meets
your need. For example, almost all of the open source projects I work
on have the underlying goal of getting people to do more interesting
things with Java. This means I want to code
On Aug 28, 2:16 pm, Michael Neale michael.ne...@gmail.com wrote:
So BSD would be considered more mixable then Apache2?
Actually, I have no idea. :) Just read you have to be careful.
Probably doesn't matter so much with the 'BSD style' as you say.
I did read about a license once that
yes, i do like the if you sue me over a patent you can take my code
and shove it clause.
On Aug 27, 2:46 pm, Michael Neale michael.ne...@gmail.com wrote:
Does BSD have the be cool on the patents clause to provide author
protection etc? from what I remember, other then that they are very
Well, the normal GPL isn't suited to libraries because they would
require the entire app to become GPL. So they made the LGPL. But
people just moved to Apache and BSD.
I like Apache 2. But it's not just about what's a good license, you
have to consider how you might need to mix them.
On Aug
Hi Jan
OSS Watch provides guidance albeit it is geared to helping the UK
academic community:
http://www.oss-watch.ac.uk/
http://www.oss-watch.ac.uk/resources/ipr.xml
Hope that helps.
Cheers
Mike
2009/8/26 Jan Goyvaerts java.arti...@gmail.com:
Putting a project on Kenai requires the choice
Thanks ! That's indeed the kind of accessible explanations I am
looking for.
What would be the logical choice for a care-free open source project ?
Everybody can use it, modify it, bla bla bla and the usage is your
sole responsability.
On Aug 26, 1:55 pm, Mike Jones mike.a.jo...@gmail.com
BSD all the way
On Aug 26, 2009, at 2:27 PM, Jan Goyvaerts wrote:
Thanks ! That's indeed the kind of accessible explanations I am
looking for.
What would be the logical choice for a care-free open source project ?
Everybody can use it, modify it, bla bla bla and the usage is your
sole
Yes, I once used Apache 2.0 but now I'm thinking New BSD is the way to
go. And one of the main reasons I read was that, especially to non-
java people, many see BSD and immediately understand what that's
going to be. It's also easier when more and more licenses are
becoming BSD. And it
Does BSD have the be cool on the patents clause to provide author
protection etc? from what I remember, other then that they are very
similar. But BSD style seems to mean (in most peoples minds these
days) the most liberal to everyone (user and author, not just
author).
On Aug 27, 8:34 am,
11 matches
Mail list logo
