On Fri, May 13, 2011 at 2:30 PM, Boštjan Mejak <[email protected]> wrote:
> So if I want to create a software for which I don't want to give the source
> code to the world, I use the MIT license and I am fine? Also, which
> particular BSD license is similar to the MIT license in the means of not
> needing to give the source code?
>

I think you've got the wrong end of the stick. If you don't want to
allow people to have the source code, don't release the source code at
all.

BSD/MIT/Apache are all permissive software licenses, if you release
your code under one of those licenses, people can use it for whatever
they want.

GPL/LGPL are restrictive software licenses, they require users of the
code to contribute changes/release source code for code linked to the
licensed code, or any changes to the licensed code, *if* the code is
distributed to other parties.

AGPL is a more restrictive version of GPL that requires changes/source
to be released even if the code is not distributed to other parties,
but is just used on a website that produces content for other parties.

Cheers

Tom

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to