From dev-return-49011-archive-asf-public=cust-asf.ponee.io@couchdb.apache.org Tue Feb 4 05:07:46 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id CAC15180647 for ; Tue, 4 Feb 2020 06:07:45 +0100 (CET) Received: (qmail 30192 invoked by uid 500); 4 Feb 2020 05:07:38 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 30069 invoked by uid 99); 4 Feb 2020 05:07:38 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Feb 2020 05:07:38 +0000 Received: from [192.168.169.22] (toroon0560w-lp130-07-64-229-95-192.dsl.bell.ca [64.229.95.192]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id 2CD7C4FB1; Tue, 4 Feb 2020 05:07:38 +0000 (UTC) Subject: Re: Removal of ibmcom/couchdb3 preview image To: CouchDB Developers References: <03c7c597-3dac-1bde-ab3c-cb22b8138c02@apache.org> <9226EBA0-6993-4E1B-ADFE-610C91B86BD9@apache.org> <09fed35b-c844-f807-dae9-4c2377599be8@apache.org> Cc: private@couchdb.apache.org From: Joan Touzet Organization: Apache Software Foundation Message-ID: Date: Tue, 4 Feb 2020 00:07:37 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <09fed35b-c844-f807-dae9-4c2377599be8@apache.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit To quote a long time Apache member who's discussing a very similar issue in parallel over on builds@apache.org right now: > Downstream users trust Apache because of our provenance rules (per feedback > over the years). Spoiling that assurance, spoils our reputation; that is > kind of at the heart of the issue for the Board to debate. (-Greg Stein) I don't want to fight over this issue with you, or with them. Let's find a way to finesse this and get the involvement we need from others, without exacerbating the problem, OK? -Joan On 2020-02-04 12:05 a.m., Joan Touzet wrote: > Adam, > > I didn't specifically go after Will. Will was kind enough to step in and > help, which is great. > > Legal has been very, very clear on this. During my time on the board > it's come up as well. We do not want to incur their wrath. > > We *cannot* be pushing dev or master builds out to the general public. > Period. > > Making dev builds available to people who *directly* participate here - > on dev@couchdb.a.o - is fine. Making it available to the general > population outside of that mailing list - be that contributors who only > work on GitHub, people on Slack, Twitter, blogs, etc. is expressly > forbidden. > > I mean, we need more people on dev@ - how about trying to get them to > come here first? We could have a *passworded* Docker repo and get them > to pull it from there, that's fine. Or you could just tell people to: > >   git clone https://github.com/apache/couchdb-docker >   docker build dev -t couchdb:dev >   docker run couchdb:dev > > and report issues here. Is 3 lines harder than 1? Not really. > > You can go take this up with Legal if you want directly, but I > anticipate the answer will be a resounding *no*. I'm not going to make > their argument for them. > > -Joan > > On 2020-02-03 6:19 p.m., Adam Kocoloski wrote: >> I pushed for a `couchdb3` preview image — heck, I built the first one >> myself 6 months ago (!) and hosted it in my own Docker Hub account. >> The upcoming CouchDB 3.0 release is better off for all the little bugs >> we found and fixed as a result of those pulls. Appropriately >> documented, it’s just an alternative version of >> https://repo-nightly.couchdb.org >> >> If you want to take an IBMer to task for violation of subsection II, >> part D of some ASF by-laws, pick me. Will has done a phenomenal job >> chasing down all our internal teams and encouraging them to work with >> us directly and avoid forking codebases or switching databases to meet >> their individual roadmaps, and this image was a big assist in that >> regard. >> >>   Given that the publication of this image had such a positive effect >> on the quality of the software that we *are* releasing, I’d like to >> see if we can find a way to publish nightly Docker images in a more >> suitable location post 3.0. Thanks, >> >> Adam >> >>> On Feb 3, 2020, at 1:39 PM, Will Holley wrote: >>> >>> Thanks Joan for highlighting the problem; the image has been removed >>> from >>> DockerHub. >>> >>> On Mon, 3 Feb 2020 at 17:46, Joan Touzet wrote: >>> >>>> On 2020-02-03 12:34, Jan Lehnardt wrote: >>>>> Thanks Joan for raising this, >>>>> >>>>> I’m throwing in an extra “this is bad” because of the version number. >>>> 3.0 is not a thing yet and we have brought that up with several >>>> IBMers that >>>> calling anything intermediate “CouchDB3” (this is isn’t the first >>>> time) is >>>> problematic in the CouchDB Slack. >>>>> >>>>> Y’all need to do better. Is suggest the removal of this image >>>>> blocks the >>>> 3.0.0 release, to make sure nobody gets the wrong bits. >>>> >>>> >>>> I agree - I was going to fork 3.x and 3.0.x today but I'll hold off >>>> until this gets resolved. We still have 2 documentation issues that >>>> need >>>> to be resolved, and verification of the Windows build, before we can >>>> release anyway. >>>> >>>> -Joan >>>> >>>>> >>>>> Best >>>>> Jan >>>>> — >>>>> >>>>>> On 3. Feb 2020, at 18:08, Joan Touzet wrote: >>>>>> >>>>>> Hi IBM people, >>>>>> >>>>>>   https://hub.docker.com/r/ibmcom/couchdb3 >>>>>> >>>>>> This is a problem, especially because i'm seeing 50K+ pulls on this >>>> image already. >>>>>> >>>>>> We've not yet released CouchDB 3.0. Any use of this image outside of >>>> our immediate developer community is a direct violation of Apache >>>> release >>>> protocols, and could result in serious problems down the road. >>>>>> >>>>>> If you need a dev image for CouchDB to build Fauxton, that's one >>>>>> thing >>>> - but that image needs to be built each time, or hosted on a *private* >>>> repository with credentials. >>>>>> >>>>>> Please take this image offline immediately. >>>>>> >>>>>> -Joan "not messing around" Touzet >>>>> >>>> >> >>