User:Shrey1608

Personal Details

Name: SHREY DHARMENDRA MODI
Email: modishrey007@gmail.com
IRC: shrey1608
Github: https://github.com/shrey1608
Timezone: GMT+5.30hrs

About Me

Ever since i entered teenage, software development has been my passion. I still remember sitting in front of my laptop and coding "Hello Shrey" for the first time in C and getting the output on the blank screen gave me goosebumps.So in my middle school i learned C through books and making projects and then proceeded towards C++ in high school and made more advanced projects. I was insatiable

The passion carried me through my education in engineering and majoring in Information Technology.Here there were more opportunities and resources available to me to improve my skills to be somewhat ready for the Tech industry and also to contribute in opensource for that i did a summer tech internship after the freshman year and started to do contributions on GitHub and learnt what industry needs for me and what i have to improve on and the passion increased more towards the field.

And this mad passion doesn't let me move backwards and omits procrastination towards work and its calling me to work more and more in this beautiful industry and to provide contributions for its improvement.

Why is it that I am interested in Apertium?

Apertium being an open source offers people to contribute something meaningful to their culture.Following the principles of preserving culture and heritage through language, Apertium connects both ancient and modern through advances in machine translation platforms.

Coming from a land where over 19500 languages are spoken Language Translation plays an important role out here.Meeting different people with different language makes it difficult to communicate but it is overcome'd by the translation tool but isn't overcome'd by other translation tools while apertium takes care of the minority languages which is ignored by others which is one the reason i got attracted towards Apertium to give it a coverage of as many languages as possible.

The other one is that many translation software's are just available online while apertium is available in both modes online as well as offline. Internet access is not available to everyone and everywhere around the world so this results in an advantage to Apertium over others.

Which of the published tasks are you interested in? What do you plan to do?

I am interested for the task “Improvements to Apertium Website”. The changes i plan to make in the apertium websites are: • Improving Detection of languages.
• Adding dictionary lookup mode.
• Making better GUI.
• Providing a feedback feature for the users and providing that data to the apertium team.
• Improving apertiums's API (apy-py).
• Making 'Did You Mean' style if people choose an unlikely source language.
• Add a mode that colors the resulting translation depending on how reliable it is.

This Features will be Helpful to both the Apertium users and the Apertium Team

Reasons why Google and Apertium should sponsor it?

I am currently pursuing my Bachelors degree in computer science. Participation in GSoC will for sure be a great step towards becoming a better developer,contributor and a programmer. The project will give me the chance to read, understand and implement the ideas mentioned in different publications. This will be a great experience and will help me acquire new and necessary skills.By being accepted and successful in GSoC program, it would make a huge impact on my CV and hence my career. The stipend and the opportunity to have a job interview with google are huge benefits to a fresh graduate student like me.

How and who will it benefit in society ?

People speaking minority languages or majority languages are included in apertium which will help them to learn ,communicate as well as speak different language through language translation , people who want to know what written language it is can know through the language detection feature , people who cant read documents in different languages will be able to translate it to their known language through document translation feature and the people who want to translate the entire web page can translate it through apertium. so a lot of people will get benefited through this improvement and the user base of apertium would also increase and also people who want to contribute a language pair of their language can also do easily increasing apertium's language coverage.

Pre GSOC

Week 1 (From April 1 - To April 7)	Discuss more about the project with the mentors. Solve some issues and do PR's on GitHub.
Week 2 (From April 8 - To April 15)	Discuss with mentors some of the thoughts and ideas proposed in the documentation. Modify the documentation to reflect the new refactored code. Solve some issues and do PR's on GitHub.
Week 3 (From April 16 - To April 23)	Detailed view of the apertium API (apy-py) Solve some issues and do PR's on GitHub.
Week 4 (From April 24 - To May 1)	Detailed view of Html,css,Bootstrap and js scripts in the Html tools Solve some issues and do PR's on GitHub.
Deliverable	Pr's to the issues out there. Understanding apertium in a more detailed way.

Community Bonding

Community Bonding (From 4th May to 30th May)

Ask The mentor about 'IMPORTANT' information and improvements. Inspect the python and web scripts. Get used to Tornado Framework.

First milestone

Week 1 (From April 19 - To April 25)	Continue and finish any non-complete tasks from the previous two weeks, further refactoring, bugs/issues fixing, documentation, evaluation and testing, etc. Search for and discuss some newer and more efficient methods other than training maximum entropy models. The search will include looking at some related papers and will start with the mentioned ones above.
Week 2 (From April 26 - To May 2)	Continue searching for and discussing some alternative methods to max entropy models. Discuss some other previously proposed ideas and thoughts, like : Generating all possible ambiguous combinations for some splits of a sentence and not the other two methods we have tried so far (to generate some samples or all combinations of a sentence). Other thoughts also on the default rule, alternative translations for one word in the lexical form, and others found in details in the documentation.
Week 3 (From May 3 - To May 9)	Design and Implement some of the valid thoughts and ideas.
Week 4 (From May 10 - To May 16)	Continue coding, testing and debugging. Write documentation. Train one pair and evaluate its accuracy.
Deliverable	Hopefully, more accurate, clean and robust weighted transfer rules module.
After exams (From June 21 - To June 28)	After exams, I will familiarize myself again with the code because my memory is not good enough :) . Also write the mentor evaluation, complete any unfinished documentation, tests or evaluations, and fix any reported issues or bugs.

Second milestone

Since training one pair takes some considerable time, typically 2-3 days, and in that time I will be idle. So we can follow a strategy of implementing or modifying one idea and then train a pair to show how much is the gain for such idea and while training, I can start in implementing another one and so on.

Week 5 (From June 28 - To July 4)	Compare the new evaluation with past evaluation. After discussing the results, start modifying, adding or removing some parts of the module. Or even start searching or designing another idea/s.
Week 6 (From July 5 - To July 11)	Search for, modify, design and implement some other ideas. Evaluate these ideas by training a pair and comparing with past results.
Week 7 (From July 12 - To July 18)	Fix any reported bugs or issues. Finish the enhancing phase, by making a documentation of the design and implementation done. And preparing a report with all the evaluation results and gain so far with the implemented ideas.
Week 8 (From July 19 - To July 25)	Read apertium2 document again, read deprecated or out of date parts from different sources and collect all the up to date transfer files specifications in a new document.
Deliverable	More accurate weighted transfer rules module, with an evaluation report and documentation.

Third milestone

Week 9 (From July 26 - To August 1)	Fix any errors found in the module after collecting the up to date specifications. Start designing and implementing the extension to the module to both inter- and post-chunk transfer files.
Week 10 (From August 2 - To August 8)	Continue coding and start testing and debugging.
Week 11 (From August 9 - To August 15)	Fix any reported bugs or issues. Finish coding, testing and debugging. Train one chosen pair and evaluate its accuracy.
Week 12 (From August 16 - To August 19)	Finish any incomplete tasks. Update the documentation and evaluation report.
Deliverable	Extended weighted transfer rules module, with documentation and evaluation report.