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

Hi Christian,

On 9 March 2023 3:47:51 pm IST, Christian Couder <> wrote:
>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 suppose you should now see me as an Org admin for the 2023 program.

I thought I was already in as an Org Admin but I somehow have missed completing the process. Sorry about that.

>I have emailed to get support and will see what happens.
>Let me know if you have ideas about this.

The thing is potential mentors need to login to the GSoC portal and accept org member agreement and program rules. After you (or any Org Admin) should be able to add that person to the program. Here's the relevant snippet from Google's mail:

-- 8< --
Trying to invite Mentor and Org Admins from GSoC 2022 to the GSoC 2023 program?

If a person was a Mentor or Org Admin for your org in 2022 then they just need to log in to and click on the 2023 bar which will show them the 2023 Program Rules and Org Member agreement that they need to read and agree to. Once they have done that they will appear in the Org Admin's dropdown of folks to add to the 2023 program.

-- >8 --

Hope this helps.

Victoria and Hariom,

Do kindly log into the portal and complete the process and let us know. Once that's done, we'll add you as mentors to the 2023 GSoC program.


Sent from my Android device with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2023-03-09 17:20 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
2023-03-09 17:19   ` Kaartic Sivaraam [this message]
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).