2009/8/17 Alex Holkner <[email protected]>: > This sounds like it could be a real issue now, given that i'm probably not > going to be the one handling distribution. I'm open to suggestions as to an > appropriate license, and copyright reassignment if necessary. (Please > provide examples of projects that use these licenses). > My intention is that documentation be free to edit and redistribute, however > I would like to restrict publication with a price tag attached (i.e., as a > book). I have refused publication offers of this kind in the past and would > like to continue doing so, if possible. If such a license isn't feasible > then I will accept a free license. Compatibility with Debian is not a > priority for me.
Well, the obvious answer for a license which fits your requirements would be something like CC-NC-SA (possibly with an attribution clause, if you feel strongly about that). Unfortunately, I don't know of any projects which use this, largely because the noncommercial clause is seen as anathema by a fairly vocal portion of the free software community. Personally, I would have no problems with the existing documentation being available under such a license, or with any future contributions I make being subject to it, but I imagine some more FOSS-centric contributors might be less than thrilled. I do appreciate the large amount of leeway available in the licensing of Pyglet, but I accept that such is not so necessary for the documentation. However, one point I'd raise is that a large portion of the documentation (the API reference) is contained in the source files, which are themselves BSD licensed. I imagine this was unintentional, but it could be argued by someone who wanted to that the API reference is therefore available for publication on a commercial basis. I don't know if this would influence your decision, or even if separate licenses for the API reference and programming guide are something you might consider. Martin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. 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/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
