- 1 Apertium GSoC 2019 Python API(APy) for Apertium
- 2 Contact Information
- 3 Why is it that you are interested in Apertium?
- 4 Which of the published tasks are you interested in? What do you plan to do?
- 5 Why Google and Apertium should sponsor it?
- 6 How and who it will benefit in society?
- 7 Work Plan
- 8 Contribution to Apertium
- 9 Education
- 10 Experience
- 11 Non-summer of code plans
- 12 Links
Apertium GSoC 2019 Python API(APy) for Apertium
Name: Ayush Jain
E-mail address: email@example.com
Alternate email: firstname.lastname@example.org
Mobile Number: +91 9045511472 (India)
IRC nick: ayushjain
Timezone: UTC +5.30
Why is it that you are interested in Apertium?
I belong to India, a country with 22 different spoken languages and 720 dialects. Being from a nation with vast languages and a student of Computer Science, I strive to solve the problems in language translation through my knowledge of programming and natural language processing. I face difficulty when I travel to different regions and communicate with different people. I like the concept of Apertium as an open source language translator as it solves the problem of language translation with ease. As I am a student of Computer Science, I have a keen interest in programming and development. I am proficient in web development and want to apply my knowledge of machine translation by contributing in Apertium. I have an urge to improve open source language translation with Apertium.
Which of the published tasks are you interested in? What do you plan to do?
I am planning to work on the either or both of the listed projects:
- Python API/library for Apertium
- Improvements to the Apertium website
As I am skilled in web development and have appropriate experience working on it, I decided to work on improving Apertium website by contributing to its API called APy and also improve the frontend of the website for better user experience along addition of new functionality.
Why Google and Apertium should sponsor it?
How and who it will benefit in society?
As most people use Windows, adding support for windows will increase the user base of Apertium. A pip install for windows would make development process a lot easier for the developers. Adding certain capabilities of Apertium such as dictionary/synonym lookup and webpage translation to the website would help in increasing the users and expand the uses of Apertium.
|Community Bonding Period||Getting to know all the mentors and getting acquainted with complete documentation of apertium. Acknowledge the problem statement and start working on a possible solution with focus on each detail.||6 May - 26 May|
|Phase 1||Working on apertium-apy and lttoolbox and making it available on windows.||27 May - 26 June|
|Phase 2||Working on improvements to apertium website and adding functionalities.||27 June - 26 July|
|Phase 3||Wrapping up the project with proper documentation and project report.||27 July - 25 August|
|6 May - 26 May||Community Bonding Period||
||Report for next week’s work plan.|
|27 May - 2 June||Week 1 : Setting up apertium for windows||
||An installable prototype for installing apertium on windows.|
|3 June - 9 June||Week 2 : Apertium support for various platforms||
||Complete installation of apertium for windows using pip|
|10 June - 16 June||Week 3: Working on lttoolbox||
||A working transducer function using SWIG to convert C++ functions in python script.|
|17 June - 26 June||Week 4: Improving SWIG API.||
||Releasing the SWIG API for lttoolbox.|
|27 June - 3 July||Week 5: Adding dictionary lookups||
||Dictionary lookup functionality on the website.|
|4 July - 10 July||Week 6: Reliability visualization||
||Reliability visualization ready for release.|
|11 July - 17 July||Week 7: Did you mean functionality||
||Functional language detection and did you mean feature.|
|18 July - 24 July||Week 8 : Integrating the functionalities in the website||
||Improved Apertium website ready for deployment.|
|25 July - 31 July||Week 9: Bug Fixing 1||
||Complete apertium-apy with documentation.|
|1 August - 7 August||Week 10: Bug Fixing 2||
||Complete lttoolbox implementation|
|8 August - 14 August||Week 11: Bug Fixing 3||
||Making website release ready.|
|15 August - 21 August||Week 12: Releasing Apertium website||
||Release Apertium website for users.|
|22 August - 26 August||Week 13: Wrapping up||
||Release final production.|
Contribution to Apertium
I have been contributing to Apertium for quite a while now.
Here is a list of my contributions various Apertium contributions :
- Issues :
- apertium-html-tools = 1
- apertium-apy = 2
- Merges :
- Apertium-apy = 1
- Pull requests :
- apertium-html-tools = 1 open.
- Apertium-apy = 2 open
I have been working on the issues in html-tools and apertium-apy under the guidance of my mentor.
One of my pull request has been merged in which I have added an index page for localhost:2737 in apertium-apy along with unit test written in tornado.
I am working on 3 other pull requests which are still open and involves complex issues. It includes :
- Finding langNames.db using pkg_resources.
- Creating source TSV files for SQL database.
Here you can see my github timeline for contributions in Apertium :
I am pursuing my degree of Bachelor of Technology in Computer Science Engineering at IIIT Una, India. I am a student of second year enrolled in a four year course of CSE. I have completed my intermediate with 95.2% marks with computer science as additional subject.
Non-summer of code plans
Google Summer of Code lies during the summer vacations of the college. I will be able to devote 40 hours per week and more if necessary to Apertium during summer of code. I might have a small vacation plan but that lies in between the Community bonding period and I will be able to manage my work accordingly. I also acknowledge that GSOC is my foremost priority and I won’t be working on any other internship, training or classes if selected for GSOC.