MySQL absent from Google Summer of Code this year

hingo's picture

Google Summer of Code is now open for student applications and people (like Ronald Bradford) are noticing that MySQL is not participating this year. (Drizzle otoh is a mentoring organization.)

As noted by LenZ in Ronald's blog, we did apply, but did not get selected. In detail, what happened was that Colin Charles from Monty Program was in contact with his former collagues at Oracle, and found out that they had no plans to apply for GSoC this year. I of course have little insight into the motivations and prioritizations of Oracle managers, but I guess it is safe to assume that "the person who used to be the MySQL administrator for GSoC does not work for MySQL/Oracle anymore" must have been a strong contributing factor. Since Colin is that person, it was agreed that he would submit the GSoC application in usual fashion, after which MySQL developers from any fork or employer could become mentors under that umbrella.

Since we cannot use the project name "MySQL" that is owned and trademarked by Oracle, the application was submitted as "MariaDB" but the text made notice that MySQL's community team is on board with it.

Alas, the GSoC is becoming increasingly popular, and Google's team had a hard time selecting among the many applications. In the end our application was not selected. Since MySQL is one of the leading Open Source projects in the world, and had participated every year, this was a bit of a disappointment. Reviewing the application I can only conclude that on Google's end (even with the personal connections we have and everything) our application may have looked like some small fork, and it may have been unclear to them what the relationship this really has "with the real MySQL", etc.

This is the cost of a project forking. (Or, as Philip Antoniades argued, in this case it's not even a proper fork, yet we carry some of the same downsides here...) In the short term it is costly for each of the branches and things like this happen. It is unfortunate, and one can only hope that in the long term the forking proves worthwile.

Which is to say, better luck next time!

(You can still contribute code to MariaDB during the Summer, we'll be happy to mentor you :-)

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Anonymous friend's picture

PHP,another popular

PHP,another popular opensource project wasn't chosen either: same happened to other "popular" projects, maybe they decided to change the projects a bit?

hingo's picture

PHP not selected either

I didn't notice that. Weird. So maybe they did choose new projects and some of the established projects were left out? Which others in the league of PHP and MySQL are out?

Mark Callaghan's picture

Kudos to Drizzle

Without passing judgement on MariaDB, Drizzle has done a great job building a community of developers and is a great fit for GSoC.

hingo's picture

Go Drizzle

Indeed, and thanks for not passing judgement on MariaDB :-)

If we could combine the best parts of Drizzle (community, modularity, easier to work on) and MariaDB (production quality, backward compatible) I would be happy.

Anyway, Drizzle is doing a great job with the students that flooded their IRC channel last week, they certainly deserve their GSoC ticket.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Use [fn]...[/fn] (or <fn>...</fn>) to insert automatically numbered footnotes.
  • Allowed HTML tags: <h1> <h2> <h3> <h4> <p> <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <br> <sup> <div> <blockquote> <pre> <img>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically. (Better URL filter.)

This question is for testing whether you are a human visitor and to prevent automated spam submissions.