Fwd: GDB/GCC/Hurd GSoC 2013 projects

[Fotis Koutoulakis]

---------- Forwarded message ----------
From: Fotis Koutoulakis <fotis.koutoulakis@gmail.com>
Date: Wed, Jun 26, 2013 at 12:53 PM
Subject: Re: GDB/GCC/Hurd GSoC 2013 projects
To: Thomas Schwinge <thomas@codesourcery.com>


Please excuse me for failing to appear at the weekly IRC Meeting. I
promise that this won't happen again.

I would like you to know that I am working full time, and I am
currently engaged studying documentation for both the GCC and the
Hurd. I am done mostly with the Hurd documentation, and I am currently
studying some documents for the GCC. I believe that in the week, I
will be able to start writing code. I have not met any severe
obstacles so far.

I will write a report on the Hurd website today.

Please accept my apologies, and be ensured that I will do my best to
ensure that I am online and available on the IRC for any thing you
might want to contact me about.

Thanks for your time.

On Wed, Jun 26, 2013 at 11:13 AM, Thomas Schwinge
<thomas@codesourcery.com> wrote:
> Hi Fotis!
>
> Neither have you shown up at the scheduled weekly IRC meeting, nor have
> you given any notice that you wouldn't be able to make it this week.
> Also, I have not seen any kind of status report from you in a very long
> time.
>
> I know you have been busy with university work before, which is fine, but
> in the application process you stated that »after the 20th of June, I
> will be able to work full time«.  I'm not aware/have not been made aware
> of any other obstacles that would take your time now.
>
> Please explain, and send a status report immediately.
>
> I have always encouraged you to report early if there are any issues you
> need help with, which I have not seen you do.
>
> Be aware, as I reported in the weekly IRC meeting, that I'll be away
> starting tomorrow morning through Monday, inclusive.  Samuel will lead
> the next IRC meeting on Monday.
>
>
> Sorry for the rather harsh words, but Google, as your current employer,
> has assigned to me, in my position of dubbed GSoC mentor, the
> responsibility for making sure you're complying to the program guidelines
> -- which I currently can't be sure of.  It is now the time to fix this.
>
>
> Below, I'm repeating the rules that I thought we agreed on.  If anything
> of that is inconvenient for you, including the timing of the weekly IRC
> meeting, we can certainly address your wishes -- once we know them.
>
>
> On Thu, 20 Jun 2013 12:52:20 +0200, I wrote:
>> I propose the following scheme: effective now, GSoC students send a
>> weekly report at the end of each week (so, on Friday, or on the weekend
>> -- as an exception at the very latest one hour before the following
>> regular IRC meeting), and regular IRC meetings are held each Monday,
>> during the GSoC students' day-time, that is, between 7 UTC and 12 UTC
>> (translating to 9 UTC+2 and 14 UTC+2, and 15 UTC+8 and 20 UTC+8).
>> Unfortunately, this probably will be inconvenient for Ian and Luis, so I
>> do not expect you to attend regularely, but rather be consulted on
>> demand.  More specifically, would Monday, 8 UTC (10 UTC+2, 16 UTC+8) work
>> for everyone, typically?  ("Everyone" here means the GSoC students, GSoC
>> mentors, and everyone else who is interested.)
>>
>>
>> Of course, despite the regular meeting, you're still very much encouraged
>> to discuss issues early, as they come up, instead of waiting for the next
>> meeting.
>>
>>
>> Weekly reports, as discussed before:
>>
>> | Weekly reports.  Additional to the IRC meetings and any other emails you
>> | send, we'd like some sort of weekly report, covering what you have done
>> | in the last week, what worked fine, what didn't, and so on.  How/where
>> | you do the reporting, we don't really care, as long as it's publically
>> | accessible.  You can send a weekly status email, or post an article on
>> | your personal blog, of host a page/blog on the GNU Hurd wiki (which
>> | several GSoC students have done in the past; see some of the subpages on
>> | <http://darnassus.sceen.net/~hurd-web/user/>).
>> |
>> | It is best of course, if there is some correlation between the timeline
>> | you proposed in your GSoC project applications and the progress you're
>> | actually making, but it is to be expected that you have to adjust the
>> | former.  (And don't worry if ther are weeks where you don't seem to get a
>> | lot done -- things take time.)  Please do make some effort to predict how
>> | log certain tasks will take (and then how long they actually took...):
>> | this is a good exercise for the difficult topic of software development
>> | time scheduling (speaking from my own experience...) ;-) and that surely
>> | will be helpful later in your jobs, too.
>
>
> Grüße,
>  Thomas



--
Fotis 'NlightNFotis' Koutoulakis

- "Non semper aestas erit; venit hiems."


--
Fotis 'NlightNFotis' Koutoulakis

- "Non semper aestas erit; venit hiems."