Skip navigation

Following the original announcement, more than 70 students applied to the Go OpenOffice project for the Google Summer of Code. I was truely impressed, and want to say “thank you!” to all that took the sometimes considerable effort to write a good application.


Choosing six projects among those many was not easy; but I think the collective mentors did an outstanding job selecting both excellent students and relevant tasks – so I’m happy to announce this year’s Go OpenOffice GSoC participants (in order of their last name):

Andrés Correa Casablanca will work on performance improvements

Jesús Corrius will have Win32 OOo cross-compile under Linux

Maja Djordjevic will add Hyperlink/Reference navigation buttons

Dona Hertel will extend the functionality of the templates in Impress

Tzvetelina Tzeneva will improve OOo Writer’s document comparison

Jonathan Winandy will add an Ocropus OCR integration to OOo

Yay to the successful applicants!

To all those who applied, but have not been selected: the competition was fierce, I can assure you, so don’t be put off, try again next year – and maybe give yourself this extra bit of a head start and continue working on OOo! We’ll always and happily mentor you, if you’re enthusiastic and willing to learn – just come and ask us, you already know where!

That only leaves me to thank Google for sponsoring us; thanks to all who applied, thanks to the mentors – without you folks, all of this just won’t happen! Looking forward to a wonderful summer 2009!



  1. Hi,

    I would like to congratulate the students that have been accepted into the program.
    I have a question for Thorsten and the group of mentors
    from Go-OO. For which tasks will the accomplishments of this summer be
    contributed to and maintained in the source repository?

    Good luck with the projects

    • Regarding the question what code will be contributed to upstream OOo – well, the go-oo summer of code project was highlighted as clearly distinct from OOo:

      “We also have a distinctive approach to code ownership – believing that nicely separable pieces of code should not be assigned to, owned and exploited by a single corporate entity, but owned by all.”


      The students applied under these conditions, so I guess it’s fair to leave the exact implementation and the question of upstreaming (and the timing thereof) as a discussion between mentor and mentee over their jointly produced code. So I anticipate that much of the work will appear first in go-oo, and in some areas, code will be sent up-stream.

      It is a bit of a pity here that Sun did not engage with the process, and didn’t offer any mentors – as that would have given much more weight in this question.

      • As has been rejected in 2008 the project didn’t consider an application for GSoC 2009 promising. Instead we might prepare a program to foster code contributions and win new participants specific
        to as it was recommended by Google.

        I must have missed the evidence of the preparations by Go-OO to participate in GSoC. This would have given the chance to openly talk
        about ways to collaborate on tasks beforehand. You will certainly understand that many OOo contributors are not much induced to engage in a program that separates itself from

        I’m not sure students are fully aware that they work on “a branch, or distribution” and potentially do not “add to the project”. It would be much appreciated if the mentor/mentee pairs come to an agreement about the home of their code in an early stage. This helps contributors to think about the extent of a possible involvement.

        And actually students shouldn’t have to care about things like that but have fun and enjoy working on the code base.

        Again, good luck with the projects

  2. Thorsten: Your accusation of “not engaging” is inappropriate and I’d encourage you not to repeat it.

    Sun made many applications to GSoC last year for many projects, which was a lot of work as you can imagine, and all were rejected by Google out of hand. Google’s excuse was they were punishing Sun for the contract dispute between the Java business unit and Apache, but many, many people were very disappointed that they were treated not as community members but as “Sun”.

    This year I enquired in advance whether the same thing was going to happen again and Google told me proposals from Sun staff would not be welcome at GSoC. Sun staff will instantly engage with GSoC when we’re assured we’ll not be wasting our time by applying.

    • wrt. not engaging; we asked Sun community members to help mentor or co-mentor proposals. Certain code does go to Sun from ooo-build, and it seems a reasonable request. Those requests were turned down.

      Wrt. your unusual theories around Google’s motivation – I notice MySQL was sponsored for the last two years – and Google seems a reasonable company, and a good open source player to boot. *If* your explanation is fair, then I imagine Sun did something unbelievably shoddy to Google to provoke it. Given Sun’s past form around OO.o, that really wouldn’t surprise me.

2 Trackbacks/Pingbacks

  1. By GSoC 2009 Wrap-Up « Thorsten’s Weblog on 24 Oct 2009 at 1:43 pm

    […] gsoc With the mentor summit coming up, it’s high time to wrap up this year’s Google Summer of Code for ooo-build. We started the term with 6 students, of which one was sadly missing in action right from the […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: