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 328983858294 for ; Mon, 25 Mar 2024 10:08:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 328983858294 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 328983858294 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=1711361336; cv=none; b=Kz2xjBRSs+0IQN9V6ryn84aWDP8aIg5272+wPeKpPXvDUQQg27W6dSjXZ52OfXjrOYVB9TyN+ONtuPorgzUPFxm3IXjoAXtkQOFXs3fSN22pXZBXM4JvQTFcgsK6Fdxuj0V8GlqQ+bL8gwfQDXN4EYeUfmv41sizFUUqWylYABc= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1711361336; c=relaxed/simple; bh=PNP0LtDfq+sdoz3LoRbEkHCjn1zoEveKc+uuEVwClWE=; h=Date:From:To:Subject:Message-ID:MIME-Version; b=jes5r1dWIJauGbCO+oUMncmtaASPy9YSaW6d7a4MzMOxgQIloTv5SNvzb3spF6E5WHIkbkFiSSUpR+oNJdOKdOlPhpuq8TExnVvV1tXx11s7fHhU9H5ZYIt54uWBpOyZmd5LYLXNfRvKo/A9hr5BEOG70q+50yT+YTOTMSvykuI= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by gnu.wildebeest.org (Postfix, from userid 1000) id E9A56300046F; Mon, 25 Mar 2024 11:08:52 +0100 (CET) Date: Mon, 25 Mar 2024 11:08:52 +0100 From: Mark Wielaard To: gcc-rust@gcc.gnu.org Subject: Sourceware 2024 - The Plan Message-ID: <20240325100852.GP5673@gnu.wildebeest.org> Reply-To: overseers@sourceware.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,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: The Sourceware Project Leadership Committee in discussion with the Software Freedom Conservancy staff came up with the Sourceware 2024 plan and is looking at longer term projects that would be needed to keep your infrastructure running smoothly and securely for the next couple of years. We are currently discussing how to distribute these tasks over paid staff, overseers, project admin volunteers and contractors. We realize that our plans may not be your plans, so really like to get feedback. It is our goal to offer a worry-free, friendly home for Free Software core toolchain and developer tools projects. So please do reach out and share your ideas on the overseers mailinglist, file infrastructure bugs, join our channel #overseers on irc or join one of the monthly open office hours: https://sourceware.org/mission.html#organization For 2024 we want to concentrate on isolating and scaling the services. In the last two years we doubled the number of machines (and more are on the way!) that we run the services on. And some of the new services are already setup in containers or on isolated VMs. But most of the services are still isolated through traditional unix mechanisms. Moving those into their own container or VM will help scaling by making it easy to move between separate physical machines. It will also provide security in depth. It is our preference to run distro packaged software (e.g. mailman, postfix, public-inbox, etc.). That way we have easy security updates. But for some services we track an upstream stable branch (e.g. buildbot, patchwork and bugzilla). While isolating/containerizing these services we will also publish the internal git repos (if they contain any local adjustments), so we can easier share patches with other organizations. Ideally we'll also publish ansible playbooks. That way, over time, we will provide services that anybody can replicate and setup themselves. Longer term we identified a couple of thing, mainly around isolation (the theme of 2024), email, spam, mailinglists, search, AI bots and services upgrades that we believe are important to prepare for. Concretely we are looking at: - mailman2 upgrade/replacement https://sourceware.org/bugzilla/show_bug.cgi?id=31545 - bugzilla upgrade https://sourceware.org/bugzilla/show_bug.cgi?id=31547 - (local) search and AI bot/spiders, sitemaps, ... https://sourceware.org/bugzilla/show_bug.cgi?id=31551 https://sourceware.org/bugzilla/show_bug.cgi?id=31548 https://sourceware.org/bugzilla/show_bug.cgi?id=30610 https://sourceware.org/bugzilla/show_bug.cgi?id=31549 - Distributed spam fighting https://sourceware.org/bugzilla/show_bug.cgi?id=31550 - buildbot email templates, pre-commit testing, buildbot-travis, ... https://sourceware.org/bugzilla/show_bug.cgi?id=31552 More items can be found in the Sourceware infrastructure bugzilla https://sourceware.org/bugzilla/buglist.cgi?component=Infrastructure&product=sourceware&resolution=--- If you read this far we really like your feedback, even if it is a simple "OK!", Reply-To: overseers@sourceware.org Or add you comments to the bugzilla items above. And take a look at other ways to participate https://sourceware.org/mission.html#organization You can also help by becoming a Conservancy Sustainer https://sfconservancy.org/sustainer/ or donating directly to Sourceware https://sourceware.org/donate.html Thanks, Frank Ch. Eigler, Christopher Faylor, Ian Kelling, Ian Lance Taylor, Tom Tromey, Jon Turney, Mark J. Wielaard, Elena Zannoni