John Cowan <co...@mercury.ccil.org> writes: >I don't think it is. Clauses 1 and 2 (as usual for BSD) require that the >license itself be preserved by downstream distributors. That license >already includes the pointer required by clause 4 -- in the text of >clause 4 itself. So clause 4 is self-satisfying taken in conjunction >with clauses 1 and 2. > >All good. > >/me snickers.
:-) It's not clear what "include a pointer" means legally. Is the reference in the LICENSE file enough, or do they mean a hyperlink? A hyperlink that is shown somewhere in the UI where such information is customarily shown? IOW, the issue is not so much that it's a badgeware license as that one can't quite tell to what degree or in what way it's a badgeware license. -K >> 1. Redistributions of source code must retain the above copyright >> notice, this list of conditions and the following disclaimer. >> 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. Neither the name of Charles River Analytics nor the names of its >> contributors may be used to endorse or promote products derived from >> this software without specific prior written permission. >> 4. Redistributions in any form must include a pointer to Charles River >> Analytics' website (www.cra.com) and probabilistic modeling services. _______________________________________________ License-discuss mailing list License-discuss@opensource.org http://projects.opensource.org/cgi-bin/mailman/listinfo/license-discuss
