bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

GDB/GCC/Hurd GSoC 2013 projects


From: Thomas Schwinge
Subject: GDB/GCC/Hurd GSoC 2013 projects
Date: Thu, 20 Jun 2013 12:52:20 +0200
User-agent: Notmuch/0.9-101-g81dad07 (http://notmuchmail.org) Emacs/23.4.1 (i486-pc-linux-gnu)

Hi!

On Thu, 20 Jun 2013 11:55:42 +0200, Samuel Thibault <samuel.thibault@gnu.org> 
wrote:
> Justus Winter, le Thu 20 Jun 2013 10:58:09 +0200, a écrit :
> > Quoting Samuel Thibault (2013-06-18 22:43:33)
> > > AIUI, SoC has begun yesterday, we should probably settle for a weekly
> > > meeting?

Thanks for taking the initiative on this!

> > https://dudle.mafiasi.de/Hurd_GSoC_weekly_meeting/
> 
> On the long term, I don't really have any weekly contraint. What I have
> filled is only my conflicts for the coming week.

Similar for me -- though, in my case, having meetings during my daytime
will be more likely to have me attend regularely, as there are often
different kinds of things in the evenings.

I would expect the GSoC students to typically be available during their
respective daytime, which I think is UTC+2 for Fotis and Justus, and
UTC+8 for 陆岳.  (That means, I don't expect you to "switch timezone"
just for GSoC.)

The mentors that are not in UTC+2 are Ian with UTC-8 (?) and Luis with
UTC-3.

So, if we wanted everyone to attend at the same time, that would be
inconvenient for different folks, depending on the time selected.

I do not know whether Ian and Luis plan to regularely attend the meetings
(you're very welcome to, of course!), or rather be consulted on demand?

It would be possible to hold separate meetings for the different GSoC
students (and thus relax the timezone spans), but that would potentially
require more effort (time) on the mentors' side (for repeatedly
discussing general issues, not specific to one GSoC project).


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

Attachment: pgpfNOxVw1qDd.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]