[Playlist] licensing

[Chris Anderson]

I think LGPL / MIT / BSD are all roughly equivalent in terms of usage.
MIT is the Rails license, so I'm comfortable with it. Dojo uses the
New BSD, so maybe there are reasons to choose it.

I think I'm going to go with MIT unless there are strong reasons not to.

On 5/3/07, Lucas Gonze <lgonze at panix.com> wrote:
>
> We'd be happy to host.  That would be very excellent.
>
> I think that our goal here is to create a canonical library for
> transforming between JSON and XML, so we want to discourage people from
> forking the code for any reason.  LGPL might be effective at doing that,
> since few web apps are GPL'd.
>
> Does that prevent usage?
>
> On Thu, 3 May 2007, Chris Anderson wrote:
>
> > I'm trying to pick a license for my XSPF -> JSON Javascript parser.
> > I'm having trouble understanding the impact of GPL-style (share-alike)
> > licenses for Javascript. The parser will be useless unless commercial
> > sites can include it in their codebase without repercussions. It's
> > hard to know whether using Javascript on your site is more like
> > linking to a library, or including the library's code in your program.
> > For that reason, I'm considering going with the MIT license.
> >
> > I'd also like to host the project with xspf.org, so I'm open to
> > suggestions about picking a license that works for integration into
> > the project.
> >
> > --
> > Chris Anderson
> > http://jchris.mfdz.com
> >
> > _______________________________________________
> > Playlist mailing list
> > Playlist at lists.musicbrainz.org
> > http://lists.musicbrainz.org/mailman/listinfo/playlist
> >
> >
>
> _______________________________________________
> Playlist mailing list
> Playlist at lists.musicbrainz.org
> http://lists.musicbrainz.org/mailman/listinfo/playlist
>


-- 
Chris Anderson
http://jchris.mfdz.com