User:AMR-KELEG/GSoC19 Proposal

Personal Information

• Name: Amr Keleg

• E-mail address: amr.keleg@eng.asu.edu.eg / amr_mohamed@live.com

• IRC: AMR-KELEG

• Location: Cairo, Egypt

• Timezone: UTC+02

• Github: https://github.com/AMR-KELEG

• LinkedIn: https://www.linkedin.com/in/amr-mohamed-hosny/

• Twitter: https://twitter.com/amrkeleg

• Current job: A MSc student and a teacher assistant at Computer and systems department, Faculty of Engineering, Ain Shams university, Cairo, Egypt.

• Experimental blog: https://ak-blog.herokuapp.com

Skills and qualifications

• Past GSoC participant.

• Competitive programming.

• Worked for one year on developing sentiment analysis model for Arabic language.

• Made several contributions to open source projects

• Participated in online and on-site competitive programming contest.

• Completed Udacity's data analysis nanodegree.

• Good command of git and the GitHub process of contribution.

• Experienced in using C++ and python.

• Using Ubuntu for more than 3 years.

• Basic knowledge of shell scripting.

Coding challenge

Code repository: https://github.com/AMR-KELEG/apertium-unsupervised-weighting-of-automata

Project Information

Why is it that you are interested in Apertium?

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

Include a proposal, including

   * a title,
   * reasons why Google and Apertium should sponsor it,
   * a description of how and who it will benefit in society,
   * and a detailed work plan (including, if possible, a schedule with milestones and deliverables).

Work plan

• Week 1:
• Week 2:
• Week 3:
• Week 4:

• Deliverable #1

• Week 5:
• Week 6:
• Week 7:
• Week 8:

• Deliverable #2

• Week 9:
• Week 10:
• Week 11:
• Week 12:

• Project completed

Include time needed to think, to program, to document and to disseminate.

If you are intending to disseminate to a conference, which conference are you intending to submit to. Make sure to factor in time taken to run any experiments/evaluations and write them up in your work plan.

List your skills and give evidence of your qualifications. Tell us what is your current field of study, major, etc. Convince us that you can do the work.

List any non-Summer-of-Code plans you have for the Summer, especially employment, if you are applying for internships, and class-taking. Be specific about schedules and time commitments. we would like to be sure you have at least 30 free hours a week to develop for our project.