Difference between revisions of "Google Summer of Code/Application 2016"

From Apertium
Jump to navigation Jump to search
(Created page with "::: Editing the 2015 application, which by the way, failed. ::: Mikel Forcada is already registering it at https://summerofcode.withgoogle.com/ but many details are missing. ...")
 
 
(27 intermediate revisions by 3 users not shown)
Line 1: Line 1:
  +
::Being prepared by mlforcada, new template!
−
::: Editing the 2015 application, which by the way, failed.
  
−
::: Mikel Forcada is already registering it at https://summerofcode.withgoogle.com/ but many details are missing.
  
   
  +
=Public Profile=
   
  +
==Website URL==
−
;Organisation ID*
  
  +
[http://wiki.apertium.org http://wiki.apertium.org]
   
  +
==Tagline==
−
;Organisation name*
  
  +
A free/open-source rule-based machine translation platform
   
  +
==Logo==
−
;Description*
  
  +
[https://lh3.googleusercontent.com/HybCGfSck0XU-z9--ERhU_JP9QYfgqNopMtOntcpE1R-UaxbOWQfgnwayFb_ImoySr4pckhQOwd9aJ34Cp95pQ=s300 GCI Logo]
   
  +
==Primary Open Source License==
−
;Tags
  
  +
GNU General Public License version 3.0 (GPL-3.0)
   
  +
==Technology Tags==
−
;Main license*
  
   
  +
C++, Python, Perl, XML, finite-state technology
−
GNU GPL 2.0 or later
  
   
  +
==Topic Tags==
−
;Ideas list*
  
  +
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
  
  +
[http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code]
  +
(to be updated)
   
−
;Mailing list
  
   
  +
=Descriptions=
−
https://lists.sourceforge.net/lists/listinfo/apertium-stuff
  
   
  +
==Short Description==
−
;Organisation website*
  
  +
Free/open-source rule-based machine translation platform
   
  +
==Long Description==
−
https://apertium.org
  
  +
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 and even Basque→English). The platform provides
   
  +
# a language-independent machine translation engine
−
;IRC Channel
  
  +
# tools to manage the linguistic data necessary to build a machine translation system for a given language pair and
  +
# linguistic data for a growing number of languages and language pairs
   
  +
=Proposals=
−
irc.freenode.net/#apertium
  
   
  +
==Application instructions==
−
;Feed URL
  
  +
We have a Wiki page with tips and an application template: [http://wiki.apertium.org/wiki/Top_tips_for_GSOC_applications] . Here are the main tips to help you when writing your GSOC application with Apertium.
  +
# 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.
  +
# Be appropriate: Demonstrate you have a knowledge of Apertium, how it works and the problem it has that you'd like to solve.
  +
# 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.
  +
# 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, hang out on IRC, ask for feedback, and refine your application based on feedback. If you are remembered, you are more likely to be picked.
  +
#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==
−
;Google+ URL
  
  +
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
   
  +
=Contact Methods=
−
;Twitter URL
  
   
  +
==IRC Channel==
−
;Blog page
  
  +
  +
[http://wiki.apertium.org/wiki/IRC]
   
  +
==Mailing List==
−
;Facebook URL
  
  +
  +
[https://lists.sourceforge.net/lists/listinfo/apertium-stuff]
   
  +
==General Email==
−
;If you chose "veteran" in the downdown above, please summarise your involvement in Google Summer of Code and the successes and challenges of your participation. Please also list your pass/fail rate for each year.
 
  +
  +
apertium-contact@lists.sourceforge.net
   
  +
=Links=
−
Apertium took part in GSoC in 2009, 2010, 2011, 2012, 2013 and 2014. We received 9 slots in 2009, 9 again in 2010, 11 in 2011, 12 in 2012 although we gave one slot back to the pool, making 11, 11 in 2013, and 16 in 2014. We are very happy with the results of our participation. Our main successes and challenges are described below:
  
   
  +
==Google+ URL (optional)==
−
Successes:
  
  +
https://plus.google.com/+ApertiumOrg
   
  +
==Twitter URL (optional)==
−
* Getting useful results: Year upon year the majority of projects we have had were successful in that they produced useful, working code, and over half were released, which means that the code got to a sufficient level to be let into the world.
  
−
* Getting maintainable results: Around half the projects each year have had outside developers (e.g. not the students nor their mentors) work on them.
  
−
* Attracting and keeping new developers: We have had a total of 49 students, of these, around 15 are regulars on IRC, and several have gone on to become mentors in their own right. Several of our GSOC students from previous years also helped us out with mentoring for the GCI.
 
−
* Selecting applicants: We continued refining our selection process, and found it worked as well as in 2013, but with less overall effort.
 
   
  +
==Blog URL (optional)==
−
Challenges:
  
   
  +
=Your details=
−
* Getting students to work quickly: Apertium is a fairly complex pipeline mixing programming knowledge with linguistic knowledge; getting started is not always straightforward and a special effort needs to be made to break the problems to be addressed by students into "chewable" pieces.
  
−
* Getting the final furlong: Many of our GSOC projects were successful, in that the code worked, but they needed some finishing touches to be release-worthy. Encouraging students to do this proved in some cases difficult.
  
−
* Persuading students to publicise their results, in 2009 we got around half of our students to present their work to the wider community, and in 2010 two (though two students who completed their projects outside of GSoC also presented their work), but some either didn't plan to have the time or we weren't persuasive enough. In 2011/2012 we had one student present their work. In 2013, we had two students present papers, and in from our 2014 participation we have three students planning to submit papers to an international conference on MT.
  
   
  +
==Why does your org want to participate in Google Summer of Code?==
−
Pass/fail rate by year:
  
   
  +
* Apertium likes GSoC: it is a programme that supports free/open-source (FOS) software as much as we do!
−
* 2009: 8 pass, 1 fail
  
  +
* 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.
−
* 2010: 8 pass, 1 fail
  
  +
* 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.
−
* 2011: 9 pass, 2 fail
  
−
* 2012: 10 pass, 1 fail
  
−
* 2013: 10 pass, 1 fail
  
−
* 2014: 15 pass, 1 fail
  
   
  +
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.
−
;Why is your organisation applying to participate in Google Summer of Code 2015? What do you hope to gain by participating?*
  
   
  +
==How many potential mentors have agreed to mentor this year?==
   
  +
16-20
−
Apertium is applying again for two main reasons:
  
   
  +
It would be nice to have every mentor sign here:
−
* Apertium likes Google Summer of Code: it is a programme that supports open-source as much as we do!
  
  +
* --[[User:Mlforcada|Mlforcada]] ([[User talk:Mlforcada|talk]]) 18:05, 10 February 2016 (CET)
−
* Apertium needs Google Summer of Code: it is an incredible opportunity for us to spread the word about our project, to attract newcomers and to improve the platform
 
  +
* --[[User:Unhammer|unhammer]] ([[User talk:Unhammer|talk]]) 09:22, 11 February 2016 (CET)
  +
* --[[User:Tino Didriksen|Tino Didriksen]] ([[User talk:Tino Didriksen|talk]]) 17:23, 18 February 2016 (CET)
   
  +
==How will you keep mentors engaged with their students?==
−
What we hope to gain by participating is more students getting to know open-source, contributing to open-source and, especially if they are passionate about languages and computers, contributing to Apertium.
 
   
  +
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.
−
;How many potential mentors do you have for this year's program? What criteria did you use to select them?*
  
   
  +
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.
−
* We have 14 potential mentors.
  
−
* Active contributors: All of our mentors are active contributors to the project. Most of us know each other personally, either through meet ups, working together or conferences.
 
−
* Knowledgeable in their field: Many of our mentors are university professors or PhD students or graduates. However, this is not enough to be considered for mentoring.
  
−
* Enough time to spare: We ensure that our mentors have enough time to spare. Members of the project who have less than 5-10 hours/week to dedicate to their student are discouraged from applying to be a mentor.
  
−
* Experience with mentoring: The majority of our mentors also have experience with mentoring (from past GSOCs), either they have been mentors, or in some cases, been mentored. Any new mentors are paired with an experienced mentor.
 
   
  +
==How will you help your students stay on schedule to complete their projects?==
−
;What is your plan for dealing with disappearing students?*
  
   
  +
We will only accept applications that contain a well-defined weekly schedule, with clear milestones and deliverables and, if possible, with a section on risk management (risks, their probability, their severity, and mitigating actions). Applications should also plan for holidays and try and plan for other absences.
−
Students will be encouraged to let us know how they want to break up their time, and to plan for holidays and try and plan for other absences. This will avoid both mentors and students wasting time. If a mentor reports the unscheduled disappearance of a student (72-hour silence), they will be contacted by the administrators. If silence persists, their task will be frozen and we will report to Google.
 
   
  +
Students will be encouraged to let us know if they need to reschedule or take a break, should the need arise. Students may also need consultation when they are stuck, or personal matters interfere with their work: we will try our best to reach out for them, be open and friendly, and provide as much support as we can to help them out. We've been students too!
−
;What is your plan for dealing with disappearing mentors?*
  
   
  +
Detailed scheduling will avoid both mentors and students wasting time. If a mentor reports the unscheduled disappearance of a student (72-hour silence), they will be contacted by the administrators. If silence persists, their task will be frozen and we will report to Google, to proceed according to the rules of GSoC.
−
It is quite unlikely, since all of the mentors are very active developers, with long-term commitment to the project — they are people we have met face-to-face at conferences, workshops or even in daily life.
  
   
  +
==How will you get your students involved in your community during GSoC?==
−
However, there is always the possibility that some problem comes up, so we also assign backup mentors to all projects, and in many cases there are more than two mentors for a particular project.
  
   
  +
First, we encourage all of our students visit our IRC channel (#apertium @ freenode) as often as possible, even before the start of the program, since that would help them find a suitable mentor and a useful project that they can work on. We advice them strongly to read our Wiki pages and manuals, use our system, try to break it and fix it, and finally tell us about it. As a result, students get familiar with Apertium before the coding period starts, which increases their chances of ending up with a successful project.
−
If a mentor cannot continue for whatever reason, the backup/co-mentor will take over, and one of the organisation administrators will take on the role of second backup mentor.
 
  +
In addition, we define coding challenges for each of the proposed projects, which serve both as an entry task, and as means for getting our students familiar with Apertium and involved in our community in the early stages of the program.
  +
Finally, during the coding stage, we are available to talk to our students on a daily basis and give them suggestions and advice when they get stuck.
   
−
;What steps will you take to encourage students to interact with your project's community before and during the program?*
 +
==How will you keep students involved with your community after GSoC?==
   
  +
We have found that the following has helped us have quite a high retention rate in previous years:
−
First, we encourage all of our students visit our IRC channel (#apertium @ freenode) as often as possible, even before the start of the program, since that would help them find a suitable mentor and a useful project that they can work on. We advice them strongly to read our Wiki pages and manuals, use our system, try to break it and fix it, and finally tell us about it. As a result, students get familiar with Apertium before the coding period starts, which increases their chances of ending up with a successful project.
  
  +
# Helping students out publishing papers for conferences, or assisting with academic work.
  +
# Organising workshops (such as FreeRBMT) or courses (such as http://goo.gl/jzre7e) where students can present their work to the wider community.
  +
# Encouraging students to get involved in mentoring themselves, through the Google Code-In programme.
  +
# Passing on information about MSc and PhD positions, and academic and other grants.
   
  +
==Has your org been accepted as a mentoring org in Google Summer of Code before?==
−
In addition, we define coding challenges for each of the proposed projects, which serve both as an entry task, and as means for getting our students familiar with Apertium and involved in our community in the early stages of the program.
  
  +
Yes
   
  +
==Which years did your org participate in GSoC?==
−
Finally, during the coding stage, we talk to our students on a daily basis and give them suggestions and advice when they get stuck.
  
  +
*2014
  +
*2013
  +
*2012
  +
*2011
  +
*2010
  +
*2009
   
  +
==What is your success/fail rate per year?==
−
;What will you do to encourage your accepted students to stick with the project after Google Summer of Code concludes?*
  
   
  +
*2009: 8 pass, 1 fail
−
We have found that the following has helped us have quite a high retention rate in previous years:
  
  +
*2010: 8 pass, 1 fail
  +
*2011: 9 pass, 2 fail
  +
*2012: 10 pass, 1 fail
  +
*2013: 10 pass, 1 fail
  +
* 2014: 15 pass, 1 fail
  +
  +
==If your org has applied for GSoC before but not been accepted, select the years:==
  +
* 2015
  +
* 2008
  +
  +
== (another question I cannot add due to Spam filtering)==
  +
  +
We are not new, but we were not selected for 2015 after 6 years of participation.
   
  +
==Are you part of a foundation/umbrella organization?==
−
* Helping students out publishing papers for conferences, or assisting with academic work.
  
−
* Organising a workshop (FreeRBMT) where students can present their work to the wider community
  
−
* Encouraging students to get involved in mentoring themselves, through the GCI programme
  
−
* Passing on information about MSc and PhD positions, and academic and other grants.
 
   
  +
No
−
;Are you a new organisation who has a Googler or other organisation to vouch for you? If so, please list their name(s) here.
  
   
  +
==What year was your project started?==
−
;Are you an established or larger organisation who would like to vouch for a new organisation applying this year? If so, please list their name(s) here.
  
   
  +
2004
−
Moses
  
   
  +
==Anything else we should know (optional)?==
−
;Is there anything else we should know or you'd like to tell us that doesn't fit anywhere else on the application?
  
   
  +
Apertium started in an university environment (the Univ. d'Alacant in Spain) and has been extensively used as a research platform: at least three PhD and several MSc theses have used it and released new resources or tools. Apertium resources have been converted to other formats such as LMF, RDF.
−
[[Category:Google Summer of Code|Application 2015]]
  
  +
Apertium is used by some companies, mainly in Spain (Prompsit, imaxin|software, Elhuyar), and is even used by the Spanish Administration to translate public service information to the languages of Spain.

Latest revision as of 16:23, 18 February 2016

Being prepared by mlforcada, new template!

Public Profile[edit]

Website URL[edit]

http://wiki.apertium.org

Tagline[edit]

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

[edit]

GCI Logo

Primary Open Source License[edit]

GNU General Public License version 3.0 (GPL-3.0)

Technology Tags[edit]

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

Topic Tags[edit]

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

Ideas list[edit]

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


Descriptions[edit]

Short Description[edit]

Free/open-source rule-based machine translation platform

Long Description[edit]

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 and even Basque→English). 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 languages and language pairs

Proposals[edit]

Application instructions[edit]

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, hang out on IRC, 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[edit]

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

Contact Methods[edit]

IRC Channel[edit]

[2]

Mailing List[edit]

[3]

General Email[edit]

apertium-contact@lists.sourceforge.net

Links[edit]

Google+ URL (optional)[edit]

https://plus.google.com/+ApertiumOrg

Twitter URL (optional)[edit]

Blog URL (optional)[edit]

Your details[edit]

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

  • Apertium likes 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?[edit]

16-20

It would be nice to have every mentor sign here:

How will you keep mentors engaged with their students?[edit]

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?[edit]

We will only accept applications that contain a well-defined weekly schedule, with clear milestones and deliverables and, if possible, with a section on risk management (risks, their probability, their severity, and mitigating actions). Applications should also plan for holidays and try and plan for other absences.

Students will be encouraged to let us know if they need to reschedule or take a break, should the need arise. Students may also need consultation when they are stuck, or personal matters interfere with their work: we will try our best to reach out for them, be open and friendly, and provide as much support as we can to help them out. We've been students too!

Detailed scheduling will avoid both mentors and students wasting time. If a mentor reports the unscheduled disappearance of a student (72-hour silence), they will be contacted by the administrators. If silence persists, their task will be frozen and we will report to Google, to proceed according to the rules of GSoC.

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

First, we encourage all of our students visit our IRC channel (#apertium @ freenode) as often as possible, even before the start of the program, since that would help them find a suitable mentor and a useful project that they can work on. We advice them strongly to read our Wiki pages and manuals, use our system, try to break it and fix it, and finally tell us about it. As a result, students get familiar with Apertium before the coding period starts, which increases their chances of ending up with a successful project. In addition, we define coding challenges for each of the proposed projects, which serve both as an entry task, and as means for getting our students familiar with Apertium and involved in our community in the early stages of the program. Finally, during the coding stage, we are available to talk to our students on a daily basis and give them suggestions and advice when they get stuck.

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

We have found that the following has helped us have quite a high retention rate in previous years:

  1. Helping students out publishing papers for conferences, or assisting with academic work.
  2. Organising workshops (such as FreeRBMT) or courses (such as http://goo.gl/jzre7e) where students can present their work to the wider community.
  3. Encouraging students to get involved in mentoring themselves, through the Google Code-In programme.
  4. Passing on information about MSc and PhD positions, and academic and other grants.

Has your org been accepted as a mentoring org in Google Summer of Code before?[edit]

Yes

Which years did your org participate in GSoC?[edit]

  • 2014
  • 2013
  • 2012
  • 2011
  • 2010
  • 2009

What is your success/fail rate per year?[edit]

  • 2009: 8 pass, 1 fail
  • 2010: 8 pass, 1 fail
  • 2011: 9 pass, 2 fail
  • 2012: 10 pass, 1 fail
  • 2013: 10 pass, 1 fail
  • 2014: 15 pass, 1 fail

If your org has applied for GSoC before but not been accepted, select the years:[edit]

  • 2015
  • 2008

(another question I cannot add due to Spam filtering)[edit]

We are not new, but we were not selected for 2015 after 6 years of participation.

Are you part of a foundation/umbrella organization?[edit]

No

What year was your project started?[edit]

2004

Anything else we should know (optional)?[edit]

Apertium started in an university environment (the Univ. d'Alacant in Spain) and has been extensively used as a research platform: at least three PhD and several MSc theses have used it and released new resources or tools. Apertium resources have been converted to other formats such as LMF, RDF. Apertium is used by some companies, mainly in Spain (Prompsit, imaxin|software, Elhuyar), and is even used by the Spanish Administration to translate public service information to the languages of Spain.

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