On 7/4/07, Jonas <[EMAIL PROTECTED]> wrote: > > The `license link`_ is in the main page of AroundWord_. And the > discussion about the license's election is on this thread_. > You can read there why I choosed the license --that is Affero GPLv1 > and is compatible with GNU GPLv2-- for an end-user application, so I > don't repeat anything of what I have already said. > > Please reply any comment in that thread. Thanks. > > .. _license link: http://www.aroundword.org/wiki/License > .. _AroundWord: http://www.aroundword.org/ > .. _thread: > http://groups.google.com/group/aroundword-discuss/browse_thread/thread/f7910c0f83d099d6
Thanks. But I don't care much about what AroundWord itself uses, not am I inclined to post in a group that is extremely hostile to anything non-GPL. I just don't want to see GPL spread to other Pylons components or dependencies. It alarmed me a bit when I thought it said Nose was GPL. Then I looked closely at the Nose site and saw it's LGPL. It also seems a little funny to be worried that a company might, gosh, make proprietary improvements to a blog application that's maybe ten or twenty pages of Python code total. It's not like it's the Mona Lisa or Zope or MySQL or something big like that. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
