Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Wed, 15 Dec 2021 22:22:41 +0100
From: jvoisin <>
Subject: Current state and future of musl development infrastructure

Hello everyone,

I had some small chitchat with dalias on irc, both on #musl and
privately about the ideal infrastructure for musl development, but it's
better to discuss those topics on the mailing list.

I think that everyone agrees that we need a bugtracker, and likely some
CI. Something lightweight (ho heavy dependencies), self-hosted, that can
integrate well with emails/mailing-lists/patch tracking/…

Here is a small selection, feel free to suggest more:

- in Perl
- no need to present it
- from sourcehut, can be tightly
integrated with other pieces, like mailing lists, git commit/patches/…,
continuous integration, …

dalias is very adamant that CI & testing don't belong in the same repo
as software, but in a separate one.

Most of the forges providing continuous integration (gogs, gitea,
gitlab, …) don't play nice with emails, except sourcehut ( ), which is "email first".

Henceforth, I think that a good move forward would be to go with sourcehut:

- easy to self-host (python+go)
- lightweight (both server-side and client-side)
- designed around mailing-list/patches first
- powerful continuous integration, on multiple OS and multiple architectures
- usage documented for newcomers (my generation is used to issuing
pull-requests: sending patches by email is completely alien)
- maintained by some musl users ;)

What do you people think?

Julien (jvoisin) Voisin
GPG: 04D041E8171901CC

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.