Skip to main content

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.

What to Include

  • Personal Information: Contact details and background
  • Project Description: Clear explanation of what you’ll build
  • Implementation Plan: Detailed timeline with milestones
  • Qualifications: Your relevant skills and experience
  • Community Engagement: Prior contributions and involvement

Length Recommendations

  • Total Length: 5-10 pages
  • Project Description: 1-2 pages
  • Implementation Plan: 2-3 pages with detailed milestones
  • Qualifications: 1-2 pages
Quality matters more than quantity. Focus on clear, specific plans rather than lengthy descriptions.

Template

Copy and customize the template below:
# GSoC 2026 Proposal: [Your Project Title]

## Personal Information

- **Name**: [Your Full Name]
- **Email**: [your.email@example.com]
- **GitHub**: [github.com/yourusername]
- **Discord**: [YourDiscord#1234]
- **University**: [Your University Name]
- **Major/Year**: [Your Major, Expected Graduation Year]
- **Time Zone**: [Your Time Zone]
- **Location**: [Country, City]

## Abstract

[Write a 2-3 sentence summary of your project. This should be a high-level overview that captures the essence of what you're proposing.]

## Project Description

### Background and Motivation

[Explain the context of the problem you're solving. Why is this project important? What need does it address?]

### Problem Statement

[Clearly define the specific problem or gap your project will address. Be specific about current limitations.]

### Proposed Solution

[Describe your approach to solving the problem. What will you build or implement? How will it work?]

### Technical Approach

[Provide technical details about your implementation approach. What technologies, libraries, or frameworks will you use? What architecture or design patterns?]

### Expected Outcomes

[List the concrete deliverables and outcomes. What will exist at the end of the project that doesn't exist now?]

## Implementation Plan

### Phase 1: [Phase Name] (Weeks 1-4)

**Goals**:
- [Primary goal 1]
- [Primary goal 2]

**Milestones**:
- Week 1: [Specific milestone]
- Week 2: [Specific milestone]
- Week 3: [Specific milestone]
- Week 4: [Specific milestone]

**Deliverables**:
- [Concrete deliverable 1]
- [Concrete deliverable 2]

### Phase 2: [Phase Name] (Weeks 5-8)

**Goals**:
- [Primary goal 1]
- [Primary goal 2]

**Milestones**:
- Week 5: [Specific milestone]
- Week 6: [Specific milestone]
- Week 7: [Specific milestone]
- Week 8: [Specific milestone]

**Deliverables**:
- [Concrete deliverable 1]
- [Concrete deliverable 2]

### Phase 3: [Phase Name] (Weeks 9-12)

**Goals**:
- [Primary goal 1]
- [Primary goal 2]

**Milestones**:
- Week 9: [Specific milestone]
- Week 10: [Specific milestone]
- Week 11: [Specific milestone]
- Week 12: [Specific milestone]

**Deliverables**:
- [Concrete deliverable 1]
- [Concrete deliverable 2]

[Continue with additional phases as needed for 350-hour projects]

### Testing Strategy

[Describe how you'll test your implementation. What types of tests will you write? How will you ensure quality?]

### Documentation Plan

[Explain how you'll document your work. User guides? API documentation? Code comments?]

### Potential Challenges and Mitigation

| Challenge | Mitigation Strategy |
|-----------|-------------------|
| [Challenge 1] | [How you'll address it] |
| [Challenge 2] | [How you'll address it] |

## Qualifications

### Relevant Experience

[Describe your background and experience relevant to this project. Programming experience, coursework, personal projects, etc.]

### Technical Skills

**Programming Languages**:
- [Language 1]: [Proficiency level - Beginner/Intermediate/Advanced]
- [Language 2]: [Proficiency level]
- Go: [Your Go experience level]

**Tools and Technologies**:
- [Tool/Technology 1]: [Experience level]
- [Tool/Technology 2]: [Experience level]

**Security Experience**:
[Describe any security-related experience or knowledge]

### Contributions to ProjectDiscovery

[List your contributions to ProjectDiscovery projects. Include PR links, issue reports, documentation improvements, etc.]

- PR #XXX: [Brief description] - [Link]
- Issue #XXX: [Brief description] - [Link]
- [Other contributions]

### Other Open Source Contributions

[List relevant contributions to other open source projects, if any]

- Project: [Contribution description] - [Link]

### Past Projects

[Describe 1-2 relevant past projects that demonstrate your ability to complete this work]

**Project Name**: [Name]
- Description: [What you built]
- Technologies: [What you used]
- Link: [GitHub or demo link if available]

## Availability and Time Commitment

### Availability

[Describe your availability during the GSoC period. Be honest about any commitments, exams, or conflicts.]

- **Total Hours**: [175 or 350 hours over X weeks]
- **Weekly Commitment**: [X hours per week]
- **Peak Availability**: [When you're most available]
- **Limited Availability**: [Any known conflicts or reduced availability periods]

### Communication Plan

[Explain how you'll stay in touch with mentors]

- **Weekly Sync**: [Proposed meeting schedule]
- **Daily Updates**: [How you'll provide progress updates]
- **Primary Channel**: [Discord, Email, etc.]
- **Response Time**: [Your expected response time]

## Post-GSoC Plans

[Explain how you plan to continue contributing after GSoC ends. Long-term maintenance? Additional features? Community involvement?]

## Why ProjectDiscovery?

[Explain why you want to work with ProjectDiscovery specifically. What attracts you to the organization and this project?]

## References

**Project Links**:
- [Relevant tool documentation]
- [Related GitHub issues]
- [Technical references]

**External Resources**:
- [Papers, articles, or documentation you've researched]

**Contact**:
- Best way to reach me: [Email/Discord/etc.]
- Preferred communication times: [Your timezone and available hours]

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

Review Checklist:
  • All sections are complete and specific
  • Timeline is realistic and detailed
  • Technical approach is clear
  • You’ve made prior contributions to ProjectDiscovery
  • You’ve discussed your proposal with mentors
  • Proposal is proofread for clarity and grammar
  • Links work and references are accurate

Next Steps

  1. Copy this template and fill in your details
  2. Discuss with mentors on Discord before finalizing
  3. Review the evaluation criteria
  4. Submit via the official GSoC website
  5. Iterate based on feedback
Need help? Join our Discord community and ask questions in the #gsoc channel. Mentors are here to help you succeed!