Application Process & Proposal Guidelines

How to write a successful GSoC proposal for ProjectDiscovery

Application Process & Proposal Guidelines

Learn how to write a compelling GSoC proposal that stands out. A well-crafted proposal significantly increases your chances of acceptance.

Application Timeline

Date	Action
March 16, 2026	Applications open on GSoC website
March 16-30	Draft proposal, get mentor feedback, iterate
March 31, 18:00 UTC	⚠️ Application deadline - Submit final proposal
April 30, 2026	Accepted contributors announced

Deadline: March 31, 2026 at 18:00 UTC. No late submissions are accepted. Submit early!

View full timeline →

Before You Apply

Prerequisites Checklist

Before writing your proposal:

• ✅ Joined ProjectDiscovery Discord
• ✅ Tried at least 2-3 of our tools
• ✅ Made at least 1 code contribution (strongly recommended)
• ✅ Discussed project ideas with mentors
• ✅ Read relevant tool documentation
• ✅ Understand the codebase basics

Contributors who make meaningful contributions before applying have significantly higher acceptance rates.

Proposal Structure

Your proposal should include these sections:

1. Personal Information

• Full name and contact details
• GitHub and Discord usernames
• University and graduation year (if applicable)
• Time zone and location
• Expected availability

2. Abstract (2-3 sentences)

Concise summary of your project:

• What problem you’re solving
• Your approach
• Expected outcome

Example: “This project will implement a performance profiling framework for Nuclei templates to identify bottlenecks and optimize scan speed. The solution includes profiling hooks in the template engine, a CLI analysis tool, and a web dashboard for visualization. The expected outcome is 20-30% improvement in template execution speed for complex scans.”

3. Project Description

Problem Statement

• What problem are you solving?
• Why is this important?
• What are current limitations?
• Who will benefit from this?

Proposed Solution

• Your approach to solving the problem
• Why this approach is appropriate
• Alternative approaches considered
• Expected benefits

Technical Approach

• Specific implementation details
• Technologies and libraries you’ll use
• Architecture and design patterns
• Integration with existing code
• Performance considerations

4. Implementation Plan

Break your project into phases with specific milestones:

Phase 1: Foundation (Weeks 1-4)

• Week 1: [Specific milestone with deliverable]
• Week 2: [Specific milestone with deliverable]
• Week 3: [Specific milestone with deliverable]
• Week 4: [Specific milestone with deliverable]
• Deliverables: [Concrete, testable outcomes]

Phase 2: Core Development (Weeks 5-8)

• Detailed weekly milestones
• Deliverables: [What will be completed]

Phase 3: Integration & Testing (Weeks 9-12)

• Testing, documentation, polish
• Deliverables: [Final outcomes]

Each milestone should be specific and measurable. Instead of “Implement feature X”, write “Implement feature X with unit tests achieving 80% coverage”.

5. Testing Strategy

• Unit tests for core functionality
• Integration tests for feature interactions
• Performance benchmarks
• Edge case handling
• Test coverage goals (aim for 70-80%)

6. Documentation Plan

• Code comments and docstrings
• README updates
• User guide or tutorial
• API documentation (if applicable)
• Example usage

7. Qualifications

Your Experience

• Programming background
• Relevant coursework or projects
• Professional experience (if any)
• Open source contributions

Technical Skills

• Go: Proficiency level and experience
• Other languages: Relevant skills
• Tools: Version control, CI/CD, etc.
• Security: Any security-related experience

Contributions to ProjectDiscovery

List your contributions with links:

• PR #123: Description - [Link]
• Issue #456: Description - [Link]
• Documentation improvements - [Link]

Past Projects

Showcase 1-2 relevant projects:

• Description
• Technologies used
• Your role
• Link to code/demo

8. Timeline & Availability

• Total hours (175 or 350)
• Weekly time commitment
• Any known conflicts (exams, vacation, etc.)
• Backup plans for conflicts

9. Post-GSoC Plans

• How you’ll continue contributing
• Long-term vision for the project
• Plans to maintain your work

10. References

• Links to relevant issues, discussions, docs
• Technical references
• Research papers or articles (if applicable)

What Makes a Strong Proposal

Technical Excellence

✅ Demonstrates deep understanding of the problem ✅ Provides specific implementation details ✅ Considers edge cases and challenges ✅ Shows familiarity with codebase ✅ Includes performance considerations

Realistic Planning

