GSoC 2020

DBpedia GSoC 2020



For the 9th time in a row, DBpedia is part of the Google Summer of Code program (GSoC). In the past years, we mentored many successful projects by female students but mostly male applicants. Now, it is time to change this narrative and work towards more diversity in science.

This year, we at DBpedia are more determined than ever to encourage female students to apply for our projects. That being said, we already engaged excellent female mentors to also raise the female percentage in our mentor team. We are proud of all female DBpedians that help to shape the future DBpedia.

DBpedia is now looking for students who want to work with us during the summer. Check our project ideas or send us your own idea, no matter how detailed it is. We will help you to draft a suitable project proposal.

Want to find out more? Please, read on. 

Pre-Application Phase 

Go and read our project ideas in the DBpedia Forum. See if one of them appeals to you. If you have questions regarding the ideas, please read the FAQ's first and in case your problem isn't solved, comment directly on the idea. 
In this pre-application stage we kindly ask you to refrain from sending us e-mails or spamming other DBpedia channels with GSoC questions. In this phase, communication between you and us is preferred to happen solely through the Forum.
Exception: In case you want to apply with your own project idea, please send an email with a project draft to Please make sure the draft adheres to the structure of our project ideas. A detailed structure can be find on the bottom of this page.
Thank you for your consideration.

Application Phase - Please continue reading, If you are a candidate student

Official start of student application is March 16th, 2020. If you are certain about a project and like to participate in this year's GSoC, there are already a few things you can do. Please carefully read all of the instructions below and start getting in touch with us.
Please note: You have to officially apply through GSoC's website. Please make sure to get in touch with our mentors (preferably via GitHub) before finalizing your proposal in order to increase the quality of your idea.

In addition to the GSoC rules and for transparency reasons:

  • DBpedia does not accept any student that is affiliated with a DBpedia member organization.
  • Any relations between the student and current DBpedia mentors and/or DBpedia member organizations must be disclosed. Such relations does not exclude the student but, will be examined on a case by case basis. This is to ensure we have fair & equal treatment to all students.

Some hints before you apply for DBpedia projects

  • increase your visibility in the DBpedia Community
  • Start communicating with current DBpedia developers as early as possible
    • ​That way, you can get to know each other and tailor a proposal to something that DBpedia really needs and wants.
  • ​Join our  DBpedia-discussion -mailinglist, where we discuss current DBpedia developments. NOTE: all mails announcing tools or call to papers unrelated to DBpedia are not allowed. This is a community discussion list.
  • If you like to join DBpedia developers discussion and technical discussions sign up and join us in Slack
  • Become a DBpedia Student and sign up for free at the DBpedia Association.

Student Application Template

Please try to structure your application according to the following template. Feel free to use these questions as guiding questions for building your project proposal. While you are working on it, feel free to discuss your ideas with the DBpedia GSoC team in the DBpedia Forum or on our mailing list or the GSoC website.

You MUST submit your application on the GSoC website for your application to be eligible.

Application title: To ease the application evaluation, use the following template to name your proposal in the GSoC website

{Project-Name-From-Ideas-Page} - {Your-Name}
e.g. "Knowledge base embeddings for DBpedia - Sergey Brin"

Contact information

  • Your Name:
  • Email Address:
  • Instant messenger name and protocol (if any):
  • Any professional (e.g. github, linkedin) or personal (e.g. blog) URLs you would like to list:


  • Project Name: One of our suggestions?, or your own idea
  • Project Description: Your own description of the project and why it's interesting
  • If you would be willing and able to work on another of our suggested project ideas instead, which ones?
  • Please describe why you are interested in this specific project:
  • Please describe a tentative project architecture or an approach to it:
  • Please detail an expected project plan and timeline with milestones:
  • Please include in your plan how will you evaluate the performance of your contribution (in terms of time, or accuracy, or both), as well as which data sets you will use for that evaluation.

Technical skills

  • Please describe in a few lines your programming knowledge or experience (if any):
  • Please describe any other project related experience (if any):
  • Please provide one or more URLs to code samples that you have written in the past or to DBpedia Spotlight's SVN/issue tracker for which you have provided a fix in the form of a pull request. (Optional but highly appreciated if provided. Proof of code ownership is also required.):

Open Source

  • Please describe any previous Open Source development experience:
  • Why are you interested in Open Source development ?

Background & education

  • What school do you attend?
  • What is your specialty/major at the school?
  • How many years have you attended there?


  • What is your current research experience? Please point us to the best paper you have read (preferably in the context of your project proposal), and the best paper you have written, if any.
  • Would you be interested in co-authoring a conference paper with your mentors about your work in GSoC 2020?

Summer plans

  • What city/country will you be spending this summer in?
  • How much time do you expect to have for this project (est. per day and per week)?
  • Please list jobs, summer classes, and/or vacations that you'll need to work around:

GSoC Experience

  • Did you participate in a previous Summer of Code project? If so, please describe your project and experience:
  • Have you applied or do you plan to apply for any other 2017 Summer of Code projects? If so, which ones?
  • Why did you decide to apply for the Google Summer of Code ?
  • Why did you decide to apply for a DBpedia Spotlight project ?

And finally...

  • ... in 2 sentences, why should we take YOU ?