Google Summer of Code/Application 2019

From Apertium
Jump to navigation Jump to search

To transfer to the application

Apertium profile (we have to provide one)

Website URL

http://wiki.apertium.org

Tagline

A free/open-source machine translation platform

Primary Open Source License

GNU General Public License version 3

Organization Category

Other

Technology Tags

C++ python bash XML

Topic Tags

machine translation natural language processing less-resourced languages

Ideas List

Short Description

Long Description

Application Instructions

Proposal Tags

Chat, Mailing List, or Email

Chat: http://wiki.apertium.org/wiki/IRC

Mailing list: https://lists.sourceforge.net/lists/listinfo/apertium-stuff

Application

Why does your org want to participate in Google Summer of Code?

OLD TEXT

  • Apertium loves GSoC: it is a programme that supports free/open-source (FOS) software as much as we do!
  • Apertium needs GSoC: it offers an incredible opportunity (and resources!) allowing us to spread the word about our project, to attract new developers and consolidate the contribution of existing developers through mentoring and to improve the platform in many ways: improving the engine, generating new tools and user interfaces, making Apertium available to other applications, improving the quality of the languages currently supported, adding new languages to it.
  • Apertium is committed to the advancement of less-resourced languages and GSoC gives an opportunity for computer-literate students speaking those challenged languages to generate FOS language technologies for them.

By participating we will gain: more students getting to know FOS software and the ethos that comes with it, contributing to it and, very especially students who are passionate about languages and computers.

How many potential mentors have agreed to mentor this year?

How will you keep mentors engaged with their students?

OLD TEXT

We select our mentors among very active developers, with long-term commitment to this decade-old project — they are people we know well and whom we have met face-to-face at conferences, workshops or even in daily life; some of them teach and do research at universities or work at companies using Apertium. For this reason, it is quite unlikely for mentors to disappear, since of them are well embedded in our community. However, there is always the possibility that some problem comes up, so we also assign backup mentors to all students, in many cases more than one backup. If a mentor cannot continue for whatever reason, one of the backup co-mentors will take over, and one of the organisation administrators will take on the role of second backup mentor.

How will you help your students stay on schedule to complete their projects?

How will you get your students involved in your community during GSoC?

How will you keep students involved with your community after GSoC?

Has your org been accepted as a mentor org in Google Summer of Code before?

Yes: 2009-2014, 2016-2018

For each year your organization has participated, provide the counts of successful and total students.

  • 2009: 8 pass out of 9
  • 2010: 8 pass out of 9
  • 2011: 9 pass out of 11
  • 2012: 10 pass out of 11
  • 2013: 10 pass out of 11
  • 2014: 15 pass out of 16
  • 2016: 11 pass out of 12
  • 2017: 10 pass out of 12
  • 2018: ???

What year was your project started?

2004 (first Google Summer of Code 2009)

Where does your source code live?

http://github.com/apertium (and some of it still in http://sf.net/projects/apertium)

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