Difference between revisions of "User:Cellzawy/GSoC2024Proposal"
Jump to navigation
Jump to search
(19 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
== Contact Information == |
|||
* Name: Ahmed A. Elhossieny |
* Name: Ahmed A. Elhossieny |
||
* E-mail address: ahmedamrelhossieny@gmail.com |
* E-mail address: ahmedamrelhossieny@gmail.com |
||
Line 7: | Line 7: | ||
* Timezone: UTC+2 |
* Timezone: UTC+2 |
||
== Background == |
|||
My name is Ahmed A. Elhossieny. I'm a dedicated student pursuing a bachelor's degree in computer science at Ain Shams University, Faculty of Computer and Information Science, and I expect to graduate in 2026. I am passionate about CSS and general web design, my skill set also includes: OOP, Data Structures, C++, Javascript, Java and Python. |
My name is Ahmed A. Elhossieny. I'm a dedicated second-year student from Egypt, pursuing a bachelor's degree in computer science at Ain Shams University, Faculty of Computer and Information Science, and I expect to graduate in 2026. I am passionate about CSS and general web design, my skill set also includes: OOP, Data Structures, C++, Javascript, Java, React and Python. I have done one contribution on apertium-html-tools to fix issue #488. |
||
== Why is it that you are interested in Apertium? == |
|||
* Apertium has |
* Apertium has an awesome and interesting community. |
||
* Apertium seems like a good place to boost my open source/technical skills. |
* Apertium seems like a good place to boost my open source/technical skills. |
||
== Why should Google and Apertium sponsor it? == |
|||
⚫ | |||
* The current UI feels a bit outdated, a new UI will make good improvement to the user experience. |
|||
* A translation suggestions feature will make it easier to contribute to the platform, which will increase the overall quality. |
|||
⚫ | |||
⚫ | |||
⚫ | |||
The project aims to add some enhancements to Apertium’s website, specifically focusing on the Apertium-html-tools repository. By addressing open issues and implementing new features which include: |
The project aims to add some enhancements to Apertium’s website, specifically focusing on the Apertium-html-tools repository. By addressing open issues and implementing new features which include: |
||
* Upgrading to Bootstrap v5 |
|||
* Creating a new UI for Apertium |
|||
The project also aims to entail finishing the suggestions interface for Apertium's web infrastructure |
The project also aims to entail finishing the suggestions interface for Apertium's web infrastructure: |
||
* Users can submit their suggestions for corrected translations through a form on the website. This form could include fields for the original text, the current translation, and the suggested correction. |
|||
* Users could also provide context or explanations for their suggestions to help the team understand the reasoning behind the correction. |
|||
* The suggestions would be sent to the backend (apertium-apy) and stored in a database. This would allow the team to review the suggestions and decide which ones to implement. |
|||
=== Work plan === |
=== Work plan === |
||
⚫ | |||
Community bonding period (May 1 - May 26) |
|||
|+ |
|||
⚫ | |||
⚫ | |||
|+ Caption text |
|||
|- |
|- |
||
! Time Period !! Goal !! Deliverable |
! Time Period !! Goal !! Deliverable |
||
|- |
|||
⚫ | |||
|- |
|- |
||
| Week 1/2 (May 27 - June 9) || Upgrading to Bootstrap v5 || PR with the upgrade |
| Week 1/2 (May 27 - June 9) || Upgrading to Bootstrap v5 || PR with the upgrade |
||
|- |
|- |
||
| Week 3/4 (June 10 - June 23) || Working on the new UI for mobile views || PR with the finished UI (mobile views) |
| Week 3/4 (June 10 - June 23) || Working on the new UI for mobile views || PR with the finished UI (mobile views) on apertium-html-tools |
||
|- |
|||
⚫ | |||
|- |
|||
⚫ | |||
|- |
|||
⚫ | |||
|- |
|||
| Week 9 (July 22 - July 28) || Testing and bug fixing for the suggestions interface || PR with bug fixes (if any) |
|||
|- |
|- |
||
⚫ | |||
⚫ | |||
|- |
|||
⚫ | |||
|- |
|- |
||
| Week |
| Week 12 (August 12 - August 18) || Project submission || |
||
|} |
|} |
||
== Non-Summer of Code Plans == |
|||
* : |
|||
* : |
|||
* : |
|||
* : |
|||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
* Week 12 (August 12 - August 18): Project submission |
|||
⚫ | |||
* '''Project completed''' |
|||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ |
Latest revision as of 01:24, 2 April 2024
Contents
Contact Information[edit]
- Name: Ahmed A. Elhossieny
- E-mail address: ahmedamrelhossieny@gmail.com
- IRC: Cellz
- GitHub: https://github.com/cellzawy
- Linkedin: https://www.linkedin.com/in/aelhossieny
- Timezone: UTC+2
Background[edit]
My name is Ahmed A. Elhossieny. I'm a dedicated second-year student from Egypt, pursuing a bachelor's degree in computer science at Ain Shams University, Faculty of Computer and Information Science, and I expect to graduate in 2026. I am passionate about CSS and general web design, my skill set also includes: OOP, Data Structures, C++, Javascript, Java, React and Python. I have done one contribution on apertium-html-tools to fix issue #488.
Why is it that you are interested in Apertium?[edit]
- Apertium has an awesome and interesting community.
- Apertium seems like a good place to boost my open source/technical skills.
Why should Google and Apertium sponsor it?[edit]
- The current UI feels a bit outdated, a new UI will make good improvement to the user experience.
- A translation suggestions feature will make it easier to contribute to the platform, which will increase the overall quality.
Proposal[edit]
Website Improvements: Misc - Suggestions[edit]
The project aims to add some enhancements to Apertium’s website, specifically focusing on the Apertium-html-tools repository. By addressing open issues and implementing new features which include:
- Upgrading to Bootstrap v5
- Creating a new UI for Apertium
The project also aims to entail finishing the suggestions interface for Apertium's web infrastructure:
- Users can submit their suggestions for corrected translations through a form on the website. This form could include fields for the original text, the current translation, and the suggested correction.
- Users could also provide context or explanations for their suggestions to help the team understand the reasoning behind the correction.
- The suggestions would be sent to the backend (apertium-apy) and stored in a database. This would allow the team to review the suggestions and decide which ones to implement.
Work plan[edit]
Time Period | Goal | Deliverable |
---|---|---|
Community bonding period (May 1 - May 26) | Discuss more about the project and define more details. | |
Week 1/2 (May 27 - June 9) | Upgrading to Bootstrap v5 | PR with the upgrade |
Week 3/4 (June 10 - June 23) | Working on the new UI for mobile views | PR with the finished UI (mobile views) on apertium-html-tools |
Week 5 (June 24 - June 30) | Making the UI responsive for computer views | PR with the finished UI (computer views) on apertium-html-tools |
Week 6 (July 15 - July 21) | Testing and bug fixing for the new UI | PR with bug fixes (if any) on apertium-html-tools |
Week 7/8 (July 1 - July 14) | Working on the suggestions interface | PR with the finished interface on apertium-html-tools |
Week 9 (July 22 - July 28) | Testing and bug fixing for the suggestions interface | PR with bug fixes (if any) |
Week 10 (July 29 - August 4) | Documentation and finalizing the project | |
Week 11 (August 5 - August 11) | Buffer week for any unexpected delays | |
Week 12 (August 12 - August 18) | Project submission |
Non-Summer of Code Plans[edit]
- I am willing to dedicate +30 hours a week for the project.
- I will be having my university final exams in June so I will be working 10 hours a week until I finish my exams.
- I am not applying for any internships at the moment.