GSoC Info

[Augie Fackler]

Hearing no objections about the meeting time, I'd like to start doing
meetings next week. I'm not sure there's any merit in doing one this
week since you're all just getting started with your projects. In the
interim please contact the mailing list and introduce yourself and
start doing any research you need.

 The first meeting will be:
<http://www.timeanddate.com/worldclock/fixedtime.html?month=6&day=1&year=2010&hour=12&min=0&sec=0&p1=64>.

Also, for benefit of students not familiar with my tendencies - I idle
in IRC 24 hours a day, but am often not at the computer. I always
respond, but if it's something pressing that requires a response,
email is a far safer bet. Every once in a while the VM gets rebooted
without me remembering to check IRC for messages first.

If you want a calendar entry for the weekly meeting (includes this
week, although I don't see a need this week), here's a Google Calendar
link to a repeating event:
<https://www.google.com/calendar/b/1/event?action=TEMPLATE&tmeid=MmlvM2ZmY21lamZuNW00ZmJ2dGc0NDBvZWtfMjAxMDA1MjVUMTcwMDAwWiBsMHMxYW8yNHRyMDJoZTFwaDg0Zm92ajh0Y0Bn&tmsrc=bDBzMWFvMjR0cjAyaGUxcGg4NGZvdmo4dGNAZ3JvdXAuY2FsZW5kYXIuZ29vZ2xlLmNvbQ>

On Thu, May 20, 2010 at 9:31 AM, Augie Fackler <durin42 at gmail.com> wrote:
> Greetings Students, Mentors, and denizens of -devel,
> The start coding date for GSoC is fast approaching. I thought I'd take
> a minute to share some notes:
> 1) Mentors have generally been assigned a topic outside their area of
> expertise. This means that your mentor can help you figure out who to
> talk to, but probably won't be able to answer anything beyond basic
> style questions.
> 2) We'll expect weekly status updates emailed to your mentor with
> -devel CC'ed. This isn't a place to ask questions, but more a place to
> have a single go-to place for the community to keep tabs on your
> project. These don't have to be long, but should at least give a
> reader an idea of what you're working on.
> 2a) We'll also expect you to attend a weekly meeting in IRC. I'm
> tentatively scheduling this for 1200 US/Chicago time on Tuesdays,
> which is 2200 UTC. If others want to propose another time, I'm open
> to suggestions, but we must stay in the time frame when folks in Europe
> and North America are awake.
> 3) Use IRC. There's almost always a group of people online that can
> help you right away with your problems.
> 4) Send overall design mails to -devel. If you're not sure where you
> should be going, this is absolutely the right thing to do. Even if you
> are sure, it's still a good idea for a major feature so you don't
> surprise a crew member and have to convince them of your approach (or
> worse, have to rewrite your awesome code).
> 5) Send patches to -devel for review.  This is probably the most
> important thing. When the summer is over, we'll be able to bundle up
> your patches fairly trivially for Google.
> 6) Last, but probably most important: participate in the
> community. Help people on mercurial@ with problems, and the same for
> IRC.
> Also, it's worth reading mpm's thoughts on SoC if you haven't already
> (or maybe reread if it's been a while):
> <http://selenic.com/pipermail/mercurial/2010-April/030996.html>.
> Thanks, Augie
>