On Fri, Mar 27, 2009 at 6:44 PM, asmeurer <asmeu...@gmail.com> wrote: > > OK. I have finished up the first draft of the application (except for > the abstract, which I will do after I have finalized the main parts). > If you all could look at it, that would be great. Feel free to > annotate right on it. It is a wiki after all.
Change: http://code.google.com/p/SymPy/issues/detail?id=1336 to: http://code.google.com/p/sympy/issues/detail?id=1336 Also find a good name for the whole application, so that people find it interesting among the others. e.g. SymPy: differential equations solvers ... maybe you can find something better. > > Some particular questions about it: > Length. Is this too short? too long? I have no idea how long a good > application should be. I think it's good. I suggest to refactor the Notes and Other Notes and make it part of the application. If you have time, one idea for improvement is to be more specific about what and how you implement things in each week. E.g. take your Notes and Other notes and make the paragraphs about each week more detailed. > Sectioning. The way I have it now, the crux of my application is > under "Summary". Is this supposed to be somewhere else, with only a > summary under "Summary"? That wouldn't make any sense, because > "Abstract" is supposed to summarize the application. Yes, Abstract is the thing that will be visible to others if your app is selected and that is the thing that people will read the most. E.g. if there are ~70+ applications at PSF, some mentors will only read the abstract. Or less. :) > Content. Mainly, how well is this written? Would you accept me based > on the application as it is now written? This very much depends on how many slots we get for SymPy and about the other applications. E.g. it's relative. But I think it has a great chance of being accepted. > Spelling and grammar. You don't need to do a check for me, but if you > see something blatantly obvious, let me know or go ahead and fix it. > > Also, does anyone know: why does python have a section for final > evaluation? It would seem that they want me to divide my time line > into the period before the midterm evaluation and the period after. > But they also have a section for the final evaluation, which doesn't > make any sense, as all of the coding should be done by then. Am I > misinterpreting this somehow? The template is here: http://socghop.appspot.com/org/show/google/gsoc2009/python I think it means what work you do before the program starts, what work you do before the midterm and what work you do before the final evaluation. Thanks for writing it up and I promise I will be now more responsive. The deadline is on Friday. Ondrej --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to sympy@googlegroups.com To unsubscribe from this group, send email to sympy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sympy?hl=en -~----------~----~----~----~------~----~------~--~---
