From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 50B993858D34; Wed, 1 May 2024 21:26:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 50B993858D34 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 50B993858D34 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=45.83.234.184 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1714598781; cv=none; b=YFz8Wx/ZfNeIxf/Fg4ut+w6RXzfA63PzrcVijhOX8jJB5Oz2tLcPKDnReb7btQfF5qVxAWyslS64DFEteSxEp543iUDxTpcHRS4o5gXE9QaBS9fz/AGIiJl9EV9RAKne7IJDYs8JcEKXqMMEcwZn4VEtTKPq+o6Tg1eQTOhhr6c= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1714598781; c=relaxed/simple; bh=WzViJiij7BZJ19sPeuQWGn02k+usW3VITMr4TrsQms4=; h=Date:From:To:Subject:Message-ID:MIME-Version; b=MlX3fYihazbNl1NgpIL9IgnE0mbaom7fVGd0cYS5XlHWKhl2EydFdWVAi5IspPkpFzl3SNZvzKYBAaCr2NXNmTcjH70hda3Bjyhl9rCH8b1KzH/6L9uOJaoGBRDL0G4qxJh3jrPpS8Oh+ruGHuVkCXAvyYyr4EEHpY+GKHZc0Hw= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by gnu.wildebeest.org (Postfix, from userid 1000) id 5A6483000589; Wed, 1 May 2024 23:26:18 +0200 (CEST) Date: Wed, 1 May 2024 23:26:18 +0200 From: Mark Wielaard To: Jason Merrill Cc: Jeff Law , "Frank Ch. Eigler" , Overseers mailing list , Joseph Myers , gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org, libc-alpha@sourceware.org, Tom Tromey , Sergio Durigan Junior Subject: Re: Updated Sourceware infrastructure plans Message-ID: <20240501212618.GB6469@gnu.wildebeest.org> References: <20240417232725.GC25080@gnu.wildebeest.org> <20240418173726.GD9069@redhat.com> <87v849qudy.fsf@tromey.com> <87wmooep76.fsf@tromey.com> <0347e05a-94c6-4ecc-aa8f-cc90358a813d@gmail.com> <0d0af1d9-21f8-4c60-ad4c-cd82c0c0cabb@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <0d0af1d9-21f8-4c60-ad4c-cd82c0c0cabb@redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,KAM_SHORT,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Jason, On Wed, May 01, 2024 at 04:04:37PM -0400, Jason Merrill wrote: > On 5/1/24 12:15, Jeff Law wrote: > >We're currently using patchwork to track patches tagged with > >RISC-V.  We don't do much review with patchwork.  In that model > >patchwork ultimately just adds overhead as I'm constantly trying > >to figure out what patches have been integrated vs what are still > >outstanding. > > > >Patchwork definitely isn't the answer IMHO.  Nor is gitlab MRs > >which we use heavily internally.  But boy I want to get away from > >email and to a pull request kind of flow. > > Do you (or others) have any thoughts about GitLab FOSS? The gitlab "community edition" still feels not very much "community". We could run our own instance, but it will still be "open core" with features missing to try to draw you towards the proprietary hosted saas version. Also it seems to have way too much overhead. The focus is clearly corporate developers where managers want assurances the mandatory "pipelines" are executed and "workflows" followed exactly. For now I am cleaning up Sergio's gerrit setup and upgrading it to the latest version, so people can at least try it out. Although I must admit that I seem to be the only Sourcewware PLC member that believes this is very useful use of our resources. Even the biggest proponents of gerrit seem to believe no project will actually adopt it. And on irc there were some people really critical of the effort. It seems you either love or really hate gerrit... But the part that interests me most is the self-registration part that Sergio setup. I believe we will need that for whatever system we end up with to make it as easy to contribute as it is with email. https://blog.sergiodj.net/posts/installing-gerrit-and-keycloak/ My personal favorite, if we really want a full "forge" would be sourcehut. We already have mirrors of all projects at https://sr.ht/~sourceware/ and there is a kind of sample "workflow" (turning a "pull request" into an email thread) at https://gnu.wildebeest.org/~mark/fsf-sourceware/presentation.html#slide18 At the moment though the only thing people seem to agree on is that any system will be based on git. So the plan for now is to first setup a larger git(olite) system so that every contributor (also those who don't currently have commit access) can easily "post" their git repo. This can then hopefully integrate with the systems we already have setup (triggering builder CI, flag/match with patchwork/emails, etc.) or any future "pull request" like system. Cheers, Mark