From: Ashish Gupta <ashmew2@gmail.com>
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: bug-guix@gnu.org
Subject: Re: Guix as GSOC Project
Date: Thu, 25 Apr 2013 13:51:39 +0530 [thread overview]
Message-ID: <CABH6M7+2QdqsTKT2_WMm5hwxAnLwAEr+aj0fhtO4L-kQ4-8a3A@mail.gmail.com> (raw)
In-Reply-To: <5178385B.4070900@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
On Thu, Apr 25, 2013 at 1:24 AM, Cyril Roelandt <tipecaml@gmail.com> wrote:
>
> On 04/23/2013 10:24 AM, Ashish Gupta wrote:
>>
>> The best part is that I'll be having a summer break from 27th May (the
date
>> when volunteers are announced) to 18th June. In those 20 days, i can do a
>> lot of learning about whatever will be relevant. And after the college
>> starts i can spend at least 35-40 hours a week working on the project i
>> will be assigned.
>
>
> So you'd be going to college and working on Guix at the same time ? I
think this might be a problem. The idea of the "Summer of Code" is that
students get to work during their summer __break__. I'm not saying this
can't be done, but working double shifts seems a bit hard to me.
>
> Cyril.
Hello Cyril, im actually accustomed to working like that, college goes on
but that will be for about 4 hours a day with no concept of "homework"
going on. It wont be "double shifts", it's actually what i do everyday,
very normal. The college will not be a part where time is invested, not at
all. It will actually be like a summer break because the hours have been
reduced by half (8 hours to 4 hours) by the college.
It is of no worry. I can keep working on Guix for 40-45 hours a week easily
enough , and maybe stretch it to 50-55 if required.
Plus as i mentioned, the 20 holidays that im getting in the beginning of
June will also help in learning about a lot of new things, using which
stuff can be implemented once the actual programming kicks off under GSoC.
Regards,
Ashish
[-- Attachment #2: Type: text/html, Size: 1980 bytes --]
prev parent reply other threads:[~2013-04-25 8:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 0:10 Guix as GSOC Project Ashish Gupta
2013-04-22 21:57 ` Ludovic Courtès
2013-04-23 8:24 ` Ashish Gupta
2013-04-23 11:50 ` Ludovic Courtès
2013-04-24 14:40 ` Ashish Gupta
2013-04-24 15:21 ` Chris Dale
2013-04-24 15:34 ` Ashish Gupta
2013-04-24 20:34 ` Ludovic Courtès
2013-04-25 9:22 ` Ashish Gupta
2013-04-26 14:35 ` Ludovic Courtès
2013-04-26 22:31 ` Xue Fuqiao
2013-04-27 7:25 ` Ashish Gupta
2013-04-24 19:54 ` Cyril Roelandt
2013-04-25 8:21 ` Ashish Gupta [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABH6M7+2QdqsTKT2_WMm5hwxAnLwAEr+aj0fhtO4L-kQ4-8a3A@mail.gmail.com \
--to=ashmew2@gmail.com \
--cc=bug-guix@gnu.org \
--cc=tipecaml@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://git.savannah.gnu.org/cgit/guix.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).