GSOC 2011 Application

From PanoTools.org Wiki
(Difference between revisions)
Jump to: navigation, search
(copied over from 2007, search&replaced 2007 with 2011)
 
(removed unnecessary stuff)
 
(39 intermediate revisions by 4 users not shown)
Line 1: Line 1:
=== Describe your organization ===
+
=== Organization Name ===
 +
Hugin - Panorama photo stitcher
  
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.
+
=== 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.
  
=== Why is your organization applying to participate in GSoC 2008? What do you hope to gain by participating? ===
+
Details in our community charter http://hugin.sourceforge.net/community/charter/
  
http://www.flickr.com/search/groups/?q=hugin
+
=== Home page ===
 +
http://hugin.sf.net
  
http://www.flickr.com/photos/sbprzd/2126554118/
+
=== Main Organization License ===
 +
GNU General Public License (GPL)
  
http://www.flickr.com/photos/sbprzd/2125768589/
+
=== 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. ===
 
=== 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
  
hugin/panotools participated in GSoC 2011. We consider this participation successful for both organization and students. Our projects were:
+
=== 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
  
* New extensible modular GUI framework for Panorama Photography. Ippei Ukai has refactored the hugin code, cleaning the interface and prepared for future Qt development while keeping wxWidgets compatibility. The upcoming hugin release will still use wxWidgets mainly because the development of specific Qt widgets is very time consuming. However, future plans are also to provide hooks for rapid GUI development with higher level languages such as Python, and it will benefit largely from his refactorization as well.
+
2008: 4/5
* Anti-ghosting HDR panorama blending and merging algorithm. During GSoC Jing presented her results at the IVRPA conference in Berkeley. She successfully finished the project and the code is now merged into hugin source code tree which we expect to release as 0.7.4 soon.
+
* Interactive Panoramic Viewer. This is a work on FreePV panoramic viewer. Since GSoC the work is still happening in the [http://freepv.svn.sourceforge.net/viewvc/freepv/freepv/branches/branch_leonox/ SoC branch of SVN]. There is no release featuring changes done by the student yet. It is quite possible to see FreePV code being integrated into VLC which is a popular cross-platform media viewer.
+
* Feature matching for panoramic images. Zoran Mesec successfully created Matchpoint - a new automatic control points generator that isn't affected by patents. Zoran also volunteered to be mentor for further Matchpoint development this year in GSoC2008 which shows his constant involvement into the project.
+
* VIPS integration. This project was supposed to bring very large images support to hugin, but failed.
+
  
=== Who will your organization administrator be? Please include Google Account information. ===
+
2009: 4/5
  
Alexandre Prokoudine will be primary administrator. He currently resides in Moscow, Russia. He is involved into open source projects since early 2002 as technical writer, GUI translator (hugin, Inkscape, Scribus, Audacity, Rosegarden etc.) and functional specifications author.
+
2010: 4/4
 
+
Being interested in design and photography since 2005 he quickly started enjoying his role of communicator between developers of various open source projects. In 2006 Jon Philips, a Creative Commons advocate, and he co-founded a CREATE project where developers of creative applications (mostly graphics related ones as of now) can meet and work out standards, unified approaches to solving real life user issues etc.
+
 
+
In 2011 Alexandre served as backup administrator of hugin/panotools and Scribus organizations for Google Summer of Code.
+
 
+
His Google account is alexandre.prokoudine@gmail.com
+
 
+
=== What license(s) does your project use? ===
+
 
+
Both hugin, enblend/enfuse, panotools and matchpoint use GPL v2 or above.
+
  
 
=== What is the URL for your ideas page? ===
 
=== What is the URL for your ideas page? ===
 
+
http://wiki.panotools.org/GSOC_2011_Ideas
http://wiki.panotools.org/SoC_2008_ideas
+
  
 
=== What is the main development mailing list or forum for your organization? ===
 
=== What is the main development mailing list or forum for your organization? ===
 
+
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.
http://lists.sourceforge.net/lists/listinfo/panotools-devel
+
  
 
=== What is the main IRC channel for your organization? ===
 
=== What is the main IRC channel for your organization? ===
 +
irc.freenode.net #hugin. The IRC is not official, and is primarily users.
  
We do not use IRC for communication. During GSoC 2011 we used Skype, but this is unlikely to happen again.
 
  
 
=== Does your organization have an application template you would like to see students use? If so, please provide it now. ===
 
=== 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
  
*  name / university / current enrollment
+
=== What criteria did you use to select the individuals who will act as mentors for your organization? Please be as specific as possible ===
* short bio / overview of your educational background
+
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.
* did you ever code in C or C++, yes/no? please provide examples of code.
+
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.
* do you photograph panoramas? please provide examples.
+
* do you make other use of hugin/panotools than for stitching panoramas? please describe and show examples.
+
* were you involved in hugin/panotools development in the past? what was your contribution?
+
* were you involved in other OpenSource development projects in the past? which, when and in what role?
+
* why have you chosen your development idea and what do you expect from your implementation?
+
* how much time you plan to invest in the project? (we expected full time 40h/week but better make this explicit)
+
* please provide a schedule of how this time will be spent on subtasks of the project. While this is only preliminary, be aware that at the beginning of the project you will be required to provide a detailed plan, and during the project you will issue weekly progress reports against that plan.
+
 
+
=== Who will be your backup organization administrator? Please include Google Account information. ===
+
Yuval Levy is chosen to be backup administrator. He did a perfect job as primary administrator during GSoC 2011. His Google associated email address is google at levy.ch.
+
 
+
=== Who will your mentors be? Please include Google Account information. ===
+
 
+
'''Pablo d'Angelo'''
+
 
+
Pablo d'Angelo is the initiator and main developer of the hugin project. He has studied computer engineering at the University of applied sciences Ulm, and is currently working at the DaimlerChrysler Research Center in Ulm, where he does research on advanced 3D reconstruction techniques for industrial quality inspection. He also has a PhD in the field of computer vision from the University of Bielefeld, which was granted in Summer 2011.
+
 
+
His Google associated account is pablo.dangelo at web.de.
+
 
+
''' Andrew Mihal '''
+
 
+
Andrew Mihal is the project lead and main developer of the Enblend/Enfuse project. He received his Ph.D. in Electrical Engineering and Computer Science from the University of California, Berkeley. His specialization is in software for electronic design automation. He is also an amateur photographer, and enjoys turning academic research papers into useful open source projects as a hobby.
+
 
+
His Google associated account is andrewcmihal at gmail.com
+
 
+
''' Jim Watters '''
+
 
+
Jim Watters 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 PanoTools (http://panotools.sourceforge.net).  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.
+
 
+
''' Daniel M German '''
+
 
+
He is assistant professor at the Department of Computer Science at the University of Victoria, in British Columbia, in Canada. He received his PhD in Computer Science from the University of Waterloo in Canada.
+
 
+
One of his areas of research is open source software development. He is interested in understanding how globally distributed individuals are able to work together to create commercial strength software. He has also explored the use of historical artefacts (such as version control logs, emails, defect tracking) to understand how a system has evolved and how this information can be used to continue its development.
+
 
+
More recently he has been interested in the field of computational photography. More specifically on how to project extreme wide-angle images and spherical panoramas into acceptable flat representations.
+
 
+
During the last year he has been the maintainer of Panotools (http://panotools.sourceforge.net).
+
 
+
As a university professor one of his jobs is the supervision of students. He has graduated 6 Master's students, and currently supervising 3 Master's, and 1 Ph.D. Student. He has supervised more than a dozen honours projects of undergraduate students in computer science.
+
 
+
He is an avid photographer. His works have been exhibited in several galleries.
+
 
+
His Google associated account is dmg at uvic.ca.
+
 
+
''' Alexandre Jenny '''
+
 
+
Alexandre Jenny is graduate from Ecole des mines de Nancy, in physics and computer sciences. He spent 5 years in the computer game industry before starting to interest in panoramic.
+
 
+
He's casual photographer and he started interest in panorama when he moved near Alps mountains. After having climbed during 5 hours and reached the top, it's really frustrating not beeing able to capture the whole panorama. So he started studying this field at this time. It was during the very early stage of Panotools. The main problem was not being able to create automatically controls points, so he wrote the first SIFT control point generator which is always used a lot today as a Panotools plugin : autopano v1.03.
+
 
+
After this first release and because he felt that some business could be build upon panoramic, he founded Kolor, a well know business which is the creator of [http://www.autopano.net Autopano Pro], a fully automatic stitcher. Autopano Pro uses an industrial strong implementation of the SIFT algorithm, but has also many other features in a single easy to use package.
+
 
+
His Google associated account is alexandrejenny at gmail.com.
+
 
+
'''Zoran Mesec'''
+
 
+
He is a student in the final year of undergraduate study of Computer and Information Science at University of Ljubljana. He has been a part of hugin's participation at GSoC 07 as a student where he successfully completed the project [[SoC2011_projects#Automatic_feature_detection_for_panoramic_images]] under the mentorship of dr. Bay. He continued to develop his work during the year and created MatchPoint, automatic control point suite. This year he is taking GSoC at a higher level, based on his past experience and knowledge in computer science and photography.
+
 
+
His Google associated account is zoran.mesec@gmail.com.
+
 
+
=== 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
+
* most of them have practical experience of applying the code to panorama production
+
 
+
=== Steering Committee ===
+
 
+
This year we also have a steering committee - a group of professionals in panorama making that will help us support our students.
+
 
+
'''G. Donald Bain'''
+
 
+
G. Donald Bain manages the Geography Computing Facility at the University of California Berkeley, where he also teaches cartography and field studies. The rest of the time he devotes to VR.
+
 
+
Hi is a board member of IVRPA.
+
 
+
He travels and take panoramas for his web site: [http://virtualguidebooks.com/ Don Bain's Virtual Guidebooks]. This project (his wife refers to it as his obsession) has taken him from Tahiti to the Arctic, from the prehistoric ruins of the Southwest to the glaciers of the Canadian Rockies. As a compulsive educator it has been a real treat, documenting and sharing his landscapes with the world. He has taken over 4000 panoramas, with about 3500 currently on the site.
+
 
+
He co-founded the World Wide Panorama, the largest international collaborative effort showcasing over 3000 panoramas from VR-artists all over the world taken over 11 editions.
+
 
+
'''Yuval Levy'''
+
 
+
Last year's GSoC admin for this team. [http://www.photopla.net/] [http://panospace.wordpress.com/]
+
 
+
'''Bruno Postle'''
+
 
+
Bruno Postle trained as an architect and now works designing and engineering lightweight/portable/temporary buildings, monumental sculptures and anything else that comes along.  Bruno has been a long-time contributor to the [[hugin]] project, and maintains a number of CPAN modules including [http://search.cpan.org/dist/Panotools-Script/ Panotools::Script], a module for manipulating hugin project files. He also [http://www.flickr.com/photos/36383814@N00/ takes panoramic photographs].
+
 
+
'''Thomas Rauscher'''
+
 
+
Thomas Rauscher is graduate student at Vienna University of Technology in computer graphics, contributed to several parts of the PanoTools like [[PanoTools Anti Aliasing Filters]], started the [[Freepv]] sourceforge project, and he is a moderator and web admin for PanoTools mailing list. He is also working 3 years in this field with his company [http://gardengnomesoftware.com/ Garden Gnome Software]. In GSoc2011 he help mentoring the [[Interactive Panoramic Viewer]] project.
+
 
+
'''Ken Turkowski'''
+
 
+
He is project leader, director, technical contributor, and/or consultant in the areas of 3D graphics, 2D graphics, digital video, image processing, computer vision, image compression, signal processing, dynamics and numerical analysis. Years ago he led research group of QuickTimeVR - the first panoramic images viewer.
+
  
 
=== What is your plan for dealing with disappearing students? ===
 
=== 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 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.
  
* students should be avid photographers;
+
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.
* students should be able to prove that their programmings skill match our request;
+
* students should be able to prove that they have experience working with a mentor.
+
 
+
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.
+
  
 
Next step is motivation.  
 
Next step is motivation.  
Line 168: Line 65:
 
The point of participating at GSoC for us is getting new contributors who bring innovation and stick to affiliated projects.
 
The point of participating at GSoC for us is getting new contributors who bring innovation and stick to affiliated projects.
  
Last year we organized delivery to student of brand new panoramic heads sponsored by their manufacturer - Agno's Tech Engineering. We are investigating such possibility for this year's project again.
+
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.
  
Depending on the context it might also be possible to structure the work as academic credits to further incentivation.
+
=== 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.
  
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.
+
=== 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.
  
=== What is your plan for dealing with disappearing mentors? ===
+
=== 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.
  
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.
+
=== 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?
=== 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. We have already organized a fund raiser to donate a fish-eye lens to one of the project maintainers [http://www.nabble.com/Fundraising-complete!-t2725697.html] in 2006, a pano head for each student in 2011, 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? ===
+
=== Anything else you'd like to tell us? ===
 +
How great it was for us in the last years?
  
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*. We intend to ask them to participate in the [http://www.worldwidepanorama.com/ World Wide Panorama].
+
=== Backup Admin (Link ID): ===
 +
* Bruno Postle, (brunopostle) will act as a backup admin
  
 
[[Category:Community:Project]]
 
[[Category:Community:Project]]

Latest revision as of 00:03, 23 March 2011

Contents

[edit] Organization Name

Hugin - Panorama photo stitcher

[edit] 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/

[edit] Home page

http://hugin.sf.net

[edit] Main Organization License

GNU General Public License (GPL)

[edit] 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.

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

No

[edit] 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

[edit] 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

[edit] What is the URL for your ideas page?

http://wiki.panotools.org/GSOC_2011_Ideas

[edit] 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.

[edit] What is the main IRC channel for your organization?

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


[edit] 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

[edit] 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.

[edit] 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.

[edit] 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.

[edit] 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.

[edit] 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.

[edit] 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?

[edit] Anything else you'd like to tell us?

How great it was for us in the last years?

[edit] Backup Admin (Link ID):

  • Bruno Postle, (brunopostle) will act as a backup admin
Personal tools
Namespaces

Variants
Actions
Navigation
tools
Tools