11---
2- title : " TEMPLATE: Contributor Project Proposal"
3- description : " TEMPLATE: Contributor Project Proposal"
2+ title : " TEMPLATE: GSoC Contributor Project Proposal"
3+ description : " TEMPLATE: GSoC Contributor Project Proposal"
44date : " 2024-01-09"
55authors : ["OSL Team"]
66template : single-sidebar.html
@@ -47,35 +47,32 @@ Instructions:
4747
4848[ List the mentors for this project proposal.]
4949
50- ### Implementation Plan
50+ ### Technical Details
5151
52- [ Describe the tasks according to the project plan/idea.]
52+ [ Detail each task, providing technical specifics, relevant reference links, and
53+ preliminary solution ideas. Include findings from any preliminary research
54+ undertaken to address the issue, along with links to the specific segments of
55+ code slated for modification or improvement. ]
5356
5457### Benefits to the Community
5558
5659[ Explain how the project will benefit the community or users.]
5760
58- ## Planned Workflow
59-
60- [ Detail your planned workflow, including the project management methodology,
61- frequency and focus of mentor meetings, progress tracking, and task management
62- strategies.]
63-
64- ## Deliverables
65-
66- [ List all expected deliverables, such as new features, documentation updates,
67- tutorials, and blog posts. Consider writing a blog post for each major feature
68- or bug fix.]
61+ ## Deliverables and Timeline
6962
7063## Timeline
7164
72- [ Provide a detailed timeline for this project proposal, including key dates and
73- tasks. This should include Community Bonding Period activities, task periods,
74- blog post submission dates, and Midterm and Final evaluation schedules.]
65+ [ Outline a comprehensive timeline for this project, specifying crucial
66+ milestones, deliverables, and tasks. Incorporate the Community Bonding Period,
67+ development of new features, resolution of bugs, enhancements to documentation,
68+ creation of tutorials, and preparation of blog posts. Break down each task to
69+ ensure clarity. It is mandatory for collaborators to write regular blog posts.
70+ Highly encouraged is the creation of individual blog posts for each significant
71+ feature developed, bug fixed, or any notable progress made.]
7572
76- | Dates | Tasks |
77- | :---- | :---- |
78- | | |
73+ | Dates | Deliverables/ Tasks |
74+ | :---- | :----------------- |
75+ | | |
7976
8077## Previous Contributions to the Project
8178
@@ -90,14 +87,6 @@ PRs, resolved issues, or types of contributions.]
9087| :------------------------ | :----- |
9188| | |
9289
93- ### Issues
94-
95- [ List all resolved issues with titles, numbers, links, and their status.]
96-
97- | Issue Title/Number | Status |
98- | :----------------- | :----- |
99- | | |
100-
10190## Why This Project?
10291
10392[ Explain your motivation for choosing this project.]
0 commit comments