git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Taylor Blau <me@ttaylorr.com>,
	Plato Kiorpelidis <kioplato@gmail.com>, git <git@vger.kernel.org>,
	Shubham Mishra <shivam828787@gmail.com>,
	Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [GSoC] Contributor candidate introduction
Date: Thu, 7 Apr 2022 09:16:44 +0200	[thread overview]
Message-ID: <CAP8UFD1x-JEX8MAmpabK4RbKgmVm1VQYNJdX3fP8Op5WMfUgVg@mail.gmail.com> (raw)
In-Reply-To: <e312b18b-f0d6-8980-9cad-74602043a1db@gmail.com>

On Wed, Apr 6, 2022 at 10:12 PM Kaartic Sivaraam
<kaartic.sivaraam@gmail.com> wrote:
>
> On 06/04/22 21:13, Taylor Blau wrote:
> > Thanks for this information, it's exactly the sort of thing that I was
> > hoping for from your response ;-).

;-) Note that my answers are based on what I know from previous years.
Rules sometimes change from year to year though, so everyone is
welcome to check.

> > Like I said in my other message, let's play it by ear whether or not we
> > need to split the project. If we get closer to the next deadline and we
> > have >1 potential GSoC students interested, then I'm happy to split it
> > up.
> >
> > One thing that I worry about a little bit is that I think a new on-disk
> > .bitmap format will be necessary for both of the projects that Plato and
> > Shubham are interested in (though I could be wrong). Since GSoC forbids
> > students from working together, it may be difficult to feasibly split
> > the bitmaps project into multiple, smaller ones.
> >
> > That said, if we do end up splitting the bitmaps GSoC project in two,
> > when would we need to do it by?
>
> To the best of my knowledge, Google does not require the proposal ideas to
> be laid out by organization before the proposal deadline (which is April 19).
> This gives the flexibility for mentors and GSoC contributors to collaborate
> and come up with a project ideas that are not present in the initial ideas
> list and write proposals for them.

I agree with this, but please keep in mind that in
https://git.github.io/General-Application-Information/ we ask
applicants to "Discuss their project by posting drafts of their
application on the mailing-list long before the deadline." So
splitting the bitmap project should be done soon, so that applicants
have time to prepare and discuss their proposals based on the splitted
project.

See also the "Note about getting involved early" section in the
document, which has information about what applicants should do when
they get involved quite late.

On https://google.github.io/gsocguides/mentor/selecting-a-student.html
there is also:

"Don’t Be That Person: Don’t even think about selecting a GSoC
contributor with whom you’ve had no contact. You should establish an
active back-and-forth prior to making a decision. If you or your GSoC
contributor have failed to make this happen, do not proceed."

Best,
Christian.

  reply	other threads:[~2022-04-07  7:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 21:43 [GSoC] Contributor candidate introduction Plato Kiorpelidis
2022-04-05 21:59 ` Taylor Blau
2022-04-06  6:25   ` Christian Couder
2022-04-06 14:11     ` Shubham Mishra
2022-04-06 15:40       ` Taylor Blau
2022-04-06 15:43     ` Taylor Blau
2022-04-06 20:11       ` Kaartic Sivaraam
2022-04-07  7:16         ` Christian Couder [this message]
2022-04-07  9:25           ` Abhradeep Chakraborty
2022-04-08 20:34           ` Taylor Blau
2022-04-08 20:46             ` Junio C Hamano
2022-04-13 20:55             ` Taylor Blau
2022-04-15 21:01               ` Plato Kiorpelidis
2022-04-18 17:54 ` Kaartic Sivaraam
2022-04-18 18:06   ` Abhradeep Chakraborty
2022-04-19  4:38     ` Shubham Mishra
2022-04-19 15:54     ` Abhradeep Chakraborty
2022-04-18 18:24   ` Kaartic Sivaraam
2022-04-19 13:16     ` Jayati Shrivastava
2022-04-19 17:40       ` Kaartic Sivaraam
2022-04-20 13:16         ` Labnan Khalid Masum
2022-04-20 19:40           ` Kaartic Sivaraam
2022-04-21  8:58           ` Christian Couder
2022-04-18 18:33   ` Plato Kiorpelidis
2022-05-09  6:44   ` Kaartic Sivaraam
2022-05-09 15:12     ` Shubham Mishra
2022-05-09 16:36       ` Taylor Blau
2022-05-09 20:13     ` Plato Kiorpelidis
  -- strict thread matches above, loose matches on Subject: below --
2022-04-05 21:30 Plato Kiorpelidis

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=CAP8UFD1x-JEX8MAmpabK4RbKgmVm1VQYNJdX3fP8Op5WMfUgVg@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=kioplato@gmail.com \
    --cc=me@ttaylorr.com \
    --cc=shivam828787@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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