GSoC_2009_Mentoring_Organization_Application

Michal Čihař edited this page Apr 18, 2016 · 2 revisions
Clone this wiki locally

About Your Organization

Description

We're creating phpMyAdmin (http://www.phpmyadmin.net/), a tool written in PHP intended to handle the administration of MySQL over the Web. It supports most MySQL features and is very widely used by hosting providers.

Why is your group applying to participate? What do you hope to gain by participating?

We would like to attract more developers to our team and bring new exciting features to our users. GSoC is great opportunity to achieve both goals.

What is the main public mailing list for your group?

https://lists.sourceforge.net/mailman/listinfo/phpmyadmin-users

What is the main IRC channel for your organization?

Channel #phpmyadmin on FreeNode

What criteria do you use to select the members of your group? Please be as specific as possible.

Selection was solely based on fact that a project developer is willing to act as a mentor. All of them are long standing developers and they have great knowledge of existing code base.

Has your group participated previously? If so, please summarize your involvement and any past successes and failures.

We did not participate directly, but in Google Summer of Code 2008 the MySQL project was kind enough to offer slots for two projects. Both projects are now in our code base and brought great improvement to our users, so we think both ended up successfully.

If your group has not previously participated, have you applied in the past? If so, for what sort of participation?

We did apply for Google Summer of Code 2008 the first time and we were not chosen directly.

What license does your organization use?

GNU GPL version 2.

What is the URL to the ideas list of your organization?

http://wiki.phpmyadmin.net/pma/SummerOfCode2009IdeasList

What is the main development mailing list for your group?

https://lists.sourceforge.net/mailman/listinfo/phpmyadmin-devel

What is the application template you would like contributors to your organization to use.

Name: What's your name?

Email / IRC / Jabber: Where can we contact you?

WWW / Blog: Do you have home page or blog?

Synopsis: A short description of your project.

Benefits to the users: What does your project bring to the users.

Deliverables: What will be the final output from your project?

Project Details: A more detailed description.

Project Schedule: Include timeline for minor milestones.

Bio: Tell us about yourself.

What is your plan for dealing with disappearing contributors?

To avoid contributors to disappear, we have to attract them enough. This will be done from beginning, where each contributor will participate on project specification and will be pushed to publish all information, so that he will get soon in touch with community and other people involved in the project. During the project lifetime, frequent communication is very important, so that contributor does not get out of members viewfinder.

What is your plan for dealing with disappearing members?

All members are long time developers of the project and thus have quite a big motivation not to disappear. In case this would happen, several other project developers are prepared to replace the member who has no time to continue in his work.

What steps will you take to encourage contributors to interact with your community before, during, and after the program?

Member will introduce a contributor to the community and the project (if it's not already done). Contributors should be subscribed to mailing lists and they will be asked about their status on a regular basis. Furthermore, they will be encouraged to write blog articles about their progress. Reporting progress will create feedback which will encourage contributors to interact. Generally the best way to encourage contributors is to communicate often, so that he know that somebody is interested in results.

What will you do to ensure that your accepted contributors stick with the project after the program concludes?

We believe that contributors who will successfully complete their GSoC project will find it reasonable to continue their activity in such a well known project to enhance their programming skills and possibly also to build their resume. Additionally, the sense of community involvement developed during the project will help the contributor stick with the phpMyAdmin project.

Who will be your backup organization administrator? Please include Google Account information.

The backup organization administrator will be Marc Delisle (Google account marc@phpmyadmin.net)

Who will your mentors be? Please include Google Account information.

marc@phpmyadmin.net, google@sebastianmendel.de, michal@cihar.com

Category:Google Summer of Code 2009