GSOC 2025 Participation Discussion

[AceTheCreator]

Happy New Year, Everyone! 🎉

I’m excited to kick off the discussion about our participation in Google Summer of Code (GSoC) 2025! After our successful debut as a standalone organization last year, I’m excited to see what we can achieve together this year.

In case you missed it, you can read all about our amazing experience in GSoC 2024 here

Where Things Stand Now

While we’re still waiting for Google to announce GSoC 2025, it’s a good time to start planning our involvement.

Last year, Google announced the program a bit later than usual, so there’s a chance we’ll hear more soon. Regardless, it’s always better to be prepared!

Let’s brainstorm project ideas, and make sure we’re ready to go when the announcement comes 🚀

Collecting Project Idea Proposals

One of the most important steps in our GSoC preparation is identifying exciting and impactful project ideas for contributors to work on. If you have any ideas, here’s how you can contribute. Share your project idea describing:

• What is the issue your project idea addresses?
• What should the contributor build or improve?
• How will this benefit AsyncAPI and its community?
• Is the project suitable for a beginner, intermediate, or advanced contributor?
• What is the estimate hours for project completion?

You can submit your project ideas proposals either as reply to this Disscussion, a seperate GitHub Discussion or GitHub Issue in AsyncAPI GitHub organization.

Don’t worry about having a fully detailed proposal, we’ll help refine the ideas together because this is a collaborative process, and even small ideas can lead to big impacts, so feel free to share!

Interested in Mentoring?

Becoming a GSoC mentor with AsyncAPI is a rewarding experience and comes with plenty of benefits, including:

• Contributing to impactful open-source work.
• Growing your own skills while helping others.
• Building meaningful connections with contributors.
• AsyncAPI exclusive swags 😜

If you’d like to participate as a mentor this year, please let us know by replying in this discussion thread.

How to connect with us

• Join our Slack workspace. Just make sure to follow our code of conduct.
• Join the dedicated Mentorship channel #mentorship that we will use to coordinate all mentorship programs at AsyncAPI

Let’s make GSoC 2025 another success story for AsyncAPI! 🚀

[AayushSaini101]

Project Idea for the Asyncapi CLI: "Introducing new Features and Scaling the CLI"

• Testing: Currently, running test cases locally is challenging due to outdated dependencies. We need to update these dependencies to enable proper debugging and test execution.
• Publish and Sync: We need to provide the ability to publish and sync AsyncAPI files with remote repositories, addressing a long-standing need within the community. This ties in with Generator doesn't pull template from private repo generator#538.
• Custom Validation: Implementing the ability to validate an AsyncAPI file against custom spectral rules would empower developers to enforce their own standards.
• CLI installation takes a lot of time [ https://github.com/[BUG] CLI installation takes a lot of time cli#1387 Research work ]
• lots of Time Taking Processes while using the Generate command.
• Feel free to add more points if you have : )

The benefit of this project: The CLI is a critical tool within the AsyncAPI community, boasting a large number of downloads and an active user base. To maintain its relevance and usability, we need to continuously update it with new features, bug fixes, and improvements that make it more user-friendly and powerful.

Project Strength: In this discussion cycle

@Souvikns @Shurtu-gal @Amzani cc: @AceTheCreator

[AayushSaini101]

Project Idea 2: Create a Java parser wrapper

Implement a Java wrapper of the Go parser, by using the C shared object resulting from the compilation here: https://github.com/asyncapi/parser/blob/master/compile.sh.

It should be fairly straightforward to code but we need to make sure we understand how to compile C for different platforms and architectures.

References

1. https://gist.github.com/steeve/6905542#gistcomment-1988684
2. https://www3.ntu.edu.sg/home/ehchua/programming/java/JavaNativeInterface.html

[mohdjami]

@AayushSaini101, these Project ideas sounds amazing, I appreciate the efforts, will research and go through them. Apart from that I'd love to see some projects/issues in Javascript/Typescript too. Looking forward to it.

[Rohanraj123]

1. Writing go parser
2. Generating C shared objects.
3. Creating Java class for JNI interaction.

Problem would be : compilation for linux : .so for windows .dll and for max .dylib
We need to make sure using gcc for linux and windows and clang for windows. Also passing data between java, go and C can leak data.
These are some problem I can see in this project from seeing it from above. It might also create an issue while memory management and stuff.

I just want to ask one thing. Is there any tools or frameworks suggested for JNI interaction testing. And after that I would love to contribute to this project. I have proficiency in java and golang. Can be visible on github.

[derberg]

parser-go is not actively maintained and it's future is unknown: asyncapi/parser-go#224

[abhishektripathi66]

@AceTheCreator @AayushSaini101 Would like to contribute in this topic.

[IITI-tushar]

Hi @AceTheCreator @AayushSaini101,

