GSoC students,

By now, we're on our fifth day into the GSoC coding timeframe, so hopefully 
everyone is busy writing code and having fun!  I have several comments and 
requests to make of everyone so we can keep having fun...  :)

First up, several of you STILL do not yet have commit access, so really need to 
step up and focus on this.  No excuses.  If your patches haven't yet been 
reviewed, you may be okay but read over some of the recently closed patches for 
common mistakes and recheck your work.  There is a patch review backlog due to 
our recent major release, but we'll be getting through most of them quickly 
now.  You can help by making your patches as small and simple and perfect as 
possible.  Pay attention to the little details.

Thank you to those of you that quickly updated the wiki page with your info.  
They all need a little work, though...  Not your fault, I wasn't very specific 
but now we can get more detailed.  This is the page we're going to send out in 
an announcement so it needs to look good and be consistent.  The title and 
summary don't need to be the same as what you had on your application.  The 
title should be short, not a long word-packed description.  The summary should 
say more than the title, but not be the paragraph from your Melange 
description.  The summary should be no more than one informative sentence.  Ask 
one of the other students to describe your project in one sentence perhaps.

Mohit: shorter title and slightly longer summary (proper sentence); Wu: longer 
summary; Check: shorter title, shorter summary (variation on title), and dead 
user page link; Kesha and Vlad: shorter summary.  Kesha, since you've 
introduced a nice clean but different template, perhaps you can update the 
other student's profiles so they're all the same.   Still waiting on 
Harmanpreet and Isaac to add your profiles.  Please have this done before 
Tuesday so we have time to review and annou

Logs!  Most of you have this down solid so far, but three are already in danger 
of a warning for not communicating a status update(!)...  Three notices will 
get you failed, so please do remember to update your log daily, not weekly.  
Even if just to say "didn't work today, went to the beach" so we know what's up.

You are all reminded to be very vocal while you're working.  Talk with others 
here on the mailing list and via IRC.  Your commit message is also useful 
communication, so commit very frequently (not just when you're "done" with 
something).  If you haven't been updating your log and you don't have commit 
access, this is a wake up call to improve your participation.  If you have any 
issue, please do let me or anyone else know.  Otherwise, looking forward to 
seeing your commits throughout the day!

Cheers!
Sean


------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to