[summerofcode] Not finnishing the project in the final date

[Linan Wang]

I think:
1, Give a "big picture" of your project as well as objective of SoC.
2, Clear description of both objective and methodology for mentors to
judge wether accept your proposal.
3, A schedule will be helpful.
4, If it's just a part of big project, leave enough space or give
detail document for following developpers.

above 4 points are only my ideas. Who knows what google thinks! :)

On 6/7/05, Florencio Cano Gabarda <fcano at ono.com> wrote:
> >   I don't know the rules, but I would strongly advise that the
> >   scope of the proposal be trimmed back to what can be done,
> >   with suggestions of "follow-on" work that could be done once
> >   the statement of work was accomplished... Then GET 'ER  DONE
> >   (the SOW - statement of work).
> 
> So, my application is about implementing complete SSL support for Python
> with a module...I'm still studying the project plannification but for
> example...if I decide that it is not possible to me to almost finnish it
> (clear coded, efficiency, easy interface, etc, etc...) before the final
> time, Should I reduce the objectives of the application to code only a
> partial implementation?
> --
> Florencio Cano Gabarda <fcano at ono.com>
> 
> 
> _______________________________________________
> summerofcode mailing list
> summerofcode at python.org
> http://mail.python.org/mailman/listinfo/summerofcode
> 


-- 
Wang
-----------------------------------------------
Email:tali.wang at gmail.com
Or: arp04lw at shef.ac.uk
Mobile:+44-7760-338-932
-----------------------------------------------