On Wed, Apr 7, 2010 at 5:29 AM, Craig Citro <[email protected]> wrote: > Hi Haoyu, > >> Now my proposal is on the Cython wiki for comment: >> >> http://wiki.cython.org/HaoyuBai/GSoC2010 >> > > Sorry about the delay -- I'm finally getting some cycles to sit down > and work on this. > > First, minor edits -- I went ahead and edited the page on the wiki and > made minor grammatical/spelling/formatting changes. I also left a few > notes where I thought you could use more explanation and/or a link -- > just search for "-cc" on the page. (We could also renumber the > references, but that's not really a big deal.) > > I had some thoughts along the same lines as Robert and Stefan for the > first part of the project -- I think that there will probably be a > little extra time needed at the beginning acclimating to the codebase. > (Though maybe the fact that you've already got two other patches up > and waiting for review suggests otherwise? ...) Also taking into > account Robert and Stefan's advice on ordering of events and how much > time things will take, I'd recommend slightly restructuring things, as > follows: > > * Weeks 1-3: bug fixes as-is, making sure to get each passing tests > and posted on trac before moving on to the next one > * Week 4: Work on pure Python mode documentation, start pinging > people for code reviews on patches remaining from weeks 1-3 > * Week 5: respond to any comments on patches, and make getting as > many patches as possible merged the goal for midterm review. > * Week 6-7: decorator support (note that some of the documentation > work was moved up) > * Week 8-9: annotation support (I'm taking into account Stefan's > comment that this is not as deep as you might expect at first) > * Week 10: cleanup, documentation, tests, etc. > > Basically, I want to really focus on getting a bunch of patches and > documentation knocked out in the first half, for two reasons: first, > as your mentor, I can be reviewing your patches and responding as a > way of monitoring your progress, and second, it means that you'll get > more familiarity with the current code and documentation before > jumping into the slightly-larger-scale decorator and annotation > projects. It also means that we have a little extra padding at the > beginning for things that take extra time (like Stefan predicted for > #465). > > Does that seems sensible? Feel free to tell me if you think I'm crazy, > or if you'd rather do it a different way. > > I'm going to go work on finishing up whatever else I have to do for > mentor registration, but I should be able to be fairly responsive by > email for the rest of the week ... and I'm getting excited about this > project! > > -cc
Hi, Thanks for all the comments! They are all very reasonable and I've updated the proposal on the wiki according to these. I have adjusted some unclear paragraphs and rearranged the schedule to follow the concern of workload and milestone for mid-term review. Hopefully now the proposal is clearer and better shaped. Thanks for your help! :) -- Haoyu BAI School of Computing, National University of Singapore. _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
