git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: Dan Moore <dan@fusionauth.io>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] git-scm.com Heroku credits update
Date: Mon, 4 Apr 2022 19:09:08 -0400	[thread overview]
Message-ID: <Ykt6lPF0JC1Mg2Tx@nand.local> (raw)
In-Reply-To: <YkcmtqcFaO7v1jW5@nand.local>

On Fri, Apr 01, 2022 at 12:22:14PM -0400, Taylor Blau wrote:
> To that end, we have a few options about what to do with the website in
> the future:

Dan Moore (cc'd) has graciously offered the support of his company
FusionAuth [1] to help assist with our hosting costs. From Dan:

    [M]y company has benefited tremendously from git and would be happy
    to foot the monthly cost if you are looking for sponsors.

External support would go a long way towards keeping our existing funds
available for things like sponsoring travel and lodging for Git Merge
attendees who could not otherwise make it in person.

Dan: thank you very much for your gracious offer. Does anybody have
objections to having some external support? I think the only change to
the site would be adding an entry to the "Sponsors" section of the about
page [2].

Thanks,
Taylor

[1]: https://fusionauth.io/
[2]: https://git-scm.com/site

  reply	other threads:[~2022-04-04 23:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 16:22 [ANNOUNCE] git-scm.com Heroku credits update Taylor Blau
2022-04-04 23:09 ` Taylor Blau [this message]
     [not found]   ` <CAKUhyqE2L9MiNvauA6kaPstvNp6ift5ehfmeFxKvb2DjPvOnsA@mail.gmail.com>
2022-04-04 23:27     ` Dan Moore
2022-04-05  3:14   ` Kaartic Sivaraam
2022-04-06  9:52   ` Phillip Wood
2022-04-11 15:21   ` Taylor Blau
2022-04-18 23:43     ` Taylor Blau
2022-04-07 21:54 ` Johannes Schindelin
2022-04-08  8:10   ` Christian Couder
2022-04-08 18:12     ` Junio C Hamano
2022-04-11 15:18       ` Taylor Blau
2022-04-11 15:16   ` Taylor Blau

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=Ykt6lPF0JC1Mg2Tx@nand.local \
    --to=me@ttaylorr.com \
    --cc=dan@fusionauth.io \
    --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.
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).