✅ Detailed week-by-week timeline ✅ Measurable milestones ✅ Appropriate scope for hours ✅ Includes testing and documentation time ✅ Has buffer for unexpected issues

Community Engagement

✅ Prior code contributions ✅ Active Discord participation ✅ Understanding of project goals ✅ Professional communication ✅ Early engagement (not last-minute)

Clear Communication

✅ Well-organized structure ✅ Clear, concise writing ✅ Proper grammar and spelling ✅ Appropriate level of detail ✅ Professional presentation

Proposal Resources

Proposal Template

Copy our template to get started

Evaluation Criteria

Understand how proposals are scored

Project Ideas

Browse available projects

Getting Started

Learn the basics

Tips for Success

Start Early

• Begin 3-4 weeks before the deadline
• Give yourself time for feedback and iteration
• Early submissions can be updated before the deadline

Get Feedback

• Share your draft with mentors on Discord
• Ask specific questions about your approach
• Iterate based on feedback
• Don’t wait until the last day

Be Specific

Replace vague statements with concrete details:

❌ “Improve performance of the tool” ✅ “Optimize template execution by implementing caching for DNS responses, reducing redundant lookups by 60%”

❌ “Add new features” ✅ “Implement three specific features: rate limiting (Week 3-4), custom headers support (Week 5-6), and response caching (Week 7-8)“

Show Your Work

• Link to your prior contributions
• Include code samples or demos
• Reference specific files/functions in the codebase
• Show you’ve done your research

Be Realistic

• Don’t over-promise
• Account for learning curve
• Include buffer time
• Better to under-promise and over-deliver

Proofread

• Check grammar and spelling
• Ensure all links work
• Format consistently
• Have someone else review it

Common Mistakes to Avoid

Avoid these pitfalls that hurt proposals:

Too Vague

❌ Generic descriptions without specifics ❌ “Will improve the tool” ❌ No technical details ✅ Specific features, approaches, and outcomes

Too Ambitious

❌ Proposing to rewrite major components ❌ 500+ hours of work in 350-hour project ❌ No buffer for problems ✅ Realistic scope with buffer time

No Prior Engagement

❌ First interaction is submitting proposal ❌ No contributions to ProjectDiscovery ❌ Hasn’t tried the tools ✅ Active community member with contributions

Copy-Paste

❌ Generic proposal that could apply anywhere ❌ Copied from other proposals ❌ No customization to ProjectDiscovery ✅ Specific to ProjectDiscovery and the project

Poor Planning

❌ Vague milestones like “Work on feature X” ❌ All work in first few weeks ❌ No testing or documentation time ✅ Detailed weekly plan with testing included

Submission Process

How to Submit

1. Create account on GSoC website
2. Find ProjectDiscovery in organization list
3. Select project (or choose “Custom Project”)
4. Upload proposal (PDF or Google Doc link)
5. Submit before deadline
6. Confirm submission was successful

Submission Tips

• Format: PDF or Google Docs (preferred for easy updates)
• Length: 5-10 pages typically (quality over quantity)
• Filename: GSoC2026_YourName_ProjectTitle.pdf
• Backup: Keep a local copy
• Early submission: You can update before deadline

Submit at least 24 hours before the deadline to account for technical issues.

After Submission

• Continue contributing: Keep making contributions
• Be responsive: Answer any follow-up questions promptly
• Stay engaged: Participate in Discord
• Be patient: Review takes time
• Check regularly: Monitor your GSoC dashboard

Evaluation Process

Your proposal will be evaluated by mentors based on:

• Technical Merit (30%): Quality of technical approach
• Implementation Plan (25%): Realism and detail of timeline
• Community Engagement (20%): Prior contributions and involvement
• Applicant Qualifications (15%): Relevant skills and experience
• Proposal Quality (10%): Clarity and professionalism

View detailed evaluation criteria →

Timeline for Applicants

3-4 Weeks Before Deadline

• Draft complete proposal
• Include all required sections
• Add technical details

2-3 Weeks Before Deadline

• Share draft with mentors on Discord
• Get feedback on approach
• Continue making contributions

1-2 Weeks Before Deadline

• Incorporate mentor feedback
• Polish and proofread
• Finalize timeline details

3-7 Days Before Deadline

• Final review
• Submit to GSoC website
• Confirm submission

After Submission

• Continue contributing
• Stay active in community
• Be available for questions

Need Help?

Ask on Discord

Get help from mentors and community in #gsoc

View Examples

See our proposal template

Good luck with your proposal! We’re excited to read it. 🚀