git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Shubham Mishra <shivam828787@gmail.com>
Cc: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	Plato Kiorpelidis <kioplato@gmail.com>,
	Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>,
	Taylor Blau <me@ttaylorr.com>, git <git@vger.kernel.org>
Subject: Re: [GSoC] Contributor candidate introduction
Date: Mon, 9 May 2022 12:36:13 -0400	[thread overview]
Message-ID: <YnlC/WA3nwRA8NQx@nand.local> (raw)
In-Reply-To: <CAC316V7dRjsLiVJLvB-PXRDVZ0NB0xin9XEWq9QBiARthNuGaw@mail.gmail.com>

On Mon, May 09, 2022 at 08:42:38PM +0530, Shubham Mishra wrote:
> Hi Kaartic,
>
> At my job, my timings are flexible. I already discussed about GSoC
> with my team and Microsoft is supportive for open source
> contributions. I have done side projects and open source contributions
> in past also, so this shouldn't be a problem. I also planned to spend
> weekends on this (I usually spend weekends on my desk, so this is fine
> for me).

Be careful to not over-extend yourself. I think it's great that you're
excited about GSoC, but in order for it to be the most successful for
you, you should make sure that your work on Git happens during the times
that work best for you.

I'm not familiar with your exact working arrangement, but I would
caution you that participating in GSoC (if your GSoC project expects
35-40 hours a week from you) _is_ equivalent to a full-time job.

If your existing full-time job allows you to spend time working on GSoC,
that's great. But if your normal work is separate from GSoC, having two
full-time commitments seems like a recipe for disaster.

> I do not have any other commitments or planned vacations throughout
> the GSoC timeline. I would be able to dedicate 35-40 hours per week :)

Likewise, GSoC shouldn't get in the way of your personal commitments.
Taking breaks is part of doing productive work ;-).

Thanks,
Taylor

  reply	other threads:[~2022-05-09 16:37 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
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 [this message]
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=YnlC/WA3nwRA8NQx@nand.local \
    --to=me@ttaylorr.com \
    --cc=chakrabortyabhradeep79@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=kioplato@gmail.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).