Before submitting a draft, please read the GSoC guide on writing proposals:
https://google.github.io/gsocguides/student/writing-a-proposal
Proposal Draft Submission
-
Create a topic in the GSoC Proposal Drafts category.
-
Post your proposal draft using the template below.
-
Mentors and contributors may ask questions or give feedback.
-
Update the draft by editing your first post directly so the latest version is always visible there.
Title
GSoC 2026 Proposal Draft – Idea NUM: DESCRIPTION – YOUR_NAME
For example:
GSoC 2026 Proposal Draft – Idea 8: Password strength indicator – laurent22
Links
Please include the following:
-
Link to the project idea
-
GitHub profile
-
Forum introduction post
-
Pull requests you have submitted to Joplin (include all of them, even if not merged — these are important for evaluation)
-
Other relevant development experience (plugins or PRs in other repositories)
1. Introduction
Briefly introduce yourself:
-
Background / studies
-
Programming experience
-
Experience with open source
2. Project Summary
Explain the project:
-
What problem it solves
-
Why it matters to users
-
What will be implemented
-
Expected outcome
-
What is explicitly out of scope (if applicable)
3. Technical Approach
Describe how you plan to implement the project:
-
Architecture or components involved
-
Changes to the Joplin codebase
-
Libraries or technologies you plan to use
-
Potential challenges
-
Testing strategy (unit/integration tests)
-
Documentation plan (user and/or developer documentation)
4. Implementation Plan
Provide a timeline with milestones.
Example:
Week 1–2
- Task description
Week 3–4
- Task description
Week 5–6
- Task description
5. Deliverables
What will exist at the end of the project?
Examples:
-
Implemented features
-
Tests
-
Documentation
6. Availability
-
Weekly availability during GSoC
-
Time zone
-
Any other commitments during the programme