From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Christian Couder <christian.couder@gmail.com>,
Patrick Steinhardt <ps@pks.im>,
Karthik Nayak <karthik.188@gmail.com>, git <git@vger.kernel.org>
Cc: Taylor Blau <me@ttaylorr.com>, Junio C Hamano <gitster@pobox.com>,
Victoria Dye <vdye@github.com>
Subject: Re: Git in GSoC 2024
Date: Thu, 22 Feb 2024 10:01:54 +0530 [thread overview]
Message-ID: <9cec06d8-971b-4c5d-9d85-969021b0dd48@gmail.com> (raw)
In-Reply-To: <CA+ARAtqicQkhKFcTxoT+GWMhCxnV-BNqd0oOcn2YwznfFnnRPw@mail.gmail.com>
Hi Christian, Patrick, Karthik and all,
On 21/02/24 10:32, Kaartic Sivaraam wrote:
>
> Christian, could you do the following so that I could add you as an Org
> Admin for the 2024 program?
>
> "Visit https://g.co/gsoc site, click on the 2024 bar which will display
> the 2024 Program Rules and Org Member agreement, read and agree to the
> same."
>
> For mentors, as Patrick and Karthik are new to the program, we need to
> invite them first and only after they've accepted the invitation can we
> add them to the program.
>
> Karthik, I was able to get your Gmail address and have sent an invite to
> you. Could you accept the same after reading through the program rules
> and member agreement?
>
> Patrick, could you kindly share with me your Gmail address so that I could
> invite you to the program?
>
Thanks for the quick turnaround all! I've added all of you to the 2024
program. I hope you're able to access the program page at [1]. Let me
know if you're facing any issues.
Also, it's official now. Git has been selected as one of the
participating organizations[2] in GSoC 2024!
Let's look forward towards a summer with great GSoC contributors who
hopefully become continued contributors to the community :-)
[[ References ]]
[1]:
https://summerofcode.withgoogle.com/organizations/git/programs/2024/timeline
[2]: https://summerofcode.withgoogle.com/programs/2024/organizations/git
--
Sivaraam
next prev parent reply other threads:[~2024-02-22 4:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 18:16 Git in GSoC 2024 Kaartic Sivaraam
2024-01-30 8:38 ` Christian Couder
2024-01-30 9:08 ` Patrick Steinhardt
2024-01-31 13:10 ` Patrick Steinhardt
2024-01-31 17:57 ` Kaartic Sivaraam
2024-01-31 18:03 ` Kaartic Sivaraam
2024-02-01 9:00 ` Karthik Nayak
2024-02-01 9:38 ` Patrick Steinhardt
2024-02-03 11:41 ` Kaartic Sivaraam
2024-02-04 14:29 ` Kaartic Sivaraam
2024-02-05 8:39 ` [PATCH] Add ideas for " Patrick Steinhardt
2024-02-05 16:43 ` Christian Couder
2024-02-05 18:55 ` Kaartic Sivaraam
2024-02-06 5:51 ` Patrick Steinhardt
2024-02-06 8:13 ` Christian Couder
2024-02-08 14:02 ` Kaartic Sivaraam
2024-02-09 6:27 ` Patrick Steinhardt
2024-02-09 8:36 ` Christian Couder
2024-02-06 5:47 ` Patrick Steinhardt
2024-02-06 8:26 ` Christian Couder
2024-02-05 17:07 ` Git in " Christian Couder
2024-02-05 18:39 ` Kaartic Sivaraam
2024-02-21 5:02 ` Kaartic Sivaraam
2024-02-21 6:19 ` Patrick Steinhardt
2024-02-21 8:43 ` Christian Couder
2024-02-21 8:59 ` Karthik Nayak
2024-02-22 4:31 ` Kaartic Sivaraam [this message]
2024-02-22 7:49 ` Patrick Steinhardt
2024-02-22 8:57 ` Karthik Nayak
2024-02-22 12:02 ` Christian Couder
2024-02-22 14:05 ` Kaartic Sivaraam
2024-02-22 15:52 ` Patrick Steinhardt
2024-02-24 17:34 ` Kaartic Sivaraam
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=9cec06d8-971b-4c5d-9d85-969021b0dd48@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@gmail.com \
--cc=me@ttaylorr.com \
--cc=ps@pks.im \
--cc=vdye@github.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).