2008/12/4 Chris Meller <[EMAIL PROTECTED]>: >> > On Wed, Dec 3, 2008 at 9:45 PM, Michael Harris wrote: >> >> 2008/12/4 Chris Meller <[EMAIL PROTECTED]>: >> > >> > On Wed, Dec 3, 2008 at 7:29 PM, Michael Harris wrote: > > That still doesn't make it less confusing or annoying to users looking for > plugins. 99% of them don't care in the slightest how it's licensed, they > just want a convenient go-to location to find them. Don't screw the users > because we're holier than the GPL. We want Extras to be the de facto > location for Habari plugins. Excluding the GPL shoots that goal in the foot > and only invites frustration and confusion.
So you're saying get rid of ASL compatibility for -extras completely ? Because if you're _not_ suggesting that, then my understanding is that, as I said, there are other non-ASL-compatible things that we wouldn't put in -extras, and hence the potential problem of different repositories already exists. >> GPLv2 stuff isn't ASL compatible, right ? So I can't just take a GPLv2 >> theme, port it, and put it in -extras. If GPLv3 is ASL compatible, I >> can change the theme and re-license it using GPLv3, then put it in >> -extras. > > Yes, you can. Read my references. From the NOTICE file that, in order to use > the GPL, you must include in every package: > > This program is free software; you can redistribute it and/or > modify it under the terms of the GNU General Public License > as published by the Free Software Foundation; either version 2 > of the License, or (at your option) any later version. I did read your reference. I've read it before too. That suggests to me that I can use a later version of the GPL, and that to put it in -extras I need to re-license the software as GPLv3, because GPLv2 isn't ASL-compatible. If you're suggesting we dump ASL-compatibility for -extras, then you can obviously ignore this. > I don't know how you can make it much more straightforward. > And from what perspective are you looking at this? From a user perspective, > who cares? If anything, it's in Extras and is ASL-compatible so you're happy > because it can't be too bad. From the developer perspective it's GPL so > you're still good. I'm talking from a developer perspective. I don't see "it's GPL so you're still good," as I've explained above. >> This is exactly what I mean. That doesn't seem particularly >> straightforward to me, and it certainly doesn't pass the "at a glance" >> test. > > Seems pretty straightforward to me. It's not backwards compatible, but > you're free to upgrade at any time with or without a reason. I can pretend > version 2 never existed and use version 3 for everything... How can you pretend v2 never existed ? If I'm using a library that's v2, or porting a theme, I have to make the decision to change the license to v3 to put it in -extras. I have to understand enough about licensing to know that I have to make the change. I'm quite happy to be convinced that I'm completely wrong on this and that it is simple, but you haven't managed that yet. -- Michael C. Harris, School of CS&IT, RMIT University http://twofishcreative.com/michael/blog IRC: michaeltwofish #habari --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
