Historical:SoC2007 application

Organization

to organize.

Did your organization participate in GSoC 2005 or 2006

We did not participate in GSoC in the past and we never applied before.

Who is the administrator

to be defined.

What license does your project use

GPL.

What is the URL for your ideas page

http://wiki.panotools.org/SoC2007_projects

What is the main development mailing list for your organization

http://lists.sourceforge.net/lists/listinfo/panotools-devel

What is the main IRC channel for your organization

do we have any?

Does your organization have an application template you would like to see students use? If so, please provide it now

not really.

Who will be your backup organization administrator? Please include Google Account information

to be defined.

Who will your mentors be? Please include Google Account Information

• Pablo?
• any other "senior" developer or academic with mentoring experience around?

What criteria did you use to select these individuals as mentors? Please be as specific as possible

• familiarity and experience with the production process of stitched panoramas
• knowledge of the universe of code applied to stitched panoramas
• experience in mentoring junior coders, possibly from an academic environment
• in depth knowledge of user requirements
• ...

What is your plan for dealing with disappearing students

there have been a number of potential students showing up in our community. We think the risk of disappearing is minimal. We can try to structure the work as academic credits to incentivate the student not to disappear. However, if shit happens, we feel we have a responsibility toward Google and toward our community to deliver. It might take longer than expected if the usual suspects do the contribution, but we will get there. We are determined to work on hugin, with or without student and with or without Google's sponsorship.

What is your plan for dealing with disappearing mentors

The selected mentors are well known and connected in the community. We estimate the risk of a disappearing mentor to be very low. To minimize the impact of such an unlikely event we strive to have two mentors per project that can replace each other seamlessly. In the event that one of the two mentors disappears, recruiting efforts for a backup mentor will start immediately. Our steering committee is well connected and will support the organizer in the efforts to recruit replacement mentors. Our community has already experienced the disappearing of key figures on important projects and survived the test when Helmut Dersch, founding father of the panotools library that is at the core of our community, disappeared.

What steps will you take to encourage students to interact with your project's community before, during and after the program

First of all, we hope to recruit a student from the community. This is a growing and vibrant community. We will make sure that the student has the specialized gear to shoot panoramas and we will make sure they get the bug that all of us have. It's passionating photography. We have already organized a fund raiser to donate a fish-eye lens to one of the project maintainers and we can do this again and again.

What will you do to ensure that your accepted students stick with the project after GSoC concludes?

We will make sure he or she enjoys the practical aspects of panorama photography. Part of the assignement will be of practical nature: *use* the software to learn it, not just *code*.