From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 25347 invoked from network); 15 Dec 2021 21:22:56 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 15 Dec 2021 21:22:56 -0000 Received: (qmail 21627 invoked by uid 550); 15 Dec 2021 21:22:54 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 21590 invoked from network); 15 Dec 2021 21:22:53 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dustri.org; s=gm1; t=1639603362; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=ClZVlrsdaCyQ5SEyAWeZn4NTWN8hG2an7r39KRSc4zE=; b=WFjiwgaT9NL6npuMGt23KK7tFmRb1TxdACPkLa1l8PXz01+qwj/QJ2Dt/56Tq7KxVykycK 2bgQ7LDgjgSqdORZfYzx0wNPpPOmqMOaLyTRutCYQrKTqaFPaaz07ntcxHUrLLhNzEXr80 +8FEvJGVR/bvt3tDYpESdTJA/ePnUliNw/JQNKDeUd1CpEHHBRok87V/fMhE+oKdTgkNrc oYH/sG+2AyZ3yP6C2phEJPGpkIQrFXRaT5/bibrnvQqMPoYoGQAdkNdT2+HD9LwIg/iT70 2bkDJwWEjH9wfl7flXtLOS2LPDUYXJnRtMzs9QMSn0DxUt3ppO/3FBb/hm4phw== To: musl@lists.openwall.com From: jvoisin Message-ID: <8ed85057-5ad8-1341-ba02-46bb15ee04bd@dustri.org> Date: Wed, 15 Dec 2021 22:22:41 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: [musl] 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: - 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