[arch-dev-public] Scope of arch-projects mailing list
Hi all, while trying to use the arch-projects mailing list for an announcement I realized, that it is (probably?) not really supposed to be used for that at the moment. It explicitly states to be used for development discussion and providing patches for dbscripts, devtools, mkinitcpio, namcap, netctl, archweb and pyalpm. It seems that apart from netctl none of the above really make much use of this anymore though when it comes to development, as the projects have pivoted towards merge/pull requests on their respective VCS forges. Unless there are any objections, I propose to * add arch-repo-management and arch-release-promotion to it * change arch-projects to *also* become a general discussion list around the above mentioned Arch Linux projects * extend mailing list "about" section with information on how each project prefers to receive patches (e.g. I do not want to use the mailing list for that, but others may) Rationale: We lack a mailing list that revolves around our internal projects and which can also be used by non "elevated users" (such as Trusted Users and Developers) for more general discussion. Given the very low traffic on the arch-projects mailing list I see no issue with it becoming a per-project discussion list as well (as in our case mailing lists seem to be mainly used for discussion and not so much for development anymore these days). Best, David -- https://sleepmap.de
On 3/2/22 21:53, David Runge via arch-dev-public wrote:
Unless there are any objections, I propose to
* add arch-repo-management and arch-release-promotion to it * change arch-projects to*also* become a general discussion list around the above mentioned Arch Linux projects
What do you mean by general discussion? The list already states it can be used for developmental discussion - anything beyond that is probably off-topic on a technical list. Otherwise changes to the list are fine. A
On 2022-02-03 22:07:09 (+1000), Allan McRae via arch-dev-public wrote:
On 3/2/22 21:53, David Runge via arch-dev-public wrote:
Unless there are any objections, I propose to
* add arch-repo-management and arch-release-promotion to it * change arch-projects to*also* become a general discussion list around the above mentioned Arch Linux projects
What do you mean by general discussion? The list already states it can be used for developmental discussion - anything beyond that is probably off-topic on a technical list.
Hm, maybe what I understand as "development discussion" just seemed too narrow to me. I agree, that that point does not have to be altered and will just extend with "and announcements" or so.
Otherwise changes to the list are fine.
Thanks for the feedback! Best, David -- https://sleepmap.de
On 03.02.22 12:53, David Runge via arch-dev-public wrote:
Hi all,
while trying to use the arch-projects mailing list for an announcement I realized, that it is (probably?) not really supposed to be used for that at the moment.
It explicitly states to be used for development discussion and providing patches for dbscripts, devtools, mkinitcpio, namcap, netctl, archweb and pyalpm.
It seems that apart from netctl none of the above really make much use of this anymore though when it comes to development, as the projects have pivoted towards merge/pull requests on their respective VCS forges.
Unless there are any objections, I propose to
* add arch-repo-management and arch-release-promotion to it
Sure.
* change arch-projects to *also* become a general discussion list around the above mentioned Arch Linux projects
Ok.
* extend mailing list "about" section with information on how each project prefers to receive patches (e.g. I do not want to use the mailing list for that, but others may)
Yeah that's probably good.
Rationale: We lack a mailing list that revolves around our internal projects and which can also be used by non "elevated users" (such as Trusted Users and Developers) for more general discussion. Given the very low traffic on the arch-projects mailing list I see no issue with it becoming a per-project discussion list as well (as in our case mailing lists seem to be mainly used for discussion and not so much for development anymore these days).
Best, David
I think that makes sense. Go for it! Sven
participants (3)
-
Allan McRae
-
David Runge
-
Sven-Hendrik Haase