couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zachary Zolton <>
Subject Re: Lounge clustering framework
Date Thu, 26 Mar 2009 14:22:18 GMT
Thanks, Mebo! I should have occasion to try to get this code working
for me in the next few weeks.


On Wed, Mar 25, 2009 at 8:00 PM, Shaun Lindsay <> wrote:
> Alright, we got legal approval to release all the Lounge code, so I did a
> bunch of cleaning up (removing Meebo-specific pathnames, moving python
> modules out of our Meebo libraries and into a lounge specific module, etc)
> and put it all up on google code.
> Since I went through and changed a bunch of the paths, there might be some
> weirdness with things not working or other assorted strangeness.
> Anyway, there's quite a bit of code there and very little documentation
> about how all the pieces fit together, so I'll put together an overview of
> how everything works and
> (hopefully) a walkthrough on getting it built and running.  If everything
> goes according to plan, I'll put all of that information in the repo
> sometime tonight.
> If anyone is interested in working on this, let me know and we can get you
> added to the project.
> Enjoy!
> Shaun Lindsay
> On Tue, Feb 24, 2009 at 1:09 PM, Jan Lehnardt <> wrote:
>> On 24 Feb 2009, at 20:54, Shaun Lindsay wrote:
>>  Hey all,
>>> We've been discussing the best way to handle releasing the Lounge code and
>>> we have some questions that you, the couch devs, might be able to help out
>>> with:
>>> 1. What license is preferred?  Since Couch is an Apache project, the
>>> Apache
>>> license is probably appropriate, however, since the Lounge is more or less
>>> a
>>> separate entity, we can probably release under any license.  Any
>>> preferences?
>> If this or parts of this are ever fed back into CouchDB it'd be easiest to
>> have
>> it under Apache License 2.0. Any oder new-style BSD license or MIT will
>> do, too, but Apache License 2.0 is very much preferred.
>> *If* any of the code will go into CouchDB we'll also need a contributers
>> license agreement (CLA)* which is another thing you lawyer might want
>> to look at, but probably not right now.
>> * See way down on
>>  2. Project hosting?  Again, since this is separate from Couch, it probably
>>> doesn't make sense to have it in the Couch repo.  We were thinking google
>>> code (since we use svn),  but I'm open to whatever.  Thoughts?
>> We can make it a sub-project of CouchDB eventually (just raising the option
>> for now), but to start off, any open source hoster will do. CouchDB used to
>> be on Google Code and it seems a reasonable choice. Of course, GitHub
>> is all the rage today and would give you more street-cred but I'd
>> understand
>> if you don't want to switch version control systems.
>>  Once we settle on a license, we'll need to run it by our lawyer to make
>>> sure
>>> we're solid and, assuming that goes well, we should be good to give out
>>> the
>>> code.
>> This is so fricken' awesome! Thanks!
>> Cheers
>> Jan
>> --

View raw message