On Sat, Mar 15, 2008 at 12:23:05PM +0100, Bartlomiej Wolowiec wrote:
On czwartek, 13 marca 2008, Michael Niedermayer wrote:
Hi
Id like to remind SOC students that everyone should select a seperate qualification task. Having 2 students work on the same task is not good. We had 2 last year who did and it caused problems, i would like to avoid that this year.
Currently we have (if i interpreted everyones mails correctly) Sascha VIVO demuxer (or vivo audio?) Marcondes VIVO demuxer (said so after sascha) andi metadata or MLP patch cleanup ? thilani MLP patch cleanup? (said so after andi)
Also maybe students should add a note to the wiki below the qualification task they selected.
Hello, in GSOC 2007 I wrote part of the code of E-AC3 decoder. Unfortunately, because of incomplete documentation and lack of samples for a long time I wasn't able to write all of it in the time of holidays, then, when the academic year was started I hadn't got much free time. I know, that it wasn't perfect, but I am keen to try once again to write something in GSOC. So I would be grateful if you may tell me, do I still have any chance to participate in GSOC 2008?
You do, it all of course strongly depends on the number of slots google will give us. As well as your last year mentors oppinion ...
I'm also keen to write some qualifying task (last year I wrote TIFF encoder and LZW compression), so I have a question, is any of the following tasks free: "Optimal huffman tables for (M)JPEG encoding", demuxer RL2 or Psygnosis YOP ?
What about getting the EAC3 code into SVN? It likely wont be as easy as the other qualification tasks but if you succeed that could have a strong effect on your chances of being accepted again (especially if we have many more qualified students than slots) Anyway the current list of qualification tasks: Sascha RL2 Marcondes VIVO demuxer andi MLP patch cleanup thilani MLP patch cleanup? (said so after andi) Ramiro mimic Alexander Strange SSE2 IDCT Deep Pal optimal mjpeg huffman table [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If a bugfix only changes things apparently unrelated to the bug with no further explanation, that is a good sign that the bugfix is wrong.