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 EFF5D3858C54 for ; Fri, 2 Sep 2022 10:15:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org EFF5D3858C54 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 887D0302AB2C; Fri, 2 Sep 2022 12:14:58 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 8B3F3403DCA4; Fri, 2 Sep 2022 12:14:57 +0200 (CEST) Message-ID: Subject: Re: proposing Sourceware as Software Freedom Conservancy member project From: Mark Wielaard To: Overseers mailing list , "Frank Ch. Eigler" Cc: Elena Zannoni , Daniel Pono Takamori Date: Fri, 02 Sep 2022 12:14:57 +0200 In-Reply-To: <5a2807ae-5807-9791-7db9-b43b04837de5@gmail.com> References: <5a2807ae-5807-9791-7db9-b43b04837de5@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE 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 Elena, On Thu, 2022-09-01 at 08:19 -0600, Elena Zannoni via Overseers wrote: > Hi folks, good to see this effort. >=20 > As one of the old timers that was there at the initial setup of the > public repos in 1998, I first of all want to thank you for keeping > this effort going smoothly for such a long time. >=20 > My team uses sourceware services every day and we wouldn't be able to > do so without your dedication. Thanks. > The announcements of latest improvements and updates and the roadmap > itself have not been seen by many people I am afraid, so I think it's > worth to point to them here: >=20 > https://sourceware.org/pipermail/overseers/2022q2/018453.html > https://sourceware.org/pipermail/overseers/2022q2/018529.html > https://sourceware.org/pipermail/overseers/2022q3/018636.html > https://sourceware.org/pipermail/overseers/2022q3/018716.html >=20 > Would it be worth to put them in the News section of sourceware.org? > Maybe also post the roadmap on a page on sourceware.org? Thanks for noticing. And yeah, maybe we aren't selling our services enough. But if we would need to then it would also probably mean the services aren't zero-maintenance (for the projects). And we really don't want to oversell. Ideally the services just keep on improving without anybody needing to care. I did just add the services from the roadmap which are more or less ready builder.sourceware.org, patchwork.sourceware.org and inbox.sourceware.org to the homepage so people can find them easily. We were actually talking about changing the homepage to be all about the projects hosted on sourceware instead of sourceware itself. So you would easily find news, mailinglists, repos and activity for each one. > It is good to see this effort to regularize the responsibilities for > Sourceware a bit more. I agree that a fiscal sponsor is a good thing to > have and the SFC seems like a good home. Hopefully the governance can be > maintained as light as possible, and hopefully it will be neutral, > having the best interest of the developer communities in mind. >=20 > I do not believe that Sourceware is broken as it is today, but > establishing a more solid structure will help to maintain it healthy for > many more years to come. That is certainly the intention! Thanks for your feedback, Mark