From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Pls Support Conservancy: https://sfconservancy.org/supporter/
Date: Tue, 22 Dec 2015 08:02:25 -0800 [thread overview]
Message-ID: <xmqqpoxyeajy.fsf@gitster.mtv.corp.google.com> (raw)
[Jeff King, Shawn Pearce and myself represent the Git project to the
Conservancy, and here is a request for help from us.]
We apologize that we're interrupting the usual content on this
mailing list with a fundraising message, but the non-profit home of
the Git project, Software Freedom Conservancy, is in urgent need of
your immediate support: https://sfconservancy.org/supporter/
Git receives a myriad of important services (see
https://sfconservancy.org/members/services/ ) from Conservancy. We
have relied on Conservancy since 2009 to provide them, and we ask
that you support them. While Git gladly contributes 10% of our
project's gross revenue to Conservancy's general fund, (while
Conservancy maintains and administers the other 90% in collaboration
with us to advance the Git project), that 10% of contributions from
all Conservancy's member projects doesn't add up to enough to even
employ one full time person, let alone the already overworked staff
of three that Conservancy has.
Conservancy's fundraiser, found at https://sfconservancy.org/supporter/
, is centered around asking individuals who care about the work that
Conservancy does to donate $120/year, or just $10/month, to support the
organization. Conservancy seeks about 2,500 Supporters to continue its
current work, and 750 Supporters to continue a "bare minimum" of
services to its projects.
Here are some of the things that Conservancy does for Git that are in
the "bare minimum" category:
* Handle our Google Summer of Code payments and travel, including
handling all financial transactions with Google to receive and then
disperse the money.
* Coordinating travel reimbursements for Git contributors to attend
conferences.
* Buying and shipping hardware to Git volunteer contributors who need
it.
* Keeping the non-profit status for us so that we don't have to form
our own org and file our own paperwork.
Here are some of the services Git has received in the wider category:
* Dealing with questions from the community about the DCO and legal
issues surrounding contributions to the Git project.
* Discussing the issue of copyright governance and contributions with
large corporations who want their employees to contribute to Git
but need legal assurances or have questions relating to Git's
license or contribution policies.
* Helping us write the Git trademark policy:
https://git-scm.com/trademark , registering the trademark, and
enforcing the trademark when we need it. This assures Git users can
know that when they see something called "Git", it relates to the Git
project in some way.
* And, in fact, we do very occasionally find companies violating the
GPL on Git, and Conservancy has helped us out with that.
As you can see, Git really relies on the important work of Conservancy,
and thus the Git project leadership encourages you to choose Conservancy
as one of your charitable gifts this holiday season. (Conservancy is a
501(c)(3) charity incorporated in New York, and donations are typically
deductible on U.S. taxes.)
Please visit: https://sfconservancy.org/supporter/
next reply other threads:[~2015-12-22 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 16:02 Junio C Hamano [this message]
2015-12-24 20:56 ` Pls Support Conservancy: https://sfconservancy.org/supporter/ David Turner
2016-01-17 6:08 ` Michael Haggerty
2016-01-17 15:33 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqpoxyeajy.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).