Received: from knopi.disroot.org (knopi.disroot.org [178.21.23.139]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 46839782B31 for <~alpine/devel@lists.alpinelinux.org>; Tue, 10 Mar 2020 16:20:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id B570D3A110 for <~alpine/devel@lists.alpinelinux.org>; Tue, 10 Mar 2020 17:20:04 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at disroot.org Received: from knopi.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oNf0C00PfxsQ for <~alpine/devel@lists.alpinelinux.org>; Tue, 10 Mar 2020 17:20:03 +0100 (CET) Subject: Re: Does it make sense to keep ~alpine/aports running? DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1583857203; bh=eiviY3TlDcWrQ6K0hCIio7JehAQSDSyILushERyaCBQ=; h=Subject:To:References:From:Date:In-Reply-To; b=UBuFAPCPffqmTIBnDkDaSEkdVRYNllHtNEYy/nNCibznxM7Av2dRN1c6EOQ1/O9mp iaezl4ZMlm2jKzyHM9gIZJ7plRpdqqyXWtl8g856KoBXDT5DpNcBB+14wvp/nlnQ9m fXmcSFGzQI3xsSDxauoBvX9zYKXz8deS6INUpzP0V8Y4Be2unG5HVWTovLkRsV5Gos Yy4byp52EpuRivW77qTiknjSavNbVGkEVk23cYM8FpThSMcCe9QWSywHtmPW8vG0ek zCZFpsA5fO0e4jiGFlO4OYUe5/q0x455b+pC02GMyJ+SwWTmKl3wqfhhscEay6PHom NFYUPOwAHNWYA== To: ~alpine/devel@lists.alpinelinux.org References: <24b91bd507e8151d41ac1d9866a4fd7a07febfe0.camel@cogitri.dev> <20200310170643.7a475808@ncopa-desktop.copa.dup.pw> From: Bart Ribbers Message-ID: Date: Tue, 10 Mar 2020 17:20:01 +0100 Mime-Version: 1.0 In-Reply-To: <20200310170643.7a475808@ncopa-desktop.copa.dup.pw> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Hi, On 2020-03-10 17:13, Natanael Copa wrote: > So, one of the major reasons we kept a patch mailing list was because > there was people who would not contribute via github. I think the > majority of those are ok to contribute via gitlab, so that is not as > big problem nowdays. > > I guess it boils down to if we want make it easy for contributors who > don't want sign up in gitlab, or prefers `git send-email` at the > expense of the reviewers. (and contributors who would need check both > mailing list and gitlab if someone else has provided same patch). Do note that Gitlab supports sending patches and responding to issues and MR's via email, there is just the problem that it's only available in the enterprise edition of Gitlab. 1. reply by email [1] 2. new issue by email [2] 3. new merge request by email [3] [1] https://docs.gitlab.com/ee/administration/reply_by_email.html [2] https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#new-issue-via-email [3] https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html#new-merge-request-by-email-core-only I personally do not think it's worth considering due to having to get a Gitlab license and having to run proprietary code on the Alpine infrastructure, but maybe opinions differ? There is also a quite extensive GitLab API, I can imagine someone writing a wrapper around it to allow using email with it. Best regards, Bart