[Biopython] New project for Google Summer of Code 2011

Mikael Trellet mikael.trellet at gmail.com
Fri Apr 8 08:26:05 EDT 2011


Dear all,

You will find on
http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/mika_el/1my
main changes, explained above ;)



> Make the link to your GitHub repository part of your 'On the
>  author' section. Reviewers will definitely want to see your
>  previous work so a sentence pointing it out will prevent it being
>  overlooked in the Additional Info section.
>

Done ;)

- Week 1 is the start of coding, so you should move your preparation
>  bullet points (Study/Evaluate) to the community bonding period,
>  and leave the coding period only for work.


Ok I changed the first week, adding something more concrete and allowing
longer period for the extension of IUPAC.Data, it will be an editing of an
existing module so I'll have to be careful and stuck to the previous work,
longer period isn't excessive I think.

- You mention tests in several places but without any detail.
>  Reviewers will want to see that you've thought out the
>  functionality you are planning to unit test further than "I will
>  write tests for everything."


You're completely right, I tried to be more accurate on these parts, does it
seem enough ?


> Week 11 needs some text to demonstrate how you plan to wrap things
>  up. Keep in mind that's the last thing a reviewer will read so it
>  should leave a good impression.


I developed this part, it seems to be a standard checking but I may have
forgot something obvious..?

Thanks again for your precious remarks,

Cheers,

Mikael



On Fri, Apr 8, 2011 at 12:34 PM, Brad Chapman <chapmanb at 50mail.com> wrote:

> Mikael;
> Great work on getting this together. Some last minute suggestions:
>
> - Make the link to your GitHub repository part of your 'On the
>  author' section. Reviewers will definitely want to see your
>  previous work so a sentence pointing it out will prevent it being
>  overlooked in the Additional Info section.
>
> - Week 1 is the start of coding, so you should move your preparation
>  bullet points (Study/Evaluate) to the community bonding period,
>  and leave the coding period only for work.
>
> - You mention tests in several places but without any detail.
>  Reviewers will want to see that you've thought out the
>  functionality you are planning to unit test further than "I will
>  write tests for everything."
>
> - Week 11 needs some text to demonstrate how you plan to wrap things
>  up. Keep in mind that's the last thing a reviewer will read so it
>  should leave a good impression.
>
> Thanks again for all the work,
> Brad
>
> > Dear all,
> >
> > I just submitted my proposal few minutes ago on google-melange ! So you
> will
> > find everything you want on this link :
> >
> http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/mika_el/1
> >
> > As I'm not sure everybody can access to it, I add in attachment the
> proposal
> > document with the new timeline, stucking to the Google agenda of GSoC.
> >
> > I'm wainting for your reviews,
> >
> > Cheers,
> >
> > Mikael
> >
> >
> >
> > On Fri, Apr 8, 2011 at 1:09 AM, Mikael Trellet <mikael.trellet at gmail.com
> >wrote:
> >
> > > Good might to all,
> > >
> > > A night update : I created successfully everything I needed for my
> github
> > > account (not without problems !!). So you can find on these two links,
> my
> > > group project from my first year of master and a simple script I wrote
> 2
> > > months ago for my daily work :
> > >
> > > https://mtrellet@
> github.com/mtrellet/Protein-classification--2009-2010-Master-1-.git
> > > https://mtrellet@github.com/mtrellet/Parsing-PDB-files.git
> > >
> > > Unfortunately my master project comments are in french...
> > >
> > > I will finish the timeline according to the google agenda tomorrow
> morning
> > > and I will submit a first draft of my project just after. So you have
> still
> > > time to ask me some questions or make some remarks, I'm available to
> answer
> > > as fast as possible to your interrogations.
> > >
> > > Cheers,
> > >
> > > Mikael
> > >
> >
> >
> >
> > --
> > Mikael TRELLET,
> > Computational structural biology group, Utrecht University
> > Bijvoet Center,
> > The Netherlands
> > _______________________________________________
> > Biopython mailing list  -  Biopython at lists.open-bio.org
> > http://lists.open-bio.org/mailman/listinfo/biopython
>



-- 
Mikael TRELLET,
Computational structural biology group, Utrecht University
Bijvoet Center,
The Netherlands


More information about the Biopython mailing list