mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [musl] Current state and future of musl development infrastructure
Date: Thu, 16 Dec 2021 00:02:20 -0500	[thread overview]
Message-ID: <20211216050220.GL7074@brightrain.aerifal.cx> (raw)
In-Reply-To: <5faf9ff0eaa6b72ac3c3b22e3a41bde071ae5806.camel@zv.io>

On Wed, Dec 15, 2021 at 04:52:05PM -0600, Zach van Rijn wrote:
> 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?

This is roughly what we need: a place to represent long-term state for
the subset of issues that cannot be resolved immediately. Historically
that was very few, but what happens is that they start to accumulate
over time -- this is rather inherent in their nature.

Representing immediately fixable bugs would be fine too, but less
important.

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

No, I don't think so. The problem is not that the list is overloaded
for multiple uses. The problem is that there's limited capability to
search for and reply into existing historical threads unless you're a
list member with your copy of the archive, and there's no way to link
new requests with old ones like "duplicate of..." relationship in a
bug tracker, nor any easy way to filter on "still open" vs "resolved",
etc.

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

Yes. Having this automated would be really nice. Even better if it
could be done not just for the official upstream repo but for proposed
patches/patchsets or third-party git branches (on some sort of
request).

I'd really love if the CI were optimized to do incremental builds and
reuse artifacts as much as possible for rapid results, but doing that
right probably requires fixing missing dependency tracking in the
build.

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

A manually curated TODO list/wishlist on the wiki was how this was
managed for the last N years, and it wasn't really good because it
failed to link community discussion of the issue and didn't capture
things not already valued by me or community. Even with a bug tracker
it would be perfectly fine (and much more effective than it is now) to
have a TODO/roadmap, since it could *link to* the relevant tracker
items for more detail and record of what exactly is wanted or proposed
and why.

Rich

  reply	other threads:[~2021-12-16  5:02 UTC|newest]

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

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20211216050220.GL7074@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.vuxu.org/mirror/musl/

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