From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from elastic.org (elastic.org [96.126.110.187]) by sourceware.org (Postfix) with ESMTPS id 73261385C41B for ; Tue, 30 Aug 2022 18:03:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 73261385C41B Authentication-Results: sourceware.org; dmarc=pass (p=quarantine dis=none) header.from=elastic.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=elastic.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=elastic.org ; s=default2; h=Content-Type:MIME-Version:Message-ID:Subject:Cc:To:From:Date: Sender:Reply-To:Content-Transfer-Encoding:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=0BeUIfPa6rUIU+4N2wussKFqdhnfXInV1jXlb91YrLE=; b=jX2AD2Rz3Rskk8c6Fmdi1HfQWd lT+Q28M3n9JUZz6s1wu6P+A1nG4FO6k4vMCQ/VocLzIysSB6r79lPlghbR1psKcQVb1YIjlWR+LS2 Fdw+GtD/QZYqu+/iAlsBfvEODvgQy/MX2YNpzWNrncQdUjm6EUEYShl9ATKQj3ieUBTPxDoAtSuwn MjZexvpaj5DmNsZT6ErO4Banpuhpby+Y4vLy6O0/l+8CmFxVQsjI8pe6SsaQ8qDmAMO1jx9nBr5nl 13V4EBrtfGACXRQ2T9eCeRzs6ScQxZwq/LyEHwOqiuw28wy97PC/nsKynIg6jlJbmzOZsN0NNlH4F WPyRZ7gg==; Received: from vpn-home.elastic.org ([10.0.0.2] helo=elastic.org) by elastic.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1oT5Zx-0006gR-2u; Tue, 30 Aug 2022 18:03:13 +0000 Received: from very.elastic.org ([192.168.1.1]) by elastic.org with esmtp (Exim 4.94.2) (envelope-from ) id 1oT5Zx-000Asg-Ar; Tue, 30 Aug 2022 14:03:13 -0400 Received: from fche by very.elastic.org with local (Exim 4.95) (envelope-from ) id 1oT5Zx-004DIb-9X; Tue, 30 Aug 2022 14:03:13 -0400 Date: Tue, 30 Aug 2022 14:03:13 -0400 From: "Frank Ch. Eigler" To: overseers@sourceware.org Cc: "Bradley M. Kuhn" , Daniel Pono Takamori Subject: proposing Sourceware as Software Freedom Conservancy member project Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Sender-Verification: "" X-Spam-Status: No, score=-98.8 required=5.0 tests=BAYES_50,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE,USER_IN_WELCOMELIST,USER_IN_WHITELIST autolearn=ham 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 overseers of the hosting server sourceware.org aka cygwin.org aka gcc.gnu.org aka (others *) invite the community to assist us in further securing the future of the service. Red Hat has been and continues to be a generous sponsor of the hardware, connectivity, and the very modest employee time it requires. We are glad to report there are zero indications of any change to this commitment. Things are stable, new services are coming online, and users seem to be happy. However, it is always good to think about any future needs. To protect confidence in the long term future of this hosting service, we have reached out to the Software Freedom Conservancy (SFC) to function as a "fiscal sponsor". For those who aren't familiar with it, the SFC is a registered US 501(c)(3) public-benefit charity, associated with dozens of major FOSS projects, including Buildbot, Inkscape, Git, Outreachy, QEMU and Xapian: https://sfconservancy.org/projects/current/ SFC takes open applications from FOSS communities and projects. Our application process has just begun. As a part of this effort, we contemplate no necessary technical change or disruption of any sort, including to operations, governance, or hosted project procedures or licensing. It would be solely a way to help future needs by providing routing for financial contributions, and have an official, charitable entity (with a real legal existence) for supporting sourceware.org. If accepted as a member project, sourceware.org would have access to this list of services from SFC, and possibly more: https://sfconservancy.org/projects/services/ This year, we set up a roadmap to improve the services for tracking and automation of email based patches and testing https://inbox.sourceware.org/overseers/YrLdfDWzq1T4k5xg@wildebeest.org/ This resulted in the launch of several new or updated services (builder.sourceware.org, patchwork.sourceware.org and inbox.sourceware.org). This didn't need any additional funds (except for the sourcehut mirror which costs $10 a month). We are proud to operate these services with minimal costs so we can sustain them both in good and in bad years. But that doesn't mean everything has to be done on a zero budget. Financial contributions are more than welcome so that if the need arises we can contract for some unusual admin stuff or additions to services like bugzilla, buildbot, patchwork, public-inbox or sourcehut. There are a few small-ticket items that we would dearly welcome community assistance with. This is just a draft of a draft, just to give you an idea of the scope. No gigaprojects, just community scale: helping each other out. That kind of low-budget efficiency seems to be a perfect match for SFC. - For helping future overseers come on board, we'd love someone's help to write refreshed SOP documentation about how things work and how to fix problems. - We could use more documentation for projects to help them come on board, operate their share of the infrastructure, and easily leave if they like. - We might need a new security review and more tooling to manage credentials and access. - We could use help further automating the management of the new buildbot system, and would love ever more build workers. - Some projects operate extra infrastructure services on sourceware that require occasional updates, which they would prefer to offload to someone else. These are only some ideas. We'd love yours. We can start tracking these on bugzilla, why not? https://sourceware.org/bugzilla/describecomponents.cgi?product=sourceware We would especially love to hear from people who are able to oversee and/or carry out this kind of work. If our application to the SFC succeeds, we need likeminded folks to help officially judge funding priorities. We promise the SFC application & committee work would be as low-stakes and informal as possible. Bradley and Daniel from the Conservancy have agreed to monitor this discussion and answer any questions about what the SFC can and cannot do to help us if we become an SFC member project. Sourceware has been operating since 1998. With your advice and help, we can keep hosting projects and their developers, comfortably and steadily, another few decades. https://sourceware.org/mission.html Chris Faylor Frank Eigler Mark Wielaard (others *): We are reaching out to the 20 most active projects on Sourceware (binutils, bunsen, bzip2, cgen, cygwin, debugedit, dwz, elfutils, gcc, gccrs, gdb, glibc, insight, kawa, libabigail, libffi, newlib, sid, systemtap, valgrind) about this proposal to make sure nobody is caught unaware. And Sourceware is also responsible for preserving the history of another 40 projects which are either less active, have been archived or moved on.