I am interested in working with AsyncAPI as a GSoC contributor. If possible, could you please guide me on how I can maximize my chances of getting selected or provide any tips that might help?

It’s difficult to find active issues and get assigned to them. If there are any ongoing projects, I am willing to contribute as a volunteer.

Good luck with GSoC 2025!

[harshita9104]

Hello @AceTheCreator , @AayushSaini101
I hope this message finds you well, Could you please guide on which project to start working on for GSOC 2025
Thank you.

[Valley-15]

Hello @AceTheCreator @AayushSaini101 , I am an opensource web developer interested to contribute in AsyncApI, could you send contribution guide

[Rohanraj123]

Integration of AsyncApi with Kubernetes.
A tool built in Golang to deploy and manage AsyncAPI-defined services on Kubernetes.
It will help in simplifying the deployment of event-driven systems in Kubernetes.

Goal is to build a Golang tool that can deploy and manage AsyncAPI-defined services on Kubernetes. This tool would automate the generation of Kubernetes manifests (such as Deployments, Services) from AsyncAPI specs, configure messaging systems like Kafka or RabbitMQ, and offer observability features for deployed services.

I would love to hear suggestions on this idea. Also if selected then I would love to work on this idea as well.

[Manancode]

My Idea : Cross-Protocol Message Testing Framework

Currently, users face challenges when testing applications that use multiple messaging protocols (like Kafka, WebSocket, MQTT) together. There's no unified way to test message flows across these different protocols, validate messages, or visualize the entire system working together

We can Build a comprehensive testing framework that includes:

• A unified testing interface for multiple protocols
• Mock servers for each supported protocol
• Automated test case generation from AsyncAPI specifications
• A web-based dashboard for visualizing message flows and test results
• Test report generation
• Protocol-specific validation rules

This framework will:

• Save developers significant time by enabling testing of complex flows in one place
• Reduce errors by providing comprehensive testing across protocols
• Make it easier to debug issues with real-time visualization
• Help teams ensure their message-based systems work correctly
• Improve the quality of event-driven applications

We can use Glee to create mock servers for Kafka, MQTT, WebSocket, and more. It can help in simulating real-time message flows.

would love to discuss and take more inputs regarding this from the mentors
@AceTheCreator

[AayushSaini101]

Project Idea: New Template Java+Quarkus template for the Asyncapi Generator

I want to propose a new idea for a template that is Java+Quarkus. Quarkus is a very popular and open-source framework as well as very fast-growing in the cloud native community, I also used it in my company,

Around the world, in 2024, over 1334 companies started using Quarkus https://6sense.com/tech/other-dev-tools/quarkus-market-share.

Understanding template: https://www.asyncapi.com/docs/tools/generator/template

[aakankshabhende]

@AayushSaini101 @AceTheCreator I would love to mentor this.

[AayushSaini101]

Thanks @aakankshabhende happy to collab lets wait for the approval

[abhishektripathi66]

@AceTheCreator @AayushSaini101 Would like to contribute in this topic.

[NalinDalal]

how do i get started?

[hxrshxz]

Project Title: Dockerizing the AsyncAPI Specification Repository for Simplified Development and Deployment

1. What is the issue your project idea addresses?

Setting up a development environment for the AsyncAPI Specification repository can be a bit tricky for new contributors. Issues like dependency conflicts, version mismatches, and the challenge of ensuring a consistent environment across different machines can slow down the onboarding process. Furthermore, the absence of a containerized setup limits the ability to integrate seamlessly into CI/CD pipelines, and it can make automated testing less efficient. By Dockerizing the repository, these challenges can be addressed, streamlining the development process and improving the overall experience for contributors.

2. What should the contributor build or improve?

Here’s what I plan to work on:

Dockerizing the repo: I’ll create a Dockerfile to containerize the AsyncAPI Specification repository, making sure all the required dependencies for development and testing are pre-configured.
Service orchestration: If necessary, I’ll develop a docker-compose.yml file to help orchestrate multiple components (such as parsers, validators, or related services), ensuring everything runs smoothly together.
CI/CD integration: I will integrate the Docker setup into existing CI/CD pipelines to enable reliable and reproducible builds and tests, making sure everything works seamlessly.
Optimized Docker images: The Docker images will be lightweight and secure, with a focus on multi-stage builds to optimize both development and production environments.
Comprehensive documentation: I’ll write clear documentation explaining how to use the Docker setup for local development, running tests, and incorporating it into CI/CD workflows.

3. How will this benefit AsyncAPI and its community?

For contributors: By providing a containerized setup, I can drastically reduce setup time and eliminate the "works on my machine" issue. New developers will be able to start contributing more quickly and with fewer environment-related headaches.
For maintainers: A standardized development environment means that all contributors will be using the same tools and versions, ensuring fewer inconsistencies across different setups.
For the broader community: Dockerizing AsyncAPI tools will make it easier to distribute them, encouraging more people to adopt and use the tools. It also streamlines the process of deploying these tools in different environments.
For CI/CD workflows: A containerized setup will ensure automated builds and tests are performed in consistent environments, making the whole process more reliable and reducing time spent debugging issues related to local configurations.

