From: Christian Couder <christian.couder@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: git <git@vger.kernel.org>, Victoria Dye <vdye@github.com>,
Hariom verma <hariom18599@gmail.com>,
Derrick Stolee <stolee@gmail.com>, Taylor Blau <me@ttaylorr.com>
Subject: Re: GSoC 2023
Date: Fri, 10 Mar 2023 13:38:32 +0100 [thread overview]
Message-ID: <CAP8UFD2qvvjy47=7Zu=jHOHAziG8=vLXje_MW4QrZ-Jrx_wZNA@mail.gmail.com> (raw)
In-Reply-To: <07423D73-8CD9-498B-89E7-7241AC6490D3@gmail.com>
Hi Kaartic,
On Thu, Mar 9, 2023 at 6:19 PM Kaartic Sivaraam
<kaartic.sivaraam@gmail.com> wrote:
> On 9 March 2023 3:47:51 pm IST, Christian Couder <christian.couder@gmail.com> 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.
Yeah, I see you as an Org Admin and Victoria and Hariom as mentors.
> I thought I was already in as an Org Admin but I somehow have missed completing the process. Sorry about that.
No worries. Thanks for doing it!
> >I have emailed gsoc-support@google.com 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:
I see. Thanks for figuring that out! I guess I was too focused on the
Firefox login bug, that I thought there were actually more bugs...
> 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.
Thanks Victoria and Hariom for completing the process too!
prev parent reply other threads:[~2023-03-10 12:38 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
2023-03-09 18:45 ` Hariom verma
2023-03-10 0:56 ` Kaartic Sivaraam
2023-03-10 12:38 ` Christian Couder [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP8UFD2qvvjy47=7Zu=jHOHAziG8=vLXje_MW4QrZ-Jrx_wZNA@mail.gmail.com' \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=hariom18599@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=me@ttaylorr.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.
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 NNTP newsgroup(s).