public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>,
	"Frank Ch. Eigler" <fche@elastic.org>
Cc: Elena Zannoni <ezannoni@gmail.com>,
	Daniel Pono Takamori <pono@sfconservancy.org>
Subject: Re: proposing Sourceware as Software Freedom Conservancy member project
Date: Fri, 02 Sep 2022 12:14:57 +0200	[thread overview]
Message-ID: <f635ab8dcada4f1258dddd8ff8efdda5392a571b.camel@klomp.org> (raw)
In-Reply-To: <5a2807ae-5807-9791-7db9-b43b04837de5@gmail.com>

Hi Elena,

On Thu, 2022-09-01 at 08:19 -0600, Elena Zannoni via Overseers wrote:
> Hi folks, good to see this effort.
> 
> 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.
> 
> 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:
> 
> 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
> 
> 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.
> 
> 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

  parent reply	other threads:[~2022-09-02 10:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 18:03 Frank Ch. Eigler
2022-09-01 14:19 ` Elena Zannoni
2022-09-01 18:10   ` Christopher Faylor
2022-09-02 10:14   ` Mark Wielaard [this message]
2022-09-01 18:45 ` Corinna Vinschen
2022-09-01 18:54   ` Frank Ch. Eigler
2022-09-02 10:51   ` Mark Wielaard
2022-09-02 11:47 ` Mark Wielaard
2022-09-05 12:20 ` Dodji Seketeli
2022-09-08 19:16 ` SFC offers project membership to Sourceware; three video-chat discussion times with SFC available Daniel Pono Takamori
2022-09-09 14:55   ` Karen M. Sandler
2022-09-10 17:55     ` Karen M. Sandler
2022-09-10 22:32       ` SFC video-chat discussion meeting notes Mark Wielaard
2022-09-12 16:34         ` Daniel Pono Takamori
2022-09-12 17:05           ` Daniel Pono Takamori
2022-09-12 19:09             ` Daniel Pono Takamori
2022-09-01 19:18 proposing Sourceware as Software Freedom Conservancy member project Marc
2022-09-01 19:47 ` Frank Ch. Eigler
2022-09-01 20:47   ` Christopher Faylor
2022-09-02 11:10   ` Mark Wielaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f635ab8dcada4f1258dddd8ff8efdda5392a571b.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=ezannoni@gmail.com \
    --cc=fche@elastic.org \
    --cc=overseers@sourceware.org \
    --cc=pono@sfconservancy.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).