Project summary claims license is "New BSD License", but LICENSE contains text of the MIT license

[Ido Sebastiaan van Oostveen]

A issue on google code seems to rightfully state that we list our
project as "New BSD License" while our LICENSE file is the MIT License.

http://code.google.com/p/django-command-extensions/issues/detail?id=87

Now i think the biggest difference between the BSD and MIT style license
is the notice prohibiting the use of the name of the copyright holder in
promotion.

As stated in the New BSD License as:
* Neither the name of the <organization> nor the
names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.

I'm +1 on adding this disclaimer as I (with my i-am-not-a-lawyer hat on)
would think that nobody wants his good name used by third parties
without permission first.

That would mean we can either change the license to new-bsd or using the
modified version of MIT license as shown on wikipedia:
http://en.wikipedia.org/wiki/MIT_License

Either way it would be nice to have google code reflect the actual
license :)

Regards,
Bas

[Michael Trier]

On Mon, Mar 30, 2009 at 4:34 AM, Ido Sebastiaan van Oostveen <v.oos...@gmail.com> wrote:

A issue on google code seems to rightfully state that we list our
project as "New BSD License" while our LICENSE file is the MIT License.

http://code.google.com/p/django-command-extensions/issues/detail?id=87

Now i think the biggest difference between the BSD and MIT style license
is the notice prohibiting the use of the name of the copyright holder in
promotion.

As stated in the New BSD License as:
    * Neither the name of the <organization> nor the
      names of its contributors may be used to endorse or promote products
      derived from this software without specific prior written permission.

I'm +1 on adding this disclaimer as I (with my i-am-not-a-lawyer hat on)
would think that nobody wants his good name used by third parties
without permission first.

Yeah that was a mistake.  It should be New BSD License.  That was the intent all along.

 

--
Michael Trier
http://blog.michaeltrier.com/
http://thisweekindjango.com/

[Will Hardy]

As far as I know, all you need is for each contributor to consent,
unless we have already assigned our copyright to eg the project leader
or google or something (I don't read enough fine print)...

I am happy to consent to a change to BSD.

Cheers,

--
Will Hardy
e: wi...@willhardy.com.au
w: http://www.willhardy.com.au



2009/3/31 Michael Trier <mtr...@gmail.com>: