Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion 2025/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -259,4 +259,4 @@ The goal of this project is to elevate the open-source Keploy Playground for the
| a GitHub App to Trigger GitHub Actions | https://github.com/keploy/keploy/issues/2531 |
| Denoise Unexpected Parameters in Keploy Testcases | https://github.com/keploy/keploy/issues/2527 |
| Implement Idempotency Check for GET Requests | https://github.com/keploy/keploy/issues/2526 |
| SON Diff viewer re-alignment to top | https://github.com/keploy/keploy/issues/2524 |
<!-- | SON Diff viewer re-alignment to top | https://github.com/keploy/keploy/issues/2524 | This issue is closed-->
71 changes: 51 additions & 20 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,39 +10,42 @@ It captures the external dependency network calls (like database queries, intern

Developers can use keploy alongside their favorite unit testing framework to save time writing testcases.

# Keploy + Google Summer of Code, 2024
This is the main place for all information related to Keploy's participation in Google Summer of Code, 2024 as a mentoring organization.
# Keploy + Google Summer of Code, 2026
This is the main place for all information related to Keploy's participation in Google Summer of Code, 2026 as a mentoring organization.

## What is Google Summer of Code?

[Google Summer of Code](https://summerofcode.withgoogle.com/) is a 16 years old program, run every summer, with the intention of bringing more students into open source.
[Google Summer of Code](https://summerofcode.withgoogle.com/) is a 21 years old program, run every summer, with the intention of bringing more students into open source.

Open source projects apply as mentor organizations and if they are accepted, students send proposals to them to work on a few months' long project. Projects can be planned out by the organizations in advance or can be proposed by students.

Google pays the students, not the organizations they work with. Beginning in 2024, Google is opening the program up to all newcomers of open source that are 18 years and older.
Google pays the students, not the organizations they work with. Beginning in 2026, Google is opening the program up to all newcomers of open source that are 18 years and older.

You can read more about the format of the program and its goals [here](https://google.github.io/gsocguides/mentor/).


## What is the timeline for GSoC 2024?
## What is the timeline for GSoC 2026?
[Full timeline](https://developers.google.com/open-source/gsoc/timeline)

|Important events | Deadline|
| ----- | ----- |
| Organization Applications Open | January 22, 2024|
| Organization Application Deadline | February 6, 2024 |
| Organizations Announced | February 21, 2024 |
| Potential GSoC contributors discuss application ideas with mentoring organizations | February 22 - March 18, 2024 |
| GSoC contributor application period | March 18 - April 2, 2024 |
| Accepted GSoC Contributor projects announced | May 1, 2024 |
| Contributors work on their Google Summer of Code projects | May 27, 2024 - August 26, 2024|
| Mentors submit final GSoC contributor evaluations (standard coding period) | August 26, 2024 - September 2, 2024|
| Initial results of Google Summer of Code 2024 announced | September 3, 2023 |
| Students work on their Google Summer of Code project | May 1, 2024 - November 4, 2024|
| Organization Applications Open | January 19, 2026|
| Organization Application Deadline | February 3, 2026 |
| Organizations Announced | February 19, 2026 |
| Potential GSoC contributors discuss application ideas with mentoring organizations | February 19 - March 15, 2026 |
| GSoC contributor application period | March 16 - March 31, 2026 |
| Accepted GSoC Contributor projects announced | April 30, 2026 |
| Contributors work on their Google Summer of Code projects | May 1 - August 24, 2026|
| Midterm evaluation for Google Summer of Code projects | July 6 - July 10, 2026|
| Mentors submit final GSoC contributor evaluations (standard coding period) | August 17 - August 31, 2026|
| GSoC contributors with extended timelines continue coding | August 24 - November 2, 2026 |
| Final date for all GSoC contributors to submit their final work product and final evaluation | November 2, 2026 |
| Final date for mentors to submit evaluations for GSoC contributor projects with extended deadlines | November 9, 2026 |
| Students work on their Google Summer of Code project | May 1 - November 2, 2026|

#### Statistics
- Since year 2005, 20,000+ students and 19,000+ mentors from over 118 countries has came together to participate in GSoC
- Approximately 38+ million lines of code have been produced
- Since year 2005, 22,000+ students and 21,000+ mentors from over 123 countries has came together to participate in GSoC
- Approximately 48+ million lines of code have been produced

---

Expand All @@ -59,15 +62,43 @@ Please read [The Mentor Guide](MENTOR-GUIDE.md).

Students should have knowledge of git, go, and markdown for most projects since the project work heavily depends on them.

We invite students to look into [our open proposals](https://github.com/keploy/gsoc/tree/main/2023), ask mentors questions to understand the projects better and if interested apply for the project when the application period opens.
We invite students to look into [our open proposals](https://github.com/keploy/gsoc/tree/main/2025), ask mentors questions to understand the projects better and if interested apply for the project when the application period opens.

Mentors would like to know why the project interests the student, whether they have the pre-requisite skills, and most importantly, how they plan to implement it.

We encourage Contributors to set up Keploy for local development and play around with the code and tests to get more comfortable with the project.

## GSoC 2026 Project Ideas

| Project | Difficulty | Hours |
| ------- | ---------- | ----- |
| MCP Server for Keploy (Model Context Protocol Integration) | Medium-Hard | 350 |
| Keploy Blog Website Refactoring, Redesign & Performance Improvements | Medium | 350 |

Here is a brief overview of the projects available for GSoC 2026. For full details, see the [2026 Participant Guide](https://github.com/keploy/gsoc/tree/main/2026).

## Proposal Template

Use our **[Proposal Template](https://docs.google.com/document/d/1yRWf5pXuUij-UwlXB9knDKqk9VYvV5GrNf865p77Y1U/edit?usp=sharing)** when writing your proposal. We recommend the use of Google Docs. Also see the [Proposal Guide](PROPOSAL-GUIDE.md) for more details.

## Our Past GSoC Projects
- [GSoC 2025 Projects](https://github.com/keploy/gsoc/tree/main/2025)
- [GSoC 2024 Projects](https://github.com/keploy/gsoc/tree/main/2024)
- [GSoC 2023 Projects](https://github.com/keploy/gsoc/tree/main/2023)
- [GSoC 2022 Projects](https://github.com/keploy/gsoc/tree/main/2022)

## Make your first contribution here - Solve a Good First Issue

| What to Fix | Good First Issue |
| -------- | ------- |
| Redesign Questions card, Prev/Next cards | https://github.com/keploy/keploy/issues/3657 |
| Fix broken anchors in the doc website | https://github.com/keploy/keploy/issues/3649 |
| Linter for PR changes for samples-go | https://github.com/keploy/keploy/issues/3550 |
| Add New Quickstarts for More Languages (Rust, Ruby, C++, Perl, PHP) | https://github.com/keploy/keploy/issues/3521 |
| Fix blog navbar dropdown ui on mobile devices | https://github.com/keploy/keploy/issues/3431 |
| More Good First Issue | https://github.com/keploy/keploy/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Good%20First%20Issue%22 |

## Community support
We'd love to collaborate with you to make Keploy great. To get started:
* [Slack](https://join.slack.com/t/keploy/shared_invite/zt-12rfbvc01-o54cOG0X1G6eVJTuI_orSA) - Discussions with the community and the team.
* [GitHub](https://github.com/keploy/keploy/issues) - For bug reports and feature requests.

* [GitHub](https://github.com/keploy/keploy/issues) - For bug reports and feature requests.