3 ms·
Interesting post from Zed there. It's even gone so far that people demand that we use the BSD license (or any license) that doesn't require credit for using yo
by ErrantX 16y ago
Interesting post from Zed there.
It's even gone so far that people demand that we use the BSD license (or any license) that doesn't require credit for using your work. Other programmers don't want to have to put your name in a credits section of their applications.
Counter opinion (I realise this is only a subset of Zeds point, which I do agree has some useful points)?
The reason many of us like to see libraries, frameworks and support structure (as opposed to software which has an end use) licensed under BSD or similar is less because we actively desire to remove attribution.. but because we like to have control over our own code licensing choices. Generally programmers are pretty good about credit. More importantly the GPL does not force you to mention anything in the credits... at all... you can just leave all the references in the code - and in many cases people just won't read that. So I don't buy this argument much at all.
(side point: I maintain a couple of FOSS/Open Source projects and love the idea of stuff I find interesting being used in all sorts of ways. I couldn't really care less about whether someone makes $100 Million using it in their app. In fact I do care about that; firstly I care positively about the fact that I helped them with their success. Secondly I kick myself that it wasn't something I thought of doing. Doh! I prefer to trust that someone will use my code ethically; by which I mean a) tell other people about the cool piece of code X that they are using and b) contribute back to us. But I personally don't like the idea of forcing that behavior :P
Although; it's understandable why people do use the GPL for non-software code).
You know; on a related note I think the section before the above quote was interesting. And he has something of a point - that we don't think enough about the people making useful code for us. I don't think we are stealing their soul :) but there is definitely a lack of communication (even when the GPL is in use).
tl;dr - I don't buy the idea that certain licenses address the problem of programmer fame.
- icefox 16y agoEveryone knows that BSD requires you give them credit. Right? Right? I hope people are fulfilling the full requirement of the copyright and not just #1 "2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the <organization>." For example in safari click Help/Acknowledgments
- ErrantX 16y agoI'm not sure that insists on credit being given on, say, the credits page of your website, it refers to the source release. If you don't mention that you are using X on the site then there is no requirement (as I interpret it) to say "X is made by". (Most people do link the X's website though, which I would call courteous attribution).
- gxti 16y agoThe third clause was removed in 1999, although apparently some software is still using the 4-clause form. http://en.wikipedia.org/wiki/BSD_licenses http://en.wikipedia.org/wiki/BSD_licenses
- mindcrime 16y agoThe "advertising clause" is only found in the old 4-clause BSD license though (or licenses derived from the 4-clause BSD). But that style has gone out of favor, as people found the advertising clauses caused problems, such as a proliferation of required attributions (especially obnoxious in the case of "badgeware" clauses which require something displayed as part of the UI), and not being GPL compatible. But as long as you maintain the copyright notice (which is required by the vast majority of licenses) then attribution is implicit... you just have to read the code to find it. http://en.wikipedia.org/wiki/BSD_licenses#4-clause_license_.28original_.22BSD_License.22.29 http://en.wikipedia.org/wiki/BSD_licenses#4-clause_license_....