mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kaartic Sivaraam <>
To: Christian Couder <>
Cc: git <>
Subject: Re: GSoC 2023
Date: Mon, 23 Jan 2023 23:11:13 +0530	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Christian,

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.

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. To quote Google,

   If your org applied to GSoC in 2022 your Org Admin will have a very
   quick and easy 2023 application. : ) As mentioned last year, the
   webapp is now evergreen so if your org applied in 2022 all of the
   information for the org application is still in the system so the Org
   Admin will have a couple of quick steps to follow during the
   application window.

Do feel free to let me know if it works otherwise, Christian. I'll be 
glad to look into it.

> The GSoC contributor application deadline is April 4 - 18:00 UTC, so
> (co-)mentors and org admins are already welcome to volunteer. We also
> need project ideas to refresh our idea page from last year
> (

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


  reply	other threads:[~2023-01-23 17:41 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 [this message]
2023-01-24 16:38   ` Christian Couder
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 \ \ \ \ \

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