Page MenuHomePhabricator

GSoC 2010 Mentoring Organization Application
Updated 3,385 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 2009 Mentoring Organization 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 different components: Enlightenment Window Manager, 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 a canvas library (Evas), an operating system 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" without requiring changes to the application code). These libraries are extremely fast and lightweight. So much so they have been adopted by many other organizations. Most notably, organizations such as Samsung, Openmoko, Maemo, Terrasoft, the Canola project, and more.

  1. Why is your organization applying to participate in GSoC 2010? 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.
  2. Did your organization participate in past GSoCs? If so, please summarize your involvement and the successes and challenges of your participation.


    We participated in both 2009 and 2008, and 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. Our initial hope of having students to keep on with the project, after the Summer of Code is over, was fulfilled as a good amount of them continued to be active contributors or at least as experienced users that often help with good patches.
  3. If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?
  4. We did participate before.
  5. What license(s) does your project use?
    • New and Simplified BSD licenses: most old components
    • LGPL 2.1/3: newer components (eina, elementary, ethumb...)
  6. What is the URL for your ideas page?
  7. Google Summer of Code 2010 Project Ideas
  8. What is the main development mailing list for your organization?
  10. What is the main IRC channel for your organization?
  11. We can be reached on irc.freenode. #e is for general purpose questions, while #edevelop is primarily code/development related.
  12. Does your organization have an application template you would like to see students use? If so, please provide it now.
  13. Who will be your backup organization administrator?
    • Ian Caldwell (Inc)
  14. What criteria did you use to select these individuals as mentors? Please be as specific as possible.
    • They must be a member who has been around awhile.
    • They must be a developer who has shown experience and or exceptional knowledge in this area and as well made multiple extensive commits proving their knowledge.
    • They must be readily available to students for questions in order to assist them.
    • **TODO
    • TODO**
  15. 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 put their work in our archive for future possibilities of picking it up again.
  16. 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
  17. 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.
  18. What will you do to ensure that your accepted students stick with the project after GSoC concludes?
  19. 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 did this the last years and it worked quite well, of course there is always room for improvements!

Imported from
1 barbieri 2010-03-05 11:31:27 initial contents
2 inc 2010-03-05 11:38:38
3 vtorri 2010-03-05 21:02:20
4 vtorri 2010-03-05 21:02:47
5 Toma 2010-03-06 00:45:54
6 Toma 2010-03-06 16:53:35
7 Toma 2010-03-06 17:02:55
8 Toma 2010-03-06 17:03:43
9 devilhorns 2010-03-07 21:01:46

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