[beepy-devel] MIT License

[Justin W. <dae...@ei...>]

Hi folks,

After some of the recent communication on the list, I've had a good hard
look at the current BEEPy license and thought about my original
intentions for the licensing.

I believe I'd like to change the license for BEEPy from LGPL to the MIT
license to make the library more compatible with Python in general, the
Twisted framework (Hi guys), and other software. I think the LGPL, in
this instance, is too belaboured with legalese for people to easily
incorporate it into their software. BEEPy is a tiny little library that
really belongs inside a larger project like the Python standard library
or the twisted framework.

Does anyone have any objections to relicensing BEEPy as MIT?

I think the purposes of BEEPy, and BEEP in general, would be better
served by making access to a high level language library for BEEP more
accessible. Those Vortex guys, with their XML-RPC and everything, they
think they're so hot; well we'll show them! ;)

More seriously, I've recently learned a lot about how the Twisted
framework really works, and I think I can fold some of that knowledge
into BEEPy. There are some serious brains at work over there at divmod,
and I'd like to take advantage of their great work. It's been a while
since I actively developed BEEPy, but I think I can make some useful
updates.

I know this is an uber-low traffic list, but if anyone has any comments,
please speak up. I really do value your feedback; I'm not smart enough
to grok this stuff on my own.

And thanks for still caring about BEEPy. :)

-- 
Justin Warren <dae...@ei...>