From: jvoisin <julien.voisin@dustri.org>
To: musl@lists.openwall.com
Subject: [musl] Current state and future of musl development infrastructure
Date: Wed, 15 Dec 2021 22:22:41 +0100 [thread overview]
Message-ID: <8ed85057-5ad8-1341-ba02-46bb15ee04bd@dustri.org> (raw)
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:
- https://bestpractical.com/request-tracker in Perl
- https://www.bugzilla.org/ no need to present it
- https://todo.sr.ht/~sircmpwn/todo.sr.ht 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 (
https://sourcehut.org/ ), 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
dustri.org
next reply other threads:[~2021-12-15 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 21:22 jvoisin [this message]
2021-12-15 22:52 ` Zach van Rijn
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:
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=8ed85057-5ad8-1341-ba02-46bb15ee04bd@dustri.org \
--to=julien.voisin@dustri.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).