Repository navigation
docs: update GSoC contribution guide from 2023 to 2026 - #836
Manthan-Shirsath wants to merge 1 commit into
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
chilkotiKartik
left a comment
chilkotiKartik
left a comment
There was a problem hiding this comment.
LGTM! Thoroughly verified changes in docs: update GSoC contribution guide from 2023 to 2026. Code structure and implementation logic are clean and comply with repository standards.
dhananjay6561
left a comment
dhananjay6561
left a comment
There was a problem hiding this comment.
Thanks for picking this up @Manthan-Shirsath, this page was definitely overdue for an update. Left a few inline comments.
One blocker that isn't tied to a specific line: the live site serves docs version 4.0.0, so changes to docs/gsoc/contribution-guide.md alone won't show up on the website. Please apply the same update to versioned_docs/version-4.0.0/gsoc/contribution-guide.md as well.
Also, while you're in this file, the line "Keploy is among the first few mentoring organizations from India 🇮🇳 this year!" in the Keploy X GSoC section is stale in the same way. Could you reword it so it isn't tied to a specific year?
|
|
||
| [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 20+ years old program, run every summer, with the intention of bringing more students into open source. |
There was a problem hiding this comment.
The blank line between this paragraph and the next one got removed, so they'll render as a single paragraph. Please add it back.
Also a small wording nit: "is a 20+ years old program" reads a bit off. Something like "has been running every summer since 2005" avoids the number going stale again.
| 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 2023, 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 2024, Google opened the program up to all newcomers of open source that are 18 years and older. |
There was a problem hiding this comment.
GSoC actually opened up to all newcomers 18+ starting in 2022, not 2024 (the 2023 in the original was wrong too). Reference: https://opensource.googleblog.com/2022/02/Google%20Summer%20of%20Code%202022%20is%20open%20for%20mentor%20organization%20applications.html
Since the program is no longer students-only, could you also change "Google pays the students" to "contributors"?
| 1. If you are new to Keploy, try setting up Keploy in your local machine and running one (or more) of the sample applications. You can refer the [docs](#docs). | ||
| 2. You can then check out the [projects](#projects) that are selected for GSoC 2023 and try completing the tasks in the task list. Remember, the tasks will act as a selection criteria for shortlisting candidates. | ||
| 3. You can connect with the mentors over slack to clear any of your doubts. | ||
| 2. You can then check out the [projects](https://github.com/keploy/gsoc) that are selected for the current GSoC year and try completing the tasks in the task list. Remember, the tasks will act as a selection criteria for shortlisting candidates. |
There was a problem hiding this comment.
Minor: this now points off-page even though there's a projects section right below. Either link to #projects-in-gsoc-2026 or point directly at the year folder in the gsoc repo, whichever fits better with the timeline change below.
| - Design: creating logos, icons, or other design elements for the project. | ||
|
|
||
| If you are interested in making a non-code contribution to a Keploy project, please reach out to the project mentors to discuss how you can best contribute. --> | ||
| ## Projects in GSoC 2026 |
There was a problem hiding this comment.
Hardcoding the year here means this heading goes stale again next year. Maybe just "Projects" or "Current GSoC Projects", since the content already links to the repo for the current year's ideas.
| | Important events | Deadline | | ||
| | ---------------------------------------------------------------------------------- | ---------------------------- | | ||
| | Organization Applications Open | January 2026 | | ||
| | Organizations Announced | February 19, 2026 | | ||
| | Contributor Application Period | March 16 - March 31, 2026 | | ||
| | Accepted GSoC Contributors Announced | April 30, 2026 | | ||
| | GSoC Coding Period | May - August 2026 | |
There was a problem hiding this comment.
The exact dates shift every year, and hardcoded dates are what made this page outdated in the first place. Instead of the table, could you keep a short description of the general flow (org applications in Jan-Feb, contributor applications in March, results around April-May, coding over the summer) and link the official timeline: https://developers.google.com/open-source/gsoc/timeline
That page always reflects the current year, so we won't need a PR every January to keep this updated.
|
Hey! I noticed the Hacktoberfest documentation still describes the traditional pull-request-based format and mentions Keploy participating in Hacktoberfest. Hacktoberfest 2026 has changed its format, with PRs no longer counting toward rewards. I couldn't confirm whether Keploy is participating this year. Are these docs still intended to describe Keploy's current Hacktoberfest activities? If an update is needed, I'm happy to work on it. We could address it in this PR if you think it's within scope, or open a separate issue and assign it to me. If Keploy is no longer participating, we could also consider removing the page or retaining it as historical documentation. |
|
@Manthan-Shirsath good catch, but let's keep this PR scoped to GSoC. I'll check internally whether we're doing Hacktoberfest this year and open an issue if the pages need updating. |
Signed-off-by: Manthan Shirsath <manthanshirsath23@gmail.com>
16bad23 to
1a3965a
Compare
This branch has not been deployed
3 participants
What changed
Why
The GSoC contribution guide was outdated by 3 years, showing stale project listings and incorrect timeline dates that would mislead new contributors.