Historical:GSOC 2011 Student Application

From PanoTools.org Wiki
Revision as of 17:46, 5 June 2020 by Erik Krause (talk | contribs) (Erik Krause moved page GSOC 2011 Student Application to Historical:GSOC 2011 Student Application)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

The application deadline is April 8 19:00 UTC.


Tell us who you are and at which University you're studying what at the moment. Please give us some background on yourself with a short bio and introduce yourself to the hugin-ptx Google Group we're looking forward to read your email. Then you should get yourself an account on this wiki and add your project proposal.

It's optional but nice if you also tell us about your photography skills in your introduction. What kind of photographic gear do you use, do you photograph panoramas? Show us some of your examples, preferably somewhere online, not attached to the email (i.e., show us your flickr, deviantart or some other online gallery of yours). If you make other use of hugin/panotools than for stitching panoramas we'd also like to hear about it. Such ideas are almost always very interesting.

Your Coding Skills

If you're adding a project proposal, make sure to let us know what platform you use to code. Tell us about your hardware and operating system. Then we'd like to know a bit more about your coding experience: Did you ever code in C or C++, or are you a guru in some other language?

Tell us more about your involvement with hugin/panotools in your introduction (not optional): Have you done some work in the past? What did you contribute to hugin/panotools? If you were involved with other OpenSource projects we are definitely interested to know more about this. Which project did you support, when and in what role?

Set yourself up

Get up and running with your system to build Hugin, Panotools and Enblend-Enfuse from our repository. Informations for several OSses can be found here: Fedora, OS X, Windows, Ubuntu and Gentoo.

If you need help on compiling, ask on the mailing list. If you're successful, we'd like to hear it too. If you find an error/omission on the wiki page, do correct it, it's a wiki!

To show proficiency of the toolchain, we ask you to produce a patch against Hugin's repository. This helps us to assess your coding style. You can find ideas in our tracker, either bug reports or feature requests. Optimize your time, you don't have to impress us. Then talk about your your patch for peer review on our mailing list. We do not consider applications without patches.

Get going

  • First you probably need to familiarize yourself with how the past Summers of Code went; so you might want to read up the necessary pages in the Summer of Code overview first.
  • Add yourself/your project with a short synopsis to the list of projects on the wiki, don't forget to put
    to the bottom of the page you make, so it will show up in the overview. In the page of your proposal, make clear 1) what you want to achieve and 2) what do you expect from your implementation. If you chose an idea from the Blueprints over at Launchpad tell us why and what you'd exactly like to do with it. If you're having an idea of your own, tell us more about it. We want to know what's great about and why it would be of benefit for hugin. On your proposal page, tell us why you're suited to carry out the project.
  • Be prepared to tell us how much time do you plan to invest in the project before, during and after the Summer of Code? We expected full time 40h/week during GSoC, would that be doable for you?
  • Please provide a schedule of how this time will be spent on subtasks of the project. While this is only preliminary, you will be required to provide a detailed plan latest at the beginning of GSoC and during the project you will issue weekly progress reports against that plan.