docs: add GSoC 2026 project ideas#2276
Merged
asyncapi-bot merged 6 commits intoasyncapi:masterfrom Feb 2, 2026
Merged
Conversation
AceTheCreator
requested review from
asyncapi-bot-eve,
bandantonio,
derberg and
thulieblack
as code owners
📝 WalkthroughWalkthroughAdds a new GSoC 2026 project ideas documentation page with five mentorship proposals (details, mentors, contact, FAQ) and updates the 2025 GSoC page frontmatter Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Fix all issues with AI agents
In `@docs/050-mentorship-program/summer-of-code-2026-project-ideas.md`:
- Line 43: The header link text "Improving the AsyncAPI React Component "
contains a trailing space inside the square brackets; remove the trailing space
so the line reads ## 4) [Improving the AsyncAPI React
Component](https://github.com/asyncapi/asyncapi-react/issues/1214) to satisfy
markdownlint MD039 (no-space-in-links) and avoid the extra space in the link
text.
- Around line 14-18: The section header "AsyncAPI Generator Maintainership -
Hands-on Open Source Experience" should hyphenate the compound adjective; update
the header string to "AsyncAPI Generator Maintainership - Hands-on Open-Source
Experience" (locate the header text in the markdown for this project idea and
replace the unhyphenated "Open Source" with "Open-Source").
- Around line 32-34: Replace the hard-coded counts in the paragraph under the
heading "## 3) [AsyncAPI Website Maintainership - From Contributor to
Maintainer]" by either appending an explicit date (e.g., "over 130 open issues
and 100+ open pull requests as of YYYY-MM-DD") or using softer wording (e.g.,
"dozens of open issues and many open pull requests") so the statement doesn’t
become stale; update the sentence that currently reads "with over 130 open
issues and 100+ open pull requests" accordingly.
- Around line 23-30: The Tenz Delek GitHub profile link uses http and should use
HTTPS to avoid mixed-content issues; update the markdown link for "Tenz Delek"
(seen in the AsyncAPI Conference Website Maintainership & Sustainability entry)
from http://github.com/TenzDelek to https://github.com/TenzDelek and verify any
other GitHub profile links (e.g., "Azeez Elegbede") use the https scheme for
consistency.
Comment on lines
14
to
18
| ## 1) [AsyncAPI Generator Maintainership - Hands-on Open Source Experience](https://github.com/asyncapi/generator/issues/1860) | ||
| This initiative aims to guide you on a journey from being a contributor to becoming a maintainer of the project. You'll gain insight into the responsibilities of a maintainer, involving tasks beyond mere coding. | ||
|
|
||
| - 🎯 **Outcome:** Taking responsibility for the AsyncAPI Generator's project future and continuous improvement | ||
| - 🛠️ **Skills Required:** JavaScript, Docker, Testing (Jest or similar), AsyncAPI knowledge, AsyncAPI Template Development, CI/CD, Technical Documentation |
There was a problem hiding this comment.
Hyphenate “Open-Source” in the title.
Minor grammar polish for the compound adjective.
✏️ Suggested fix
-## 1) [AsyncAPI Generator Maintainership - Hands-on Open Source Experience](https://github.com/asyncapi/generator/issues/1860)
+## 1) [AsyncAPI Generator Maintainership - Hands-on Open-Source Experience](https://github.com/asyncapi/generator/issues/1860)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## 1) [AsyncAPI Generator Maintainership - Hands-on Open Source Experience](https://github.com/asyncapi/generator/issues/1860) | |
| This initiative aims to guide you on a journey from being a contributor to becoming a maintainer of the project. You'll gain insight into the responsibilities of a maintainer, involving tasks beyond mere coding. | |
| - 🎯 **Outcome:** Taking responsibility for the AsyncAPI Generator's project future and continuous improvement | |
| - 🛠️ **Skills Required:** JavaScript, Docker, Testing (Jest or similar), AsyncAPI knowledge, AsyncAPI Template Development, CI/CD, Technical Documentation | |
| ## 1) [AsyncAPI Generator Maintainership - Hands-on Open-Source Experience](https://github.com/asyncapi/generator/issues/1860) | |
| This initiative aims to guide you on a journey from being a contributor to becoming a maintainer of the project. You'll gain insight into the responsibilities of a maintainer, involving tasks beyond mere coding. | |
| - 🎯 **Outcome:** Taking responsibility for the AsyncAPI Generator's project future and continuous improvement | |
| - 🛠️ **Skills Required:** JavaScript, Docker, Testing (Jest or similar), AsyncAPI knowledge, AsyncAPI Template Development, CI/CD, Technical Documentation |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~14-~14: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...API Generator Maintainership - Hands-on Open Source Experience](https://github.com/asyncapi...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
🤖 Prompt for AI Agents
In `@docs/050-mentorship-program/summer-of-code-2026-project-ideas.md` around
lines 14 - 18, The section header "AsyncAPI Generator Maintainership - Hands-on
Open Source Experience" should hyphenate the compound adjective; update the
header string to "AsyncAPI Generator Maintainership - Hands-on Open-Source
Experience" (locate the header text in the markdown for this project idea and
replace the unhyphenated "Open Source" with "Open-Source").
Comment on lines
23
to
30
| ## 2) [AsyncAPI Conference Website Maintainership & Sustainability](https://github.com/asyncapi/conference-website/issues/919) | ||
| This project focuses on ensuring the long-term sustainability of the AsyncAPI Conference website by improving its technical foundation and onboarding a new maintainer through a hands-on GSoC experience. | ||
|
|
||
| - 🎯 **Outcome:** A well-maintained, scalable AsyncAPI Conference website with a clearly onboarded long-term maintainer | ||
| - 🛠️ **Skills Required:** Javascript/Typescript, Next.js, Web Performance, Accessibility | ||
| - 🧩 **Difficulty:** Hard | ||
| - 👩🏿🏫 **Mentor(s):** [Azeez Elegbede](https://github.com/AceTheCreator) | [Tenz Delek](http://github.com/TenzDelek) | ||
| - ⏳ **Length:** 350 Hours |
There was a problem hiding this comment.
Use HTTPS for GitHub profile links.
Consistent scheme and avoids mixed-content warnings.
🔒 Suggested fix
-- 👩🏿🏫 **Mentor(s):** [Azeez Elegbede](https://github.com/AceTheCreator) | [Tenz Delek](http://github.com/TenzDelek)
+- 👩🏿🏫 **Mentor(s):** [Azeez Elegbede](https://github.com/AceTheCreator) | [Tenz Delek](https://github.com/TenzDelek)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## 2) [AsyncAPI Conference Website Maintainership & Sustainability](https://github.com/asyncapi/conference-website/issues/919) | |
| This project focuses on ensuring the long-term sustainability of the AsyncAPI Conference website by improving its technical foundation and onboarding a new maintainer through a hands-on GSoC experience. | |
| - 🎯 **Outcome:** A well-maintained, scalable AsyncAPI Conference website with a clearly onboarded long-term maintainer | |
| - 🛠️ **Skills Required:** Javascript/Typescript, Next.js, Web Performance, Accessibility | |
| - 🧩 **Difficulty:** Hard | |
| - 👩🏿🏫 **Mentor(s):** [Azeez Elegbede](https://github.com/AceTheCreator) | [Tenz Delek](http://github.com/TenzDelek) | |
| - ⏳ **Length:** 350 Hours | |
| ## 2) [AsyncAPI Conference Website Maintainership & Sustainability](https://github.com/asyncapi/conference-website/issues/919) | |
| This project focuses on ensuring the long-term sustainability of the AsyncAPI Conference website by improving its technical foundation and onboarding a new maintainer through a hands-on GSoC experience. | |
| - 🎯 **Outcome:** A well-maintained, scalable AsyncAPI Conference website with a clearly onboarded long-term maintainer | |
| - 🛠️ **Skills Required:** Javascript/Typescript, Next.js, Web Performance, Accessibility | |
| - 🧩 **Difficulty:** Hard | |
| - 👩🏿🏫 **Mentor(s):** [Azeez Elegbede](https://github.com/AceTheCreator) | [Tenz Delek](https://github.com/TenzDelek) | |
| - ⏳ **Length:** 350 Hours |
🤖 Prompt for AI Agents
In `@docs/050-mentorship-program/summer-of-code-2026-project-ideas.md` around
lines 23 - 30, The Tenz Delek GitHub profile link uses http and should use HTTPS
to avoid mixed-content issues; update the markdown link for "Tenz Delek" (seen
in the AsyncAPI Conference Website Maintainership & Sustainability entry) from
http://github.com/TenzDelek to https://github.com/TenzDelek and verify any other
GitHub profile links (e.g., "Azeez Elegbede") use the https scheme for
consistency.
Comment on lines
32
to
34
| ## 3) [AsyncAPI Website Maintainership - From Contributor to Maintainer](https://github.com/asyncapi/website/issues/5052) | ||
| This initiative is designed to guide contributors on a hands-on journey from being an active contributor to becoming a maintainer of the AsyncAPI Website. The project currently requires additional maintainers to help manage its growing scale, with over 130 open issues and 100+ open pull requests. | ||
|
|
There was a problem hiding this comment.
Avoid hard-coded issue/PR counts without a date.
These numbers will quickly drift; suggest adding “as of ” or using softer wording.
📝 Suggested fix
-This initiative is designed to guide contributors on a hands-on journey from being an active contributor to becoming a maintainer of the AsyncAPI Website. The project currently requires additional maintainers to help manage its growing scale, with over 130 open issues and 100+ open pull requests.
+This initiative is designed to guide contributors on a hands-on journey from being an active contributor to becoming a maintainer of the AsyncAPI Website. The project currently requires additional maintainers to help manage its growing scale, with a large backlog of open issues and pull requests (as of Feb 2026).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## 3) [AsyncAPI Website Maintainership - From Contributor to Maintainer](https://github.com/asyncapi/website/issues/5052) | |
| This initiative is designed to guide contributors on a hands-on journey from being an active contributor to becoming a maintainer of the AsyncAPI Website. The project currently requires additional maintainers to help manage its growing scale, with over 130 open issues and 100+ open pull requests. | |
| ## 3) [AsyncAPI Website Maintainership - From Contributor to Maintainer](https://github.com/asyncapi/website/issues/5052) | |
| This initiative is designed to guide contributors on a hands-on journey from being an active contributor to becoming a maintainer of the AsyncAPI Website. The project currently requires additional maintainers to help manage its growing scale, with a large backlog of open issues and pull requests (as of Feb 2026). |
🤖 Prompt for AI Agents
In `@docs/050-mentorship-program/summer-of-code-2026-project-ideas.md` around
lines 32 - 34, Replace the hard-coded counts in the paragraph under the heading
"## 3) [AsyncAPI Website Maintainership - From Contributor to Maintainer]" by
either appending an explicit date (e.g., "over 130 open issues and 100+ open
pull requests as of YYYY-MM-DD") or using softer wording (e.g., "dozens of open
issues and many open pull requests") so the statement doesn’t become stale;
update the sentence that currently reads "with over 130 open issues and 100+
open pull requests" accordingly.
docs/050-mentorship-program/summer-of-code-2026-project-ideas.md
Outdated
Show resolved
Hide resolved
Contributor
|
🚀 Docs preview deployed |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@docs/050-mentorship-program/summer-of-code-2026-project-ideas.md`:
- Around line 27-28: Replace the nonstandard casing "Javascript/Typescript" in
the skills lists with the proper product casing "JavaScript/TypeScript" wherever
it appears (e.g., the line starting with "🛠️ **Skills Required:**
Javascript/Typescript, Next.js, Web Performance, Accessibility" and the other
occurrence around the later skills block), ensuring consistency across the
document.
- Around line 78-80: The paragraph under the FAQ item "2. **Is using ChatGPT for
GSoC project proposals allowed?**" is misindented relative to the following
items; fix it by aligning its indentation to match the other list entries (same
leading spaces as item 3) so it renders as a proper nested paragraph under the
numbered list — locate the block containing the exact string "We advise against
using ChatGPT or similar AI tools for your GSoC project proposals with
AsyncAPI." and adjust the leading spaces so it matches the surrounding list
indentation.
docs/050-mentorship-program/summer-of-code-2026-project-ideas.md
Outdated
Show resolved
Hide resolved
Comment on lines
78
to
80
| 2. **Is using ChatGPT for GSoC project proposals allowed?** | ||
| We advise against using ChatGPT or similar AI tools for your GSoC project proposals with AsyncAPI. If you choose to use such tools, we require that you fully disclose this in your application. | ||
|
|
There was a problem hiding this comment.
Fix indentation under FAQ item 2 for clean list rendering.
The paragraph under item 2 is less indented than item 3, which can render inconsistently.
✏️ Suggested fix
- We advise against using ChatGPT or similar AI tools for your GSoC project proposals with AsyncAPI. If you choose to use such tools, we require that you fully disclose this in your application.
+ We advise against using ChatGPT or similar AI tools for your GSoC project proposals with AsyncAPI. If you choose to use such tools, we require that you fully disclose this in your application.🤖 Prompt for AI Agents
In `@docs/050-mentorship-program/summer-of-code-2026-project-ideas.md` around
lines 78 - 80, The paragraph under the FAQ item "2. **Is using ChatGPT for GSoC
project proposals allowed?**" is misindented relative to the following items;
fix it by aligning its indentation to match the other list entries (same leading
spaces as item 3) so it renders as a proper nested paragraph under the numbered
list — locate the block containing the exact string "We advise against using
ChatGPT or similar AI tools for your GSoC project proposals with AsyncAPI." and
adjust the leading spaces so it matches the surrounding list indentation.
thulieblack
changed the title
thulieblack
previously approved these changes
Feb 2, 2026
thulieblack
reviewed
Feb 2, 2026
docs/050-mentorship-program/summer-of-code-2026-project-ideas.md
Outdated
Show resolved
Hide resolved
thulieblack
approved these changes
Feb 2, 2026
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docs/050-mentorship-program/summer-of-code-2026-project-ideas.md`:
- Line 32: Remove the trailing space at the end of the header line containing
"3) [AsyncAPI Website Maintainership - From Contributor to
Maintainer](https://github.com/asyncapi/website/issues/5052)"; edit that header
(the line starting with "## 3) [AsyncAPI Website Maintainership - From
Contributor to Maintainer]") to delete the extra space after the closing
parenthesis so the line ends immediately after the link.
| - 👩🏿🏫 **Mentor(s):** [Azeez Elegbede](https://github.com/AceTheCreator) | [Tenz Delek](http://github.com/TenzDelek) | ||
| - ⏳ **Length:** 350 Hours | ||
|
|
||
| ## 3) [AsyncAPI Website Maintainership - From Contributor to Maintainer](https://github.com/asyncapi/website/issues/5052) |
There was a problem hiding this comment.
Remove trailing space after the link.
Line 32 has a trailing space after the closing bracket, which is unnecessary.
🧹 Suggested fix
-## 3) [AsyncAPI Website Maintainership - From Contributor to Maintainer](https://github.com/asyncapi/website/issues/5052)
+## 3) [AsyncAPI Website Maintainership - From Contributor to Maintainer](https://github.com/asyncapi/website/issues/5052)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## 3) [AsyncAPI Website Maintainership - From Contributor to Maintainer](https://github.com/asyncapi/website/issues/5052) | |
| ## 3) [AsyncAPI Website Maintainership - From Contributor to Maintainer](https://github.com/asyncapi/website/issues/5052) |
🤖 Prompt for AI Agents
In `@docs/050-mentorship-program/summer-of-code-2026-project-ideas.md` at line 32,
Remove the trailing space at the end of the header line containing "3) [AsyncAPI
Website Maintainership - From Contributor to
Maintainer](https://github.com/asyncapi/website/issues/5052)"; edit that header
(the line starting with "## 3) [AsyncAPI Website Maintainership - From
Contributor to Maintainer]") to delete the extra space after the closing
parenthesis so the line ends immediately after the link.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docs/050-mentorship-program/summer-of-code-2026-project-ideas.md`:
- Line 6: Update the status line "**Program Status: Application Phase**" to
include an explicit "as of" date, e.g. "**Program Status: Application Phase (as
of YYYY-MM-DD)**"; edit the markdown where that exact string appears and replace
it with the new form so the status is time-stamped and easy to update going
forward.
🧹 Nitpick comments (1)
docs/050-mentorship-program/summer-of-code-2026-project-ideas.md (1)
10-22: Consider adding “featured” and “all projects” tables for consistency.Mentorship idea pages typically present a featured subset and a complete list via two tables; adding them would make the page consistent and easier to scan.
Based on learnings “In AsyncAPI mentorship project ideas documents, there are typically two tables: the first shows selected/featured projects (subset) and the second shows all available projects (complete list). Duplication between these tables is intentional and serves to highlight important projects while maintaining completeness.”
| weight: 200 | ||
| --- | ||
|
|
||
| > **Program Status: Application Phase** |
There was a problem hiding this comment.
Add an “as of” date to the Program Status.
“Application Phase” can become stale; add a concrete date to keep it trustworthy.
✏️ Proposed fix
-> **Program Status: Application Phase**
+> **Program Status: Application Phase (as of Feb 2, 2026)**📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| > **Program Status: Application Phase** | |
| > **Program Status: Application Phase (as of Feb 2, 2026)** |
🤖 Prompt for AI Agents
In `@docs/050-mentorship-program/summer-of-code-2026-project-ideas.md` at line 6,
Update the status line "**Program Status: Application Phase**" to include an
explicit "as of" date, e.g. "**Program Status: Application Phase (as of
YYYY-MM-DD)**"; edit the markdown where that exact string appears and replace it
with the new form so the status is time-stamped and easy to update going
forward.
Member
|
/rtm |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here's a curated list of GSoC 26 Project ideas that focus on project maintainership.
cc @thulieblack
Summary by CodeRabbit