My name is Alexandra and I'm an undergraduate Politehnic University of
Bucharest student, from Romania. I think "Native Google Chrome
support" is a cool project.
I would like to know how can I increase my chances to be accepted. Are
there any open bugs, to get my hands on ?
I have experience with C/C++, system programming, windows and linux
environments .
Thanks,
Alexandra
hi Alexandra, thanks for writing.
working on open bugs & showing your skills would definitely be worthwhile!
our Ideas for GSOC page at http://www.metalinker.org/ideas.html needs
some work, & should possibly be moved to our wiki. it also should be
updated with smaller bite size bugs for related projects (aria2,
MirrorBrain, metalink checker, DownThemAll!, Appupdater, etc)
maybe adding Metalink support to axel? (although their last release
was 3 years ago - you would want to contact them to see if they will
be willing to do a new release).
Native axel (download accelerator) support.
Difficulty: Easy to Medium.
Skills: C coding.
Progress: Tatsuhiro has released libmetalink, a C Metalink Parser. But
this will also require some axel specific code. Philipp Hagemeister,
who works on Axel plans to do this.
Details: Metalink support might require adding XML & checksum library
dependency.
and here is the bug for Metalink support in Chromium:
http://code.google.com/p/chromium/issues/detail?id=1751
you would want to read the bug, then post to the chromium-dev mailing
list mentioned
Native Google Chrome support.
Importance: High.
Difficulty: Easy to Medium?
Skills: C++ coding.
Bonus: Familiarity with libxml2, which Chrome already depends on. It
uses NSS for checksums.
Details: Feature request. Chromium code. There's also libmetalink.
Thread on chromium-dev.
--
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
)) Easier, More Reliable, Self Healing Downloads