git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: git@vger.kernel.org
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Christian Couder" <christian.couder@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Dan Moore" <dan@fusionauth.io>
Subject: [ANNOUNCE] git-scm.com updates (was: Conservancy status report (2023))
Date: Wed, 10 Jan 2024 14:43:55 -0500	[thread overview]
Message-ID: <ZZ7zezSRZfdklS4u@nand.local> (raw)
In-Reply-To: <ZRHTWaPthX/TETJz@nand.local>

On Mon, Sep 25, 2023 at 02:37:13PM -0400, Taylor Blau wrote:
> One notable change from last time is that our hosting fees have gone up
> significantly. These are entirely from Heroku's change in policy to no
> longer grant the Git project hosting credits for the git-scm.com
> project. Our costs in the meantime have been supported by a generous
> donation from Dan Moore at FusionAuth. The below email has some more
> details:
>
>   https://lore.kernel.org/git/YkcmtqcFaO7v1jW5@nand.local/
>
> It appears that since the above was written, Heroku has a new (?)
> program for giving credits to open-source projects. The details are
> below:
>
>   https://www.heroku.com/open-source-credit-program
>
> I applied on behalf of the Git project on 2023-09-25, and will follow-up
> on the list if/when we hear back from them.

Out of the blue today I received an email from Heroku saying that our
application to their open-source credit program was accepted. Quoting
from their email:

  [...] We are excited to announce that your project was a fit to
  receive $250 credits/month for one year, totaling $3,000 in credits.
  These credits have been applied to the account submitted on the
  application, and will be valid from January 2024 to December 2024.

$250 per month is more than enough to cover our hosting costs (which
average around ~$140 USD per month), so we should have plenty of room to
host git-scm.com free of charge for this year.

I know that there are some plans in the works to convert git-scm.com to
a static site in [1]. So even though we likely won't be on Heroku
forever, this should tide us over until we're ready to move to GitHub
Pages.

I would like to thank Dan Moore for his generous donation to the Git
project, which has covered our Heroku bill in past years. Now that
Heroku has agreed to cover out costs for this year, we will be able to
use the funds Dan has graciously provided to on behalf of FusionAuth for
other purposes.

Thanks,
Taylor

[1]: https://github.com/git/git-scm.com/pull/1804

      reply	other threads:[~2024-01-10 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 18:37 Git / Software Freedom Conservancy status report (2023) Taylor Blau
2024-01-10 19:43 ` Taylor Blau [this message]

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=ZZ7zezSRZfdklS4u@nand.local \
    --to=me@ttaylorr.com \
    --cc=avarab@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=dan@fusionauth.io \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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 NNTP newsgroup(s).