Closed steipete closed 12 years ago
Hi Peter,
I really don't like software licenses, they're convoluted and hard to understand… Basically all I wanted to say was that whoever uses the source add some sort of mention to the original author somewhere in the app or documentation, and if there are any enhancements done to the source it would be nice (but not required) to share those back.
BSD seems appropriate for that intended use, what do you think? if you have any other suggestions I'm open to hear them as well.
Best,
Alex.
On Sep 20, 2012, at 9:00 AM, Peter Steinberger notifications@github.com wrote:
I'm confused with the license. It's quite uncommon for code to be under a CC license. Especially this block is very subjective:
"Share Alike - If you alter, transform, or build upon this work, you may distribute the resulting work only under the same, similar or a compatible license."
How's "build upon" defined? Somehow reading this kinda reminds me of the GPL - even if you might not intended it but this license is too "fluffy" to be used in commercial projects. The CC creators even explicitly recommend against using it for code.
MIT or BSD would be great options.
— Reply to this email directly or view it on GitHub.
Hi Alex,
indeed, they are! But BSD is a great choice, one of the shortest.
I recommend this style:
Copyright (c)
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Changed to BSD license :)
On Sep 21, 2012, at 1:58 PM, Peter Steinberger notifications@github.com wrote:
Hi Alex,
indeed, they are! But BSD is a great choice, one of the shortest.
I recommend this style:
Copyright (c) , All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
— Reply to this email directly or view it on GitHub.
I'm confused with the license. It's quite uncommon for code to be under a CC license. Especially this block is very subjective:
"Share Alike - If you alter, transform, or build upon this work, you may distribute the resulting work only under the same, similar or a compatible license."
How's "build upon" defined? Somehow reading this kinda reminds me of the GPL - even if you might not intended it but this license is too "fluffy" to be used in commercial projects. The CC creators even explicitly recommend against using it for code.
MIT or BSD would be great options.