public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: "Karen M. Sandler" <karen@sfconservancy.org>
Cc: Daniel Pono Takamori <pono@sfconservancy.org>,
	Overseers mailing list <overseers@sourceware.org>,
	"Jose E. Marchesi" <jemarch@gnu.org>,
	"Bradley M. Kuhn" <bkuhn@sfconservancy.org>
Subject: Re: Proposing Sourceware as SFC member project
Date: Sat, 3 Sep 2022 18:38:21 +0200	[thread overview]
Message-ID: <YxOC/QbvTulJqp6G@wildebeest.org> (raw)
In-Reply-To: <ecdcb1c5f585ed7cc33327fd7a4441b3@sfconservancy.org>

Hi Karen,

On Sat, Sep 03, 2022 at 10:07:29AM -0400, Karen M. Sandler wrote:
> I and my staff will be monitoring this thread to answer questions on SFC's
> behalf, and presume that LF folks will do the same. We look forward to the
> discussion, particularly because we love discussion of the different ways
> that organizations accomplish fiscal sponsorship, and part of our mission is
> educating the FOSS community about non-profit governance options. And
> perhaps an entirely different approach might emerge from multiple
> organizations working together that hasn't even been thought of yet.
> 
> In any case, I'm excited to see the future for this important free software
> hosting project!

Thanks so much for your guidance and excitement. It is great seeing
the non-profit organizations working together so well. That is
especially important for a free software hosting project like
Sourceware because we host both little and big projects. Some with
their own fiscal sponsor, some without any funding at all. Being able
to share non-profit organisation resources and services is a great
thing to look forward to.

Thanks,

Mark

  reply	other threads:[~2022-09-03 16:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Yw5aTCLyYx8qqN3W@wildebeest.org>
2022-08-31 22:19 ` Jose E. Marchesi
2022-09-01  8:28   ` Mark Wielaard
2022-09-02 18:51     ` Daniel Pono Takamori
2022-09-03 14:07       ` Karen M. Sandler
2022-09-03 16:38         ` Mark Wielaard [this message]
2022-09-18 19:42         ` Moving sourceware to the Linux Foundation? No thanks Christopher Faylor
2022-09-25 22:31           ` Mark Wielaard
2022-09-26 14:07             ` Ian Lance Taylor
2022-09-26 17:05               ` Christopher Faylor
2022-09-26 19:57               ` Frank Ch. Eigler
2022-09-27 13:03                 ` Carlos O'Donell
2022-09-28  8:53                   ` Ian Kelling
2022-10-02 21:15                     ` Mark Wielaard
2022-09-28  8:33                 ` Ian Kelling
2022-09-28 10:08                   ` Frank Ch. Eigler
2022-09-26 21:53               ` Moving sourceware into the future Mark Wielaard
2022-09-27 17:12                 ` Daniel Pono Takamori
2022-09-26 22:21             ` Moving sourceware to the Linux Foundation? No thanks Carlos O'Donell
     [not found] <Yw5btfOsg6EJRvsM@wildebeest.org>
2022-09-05 15:51 ` Proposing Sourceware as SFC member project Thomas Fitzsimmons

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=YxOC/QbvTulJqp6G@wildebeest.org \
    --to=mark@klomp.org \
    --cc=bkuhn@sfconservancy.org \
    --cc=jemarch@gnu.org \
    --cc=karen@sfconservancy.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).