User:Harikrishna/GSoC2024Proposal
Contents
- 1 Contact
- 2 Background
- 3 Skills
- 4 Why am I interested in Apertium?
- 5 Proposal
- 6 Why should Google and Apertium sponsor it?
- 7 How and who will it benefit in society?
- 8 Coding Challenge
- 9 Previous Contributions
- 10 Work Plan
- 10.1 Community Bonding Period (May 1 - 26)
- 10.2 Week 1: May 27 - June 2
- 10.3 Week 2: June 3 - June 9
- 10.4 Week 3: June 10 - June 16
- 10.5 Week 4: June 17 - June 23
- 10.6 Week 5: June 24 - June 30
- 10.7 Week 6 - 7: July 1 - July 14
- 10.8 Week 8 - 10: July 15 - August 4
- 10.9 Week 11 - 13: August 5 - August 26
- 11 Non-Summer of Code Plans
Contact
- Name: Hari Krishna Reddy
- Email: hari.66.hks@gmail.com
- Location: India
- GitHub: [Hari Krishna]
- Linkedin: [Hari Krishna R.]
- IRC: satti-hari-krishna-reddy
- Timezone: GMT+5:30
Background
I am currently pursuing a Bachelor of Technology degree at Pragati Engineering College, India, specializing in Electrical Engineering with a minor in Computer Science. Fluent in Telugu (native language) and English (second language). With a strong passion for software development, I have been actively involved in various development projects for the past two years alongside my studies. My experience includes working with technologies such as React, Python, and others, which have equipped me with the necessary skills to contribute effectively to the Apertium project.
Skills
- React
- TypeScript
- Python
- Git
- Linux Basics
- React Testing
Why am I interested in Apertium?
I'm drawn to Apertium for its active community and its potential to make a real difference in Machine Translation. Its rule-based approach and support for low-resource languages align with my interests and sparking my enthusiasm to contribute and learn.
Proposal
Title: Spell-Checking Interface for Apertium's Web Tools
Deliverables
- Update and Polish Spell-Checking Interface:
- Review and update the spell-checking interface from the existing pull request in Apertium-html-tools to align with the current codebase.
- Develop APy Mode for Voikko Modules:
- Develop an APy mode for Voikko modules that allows easy access to Apertium's spell-checking capabilities using Voikko modules.
- Implementing Libvoikko Support for APy:
- Implement Libvoikko support for APy by integrating Libvoikko into APy and enabling Voikko to understand Apertium stream format.
Why should Google and Apertium sponsor it?
By sponsoring the enhancement of spell-checking capabilities, addressing the need for improving user experience and contributing to the accessibility and usability of language technology tools.
How and who will it benefit in society?
The enhancement of spell-checking capabilities within Apertium contributes to a more reliable and effective error detection and correction system for users across various languages.
Coding Challenge
I couldn't find any specific coding challenge mentioned in the project idea page.
Previous Contributions
- added a string directing to beta.apertium.org (Merged): [Pull Request #483]
- Build should not rely on git (Merged): [Pull Request #481]
- replaced double quote strings with single quotes (Merged) : [Pull Request #602]
- modified " help us improve" link (Open): [Pull Request #498]
- Improve swap lang button for language and text swapping (Open): [Pull Request #482]
Work Plan
Community Bonding Period (May 1 - 26)
During this period, I will familiarize myself with the Apertium community, discuss project details with mentors , and gain a deeper understanding of the existing codebase and project requirements.
Week 1: May 27 - June 2
- Review existing spell-checking interface in the stale pull request of Apertium-html-tools repository.
- Discuss initial observations and potential improvements with mentors.
Week 2: June 3 - June 9
- Start updating and enhancing the interface in the stale pull request by converting it to React to align with the current codebase.
Week 3: June 10 - June 16
- Engage with community for feedback and guidance.
- Continue updating the interface.
Week 4: June 17 - June 23
- Test updated interface functionality.
- Implement additional improvements based on feedback and testing.
- Update documentation.
Week 5: June 24 - June 30
- Understand the requirements for integrating Voikko modules into APy.
- Begin developing python modules that interact with Voikko's spell-checking functionality.
- Discuss with mentors to finalize a method for the APy mode to automatically detect available Voikko modes.
Week 6 - 7: July 1 - July 14
- Prepare for the midterm evaluation.
- Integrate these modules into the APy to create a new mode for spell-checking.
- Finish developing the python modules that interact with Voikko.
- Test the functionality of the APy mode and iterate on improvements based on feedback from mentors.
- Deliverable: Finalized Spell-Checking Interface.
Week 8 - 10: July 15 - August 4
- Understand the integration process for Libvoikko support into APy.
- Implement wrapper classes to encapsulate Libvoikko functionality within APy.
- Integrate wrapper classes into APy, enabling an APy mode for seamless Libvoikko support in processing text in Apertium stream format
- Conduct comprehensive testing to ensure the functionality and compatibility of Libvoikko support with APy.
Week 11 - 13: August 5 - August 26
- Discuss documentation details with mentors and organization.
- Finalize the project deliverables, addressing any pending tasks or feedback from mentors.
- Based on discussions, incorporate any additional tasks such as writing additional unit test cases or addressing any other identified areas for improvement.
- Project completed.
Non-Summer of Code Plans
My final exams will be completed by April, and I have no plans other than GSoC for the summer of 2024. I can devote 30-40 hours per week to this project.
