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

Hi everyone,

On Tue, Jan 17, 2023 at 10:34 AM 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.

So Git has been accepted to participate in GSoC 2023.

I have recently received emails with "GSoC 2023: Be sure to add Org
Admins ASAP (and Mentors too!)" as a subject. Unfortunately despite
trying several times I haven't been able to do that. There have been
emails saying that a bug was fixed, but it seems to me that there are
several bugs left preventing us to do what we are asked to.

On Firefox I cannot even log into the website. On Chromium the "Add
member" drop down list doesn't show any member that I can add despite
the fact that many people are shows in

Today is supposed to be the deadline for each project to have at least
2 Org Admins for GSoC 2023, but it looks like I am the only one and
cannot add a second one because of the bugs.

I have emailed to get support and will see what happens.

Let me know if you have ideas about this.

> 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 still have time to add project ideas to and it's still possible for
(co-)mentors to volunteer. For example perhaps someone could co-mentor
the "More Sparse Index Integrations" project along with Victoria.

A project idea that was discussed in the past was about improving the
git-scm website and perhaps removing the Heroku dependency.


  parent reply	other threads:[~2023-03-09 10:21 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
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 [this message]
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).