Difference between revisions of "Historical:GSOC 2011 Application"

Latest revision as of 18:46, 5 June 2020

Organization Name

Hugin - Panorama photo stitcher

Description:

Our organization is a composite of several open source/free software projects: hugin, panotools and enblend/enfuse. We are used to collaborating across timezones and cultures. We are purely meritocratic with no hierarchies, grant write access on our central repository very liberally, make decisions by consensus, are respectful of diversity and welcome all contributors.

Details in our community charter http://hugin.sourceforge.net/community/charter/

Home page

http://hugin.sf.net

Main Organization License

GNU General Public License (GPL)

Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating?

We have had excellent experiences in the past four years we were part of GSOC. As a team, we hope to gain new members. As Free software, we hope to gain a few new mind-blowing features. As a project, we hope to gain visibility to attract more contributors and users beyond GSoC.

If accepted, would this be your first year participating in GSoC?

No

Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.

Hugin participated in all GSoC since 2007. We consider this participation successful for both organization and students. Hugin improved greatly through the student projects from the last years. Successful projects were, just to name a few;

the Hugin Batch Processor (implemented in GSoC 2008), which made successive batch stitching of large projects possible
Masking in GUI, which enables the user to mask out parts of the panorama prior to stitching
Layout Model, enabling hugin to detect the layout of the panorama input images
OpenGL Preview, which is now generally used as the standard preview for panoramas in hugin

If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006.

2007: 4/5

2008: 4/5

2009: 4/5

2010: 4/4

What is the URL for your ideas page?

http://wiki.panotools.org/GSOC_2011_Ideas

What is the main development mailing list or forum for your organization?

The google group hugin and other free panoramic software, is our main mailing list, where we have a lively and strong community with users and developers both very welcome.

What is the main IRC channel for your organization?

irc.freenode.net #hugin. The IRC is not official, and is primarily users.

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

http://wiki.panotools.org/GSOC_2011_Student_Application

What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible

We selected our mentors for their enthusiasm and availability during GSOC. Another strong point was experience, some have academic teaching experience and others have mentored in past GSoC editions. All mentors have hands on experience with our code base and a vast knowledge of the wider universe of code applied to produce stitched panoramas and other computational graphics.

What is your plan for dealing with disappearing students?

The very first thing we'll do is make sure that we pick the right students. Our estimations are going to be based on the following criteria:

Students should be avid photographers;
Students should be able to prove that their programming skills match our request by successfully completing a vetting exercise that will test key skills and knowledge relevant to the proposed project;
Students should be able to prove that they can communicate and work well with a mentor and with the community at large.

We are going to do our best to have them understand that GSoC is both (close to) a full time job and fun, so that they treat it with responsibility, but do not consider it a total bore.

Next step is motivation.

The point of participating at GSoC for us is getting new contributors who bring innovation and stick to affiliated projects.

In case a student cannot deliver good enough results, we are not going to drop all the work he managed to do; we will keep development at the highest possible pace, to make sure the community around the affiliated project will not suffer in any way, and any amount of money invested in the project by Google isn't completely lost.

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 several backup mentors who can replace each other. We will assign two mentors (primary and secondary) to each project. In the unlikely event that one of the two mentors disappears, recruiting efforts for a backup mentor will start immediately. Our community has enough depth to provide the necessary resources. It 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, since Hugin's community is growing and vibrant. We will make sure that the student has the appropriate gear to shoot panoramas, and we will do all we can to share our passion for panoramas with them.

If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here.

Not necessary, since we have a track record with GSOC.

If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here:

Are we "large" and do we support a small organization?

Anything else you'd like to tell us?

How great it was for us in the last years?

Backup Admin (Link ID):

Bruno Postle, (brunopostle) will act as a backup admin

@@ Line 1: / Line 1: @@
-=== Describe your organization ===
+=== Organization Name ===
-Our organization is a composite of several open source/free software projects: hugin, panotools and enblend/enfuse. We are used to collaborate across timezones and cultures.  We are purely meritocratic with no hierarchies, grant write access on our central repository very liberally, make decisions by consensus, are respectful of diversity and welcome all contributors.
+Hugin - Panorama photo stitcher
+=== Description: ===
+Our organization is a composite of several open source/free software projects: hugin, panotools and enblend/enfuse. We are used to collaborating across timezones and cultures. We are purely meritocratic with no hierarchies, grant write access on our central repository very liberally, make decisions by consensus, are respectful of diversity and welcome all contributors.
 Details in our community charter http://hugin.sourceforge.net/community/charter/
-=== Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating? ===
+=== Home page ===
+http://hugin.sf.net
+=== Main Organization License ===
+GNU General Public License (GPL)
+=== Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating? ===
+We have had excellent experiences in the past four years we were part of GSOC. As a team, we hope to gain new members. As Free software, we hope to gain a few new mind-blowing features. As a project, we hope to gain visibility to attract more contributors and users beyond GSoC.
+=== If accepted, would this be your first year participating in GSoC? ===
+No
 === Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation. ===
