the FFMpeg project was very successful with it's qualification tasks<br><a href="http://guru.multimedia.cx/googles-summer-of-code-2007/">http://guru.multimedia.cx/googles-summer-of-code-2007/</a><br><br>regards,<br>mark
<br><br><div class="gmail_quote">On Nov 23, 2007 6:30 AM, Jesse Allen <<a href="mailto:the3dfxdude@gmail.com">the3dfxdude@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Nov 22, 2007 10:00 AM, Kai Blin <<a href="mailto:kai.blin@gmail.com">kai.blin@gmail.com</a>> wrote:<br>> On Thursday 22 November 2007 17:44:09 Jesse Allen wrote:<br>><br>> > From my understanding, the SoC site specifically says that you do not
<br>> > have to work on a project that has to be completed in the allotted<br>> > time. I think the idea is that google wants to encourage people that<br>> > were already working on a project before to apply and to encourage
<br>> > people to continue working in the community after the session is<br>> > complete. Now the mentoring organization could set their own<br>> > requirements, based on difficulty and scope, but I would be concerned
<br>> > with making time a limiting factor.<br>><br>> I'm not saying that we stop people from working on their stuff afterwards, nor<br>> forcing them to e.g. implement the full dll if their project is "Start an
<br>> implementation of dll x". I was talking about shrinking their proposal so<br>> they can actually manage to implement all the features they promise in their<br>> proposal in the proposed timeframe. I know that this was really hard for me.
<br>><br>> > The best alternative to the quiz would be to have the student begin<br>> > working on the project before the application. He can discuss it on<br>> > the the mailing list and hopefully show some code. This would be a
<br>> > good way to judge coding skill and the project's scope. Now in order<br>> > for this to work well, we would have to encourage people to get<br>> > started early, which really hasn't happened before right?
<br>><br>> Well, depends on how you want to do this. I think this is overly restrictive,<br>> unless you're just talking about a patch or two like Maarten proposed.<br>><br><br><br></div>Well then it sounds like we want better written proposals. Yeah the
<br>goals for my project were very broad. I didn't intentionally do it<br>that way, but it was more like at first, get it to work, sort of<br>thing. And the design wasn't complete until a month in. The only way I<br>
could have done better was to have started earlier. Mind you, I<br>actually did start in April almost two months early. If I get to do it<br>again, I will probably have a much more interesting proposal and have<br>goals that I will know will have specific results in the timeframe.
<br>This is what I'm already considering, but that is because I am<br>experienced in the program already. For new people, we will have to<br>reach out to them and help them get ready early because they won't<br>know what to do. Maybe we need pre-SoC mentors?
<br><font color="#888888"><br>Jesse<br><br><br></font></blockquote></div><br>