4. Is the project suitable for a beginner, intermediate, or advanced contributor?

This project is perfect for intermediate contributors who have experience with Docker, understand GitHub workflows, and are familiar with CI/CD concepts. While Docker is an accessible technology, integrating it with CI/CD pipelines and ensuring everything works across different services requires a bit more experience.

5. What is the estimate of hours for project completion?

I estimate that the project will require about 180-240 hours in total, broken down as follows:

Research and Planning (20-30 hours): I’ll take time to get familiar with the repository, understand its structure, dependencies, and the specific needs of the community.
Dockerfile Development (40-50 hours): Writing the Dockerfile and testing it to make sure it includes all the necessary dependencies and works smoothly in different environments.
Service Orchestration (Optional, 30-40 hours): If the repository requires multiple services to run (e.g., a parser, database, etc.), I’ll develop a docker-compose.yml file to make service orchestration easier.
CI/CD Integration (40-50 hours): Integrating the Docker setup into existing CI/CD pipelines, ensuring the Dockerized environment works well with automated tests and builds.
Documentation and Feedback (30-40 hours): Writing detailed documentation, making sure it’s clear, and incorporating any feedback from mentors or the community.
Testing and Optimization (20-30 hours): Ensuring the Docker image is as lightweight, secure, and optimized as possible while maintaining full functionality.

[abhishektripathi66]

@AceTheCreator @hxrshxz Would like to contribute in this topic.

[prashantrai-30]

Hey @AceTheCreator @AayushSaini101 ,

I’m excited about the opportunity to contribute to AsyncAPI as part of Google Summer of Code (GSoC) 2025. I’ve been exploring the project and am eager to get involved.

Could you kindly provide some guidance on the following:

• Where to find key resources or documentation that will help me understand AsyncAPI and its workflow.
• Any good first issues or tasks that I can tackle to familiarize myself with the codebase.
• Steps for setting up the project locally to start exploring and contributing effectively.

I look forward to contributing to AsyncAPI and becoming an active member of the community. Thank you for your support!

[shwetd19]

Hey @AceTheCreator @AayushSaini101

I'm really excited about the chance to contribute to AsyncAPI as part of Google Summer of Code (GSoC) 2025. I've been learning more about the project and can't wait to get started.

Project Idea: AsyncAPI Studio Plugin System

What it addresses:
AsyncAPI Studio currently has a monolithic architecture. A plugin system would allow the community to extend Studio's functionality without modifying core code.

Features to build:

• Plugin SDK with clear interfaces for extending UI, adding new validators, and custom renderers
• Hot-reload capability for plugin development
• Plugin marketplace infrastructure
• Security sandbox for third-party plugins
• Documentation generation for plugin APIs

Benefits:

• Enables community-driven feature development
• Simplifies maintenance by decoupling extensions
• Allows organizations to build private plugins for internal tools
• Creates opportunities for ecosystem growth

Difficulty: Intermediate
Estimated hours: 175-200

I'd be interested in working on this project. I have experience with plugin architectures and TypeScript/React development.

Let me know if this aligns with AsyncAPI's goals!

[Hashir-Akbar]

Project Idea for the Asyncapi Web Application : "Improving the overall performance of the web application, using SSG techniques for static pages and making the web app fast, The layout consistency fix, adding animations to web app without compromising with performance. Refactoring the UI components, fixing spacing in the design of web app, Overall fixing the design, performance and Accessibility issues "

Testing: UI testing/Performance testing/ testing for different browsers for animations. We can utilize Jest.

The benefit of this idea: First Impression is the last impression is what I believe, In order to make users comfortable of using the official docs, tutorials etc and making robust scalable platform I think we should first focus on these issues and make a timeline and type of code conduct on writing and testing the components and when the project will scale it, this will help it greatly because later on the project might become vast and it may have more components later on it will become very difficult to fix all these issues.

I am interested in working with AsyncAPI as a GSoC contributor

Google Page Insights of web app:

Desktop	Mobile
Desktop Link	Mobile Link

and Accessibility Audit:

Accessibility Audit Link

If you see any issues I am excited to check it out and fix it. We can collaborate on this idea.

[Hashir-Akbar]

We can also review these types of issues as shown in this discussion => https://github.com/orgs/asyncapi/discussions/1659

also we can check the relative UI issues and overall improve & make sure to fix.

[AayushSaini101]

@Hashir-Akbar Good Proposal, try to start contributing before on the website to show the potential thanks

[Hashir-Akbar]

@AayushSaini101 Got it, I will start contributing to it. Thank you!