Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of zachary.zolton@gmail.com
 designates 209.85.221.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=fH4IlZCn3BRFLQD4XVJilz6ibTlYHe4KJGkGdnDBoNumMHB05HOZs4szw7/BQUtZ5n
         QyTChvAZeVZGJ5EAiT28N0254iX/wnEaWKouvXLVD29u/gQQprolJsqlpg/xmZxDc/r3
         zXRBuLZJ25I8yB1BUs3X0AX0ZPmjGe4cTYgWo=
MIME-Version: 1.0
In-Reply-To: <b95ea6320903251800y6048e9d7p2847f4defefa1f5@mail.gmail.com>
References: <b95ea6320902241154j30b7e328r4be4cde4faed858a@mail.gmail.com>
	 <6A9125FF-5D79-4E0B-9F5F-E60A9828420B@apache.org>
	 <b95ea6320903251800y6048e9d7p2847f4defefa1f5@mail.gmail.com>
Date: Thu, 26 Mar 2009 09:22:18 -0500
Message-ID: <f728979f0903260722v315f997bj750abba93ad89d1f@mail.gmail.com>
Subject: Re: Lounge clustering framework
From: Zachary Zolton <zachary.zolton@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Thanks, Mebo! I should have occasion to try to get this code working
for me in the next few weeks.

Cheers,
Zach

On Wed, Mar 25, 2009 at 8:00 PM, Shaun Lindsay <shaun@meebo.com> 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.
>
> http://code.google.com/p/couchdb-lounge/
>
> Since I went through and changed a bunch of the paths, there might be som=
e
> 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 o=
f
> how everything works and
> (hopefully) a walkthrough on getting it built and running. =A0If everythi=
ng
> 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 yo=
u
> added to the project.
>
> Enjoy!
>
> Shaun Lindsay
> Meebo.com
>
> On Tue, Feb 24, 2009 at 1:09 PM, Jan Lehnardt <jan@apache.org> wrote:
>
>>
>> On 24 Feb 2009, at 20:54, Shaun Lindsay wrote:
>>
>> =A0Hey 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? =A0Since Couch is an Apache project, the
>>> Apache
>>> license is probably appropriate, however, since the Lounge is more or l=
ess
>>> a
>>> separate entity, we can probably release under any license. =A0Any
>>> 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 http://www.apache.org/licenses/
>>
>>
>> =A02. Project hosting? =A0Again, since this is separate from Couch, it p=
robably
>>> doesn't make sense to have it in the Couch repo. =A0We were thinking go=
ogle
>>> code (since we use svn), =A0but I'm open to whatever. =A0Thoughts?
>>>
>>
>> We can make it a sub-project of CouchDB eventually (just raising the opt=
ion
>> 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.
>>
>>
>> =A0Once we settle on a license, we'll need to run it by our lawyer to ma=
ke
>>> 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
>> --
>>
>>
>