GSoC: 2012
Google Summer of Code 2011
We missed the deadline for Google Summer of Code 2010 so preparations begin now to get projects, mentors and students in place for 2011.
Instructions common to Students, Mentors, Support Staff
All participants should take a look at the Summer of Code Program every now and then to be informed about updates and advices. It is also important to read the Summer of Code FAQ, as it contains useful information.
All participants will need a Google account in order to join the program. You'll save some time if you create one now.
Project Application
Mentor projects need to provide a minimum level of info about the project as detailed at http://code.google.com/soc/2008/org_signup.html This section is meant to provide copy/paste text that may be pasted into the aforementioned application form, please feel free to populate with contents.
Describe your Organization
- http://www.flightgear.org/introduction.html
- Open Source flight simulator framework
- written in C++
- multi-platform simulator
- has been in development for over a decade now
- licensed under GNU GPL
- framework used for various efforts (science, educational etc)
- recently released version 2.0
- goals of the project: Long Term Goals
- developed by contributors from all over the world
- many contributors have a professional background in aviation, sciences, maths etc.
- has created a wealth of related sub projects
- major features (property tree, highly configurable, XML-based configuration files, fully exposed internals)
- link to good reviews
Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating?
- increase awareness of the project
- get new contributors interested in the flightgear project
- recruit additional manpower
- achieve specific project goals that require full-time effort
Did your organization participate in previous GSoC years? If so, please summarize your involvement and the successes and failures of your student projects. (optional)
No, the FlightGear project has not previously participated in GSoC.
If your organization has not previously participated in GSoC, have you applied in the past?
No, there have been no previous applications.
What license does your project use?
The GNU GPL
URL for your ideas page
What is the main development mailing list for your organization?
flightgear-devel@lists.sourceforge.net: https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Archives:
- http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-devel
- http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/
Where is the main IRC channel for your organization?
- #flightgear irc.flightgear.org
- #FG-GSoC on irc.flightgear.org to co-ordinate our GSoC participation
Does your organization have an application template you would like to see students use?
Not yet, still needs to be created - can be done on this wiki page, and then be linked to directly.
Who will be your backup organization administrator?
Please enter their Google Account address. We will email them to confirm, your organization will not become active until they respond.
Mentors
What criteria did you use to select these individuals as mentors? Please be as specific as possible.
Experienced FlightGear developers with a track record of contributions to the relevant area.
Who will your mentors be?
see GSoC: Mentors
About the Program
What is your plan for dealing with disappearing students?
What is your plan for dealing with disappearing mentors?
We intend to have multiple mentors for each student so that a disappearing mentor, while unfortunate, is not necessarily critical
What steps will you take to encourage students to interact with your project's community before, during and after the program?
Any potential student will be expected to be active on IRC and/or the dev mailing-list for some weeks/months prior to acceptance as a candidate.
What will you do to ensure that your accepted students stick with the project after GSoC concludes?
As any code developed will be an integral part of the project, we would expect them to be willing to stick around and assist with further integration and development of that code. Willingness to become part of our community will be an important factor in candidate selection.
Related Pages
Useful Links
GSoC User Guide 2010 [1] The BZFlag GSoC Post Motem report 2007 [2]
| This article is a stub. You can help the wiki by expanding it. |