Profile Information

Name: Kose Bilali
Web Profile: @kosekaku
Location: South Sudan
Typical working hours (include your timezone) 9 AM-4 PM CAT

Synopsis

• Short summary describing your project and how it will benefit Wikimedia projects:

The proposed project for Google Summer of Code 2023 is to improve the functionality of VideoCutTool, a tool used to edit videos on Wikimedia Commons. The tool is currently used by volunteers to edit videos and re-upload them to the Commons. The project aims to fix existing bugs, add new features and write unit tests to enhance the tool's functionality.

• Possible Mentor(s): Vasanth Gopa, Soham

• Have you contacted your mentors already? No

Deliverables

Describe the timeline of your work with deadlines and milestones, broken down week by week. Make sure to include time you are planning to allocate for investigation, coding, deploying, testing and documentation.
Week 1-2:
Investigation and understanding of the existing codebase and identifying bugs
Allocate 20 hours for investigation and understanding the existing codebase
Allocate 10 hours for bug identification and documentation
Deliverables: Documented list of existing bugs with priority level and severity, and an understanding of the existing codebase
Week 3-4:
Fixing existing bugs
Allocate 30 hours for fixing the highest-priority bugs
Deliverables: Fixed bugs and tested changes
Week 5-6:
Adding new features:
Allocate 20 hours for planning and design of new features
Allocate 40 hours for the implementation of new features
Deliverables: New feature implementation and tested changes
Week 7-8:
Unit testing:
Allocate 30 hours for writing unit tests for existing and new features
Deliverables: Unit tests written and integrated with the codebase
Week 9-10:
Testing and Deployment:
Allocate 30 hours for testing and debugging the entire application
Allocate 20 hours for deployment and setup
Deliverables: A stable, bug-free application deployed and running in the production environment
Week 11-12:
Documentation and Community Feedback:
Allocate 20 hours for documenting the entire application and writing user manuals
Allocate 10 hours for incorporating feedback from the Wikimedia Commons community
Deliverables: Complete documentation and community feedback incorporated into the application

In summary, this timeline spans 12 weeks and includes time for investigation, bug fixing, adding new features, writing unit tests, testing, and documentation.

Participation

Describe how you plan to communicate progress and ask for help, where you plan to publish your source code, etc.
To communicate progress and ask for help throughout this project program, here are the steps that I will be taking:

Set up regular check-ins with my mentor: Schedule regular meetings with my mentor to provide updates on the project's progress and discuss any challenges that I may be facing. This will allow me to stay aligned with the project's needs and receive guidance as needed.

Use a project management tool: Use a project management tool, such as Trello, to keep track of tasks, deadlines, and progress. Share this tool with my mentor and anyone else involved in the project to provide transparency and visibility into the project's progress.

Publish source code: Publish the source code of the application on a public repository such as GitHub. This will allow my mentor and other Wikimedia foundation developers to contribute to the project and provide feedback, as well as provide a way for me to show my progress and any changes made to the codebase.

Write regular progress reports: Write regular progress reports that summarize what has been accomplished, what is currently being worked on, and what challenges are being faced. Share these progress reports with my mentors to keep them informed.

Ask for help: If I encounter any challenges or blockers, I research for help and reach out to my mentors.

By following these steps, I can ensure that I am communicating progress effectively, getting help when needed, and keeping my mentor informed and engaged throughout the program.

About Me

Tell us about a few:

• Your education (completed or in progress): Completed computer science undergraduate degree
• How did you hear about this program? Linkedin
• Will you have any other time commitments, such as school work, another job, planned vacation, etc, during the duration of the program? No
• We advise all candidates eligible for Google Summer of Code and Outreachy to apply for both programs. Are you planning to apply to both programs and, if so, with what organization(s)? No
• What does making this project happen mean to you?

Completing the project would mean a lot to me because I would have gained valuable experience working on a software project with real-world community applications. It would also mean that I have contributed to the Wikimedia Commons community and helped make a positive impact on the world. It would also provide a better user experience for contributors and make it easier for them to manage and use media files, which is essential for promoting open access to information and knowledge in the Wikimedia commons community.

Past Experience

• Please add links to any feature or bug fix you have written for a Wikimedia project during the application phase. Not yet
• Describe any relevant projects that you've worked on previously and what knowledge you gained from working on them. None
• Describe any open source projects you have contributed to as a user and contributor (include links). None

Any Other Info

Add any other relevant information such as UI mockups, references to related projects, a link to your proof of concept code, etc
I have worked on a teamwork collaboration project, where I built the UI and APIs for the platform. Development links can be found here. https://github.com/kosekaku/teamwork
I have also built a custom web portal for printing COVID-19 vaccination certificates in South Sudan : https://github.com/kosekaku/covac-certificate-ssd-react