Date: Fri, 6 Mar 2020 00:30:28 +0000 (UTC)
From: Cosmo Borsky <me@cosmoborsky.com>
To: ~alpine/devel@lists.alpinelinux.org
Message-ID: <7f0837fb-cc0a-4932-9d15-d35eceb23340@localhost>
In-Reply-To: <1583446647339.60209@axis.com>
References: <24b91bd507e8151d41ac1d9866a4fd7a07febfe0.camel@cogitri.dev> <C1371RU6KTBL.2M1PT8PA0ZN98@homura>,<CAJH62qngx01cLaXhTq3HSYOeL8sZzgL11H9PoFgCasLX2uY_tw@mail.gmail.com> <1583446647339.60209@axis.com>
Subject: Re: Does it make sense to keep ~alpine/aports running?
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


We shouldn't be so hot on removing the lists if they are not getting attention.

If the mailing list goes unattended, pinging devs should be OK. If a contributor chooses to make a GitLab account and submit a patch as a PR, they should be able to. If a contributor would like to email a patch in, they should be able to.

This seems more like the mailing list is not used extensively by devs/maintainers because it does not fit their workflow, be it testing patches, merging patches, etc.
IMO, we should discuss what could be done to fit the developer's workflow and be more inclusive of those working on the mailing list.
I've started to adapt a workflow that caters to both systems: the ability to mail and test mailed-in patches, and the ability to ease submitting PRs in eg. GitLab.

Keep in mind the lists are powered by SourceHut, which is still in its early days.
If you have ideas that would improve mailing list flow, submit a PR to SourceHut.

Here is a task related to this thread:
https://todo.sr.ht/~sircmpwn/dispatch.sr.ht/29

Additionally, other Alpine lists are powered by SourceHut:
https://lists.alpinelinux.org/lists/~alpine