GSoC_2018_mentoring_organization_application

Deven Bansod edited this page Jan 21, 2018 · 6 revisions

This is a draft of the application that the phpMyAdmin project will send to Google to apply as a mentoring organization. Students should most likely look at the applicant guide.

Why does your org want to participate in Google Summer of Code?

We got great contributions through GSoC in previous years and we want to continue improving our tool and bring new features to our users. We also want to attract new young developers to our team.

How many potential mentors have agreed to mentor this year?

4

How will you keep mentors engaged with their students?

Each mentor is a longstanding member of the project and have had prior GSoC experience. Each one is qualified to engage with students independently, which mostly occurs via email on the developer discussion email list. Additionally, each student will be a part of the mailing list where the other mentors and developers monitor their progress and discuss their projects.

How will you help your students stay on schedule to complete their projects?

Each student is expected to submit a proposed schedule as part of their application process. This schedule lists deadlines and the students are expected to follow this schedule. Student progress is monitored through regular code submissions, and their code is usually merged in to the primary development branch as soon as possible. For some of our proposed projects, this will mean student code is getting merged once or twice per week. With the remaining projects students are expected to post their code often for their mentor to review, monitor progress, and watch for any problems or pitfalls.

How will you get your students involved in your community during GSoC?

Students are asked to introduce themselves on the mailing list as part of the application process, and the mailing list continues to be an important part of their involvement throughout the summer. The mailing list is the same one where most project discussion occurs, plus students are encouraged to participate in the monthly developer IRC meetings. Students are included in the community by nature; almost all of their communication is through the same means used by community and the way their code is quickly merged will help them integrate in to our community.

How will you keep students involved with your community after GSoC?

We will show them during the program, that being part of the phpMyAdmin team would be a great experience for them. We also have prepared a specific page about this (https://github.com/phpmyadmin/phpmyadmin/wiki/GSoC_after_the_summer).

Has your org been accepted as a mentoring org in Google Summer of Code before?

Yes, except for 2016, we have participated in GSoC since 2008 (in 2008 and 2009 we participated under the MySQL project).

What is your success/fail rate per year?

  • 2008 2/2 100%
  • 2009 4/5 80%
  • 2010 7/7 100%
  • 2011 7/8 86%
  • 2012 5/6 83%
  • 2013 6/6 100%
  • 2014 6/6 100%
  • 2015 4/4 100% *
  • 2017 3/3 100%

* One student was hired by Google during GSoC, so we accepted five, but ended up with four.

Note that 2008 and 2009 were both under the MySQL program as we were not directly a mentoring organization.

If your org has applied for GSoC before but not been accepted, select the years:

  • 2016
  • 2009
  • 2008

Are you part of a foundation/umbrella organization?

Yes, Software Freedom Conservancy.

What year was your project started?

1998

Where does your source code live?

https://github.com/phpmyadmin/

Anything else we should know?

Category:Google Summer of Code 2018

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.