Google Summer of Code/Application 2016

From Apertium
Jump to navigation Jump to search
Being prepared by mlforcada, new template!

Public Profile

Website URL

http://wiki.apertium.org

Tagline

A free/open-source rule-based machine translation platform

GCI Logo

Primary Open Source License

GNU General Public License version 3.0 (GPL-3.0)

Technology Tags

C++, Python, Perl, XML, finite-state technology

Topic Tags

machine translation, computer-aided translation, morphological analysis, natural language processing, human language technologies

Ideas list

http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code (to be updated)


Descriptions

Short Description

Free/open-source rule-based machine translation platform

Long Description

Apertium is a free/open-source machine translation platform, initially aimed at related-language pairs (such as Spanish–Catalan) but which has been expanded to deal with more divergent language pairs (such as English-Catalan). The platform provides

  1. a language-independent machine translation engine
  2. tools to manage the linguistic data necessary to build a machine translation system for a given language pair and
  3. linguistic data for a growing number of language pairs.


Proposals

Application instructions

We have a Wiki page with tips and an application template: [1] . Here are the main tips to help you when writing your GSOC application with Apertium.

  1. Be realistic: We're more likely to accept realistic ideas than far-out wacky ones. But if you have a wacky idea, we might still be interested if we can turn it into something achievable in 3 months.
  2. Be appropriate: Demonstrate you have a knowledge of Apertium, how it works and the problem it has that you'd like to solve.
  3. Have a plan: Three months may seem like a long time, but it isn't. Provide a weekly plan with dates and deliverables. Leave time for getting familiar with the platform — ideally before, or in the community bonding period — and for documentation. If you plan to work on a language pair, make yourself familiar with testvoc and other quality controls, and factor those in. If you know of any breaks or absences beforehand, mention them and plan around them.
  4. Get in contact ASAP!: We get lots of proposals: only a few are good. Contact your potential mentor as soon as possible: send your proposal to the mailing list, ask for feedback, and refine your application based on feedback. If you are remembered, you are more likely to be picked.
  5. Read the Ideas Page! If you find yourself asking 'do you have any Java/Python/Fortran/x86 assembler projects...' -- you didn't read the ideas page. Read the ideas page.

Proposal Tags=

new language pair, improve existing language pair, improving the engine, improved source-language analysis, improved bilingual transfer, new end-user application, improve existing end-user application, easing language data development, improving the apertium website, improved format management

Retrieved from "https://wiki.apertium.org/w/index.php?title=Google_Summer_of_Code/Application_2016&oldid=56603"