From: David Edelsohn <dje.gcc@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: GCC Development <gcc@gcc.gnu.org>,
"gdb@sourceware.org" <gdb@sourceware.org>,
Binutils Development <binutils@sourceware.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: GNU Toolchain Fund established at the Free Software Foundation
Date: Fri, 10 Mar 2017 02:08:00 -0000 [thread overview]
Message-ID: <CAGWvnymsMOMWUv80X=Ftgj4U61rfhVVwWjnW9KRn8SX_ARXxOA@mail.gmail.com> (raw)
In-Reply-To: <CAKOQZ8yT+vuoBwXLSZQg0DtqDBp_5USy0pknYdcfaORpYPbV2g@mail.gmail.com>
On Thu, Mar 9, 2017 at 8:48 PM, Ian Lance Taylor <iant@google.com> wrote:
> On Thu, Mar 9, 2017 at 11:49 AM, David Edelsohn <dje.gcc@gmail.com> wrote:
>> A fund to benefit the components of the GNU Toolchain (GCC, GDB,
>> GLIBC, Binutils, Sourceware) has been established at the Free Software
>> Foundation.
>>
>> Personal and corporate donations are welcome!
>>
>> http://www.fsf.org/news/gnu-toolchain-now-accepting-donations-with-the-support-of-the-free-software-foundation
>
> That is great news. Thanks.
>
> Is the membership of the committee who will oversee the funds public?
The Trustees are Carlos O'Donell, Joel Broebecker and me. Carlos,
Joel and I have no interest in active fundraising, soliciting
proposals, debating or voting on how to spend the money. The GNU
Toolchain community and project leadership can decide on projects and
we will direct the FSF to distribute the funds.
As discussed at the last Cauldron, the first interest of the community
seems to be the shared infrastructure of Sourceware: hosting, system
administration, backups, and updating the websites.
Thanks, David
next prev parent reply other threads:[~2017-03-10 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 19:49 David Edelsohn
2017-03-10 1:49 ` Ian Lance Taylor via gdb
2017-03-10 2:08 ` David Edelsohn [this message]
2017-03-10 9:37 ` Jim Wilson
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='CAGWvnymsMOMWUv80X=Ftgj4U61rfhVVwWjnW9KRn8SX_ARXxOA@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=iant@google.com \
--cc=libc-alpha@sourceware.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