Hi!
It looks great, if you would like some minor comments, here they are:
*Abstract*
- I suggest focusing on the what you will do first, then the where ("linear
models, to be implemented in sklearn", rather than "this is sklearn, I'm
going to do linear models").
- "This task includes high test coverage" -> "All code accepted to
scikits.learn must include a high test coverage, "
*Outline*:
- Generally, I think references should have a space before them [1].
*Timeline*
- What does "merging back" mean for the first item? Is there a better
phrase?
- I wouldn't have documentation as a separate item in the final by itself.
Given the abstract, good documentation will be expected. Your
sub-dot-points talk about narrative documentation (i.e. how to use the
algorithm, rather than how to use the function). I would call it this:
"narrative documentation"
*References*
- Does Google expect full referencing style? If so, put that in.
Like I said, only minor things. I think this project will benefit
significantly from your involvement.
Thanks,
- Robert
On 19 April 2012 23:19, Immanuel B <[email protected]> wrote:
> Done, thanks for pointing out the urgency I wasn't aware of it.
>
> 2012/4/19 Olivier Grisel <[email protected]>:
> > Le 19 avril 2012 03:41, Immanuel B <[email protected]> a écrit :
> >> Hello all,
> >>
> >> I rewrote the timeline part of my proposal in order to make it better
> >> readable and provide clearer definitions for the steps I intend to
> follow.
> >>
> >> I would be greatfull for any comments be it on content, formulation or
> anything
> >> else before I update my proposal on the GSOC site.
> >>
> >>
> https://docs.google.com/document/d/1q-sTj8kJ-_q_i_UbRxA-_RJEcvocd0M3Y4fHij9byk0/edit
> >
> > Looks good to me, please update the GSoC page ASAP as I think the
> > final decision by the PSF is very close.
> >
> > --
> > Olivier
> > http://twitter.com/ogrisel - http://github.com/ogrisel
> >
> >
> ------------------------------------------------------------------------------
> > For Developers, A Lot Can Happen In A Second.
> > Boundary is the first to Know...and Tell You.
> > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> > http://p.sf.net/sfu/Boundary-d2dvs2
> > _______________________________________________
> > Scikit-learn-general mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
>
>
> ------------------------------------------------------------------------------
> For Developers, A Lot Can Happen In A Second.
> Boundary is the first to Know...and Tell You.
> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
> http://p.sf.net/sfu/Boundary-d2dvs2
> _______________________________________________
> Scikit-learn-general mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
>
--
Public key at: http://pgp.mit.edu/ Search for this email address and select
the key from "2011-08-19" (key id: 54BA8735)
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Scikit-learn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
