Page MenuHomePhabricator

GSoC 2009 Mentoring Organization Application
Updated 3,389 Days AgoPublic

Below is a copy of the application that we were required to fill out and the answers provided. The applications questions were very similar to last year, so our application looks quite familiar.

Q: What should a mentoring organization application look like?

A: In addition to anything else your organization would like to submit as an application, Google will be asking (at least) the following questions as part of the application process:

  1. LinkID
    • enlightenment
  1. Group Name
    • The Enlightenment Project
  1. Home Page
  1. Public E-Mail
  1. Describe your organization.
    • The Enlightenment Project is an open source project dedicated to providing advanced graphical libraries, tools, and environments. Currently, the project is made up of three different components: Enlightenment DR16, Enlightenment DR17, and the Enlightenment Foundation Libraries. While we are best known for the Enlightenment Window Manager itself, there is a long history of providing advanced libraries and tools to support the window manager and other applications, such as Imlib, Imlib2, and FnLib, which extend far beyond the window manager itself in scope. Presently, in development towards the DR17 Desktop Shell, we have created an entirely new set of libraries and tools that provide more power and flexibility than any other group of graphical libraries available: the Enlightenment Foundation Libraries. These libraries offer such functionality as an X11 canvas library (Evas), X11 abstraction layer (Ecore), and an canvas based interface layout library (Edje) that allows separation of interface and application logic (thus making every application that uses it "skinable"). These libraries are extremely fast and lightweight. So much so they have been adopted by many other organizations. Most notably, organizations such as Openmoko, Maemo, Terrasoft, the Canola project, and more.
  1. Why is your organization applying to participate in GSoC 2009? What do you hope to gain by participating?
    • The Google Summer of Code is one of the best open source events of the year. It provides students with engaging work for the summer, offers organizations the ability to recruit new blood, and pushes new source code into the wild. It is for those very reasons we wish to participate. We feel we have some project ideas that will be intriguing and challenging to a wide variety of students. While offering a student the opportunity to expand his/her horizons might be reward enough, the prospect of fresh contributors to a project is always a "Good Thing" (TM) as well. New contributors always bring new ideas and talents to a project offering the possibility of taking the project to new levels. If a Student is especially interested in Graphics, GUI design, Rendering pipelines and scaling down to Embedded space and up to high-end desktops, then We have a lot to offer as we generally tend to be on the bleeding edge of these things.
  1. What is the main public mailing list?
  1. Where is the main IRC channel
    • We can be reached on FreeNode. #e is for general purpose questions, while #edevelop is primarily code/development related.
  1. What criteria do you use to select the members of your group
    • Mentors must be well-known, long-term members of our community
    • Have a proven history of "Good Code" in our SVN
    • Must either be a managing developer for the area mentoring in, or be in good standing with the managing developer.
  1. Has your group participated previously? If so, please summarize your involvement and any past successes and failures.
    • We participated in 2008, and had a very good overall experience. We accepted 8 students last year and 6 succeeded in completing their projects. Several of them have continued on as participating members of our project. So, in addition to the great code produced from the event, we obtained long term project members. We consider it to have been a great success.
  1. If your group has not previously participated, have you applied in the past? If so, for what sort of participation?
    • N/A
  1. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
    • We applied in 2007.
  1. What license(s) does your project use? (Please choose from the list provided)
    • New and Simplified BSD licenses
  1. What is the URL for your ideas page?
  1. What is the main development mailing list or forum for your organization?
  1. What is the application template you would like contributors to your organization to use.
    • The Student Application Template can be found here.
  1. What is your plan for dealing with disappearing students?
    • Contact their peers or supervisor(s) if possible to find where they went to.
    • Ensure their code and work is continually put in a public place in our svn.
    • In the event of complete loss take their work and archive for future possibilities of picking it up again.
  1. What is your plan for dealing with disappearing mentors?
    • Each mentor presently has a backup mentor. Should a mentor become unavailable, the backup is ready to step in. Additionally, though they could not commit to providing their time through the duration of the event, we have a large community of whom many are mentor-capable and willing.
  1. What steps will you take to encourage students to interact with your project's community before, during and after the program?
    • Making the SoC event a positive experience for our students is one of our highest priorities. During our selection process the students will have a chance to meet their prospective mentors. After acceptance, we plan to announce our new students arrival on our mailing lists, as well as having an IRC "Ice Breaker" to meet the the rest of the community. Our intention is to keep them actively engaged in the community through:
    • Regular progress reports on their projects to the mailing lists
    • Community discussion and design over the mailing lists
    • Community testing and feedback on their code over both mailing lists and IRC.
    • Make sure we are readily available for their mentoring needs, and publicly provide generous amounts of positive feedback on milestones and goals achieved.
  1. What will you do to ensure that your accepted students stick with the project after GSoC concludes?
    • We hope that by providing a fun, supportive environment in which students are encouraged and guided toward making productive community contributions, we will foster a sense of pride and fraternity in the students which will last well beyond the conclusion of this program.

Although Google did not request mentors on the application, I am supplying them here for your conveniece:

Imported from
1 ravenlock 2009-03-12 12:59:09
2 ravenlock 2009-03-12 14:37:10
3 ravenlock 2009-03-12 20:38:51
4 ravenlock 2009-03-12 20:42:01
5 ravenlock 2009-03-12 21:00:18
6 ravenlock 2009-03-12 21:02:17
7 Sachiel 2009-03-13 05:57:10
8 KainX 2009-03-14 16:04:46

Last Author
Last Edited
Aug 26 2013, 3:28 PM