Git Mailing List Archive mirror
 help / color / mirror / Atom feed
From: shejialuo <>
To: Christian Couder <>
Cc: Ghanshyam Thakkar <>,
	Chandra Pratap <>,,
	Kaartic Sivaraam <>,
	Patrick Steinhardt <>,
	Karthik Nayak <>
Subject: Re: [GSoC] Welcoming our 2024 contributors and thanking our applicants
Date: Wed, 15 May 2024 18:04:59 +0800	[thread overview]
Message-ID: <ZkSIywwX20fJo-91@ArchLinux> (raw)
In-Reply-To: <>

Hi Everyone:

On Wed, May 15, 2024 at 11:19:34AM +0200, Christian Couder wrote:
> Hi Chandra, Ghanshyam and Jialuo,
> On Wed, May 8, 2024 at 6:01 AM Kaartic Sivaraam
> <> wrote:
> > As you may be aware, the results for GSoC 2024 have been officially
> > announced[1]. We have 3 contributors contributing to Git this year[2].
> Please let us know if you would like a call or some other kind of
> meeting with only your mentors or with the wider Git community. It
> could be on a regular schedule (like every few weeks) or not. It could
> be a special Slack channel with us and perhaps others who would ask us
> to be invited in it. We could also use this thread or other emails
> threads either with or without the mailing list in Cc to discuss
> things if you prefer.

I've had meetings with my mentors Patrick and Karthik this week. We've
set up bi-weekly video meetings for syncing. I think it's good to create
a Slack channel where we could help each other for some general problems
thus improving the productivity and also establishing a good

> We are suggesting this because the GSoC docs
> ( have the
> following:
> "Have a virtual introductory meeting with all of the accepted GSoC
> contributors and mentors in May to help welcome everyone and help them
> feel more like part of the community. This is something GSoC
> contributors appreciate and ask for every year in their feedback, more
> orgs should try this."
> and in an email to mentors and org admins we were also told to "Set up
> an introduction/welcome meeting with all of your GSoC contributors and
> mentors (and other community members when possible)".

I think it's nice to have a virtual introductory meeting with all of the
accepted GSoC contributors and mentors thus we could know each other

> Also please be aware that if we setup something, you might help each
> other on that channel, but you should not really work together on the
> same things as
> for example says:
> "Don’t select multiple people for the same project idea: If two GSoC
> contributors are working on the exact same project then they are
> competing with each other. Likewise, don’t make one person’s project
> dependent on another person’s project, that essentially makes it a
> team project which is not allowed or in the best interest of the GSoC
> contributors."
> Also feel free to reply to this privately to your mentors if you prefer.
> Best!


  reply	other threads:[~2024-05-15 10:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08  4:01 [GSoC] Welcoming our 2024 contributors and thanking our applicants Kaartic Sivaraam
2024-05-08 11:48 ` shejialuo
2024-05-10 20:04 ` Ghanshyam Thakkar
2024-05-15  9:19 ` Christian Couder
2024-05-15 10:04   ` shejialuo [this message]
2024-05-23 10:30     ` [ANNOUNCE] GSoC Call on June 7th at 12:00 UTC and Slack channel (was: Re: [GSoC] Welcoming our 2024 contributors and thanking our applicants) 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:

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

  git send-email \
    --in-reply-to=ZkSIywwX20fJo-91@ArchLinux \ \ \ \ \ \ \ \ \

* 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 read-only IMAP folder(s) and NNTP newsgroup(s).