mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Zach van Rijn <>
Subject: Re: [musl] Current state and future of musl development infrastructure
Date: Wed, 15 Dec 2021 16:52:05 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, 2021-12-15 at 22:22 +0100, jvoisin wrote:
> Hello everyone,
> ...
> 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/…

My primary concern is that this will create unnecessary noise and
maintenance burdens. Note IRC and the mailing list are 3rd party.

Having watched this space over the past few years I think there
is one actual problem we need to solve and many that we don't:

 1. Fixes and improvements are suggested in IRC or on the list,
then folks follow up months later to ask what is the status. The
matter is lost in the wash or it is unclear who had the baton.

Rich is busy. But is an issue tracker needed here? The rule of
thumb up to this point has been to punt it from IRC to the list.

Since Rich is the sole gatekeeper, a disciplined approach to
keeping "serious" topics/discussion to the list, and using IRC as
casual grounds for starting discussions might be sufficient. Then
a TODO list would be the right tool to ensure issues aren't lost.

For example: what of the Hexagon port?

Using an issue tracker would provide a public view of open/closed
issue status, and maybe subscriptions. Is this all that we need?

Would splitting the lists into 'musl-devel' and 'musl-support' be
enough? Even this seems like overkill.

Most of the other problems are mitigated by the sole-developer
model and general nature (libc) of this project:

  * Quality control -- each change is already carefully reviewed

  * Widespread testing by various distros

  * Relative stability and low churn -- ~50 commits in a year!

As for CI.

It would probably be helpful to be able to run libc-test and
perhaps other applications on a number of real hardware platforms
in some automated manner.

> ...
> 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:

Very few people want to read documentation to submit patches.

I must say, I had to use Google to find the sourcehut docs. Can
you find it on or ?

The ~foo/ syntax is unintuitive for newcomers.

> ...
> What do you people think?

Overall the volume of fixes/improvements/features is so low that
it might not make sense to set up and maintain any more than:

 1. A TODO list

 2. A brick-simple cluster of machines for testing



  reply	other threads:[~2021-12-15 22:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 21:22 jvoisin
2021-12-15 22:52 ` Zach van Rijn [this message]
2021-12-16  5:02   ` Rich Felker
2021-12-16 11:40     ` Natanael Copa
2021-12-16 13:50       ` Rich Felker
2021-12-16 19:20     ` Zach van Rijn
2024-01-26 17:24 ` writeonce

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).