GSoC Proposal Template

Template for writing your GSoC proposal for ProjectDiscovery

GSoC Proposal Template

Use this template as a starting point for your Google Summer of Code proposal. A well-structured proposal helps reviewers understand your approach and increases your chances of acceptance.

How to Use This Template

Copy the template below and fill in each section with your specific details. Be clear, concise, and specific about your plans. Focus on quality over quantity - a concise, well-thought-out proposal is better than a lengthy one.

Keep it focused: Aim for 5-7 pages total. Reviewers value clarity and specificity over length.

Template

Copy and customize the template below:

# GSoC 2026 Proposal: [Your Project Title]

## Personal Information

- **Name**: [Your Full Name]
- **Email**: [[e-mail]]
- **GitHub**: [github.com/yourusername]
- **Discord**: [YourDiscord#1234]
- **Time Zone**: [Your Time Zone]
- **Expected Hours**: [175 or 350 hours]

## Abstract

[Write 2-3 sentences summarizing what you'll build, how, and why it matters.]

## Project Description

### What Problem Are You Solving?

[Describe the current limitation or gap. Why does this matter?]

### Your Solution

[Explain what you'll build and how it will work. Include key technical approaches.]

### Expected Outcome

[List concrete deliverables - what will exist at the end that doesn't exist now?]

## Timeline

Break your project into phases with weekly milestones:

### Weeks 1-4: [Phase Name]
- Week 1: [Specific milestone]
- Week 2: [Specific milestone]
- Week 3: [Specific milestone]
- Week 4: [Specific milestone]

### Weeks 5-8: [Phase Name]
- Week 5: [Specific milestone]
- Week 6: [Specific milestone]
- Week 7: [Specific milestone]
- Week 8: [Specific milestone]

### Weeks 9-12: [Phase Name]
- Week 9: [Specific milestone]
- Week 10: [Specific milestone]
- Week 11: [Testing and documentation]
- Week 12: [Final polish and documentation]

[Add more weeks for 350-hour projects]

### Testing & Documentation

**Testing**: [How you'll test - unit tests, integration tests, benchmarks]

**Documentation**: [What docs you'll create - README updates, code comments, user guides]

## Your Background

### Skills & Experience

**Go Experience**: [Describe your Go programming experience]

**Relevant Skills**: [List 3-5 key skills relevant to this project]

**Past Projects**: [Briefly describe 1-2 relevant projects you've built]

### Contributions to ProjectDiscovery

[List your contributions with links. This is important!]

- PR #XXX: [Description] - [Link]
- Issue #XXX: [Description] - [Link]
- [Other contributions]

## Availability

[Be honest about your schedule]

- **Weekly Hours**: [12-15 hours for 175h projects, 25-30 hours for 350h projects]
- **Any Conflicts**: [Exams, travel, other commitments?]
- **Communication**: [How often you'll check in - suggest 2x weekly minimum]

## Why This Project?

[Briefly explain why you're interested in this project and ProjectDiscovery]

Tips for a Strong Proposal

Be Specific

Use concrete examples and specific milestones rather than vague descriptions.

Show Research

Demonstrate understanding of the codebase and existing solutions.

Be Realistic

Propose achievable goals within the timeframe. Quality over quantity.

Engage Early

Discuss your idea with mentors before submitting your final proposal.

Before You Submit

Quick Checklist:

• Timeline has specific weekly milestones (not vague goals)
• You’ve made prior contributions to ProjectDiscovery (critical!)
• You’ve discussed your idea with mentors on Discord
• Proposal is proofread and links work
• You’re being realistic about scope and time

Next Steps

1. Fill out the template above with your specific details
2. Share a draft with mentors on Discord (#gsoc channel)
3. Incorporate feedback and iterate
4. Submit via the GSoC website

Pro Tip: Start early and get feedback! Mentors can help refine your approach before you submit.

Questions? Join our Discord community and ask in the #gsoc channel. We’re here to help!