-
Notifications
You must be signed in to change notification settings - Fork 272
Warm up tasks
(Copied from spotlight, adapt)
If you are going to develop with the DBpedia team, it is important that you do the "everybody should do" tasks. It will be nice to look for tasks in our issue tracker, assign yourself, if nobody already is, and start discussing/working on the issue.
Note that these warm up tasks are targeted mainly to the selected GSoC students. Candidate students are also encouraged to try but it is not a requirement.
The best warm up task is to polish the user documentation. Read it up, ask questions, add the answers to these questions to the documentation so that the next guy doesn't have to ask them. We are slowly moving our documentation from the old wiki to the new wiki on Github. Please get the content from there, put in a new page here, save. Go back there, delete the old content and only leave a link to the new page here. Then polish the content here to contain what you looked for, didn't find and had to figure out by yourself. Fix typos (we type fast!), rephrase confusing sentences.
Download the latest code, build and try to run the software. Add to the documentation any error messages that you may find, or any information that we may have forgotten to add. Try first to run the server with files offered for download, instead of running the indexing process from scratch, because that can take a while.
You will quickly fall in love with the elegance of Scala's functional programming combined with object-oriented programming. We don't need to be the most idiomatic Scala programmers, but you'll quickly notice that some patterns just stick with you. You should invest at least an hour a day during the "community bonding period" to learn Scala. See, for example, the Scala School by the Twitter folks. We learned the language while building DBpedia Spotlight, so you can do it too.
We already tagged some tasks with the "GSoC Warm-Up Tasks". An easy task to start with could be issue #33 (ontology enrichment) or issue #12 (Disambiguate configuration). The former will give you an overview of the mapping process, while the latter of the framework internals.