[Wiki] changed: GSoC2010Application

jan  Fri, 12 Mar 2010 12:09:06 -0500

Modified page: http://wiki.horde.org/GSoC2010Application
New Revision:  1.1
Change log:  Start answering application

@@ -1,2 +1,62 @@
  + Google Summer of Code 2010 Application
+
+   1. Describe your organization.
+
+The Horde project is home for the Horde application framework written in PHP.
+The application framework is currently the basis for 45 applications  
written by developers from around the world, including the flagship  
IMP Webmail client, the popular Chora repository viewer, and a  
complete groupware suite. The guiding principles of the Horde Project  
are to create solid standard-based applications using intelligent  
object oriented design, and wide-ranging platform and backend support.  
There is great emphasis on making Horde as friendly to non-English  
speakers as possible. The Horde Framework currently supports many  
localization features such as unicode and right-to-left text, and is  
shipped with translations in over 40 languages.
+The Horde project is around since 1998 and has actively been  
maintaining and updating its code base ever since then. It was one of  
the first larger PHP projects and has set standards for object  
oriented PHP development until this day.
+
+   2. Why is your organization applying to participate in GSoC 2010?  
What do you hope to gain by participating?
+
+2010 is a milestone for the Horde project because we will be  
releasing the next major version of our application framework Horde 4.  
This will go along with a modernization of our applications, focusing  
on improved usability and ajax interfaces; a PHP component library for  
custom PHP development; and focusing on state-of-the-art PHP 5  
development practices. We hope to both inspire new developers to jump  
on the bandwagon with a modernized development environment, and also  
get help for driving the project forward and finish this process even  
faster.
+
+   3. Did your organization participate in past GSoCs? If so, please  
summarize your involvement and the successes and challenges of your  
participation.
+
+We participated in GSoCs 2005 and 2006 with a number of students. It  
was a great and exciting experience taking part at the very first  
GSoCs. But we also met some shortcomings with a few of the students  
and projects that helped us to learn how to improve the mentoring  
process for upcoming GSoCs. Problems we faced were students who need a  
stronger leadership than expected to keep in touch with the projects,  
share their progress, and really finish their work.
+
+   4. If your organization has not previously participated in GSoC,  
have you applied in the past? If so, for what year(s)?
+   5. What license(s) does your project use?
+
+OSI approved licences that vary over the different modules, mostly  
LGPL, GPL, ASL and BSD.
+
+   6. What is the URL for your ideas page?
+
+http://wiki.horde.org/SummerOfCode2010
+
+   7. What is the main development mailing list for your organization?
+
+http://lists.horde.org/mailman/listinfo/dev
+
+   8. What is the main IRC channel for your organization?
+
+#horde @ freenode
+
+   9. Does your organization have an application template you would  
like to see students use? If so, please provide it now.
+
+No.
+
+  10. Who will be your backup organization administrator?
+
+Michael Rubinsky ([email protected]) and Chuck Hagenbuch  
([email protected]) in that order
+
+  11. What criteria did you use to select these individuals as  
mentors? Please be as specific as possible.
+
+Our mentors are all developers who have been active members of the  
project for many years and are still active in current development.  
All of them have proven their development skills by contributing  
substantial and well written code to the project. They share a sense  
of social skills to as they are actively helping users, administrators  
and other developers on the mailing lists and on IRC on a daily basis.
+
+  12. What is your plan for dealing with disappearing students?
+
+First of all we will try hard to not let them disappear at all. From  
our experiences in the past we've learned that we need to keep close  
contact to the students from the very beginning and demand regular,  
active status updates. We won't allow any local development but  
require them to use the public SCM repository right from the start and  
commit early and often. They have to be available for direct  
communication through IRC or IM.
+If they fall off the earth and can't be reached by any means like IM,  
direct mail, or phone calls as a last resort, there is not much we can  
do though obviously. If we reach them we will try to find out what  
kept them from sticking to our rules, and how to improve working  
together.
+
+  13. What is your plan for dealing with disappearing mentors?
+
+We don't expect any mentors to disappear because we talk to each  
other on a daily basis and have known each other for years. If a  
mentor has to pass because of illness or similar, there are more  
developers on the project that may be able take over mentorship. And  
of course the other mentors can jump in too.
+
+  14. What steps will you take to encourage students to interact with  
your project's community before, during and after the program?
+
+We will try to give them a warm welcome and introduce them to the  
project personally as good as possible. Before the program ends we  
will discuss with them how they could imagine to further contribute to  
the project, and what roles we as the mentors see for them in the  
community. We will also try to keep them attached to their projects by  
involving them into the bug reporting and release processes as far as  
their work is affected.
+
+  15. What will you do to ensure that your accepted students stick  
with the project after GSoC concludes?
+
+See above? No idea.



-- 
To unsubscribe, mail: [email protected]