+1
> On 12 Mar 2015, at 12:44 AM, Andy Wenk <[email protected]> wrote:
>
> +1
>
> On 11 March 2015 at 20:19, Alexander Shorin <[email protected]> wrote:
>
>> +1
>> --
>> ,,,^..^,,,
>>
>>
>> On Wed, Mar 11, 2015 at 9:57 PM, Jan Lehnardt <[email protected]> wrote:
>>>
>>>> On 05 Mar 2015, at 18:49, Jan Lehnardt <[email protected]> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> between https://github.com/apache/couchdb/pull/305 and
>> https://github.com/klaemo/docker-couchdb/issues/22 I was wondering
>> whether the docker-couchdb project would be up for donating their effort to
>> us and to take over maintenance. @klaemo is up for it and we are only
>> waiting for the one other significant contributor to give their OK.
>>>>
>>>> With that out of the way: do we want this?
>>>>
>>>> Docker can be used in two capacities for CouchDB:
>>>>
>>>> 1. spin up a dev environment with all dependencies quickly.
>>>> 2. spin up a production instance of CouchDB that is all self-contained.
>>>>
>>>> Our current Dockerfile serves 1., but is poorly maintained, and
>> klaemo/docker-couchdb serves 2, and @klaemo hinted at being interested in
>> taking over maintenance of 2.
>>>>
>>>> I’d be in favour of having some Docker experience in-house that can
>> maintain both use-cases and cross-share any developments.
>>>>
>>>> If I hear no objections here, I’ll move to a vote.
>>>
>>> Thanks everyone for your input!
>>>
>>> Let’s go to a formal vote:
>>>
>>> Do we want to import the docker-couchdb project?
>>>
>>> I am +1.
>>>
>>> Best
>>> Jan
>>> --
>>>
>>>
>>
>
>
>
> --
> Andy Wenk
> Hamburg - Germany
> RockIt!
>
> GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588
>
> https://people.apache.org/keys/committer/andywenk.asc
