Received: from out1.migadu.com (out1.migadu.com [91.121.223.63]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 3B61A781955 for <~alpine/devel@lists.alpinelinux.org>; Sat, 18 Apr 2020 17:57:05 +0000 (UTC) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dereferenced.org; s=default; t=1587232624; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=FSTgqHgEC78KyNFp0cxjSABH99Ri+pUwSGKvBM4StSE=; b=rkSVB5638qIWvF68HX+LTIphyDghtw2aGGm53GYdWGt073tR0uPsaDkGAT4q+iFv6xVrdc IOo3pCSTJy+LU4ctGLzzV7V0Vf8XKa/NT7CGh+DvZh0K6nYokloO41G1CAqXSZU/ruoVT/ fY3olihndU33AF4tCVLBujcfwChjPNo= Date: Sat, 18 Apr 2020 17:57:03 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Ariadne Conill" Message-ID: Subject: Re: mailing lists, processes, modernization To: "Leo" , ~alpine/devel@lists.alpinelinux.org In-Reply-To: <20200418115508.73b3f2de@enterprise> References: <20200418115508.73b3f2de@enterprise> <66694f73048e047cadbe9e3f715801d8@dereferenced.org> X-Spam-Score: -0.10 Hello,=0A=0AOn April 18, 2020 2:55 PM, "Leo" w= rote:=0A=0A> On Sat, 18 Apr 2020 03:48:25 +0000=0A> "Ariadne Conill" wrote:=0A> =0A>> Hello,=0A>> =0A>> When Alpine was= first started, we had a single mailing list,=0A>> alpine-devel, which wa= s running on ezmlm. This served us well for=0A>> many years, but a few ye= ars ago, we started to realize that we needed=0A>> to modernize the softw= are being used in order to mitigate various=0A>> security and spam issues= with the ezmlm setup.=0A>> =0A>> This lead to Drew DeVault proposing tha= t Alpine use his Sourcehut=0A>> platform for mailing lists, which we have= used for the past 8 months.=0A>> Initially, this was seen as a good solu= tion for the original=0A>> problems we were having with the ezmlm-based s= etup, but some have=0A>> discontinued using the mailing lists, in some ca= ses leaving the=0A>> project entirely due to issues the Sourcehut softwar= e has processing=0A>> HTML e-mail, which caused incompatibility with popu= lar e-mail clients=0A>> such as the Android GMail client and the iOS EMai= l client, as well as=0A>> differences in behavior verses the earlier mail= ing list system=0A>> involving the Sourcehut solution not mailing a copy = of the message=0A>> back to its author.=0A>> =0A>> The reduced participat= ion on the mailing lists, and thus reduced=0A>> adherence to procedure fo= r coordinating system changes have reduced=0A>> its usefulness as single = source of truth for tracking system changes.=0A>> =0A>> Unfortunately, th= is brings us to a crossroads: mailing lists that are=0A>> boycotted by pa= rticipants are not a useful communications tool for a=0A>> project, becau= se of the source of truth issue. In addition, the infra=0A>> team has exp= ressed a desire to migrate all applications they manage to=0A>> run under= Docker, a desire not shared by Drew for the Sourcehut=0A>> infrastructur= e.=0A>> =0A>> Since adoption of the Sourcehut mailing list platform, we h= ave also=0A>> implemented GitLab as a Git forge. GitLab features high qua= lity issue=0A>> tracking and integrates with e-mail. This leads us to my = proposal to=0A>> replace development mailing lists with GitLab issues and= merge=0A>> requests.=0A> =0A> Correct me if I'm wrong (hopefully I am wr= ong), but e-mail integration=0A> is only for Enterprise Edition.=0A=0AThe= FOSS version of GitLab supports e-mail integration for replies, but=0Ano= t e-mail integration for submitting patches.=0A=0ASee also: https://docs.= gitlab.com/ce/administration/reply_by_email.html=0A=0AAriadne