From: Christian Couder <christian.couder@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Git Community <git@vger.kernel.org>,
Philip Oakley <philipoakley@iee.email>,
Junio C Hamano <gitster@pobox.com>, Taylor Blau <me@ttaylorr.com>,
Emily Shaffer <emilyshaffer@google.com>,
Atharva Raykar <raykar.ath@gmail.com>,
ZheNing Hu <adlternative@gmail.com>,
Derrick Stolee <stolee@gmail.com>, Victoria Dye <vdye@github.com>
Subject: Re: Git in GSoC 2022?
Date: Wed, 16 Feb 2022 16:55:30 +0100 [thread overview]
Message-ID: <CAP8UFD3prsevU_8zCXQu_BpZH+NHm+HD04RiBvOXkZkDoi+yjg@mail.gmail.com> (raw)
In-Reply-To: <65abccbe-eaae-5d68-c738-b7f9a3844bbc@gmail.com>
On Tue, Feb 15, 2022 at 9:32 PM Kaartic Sivaraam
<kaartic.sivaraam@gmail.com> wrote:
>
> On 13/02/22 3:03 pm, Christian Couder wrote:
> > On Sat, Feb 12, 2022 at 7:12 PM Kaartic Sivaraam
> > <kaartic.sivaraam@gmail.com> wrote:
> >
> >> On a related note, the organization registrations are now open for this year.
> >> The deadline is February 21 - 18:00 UTC. I'm not sure if anyone else is
> >> planning on applying for Git. In case no one else beats me to it, I plan on
> >> applying for Git around February 15 17:00 UTC.
> >
> > I was thinking about applying for Git, but I am glad that you plan to
> > do it. I will try to add some project ideas to SoC-2022-Ideas.md
> > before February 15.
>
> Thanks for adding it! I've applied for Git in GSoC 2022. The application
> information could be found here:
>
> https://git.github.io/SoC-2022-Org-Application/
Thanks for applying!
> Let me know in case anything needs to be tweaked. I mentioned that we have
> 5 mentors available counting Stolee, Victoria, Christian, Taylor and myself.
> Also, I've invited Christian as an Org Admin. In case anyone else would like
> to volunteer to be an Org Admin, do let me know.
Thanks, I accepted the invite!
Not sure we can invite possible mentors yet.
> On a lighter note, the application structure was a bit different than
> previous years due to the new website. They say that it supports persisting
> the organization information which should mean less work while applying for
> GSoC in upcoming years.
Nice!
next prev parent reply other threads:[~2022-02-16 15:55 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 18:29 Git in GSoC 2022? Kaartic Sivaraam
2022-01-26 20:05 ` Taylor Blau
2022-01-27 9:32 ` Christian Couder
2022-01-29 18:09 ` Kaartic Sivaraam
2022-02-13 13:35 ` Christian Couder
2022-02-15 20:34 ` Kaartic Sivaraam
2022-02-15 23:18 ` Hariom verma
2022-02-16 15:40 ` Christian Couder
2022-02-17 15:07 ` Hariom verma
2022-02-17 17:18 ` Kaartic Sivaraam
2022-02-18 2:14 ` Hariom verma
2022-02-26 20:29 ` Kaartic Sivaraam
2022-02-28 11:03 ` Christian Couder
2022-02-28 18:02 ` Kaartic Sivaraam
2022-03-01 13:51 ` Christian Couder
2022-03-04 18:34 ` Kaartic Sivaraam
2022-01-27 3:55 ` Bagas Sanjaya
2022-01-27 9:44 ` Christian Couder
[not found] ` <nycvar.QRO.7.76.6.2201281114440.347@tvgsbejvaqbjf.bet>
2022-01-29 18:36 ` Kaartic Sivaraam
2022-03-09 11:49 ` Johannes Schindelin
2022-03-09 19:57 ` Kaartic Sivaraam
2022-01-27 14:39 ` Derrick Stolee
2022-01-29 18:19 ` Kaartic Sivaraam
2022-02-02 17:42 ` Derrick Stolee
2022-01-27 15:00 ` ZheNing Hu
2022-01-29 17:43 ` Kaartic Sivaraam
2022-02-03 14:12 ` Philip Oakley
2022-02-12 18:12 ` Kaartic Sivaraam
2022-02-13 9:33 ` Christian Couder
2022-02-15 15:05 ` Philip Oakley
2022-02-15 20:32 ` Kaartic Sivaraam
2022-02-16 15:55 ` Christian Couder [this message]
2022-02-17 17:28 ` Kaartic Sivaraam
2022-03-07 19:38 ` Kaartic Sivaraam
2022-03-07 19:50 ` Derrick Stolee
2022-03-07 22:25 ` Hariom verma
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=CAP8UFD3prsevU_8zCXQu_BpZH+NHm+HD04RiBvOXkZkDoi+yjg@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=adlternative@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=me@ttaylorr.com \
--cc=philipoakley@iee.email \
--cc=raykar.ath@gmail.com \
--cc=stolee@gmail.com \
--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.
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).