From: Christian Couder <christian.couder@gmail.com>
To: Taylor Blau <me@ttaylorr.com>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: Git / Software Freedom Conservancy status report (2024)
Date: Wed, 18 Sep 2024 15:07:54 +0200 [thread overview]
Message-ID: <CAP8UFD3K6BvWs0iriG3RQP_2yY7+bc59wdwdwz9S_VLOkmU7sg@mail.gmail.com> (raw)
In-Reply-To: <ZurNce+1IZ68WT+/@nand.local>
On Wed, Sep 18, 2024 at 2:54 PM Taylor Blau <me@ttaylorr.com> wrote:
> Last year we spent money ($675.96 USD) sponsoring Christian Couder to
> attend the Google Summer of Code (GSoC) 2024 Mentor Summit. According to
> my mails, Karthik Nayak also attended, but I haven't seen their expenses
> reflected in Conservancy's bookkeeping, so they may have not yet
> submitted their expenses for reimbursement.
Karthik didn't attend the GSoC Mentor Summit last year, but will
attend this year (October 4 to 6). Hariom Verma wanted to attend last
year but unfortunately he couldn't get a visa.
Also please note that the money spent to attend it is more than
covered by Google, as Google gives $500 for each mentored contributor
and also gives a generous amount for the mentors to travel to the
Mentor Summit ($1200 for me last year). It looks like those amounts
are not in the same accounting bucket though.
Anyway thanks for your great work on this report!
next parent reply other threads:[~2024-09-18 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZurNce+1IZ68WT+/@nand.local>
2024-09-18 13:07 ` Christian Couder [this message]
2024-09-18 13:16 ` Git / Software Freedom Conservancy status report (2024) Taylor Blau
2024-09-18 13:23 ` Christian Couder
2024-09-18 13:13 Taylor Blau
2024-09-18 20:00 ` 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=CAP8UFD3K6BvWs0iriG3RQP_2yY7+bc59wdwdwz9S_VLOkmU7sg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@ttaylorr.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).