We have been using Slack as the primary medium of communication. Since Slack has limited the features of the Slack free versison, we are moving away from Slack and asking the contributors to communicate via the discussion forums of each project's GitHub repository or this discussion forum instead.
Each idea on this page has at least one mentor assigned. Each existing project also has a relevant discussion forum in their GitHub source repository, listed below under each project idea. Specific discussions on each project idea happens in those discussion forums.
Please feel free to introduce yourself in the discussion forum. But please avoid individual messages to the mentors as that does not support the community environment we strive to make with the GSoC and open source in general.
This year, contributors are given the option to contribute to a project full-time (35 hours a week and 350 hours in total, a large project) or half-time (about 18 hours a week and 175 hours in total, a medium-size project). We have indicated how we see a project's size/scope is, as Full-time, Half-time, and Full-time/Half-time. Whenever we have indicated Full-time/Half-time, it illustrates that the project has some flexibility to change the scope and complexity as the contributor sees fit. In any case, these are given as suggestions and contributors have the freedom to propose their own estimate of full-time or half-time in their project proposal.
The contributors are encouraged to follow this template. However, they are not expected to strictly follow this template. They are rather advised to clearly include all the requested information in their application.
1) Project Title:
2) Abstract / Project Summary:
Summarize the project in your own words.
3) Contributor Name:
4) Contributor Email and GitHub ID:
5) Potential Mentor(s):
6) Personal Background (Brief CV)
7) Project Goals / Major Contributions
(Enter as bullets)
..
..
..
8) Project Schedule
Break the timeline into periods of up to 7 days
8.1) Community Bonding Period
8.2) Development Phase
8.3) Project Completion, testing, and documentation
9) Planned GSoC work hours
This year, the full-time projects are expected a 35 hours a week contribution (large project) and half-time projects are expected a 18 hours a week contribution (medium size project). Please indicate your choice of the project length. All project ideas have an indication how we see a project to be (full-time, half-time, or a potential/flexibility to be either based on the contributor's proposal).
Please also indicate the work hours (including the timezone), that you hope to work on your project.
10) Planned absence/vacation days and other commitments during the GSoC period (including the community bonding period)
Please indicate if you have any lectures/classes, examinations, or other personal commitments. GSoC 2022 also allows flexibility of an additional two months - to complete the project at a later time frame (a shift of up to 2 additional months). Please indicate if you expect to do that as we can plan accordingly.
11) Skill Set
Your relevant skill set to complete this project. Include pointers to bug fixes, demos, and previous work.
Also include pointers to the completed Code Challenge (if applicable).