>> P.S: We need to move fast as the deadline for orgs to apply is 11th March. > > ... what happens if the student fails eg because the task caused more > work than expected?
Its for the mentor to decide. If you think that the problem is genuine, you pass the student in the evaluation and expect him to continue work even after GSoC is over, or in another GSoC. > Deadline of two days is so tight that I wonder > whether its possible to define a project other than: > work on topics: > - .. > - .. > until gsoc time is over. By 11th March, all we need to do is this: 1. Decide whether Vim is going to apply or not. 2. Apply (only admin can do that) 3. Make sure we can mentor 1-2 projects if selected. That essentially means allocating a mentor for the idea, and fleshing it out a bit. > About programming you always can only say "will take at least XX hours". Projects ideally should be doable in 12 weeks. However, some ideas may span multiple GSoC. > Defining an upper limit "at most YY hours" is always wrong. Nobody is doing that. They are just defining an upper limit on applying. -- Anurag Priyam http://about.me/yeban/ -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
