From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
Daniel Pono Takamori <pono@sfconservancy.org>,
"Bradley M. Kuhn" <bkuhn@sfconservancy.org>
Subject: Re: proposing Sourceware as Software Freedom Conservancy member project
Date: Fri, 02 Sep 2022 13:47:57 +0200 [thread overview]
Message-ID: <70a52e50d49145e70db0361dc67dfb9ab48cf0af.camel@klomp.org> (raw)
In-Reply-To: <Yw5Q4b/2nqvAi3K4@elastic.org>
Hi,
On Tue, 2022-08-30 at 14:03 -0400, Frank Ch. Eigler via Overseers
wrote:
> 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.
So this generated almost 6000 emails about the proposal and even an lwn
news article: https://lwn.net/Articles/906502/
And normally you hit at least one troll when doing such a broad public
discussion (knock on wood) which is why I was a little hesitant when
the Conservancy requested we be very public about the application. But
all responses have been positive. I didn't even get any negative
personal emails about spamming so many people.
Also asking around in some of the irc channels of a few sourceware
projects people seemed positive about the application or at worst
neutral. No negative reactions at all.
So I believe people are generally happy with how overseers are handling
sourceware and people trust SFC to be a good fiscal sponsor for the
project.
Cheers,
Mark
next prev parent reply other threads:[~2022-09-02 11:47 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
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 [this message]
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=70a52e50d49145e70db0361dc67dfb9ab48cf0af.camel@klomp.org \
--to=mark@klomp.org \
--cc=bkuhn@sfconservancy.org \
--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).