From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from second.openwall.net (second.openwall.net [193.110.157.125]) by inbox.vuxu.org (Postfix) with SMTP id A60CC2162E for ; Fri, 26 Jan 2024 18:39:30 +0100 (CET) Received: (qmail 29960 invoked by uid 550); 26 Jan 2024 17:37:14 -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 26557 invoked from network); 26 Jan 2024 17:35:22 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=midipix.org; s=mail; t=1706289873; bh=0HhZFrjll9KMmye0DWhqS8cav9ZbI17yVmaWNfMko74=; h=Date:From:To:Subject:References:In-Reply-To; b=vMEHrXz4JV43kKMMPjKY8xKLeEwQRGqZaaY4tEbNPgoD662RyfIJQ+vEMQYMMO9DA HM94KydCHXkPKAKWWfD9LAegXcw/fy9AsxbkRGeCLnHiok/guABdWEug5nSE9441AL hiu053jxFphDQbHln2iVy1UJtSNrNeKE0V8TL4XG046pwyAqDlYf/Oqjpne+/BKhqe WlebEasprdWT8H96pOpsJSjkbOs/j2NFr3URKoWsFS+rWG8YM4vg7sKdnxKSxIyGnq SdhbWH4GBAIy7+73t7cs/8d0b3Vf+oUDfSNfdeodCGDBEziJ/Q8fGYTmMLuMrfCGeT D1jzoMtyFU+dQ== Date: Fri, 26 Jan 2024 17:24:33 +0000 From: "writeonce@midipix.org" To: musl@lists.openwall.com Message-ID: <20240126172433.ftcwgsfwsnu2f5xu@midipix.org> References: <8ed85057-5ad8-1341-ba02-46bb15ee04bd@dustri.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <8ed85057-5ad8-1341-ba02-46bb15ee04bd@dustri.org> Subject: Re: [musl] Current state and future of musl development infrastructure On 12/15/2021 22:22, jvoisin wrote: > 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, … Another great option would be Pagure (https://pagure.io/pagure), which has a nice interface for online issue tracking alongside smooth email integration. To get an idea of what a self-hosted Pagure instance might look like, see https://dev.midipix.org/ A template for setting up a pagure instance can be found under: - https://dev.midipix.org/hostcfg/culturestrings/blob/main/f/public/fs/etc/pagure > > 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 > --