-hugin/panotools participated in all GSoC since 2007. We consider this participation successful for both organization and students. Our projects were:
+Hugin participated in all GSoC since 2007. We consider this participation successful for both organization and students. Hugin improved greatly through the student projects from the last years. Successful projects were, just to name a few;
+* the Hugin Batch Processor (implemented in GSoC 2008), which made successive batch stitching of large projects possible
+* Masking in GUI, which enables the user to mask out parts of the panorama prior to stitching
+* Layout Model, enabling hugin to detect the layout of the panorama input images
+* OpenGL Preview, which is now generally used as the standard preview for panoramas in hugin
-* list successful projects, maybe only select ones
+=== If your organization participated in past GSoCs, please let us know the ratio of students passing to students allocated, e.g. 2006: 3/6 for 3 out of 6 students passed in 2006. ===
+: 4/5
-=== Who will your organization administrator be? Please include Google Account information. ===
+: 4/5
-* Who's up for it? Can we do a job-share?
-=== What license(s) does your project use? ===
+: 4/5
-Both hugin, enblend/enfuse, panotools and matchpoint use GPL v2 or above.
+: 4/4
 === What is the URL for your ideas page? ===
 http://wiki.panotools.org/GSOC_2011_Ideas
 === What is the main development mailing list or forum for your organization? ===
-https://groups.google.com/forum/?pli=1#!forum/hugin-ptx or http://lists.sourceforge.net/lists/listinfo/panotools-devel
+The google group [http://googlegroups.com/group/hugin-ptx/ hugin and other free panoramic software], is our main mailing list, where we have a lively and strong community with users and developers both very welcome.
 === What is the main IRC channel for your organization? ===
-Do we have any?
+irc.freenode.net #hugin. The IRC is not official, and is primarily users.
 === Does your organization have an application template you would like to see students use? If so, please provide it now. ===
 http://wiki.panotools.org/GSOC_2011_Student_Application
-=== Who will be your backup organization administrator? Please include Google Account information. ===
+=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible ===
-?
+We selected our mentors for their enthusiasm and availability during GSOC. Another strong point was experience, some have academic teaching experience and others have mentored in past GSoC editions.
+All mentors have hands on experience with our code base and a vast knowledge of the wider universe of code applied to produce stitched panoramas and other computational graphics.
-=== Who will your mentors be? Please include Google Account information. ===
-'''Jim Watters'''
-Jim is willing to be a mentor for projects that are more on the panotools side.
-He is a Software Engineer at JFL Peripheral Solution, in Ottawa, Ontario, Canada, where he designs software for scanners. An avid user of PanoTools since 2000. A growing contributer to the source code of PanoTools since Aug 2003 and a current maintainer of [http://panotools.sourceforge.net PanoTools]. Before receiving his degree in Computer Software in 1999, he received a diploma of Fine Art in Photography in 1990.
-Most recently his attention has been directed to creating Immersive Panoramic Video.
-His google associated account is jwatters at photocreations.ca.
-'''Mentor 2'''
-Bio
-=== What criteria did you use to select these individuals as mentors? Please be as specific as possible. ===
-* Academic experience - most of them are or will very soon become PhD and have mentoring experience
-* Hands on experience with our code
-* Knowledge of the wider universe of code applied to produce stitched panoramas
-=== Steering Committee ===
-Do we have a steering committee in 2011?
 === What is your plan for dealing with disappearing students? ===
+The very first thing we'll do is make sure that we pick the right students. Our estimations are going to be based on the following criteria:
-The very first thing we'll do is making sure we pick the right students. Our estimations are going to be based on the following criteria:
 * Students should be avid photographers;
-* Students should be able to prove that their programmings skill match our request;
+* Students should be able to prove that their programming skills match our request by successfully completing a vetting exercise that will test key skills and knowledge relevant to the proposed project;
-* Students should be able to prove that they have experience working with a mentor.
+* Students should be able to prove that they can communicate and work well with a mentor and with the community at large.
-We are going to do our best to have them understand that GSoC is a both (close to) full time job and fun, so that they treat it with responsibility, but do not consider it a total boredom.
+We are going to do our best to have them understand that GSoC is both (close to) a full time job and fun, so that they treat it with responsibility, but do not consider it a total bore.
 Next step is motivation.
@@ Line 71: / Line 65: @@
 The point of participating at GSoC for us is getting new contributors who bring innovation and stick to affiliated projects.
-In case a student cannot deliver good enough results we are not going to drop all the work he managed to do and keep development at highest possible pace to make sure the community around affiliated project will not suffer in any way and any amount of money invested to the project by Google isn't completely lost.
+In case a student cannot deliver good enough results, we are not going to drop all the work he managed to do; we will keep development at the highest possible pace, to make sure the community around the affiliated project will not suffer in any way, and any amount of money invested in the project by Google isn't completely lost.
 === 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 several backup mentors who can replace others. 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.
+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 several backup mentors who can replace each other. We will assign two mentors (primary and secondary) to each project. In the unlikely event that one of the two mentors disappears, recruiting efforts for a backup mentor will start immediately. Our community has enough depth to provide the necessary resources. It 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 appropriate gear to shoot panoramas and we will do all we can to share with them our passion for panoramas.
+First of all, we hope to recruit a student from the community, since Hugin's community is growing and vibrant. We will make sure that the student has the appropriate gear to shoot panoramas, and we will do all we can to share our passion for panoramas with them.
+=== If you are a small or new organization applying to GSoC, please list a larger, established GSoC organization or a Googler that can vouch for you here. ===
+Not necessary, since we have a track record with GSOC.
+=== If you are a large organization who is vouching for a small organization applying to GSoC for their first time this year, please list their name and why you think they'd be good candidates for GSoC here: ===
+Are we "large" and do we support a small organization?
+=== Anything else you'd like to tell us? ===
+How great it was for us in the last years?
-=== What will you do to ensure that your accepted students stick with the project after GSoC concludes? ===
+=== Backup Admin (Link ID): ===
+* Bruno Postle, (brunopostle) will act as a backup admin
 [[Category:Community:Project]]