mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <>
To: Kaartic Sivaraam <>
Cc: git <>, Derrick Stolee <>,
	Victoria Dye <>,
	Hariom verma <>
Subject: Re: GSoC 2023
Date: Tue, 24 Jan 2023 17:38:31 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


On Mon, Jan 23, 2023 at 6:41 PM Kaartic Sivaraam
<> wrote:
> On 17/01/23 15:04, Christian Couder wrote:
> >
> > GSoC Org Applications open next week on Monday, January 23rd at 1800
> > UTC and close on Tuesday, February 7th at 1800 UTC.
> >
> > I am interested in mentoring and being an org admin for Git again this
> > year, so I plan to apply for Git soon.
> I would be glad to help as an Org admin this year. I don't suppose I
> have the capacity to mentor / co-mentor this year, though. I could very
> well help as much as I can passively where needed.

You are welcome to be an Org Admin, thanks!

Actually you were already an Org Admin last year and it looks like
they didn't remove people from the roles they had last year, so you
are still an Org Admin.

> One thing to note about the Org application. As per Google's claim we
> should be able to complete this year's application quickly since the new
> webapp allows us to reuse last year's application details.

Yeah, I just did it and reusing last year's application details was
quite quick. One needs to read, agree on and accept 3 long documents,
and they still ask a few questions about last year's GSoC though.

They also want an URL with an idea list, so I quickly copied and
edited last year's idea list into this one:

I removed the "Reachability bitmap improvements" idea but left the 2 others:

  - More Sparse Index Integrations (I removed `git mv` in the list of
commands that need to be improved though)
  - Unify ref-filter formats with other pretty formats

On both of them I removed all possible mentors except me though. They
are welcome to tell me that they should be added back.

> We certainly are in need of ideas and mentors for this year. Do chime in
> with your thoughts. :-)

Yeah, sure.

  reply	other threads:[~2023-01-24 16:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17  9:34 GSoC 2023 Christian Couder
2023-01-23 17:41 ` Kaartic Sivaraam
2023-01-24 16:38   ` Christian Couder [this message]
2023-01-24 19:18     ` Taylor Blau
2023-02-05 19:50     ` Hariom verma
2023-02-06 17:44       ` Kaartic Sivaraam
2023-02-07 11:58         ` Christian Couder
2023-02-06 16:58     ` Victoria Dye
2023-02-06 17:48       ` Kaartic Sivaraam
2023-02-07 21:04         ` Taylor Blau
2023-03-09 10:17 ` Christian Couder
2023-03-09 17:19   ` Kaartic Sivaraam
2023-03-09 18:45     ` Hariom verma
2023-03-10  0:56       ` Kaartic Sivaraam
2023-03-10 12:38     ` Christian Couder

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \

* 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

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).