Page MenuHomePhabricator

GSoC 2011 Mentoring Organization Application
Updated 3,381 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 GSoC_2010_Application, 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. Describe your organization.
    • The Enlightenment Project ( is an open source project dedicated to providing an advanced window manager and associated graphical libraries, tools, and environments. Currently, the project is made up of two major components: the Enlightenment Window Manager, and the Enlightenment Foundation Libraries. These components are complimented by additional applications and libraries developed by a thriving community of programmers, graphic designers, and engineers.
    • While working on Development Release 17 of the Enlightenment window manager and 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 a modular canvas (Evas), an operating system abstraction layer (Ecore), and a canvas-based interface/layout library (Edje) that allows separation of interface and application logic (thus making every application that uses it "skinable" without requiring changes to the application code). These libraries are extremely fast and lightweight. Many mobile devices, smart phones, set-top boxes, and even refrigerators run GUIs built upon the EFL. EFL has been adopted for use by many companies and organizations, including Samsung, Openmoko, Maemo, Terrasoft, and the Canola project. Commercial support and development is also available from several vendors.
  1. Why is your organization applying to participate in GSoC 2011? What do you hope to gain by participating?
    • Google Summer of Code provides a unique solution to one of the most fundamental issues facing open source software developers: the conflict between giving away the fruits of one's labor and financially facilitating the continuance of said labor. Rather than forcing students to choose between writing code and paying bills, Google has created a program which allows them to do both. While Google may indirectly benefit from the overall betterment of open source software and the global community that drives it, the most direct and significant benefits are realized by the students themselves and the participating projects.
    • While some students are existing project contributors looking for ways to make stronger or more significant contributions to the communities they already know and love, others are new recruits seeking to give back or find a group to which they can belong. Our cutting-edge software provides students with a challenging, yet rewarding, environment in which to learn and grow; they, in turn, provide us with new perspectives, new ideas, and the youthful energy for which students are so well known. Past experience with GSoC has revealed it to be a compelling force for community growth, and we hope to return again this year to experience that force anew.
  1. Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.
    • We participated in 2008 and 2009 as a mentoring organization. We feel we had a very good overall experience. We accepted 8 students first year and 6 succeeded in completing their projects. The second year we received 3 students and all of them were successful. We believe the students had a good experience as well. Several of these past students are still active developers today. In our judgment, this is one of the surest signs of a successful mentoring process.
    • We've also learned some important lessons from our mistakes and failures in past years. The importance of continuous dialogue between mentor and mentee, and between the students and the community as a whole, cannot be overstated. We realized that a lack of communication may be a sign of a confused, frustrated, or unfocused student, and that the sooner the situation is addressed, the more likely it can be resolved (and failure avoided). We've also created some additional feedback and communication channels to insure that everyone involved in the various roles of the mentoring organization is acting as part of an efficient, effective team.
  1. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
    • We participated in Google Summer of Code in 2008 and 2009.
    • We applied in 2010.
  1. What license(s) does your project use?
    • New and Simplified BSD licenses: most old components
    • LGPL 2.1/3: newer components (eina, elementary, ethumb...)
  1. What is the URL for your ideas page?
  1. What is the main development mailing list for your organization?
  1. What is the main IRC channel for your organization?
    • #E on is our main IRC channel. User support is its primary focus; it also features on-topic chat and development discussion.
  1. Does your organization have an application template you would like to see students use? If so, please provide it now.
  1. Who will be your backup organization administrator?
    • Ian Caldwell (Inc)
  1. What criteria did you use to select these individuals as mentors? Please be as specific as possible.
    • They must be well-established developers with a history of quality code and responsible community involvement.
    • They must have demonstrated significant experience and exceptional knowledge in their functional area.
    • They must commit to being readily available to students for questions in order to assist them for the duration of the event.
  1. What is your plan for dealing with disappearing students?
    • Experience has shown us that disappearing students are most likely to be new to the community and have no other contacts amongst the project developers. This makes alternative means of communication with them rather difficult. We would, of course, use any and all means of contact of which we're aware and would notify Google of the situation. We would repeat our efforts frequently and consistently for as long as necessary or until the program ended. We hope to prevent such an occurrence by maintaining an open "dialogue" with regular commits and status reports both to mentors and to the community as a whole.
  1. What is your plan for dealing with disappearing mentors?
    • All mentors are required to be long-term, well-established developers respected both within our community and externally. The likelihood of such an occurrence is extremely remote. However, each student will be assigned at least one backup mentor who will be fully capable of stepping in and taking over if necessary. Other community developers may also be called upon to provide support and guidance should this situation present itself. Many of the developers know each other personally, so many alternative methods of contacting the mentors are available should any of them lose connectivity or be out of contact for any reason.
  1. What steps will you take to encourage students to interact with your project's community before, during and after the program?
    • 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.
    • Students will be encouraged to introduce themselves on the mailing lists and initiate dialogues with both users and developers.
    • Regular (weekly?) progress reports to the community will be highly encouraged, if not required.
    • Community discussion of design and implementation will occur over the mailing lists and IRC.
    • Testing and feedback from the community on their code will be provided.
    • All developers, especially mentors, will strive to be readily available for their mentoring needs.
    • Support and encouragement will be provided publicly on milestones and goals achieved.
    • After completion, we will discuss results and engage the students and the community in evaluations of the resulting technology and future directions for it.
  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. We feel we were very successful in this during previous years, and we will strive to continue our solid track record going forward.

Imported from
1 vtorri 2011-01-25 22:28:43
2 ravenlock 2011-02-27 07:15:50
3 ravenlock 2011-02-27 07:34:30
4 ravenlock 2011-02-27 07:37:15
5 ravenlock 2011-02-27 07:51:36
6 ravenlock 2011-02-27 07:55:24
7 inc 2011-02-27 18:29:04
8 inc 2011-02-27 18:39:11
9 ravenlock 2011-02-27 19:25:39
10 ravenlock 2011-02-27 19:26:37
11 ravenlock 2011-02-27 19:29:09
12 ravenlock 2011-02-27 20:04:47
13 ravenlock 2011-02-27 20:05:57
14 ravenlock 2011-02-27 20:06:08
15 antognolli 2011-02-28 17:37:56
16 ravenlock 2011-02-28 18:51:03
17 KainX 2011-03-01 23:19:21 Major rewording of some content
18 KainX 2011-03-02 19:54:00 More rewording and cleanups

Last Author
Last Edited
Aug 26 2013, 4:13 PM