Find open source projects actively accepting contributors. Search repositories, filter by program milestones, difficulty tags, or tech stack.
Use our Orbit AI Matcher to find out! Get instant matching scores based on your developer skills, preferred frameworks, and contribution experience.
Convert your selected open-source project into a winning GSoC, LFX, or Outreachy application using Proposal Studio.
Rocket.Chat currently uses multiple virtualization patterns across list-heavy UI surfaces, especially in core room and contextual views. This makes scrolling behavior, pagination, testing, and future maintenance less consistent, and increases the effort required to review or extend list implementations. My project will establish a shared virtualization baseline for Rocket.Chat using a reusable wrapper integrated with the existing OverlayScrollbars-based scrollbar system, then apply that baseline to a focused set of core user-facing surfaces such as Threads, Discussions, and Message Search. The implementation will build on existing Rocket.Chat frontend patterns, including TanStack Query-based pagination hooks and shared query/cache infrastructure, so the migration can be incremental rather than disruptive. The main deliverables are: a reviewed shared virtualization abstraction suitable for merge, a reusable migration pattern for flat list surfaces, migrations of selected core components, focused test coverage for the wrapper and migrated screens, and contributor documentation covering wrapper usage, pagination integration, scrollbar wiring, and testing. If time allows, I will also migrate an additional core surface such as Room Files or prepare the path for future grouped-list migrations.
<p>A crucial component of the user experience with bots in Rocket chat android app is rich messages. Currently, there is only minimal support for rich messages in the Android app with the only support for Horizontal Buttons, Multiple Buttons, Image Buttons with URL and Buttons with URL.</p> <h4>I propose to enhance the user experience with bots by implementing other rich messages types, interactive rich messages, welcome screen for bots into the existing Rocket chat Android Client.</h4> <p>The goal is to improve user experience with bots by:</p> <ul> <li>Adding Webview support to the existing Rich message types.</li> <li>Adding support to the deferred rich message types like temporary text buttons, and other types which requires editing of the message.</li> <li>Implementing other Rich messages types like section with menus, overflows, buttons, Date pickers, Articles.</li> <li>Adding interactivity to the rich messages to increase usability with bots.</li> <li>Implementing a welcome screen for bots similar to facebook.</li> <li>Writing unit tests and espresso tests for UI level testing</li> <li>Implementing a bot with all the new features.</li> <li>Solving random crashes and left issues and improving documentation.</li> </ul>
<p>Primarily, my main focus of summers would be whole settings subsystem. I will work on making it more robust and improving the quality of the code.</p>
<p>Cascading Style Sheets is by far the most powerful tool in a web developer's toolbox. It helps you style the website exactly the way you imagined it to be. But all browser's aren't designed the same and some CSS rules might end up breaking your site on certain platforms. With the introduction of Firefox 76, came a new panel in inspector - The Compatibility Panel. This panel informs one of the dangerous CSS rules in the website's stylesheet and tells them exactly on which browsers, they may end up being a nuisance on. The Inline CSS Warnings helps developers detect these issues on the fly, putting addition information of the problem, just a click away. Building tools to help you instill confidence in your product - That is what the Firefox DevTools Community is working hard at.</p>
<p>Balrog is the software that runs the server side component of the update system used by Firefox and other Mozilla products. It helps ship updates faster and with much more flexibility than it's predecessor AUS (Application Update Service). However, Balrog's Admin API is mostly hand-written code, with some usage of wtforms for validation. It largely works, but it has some rough spots and inconsistencies. The move to an OpenAPI Specification will have multiple benefits including less code maintenance, multiple UI and backend bug fixes, better documentation and easier for clients to visualize and interact with API’s resources. Connexion, a framework designed for flask-based applications, will be used to handle HTTP requests based on OpenAPI Specification of the API to map the endpoints to the Balrog’s existing methods for serving the requests.</p>
<p>Amahi-Anywhere file server is complete and working as of now, but there can be certain improvements that can be done to so as to improve both, the code base as well as user experience. This proposal focuses on the implementation of those improvements and optimizations. Improvements in <strong>logging system</strong> will help the developers to get a better knowledge of the events happening in the system. The addition of a good <strong>caching mechanism</strong> will ultimately lead to a reduction of latency by a huge factor and thus will greatly enhance user experience.</p> <p>This project also focuses on the implementation of some features which in turn will make the management of the Amahi app easier with the help of special dashboards where users can easily monitor the system and take action accordingly.</p>
<p>In this project, my work will mainly focus on to develop new features for Amahi 12. Amahi is one of the best open-source media server software available right now and is well known for its easy to use interface and functionalities. The "Platform" is the core software of Amahi and it is in development for the last 7 years. Amahi 11 is the latest version of Amahi and it is officially released last year in 2018 and provides support for fedora 27. Amahi 12 is currently in the development phase and will be released soon with support to fedora 30.</p> <p>Main Objectives:-</p> <ul> <li>Improve Platform and implement new features for Amahi 12.</li> <li>Fix existing plugins and provide them support for the latest version of Amahi.</li> <li>Update Dockerfile and create new docker image supporting latest Amahi.</li> <li>Completely implement backend and plugin of friending feature. This will help Amahi users to share files and Shares with other Amahi users with permissions control.</li> <li>Implement let's encrypt feature for Amahi to generate certificates for establishing secure connections with yourhda.com subdomains.</li> </ul>
This project will enhance Makim by implementing Language Server Protocol (LSP) support for its YAML configuration files. This will introduce features like autocompletion, syntax validation, hover documentation, and custom commands directly within code editors. The project will deliver a Language Server and a VS Code extension, significantly improving the developer experience and making Makim more user-friendly.
<p><a href="https://wiki.debian.org/FreedomBox/Plinth" target="_blank">Plinth</a> is a web interface to administer the functions of the FreedomBox which is a Debian based project, and the main goal of this idea is to make it available for Fedora.</p> <p>To solve this issue, I made up a scenario in this proposal, it can be divided roughly into two parts. The first one is modifying the source code module by module to convert it to RPM-based, including replacing the apt command code with the dnf command code or fit both of them, changing the Deb-based packages into RPM-based packages which play the same roles and testing after each module finished. The second part is a little scattered, including making a RPM package for Plinth and setting up a repo for it in <a href="https://copr.fedorainfracloud.org/" target="_blank">Copr</a>, testing inside a Virtual Machine, and modifying some configuration files and the documents for users to fit the changes of Plinth during this project, at the same time, a new wiki page for Plinth in Fedora is needed.</p>
<p>The Rocket.Chat team for iOS has been working on improving the UI, and is planning to come out with a major app re-design for version 2.3.0. One of their goals to support this redesign is to add the ability to theme the application.</p> <p>My project for the summer will focus on theming the application whilst introducing a minimal amount of impact on the rest of the code base.</p>
Currently, Rocket.Chat Room Header actions follow rigid layout rules, often hiding critical tools in overflow menus and reducing workspace flexibility . This project proposes a configurable layout engine that allows administrators to define action ordering and pinning (featured) via a workspace-level JSON setting. Key deliverables include a dynamic administration UI built with Fuselage, a per-user Feature Preview for progressive rollout, and a comprehensive test suite using Jest, Playwright, and axe to ensure 100% scenario validation and zero accessibility violations .
Rocket.Chat's current message parser uses PeggyJS, which adds bundle size overhead and performance bottlenecks. This project replaces it with a fully hand-written TypeScript recursive-descent parser that produces an identical AST, passes all existing tests, and ships with zero external dependencies. Deliverables include a complete lexer and parser implementation, 100% test suite parity, property-based fuzz testing with fast-check, and a benchmark suite demonstrating measurable performance improvements and reduced bundle size.
<p>The main goal behind this project is to create a Rocket.Chat app that adds the support of transcribing previously sent audio messages on demand, and new audio messages sent with the transcription selected.</p>
<p>Implement decentralised client-side recording mechanism in Jitsi Meet, where each device records and only records the audio of the participant on that device, directly using the stream from audio recording device. Afterwards, the recordings are merged offline to form a single track.</p> <p>Potential use cases include:</p> <ul> <li>Hosting a podcast by remote collaboration.</li> <li>Remotely interviewing people over the internet, with the intention of using the recording in a radio / TV program afterwards.</li> <li>Collecting stories and oral history. Something like StoryCorps DIY but without the need to meet physically.</li> <li>Virtual choir, where multiple people sing the same song together but remotely. Audio quality is crucial here.</li> </ul> <p>This feature will potentially extend Jitsi Meet's user base to a lot more of audio content creators.</p>
Description: Implement the ability to forward messages to another channel, thread, or discussion. This is a high-demand capability that is currently missing in Rocket.Chat. It can significantly improve the user's experience and her/his productivity. The scope of this project will be limited to web applications and not to mobile apps. Deliverables: 1. Being able to forward messages and files to multiple users and rooms 2. Being able to add additional messages on top of forwarded content. 3. Being able to add text formatting in the optional message field. 4. Being able to provide a preview of the message before sharing it. 5. Ability to show “posted from this channel” below the forwarded message
This project aims to enhance team productivity within agile environments by using a chatbot-based approach. By developing a chatbot that is customized to meet the needs of agile workflows, teams will be able to streamline communication, task management, and meeting coordination. This project will be implemented via the apps engine in Rocket.chat.
The Whiteboard Integration project enhances collaborative experiences in Rocket.Chat by introducing a powerful Whiteboard App. This integration facilitates real-time visual communication, making it easy for users to create and share diagrams, drawings, and more. With a user-friendly interface and features like slash commands and action buttons, users can effortlessly create and collaborate on whiteboards. The project also offers a convenient local setup guide, allowing users to deploy the app locally for testing. This integration adds a new dimension to communication within Rocket.Chat, fostering creativity and efficient collaboration.
This project aims to deliver a Rocket.Chat App that uses generative AI to summarize any conversations across threads, channels, and DMs. For example, a user can say, "summarize my unread messages yesterday in the #engineering channel". The users can ask AI any questions regarding the messages, and subscribe to personal digests that summarize selected channels on a recurring schedule. The AI summarizer will boost the productivity of Rocket.Chat users with faster information digest, and improve community engagement by keeping everyone on the same page.
This proposal addresses the current issues with Rocket.Chat’s API documentation, which is fragmented and manually maintained, leading to inconsistent validations and outdated information. The plan is to convert all API endpoints to use the OpenAPI 3.1 standard, integrate AJV-based validation for both requests and responses, and merge all documentation into a single, interactive Swagger UI portal. The key deliverables include: A complete, OpenAPI 3.1 compliant API specification covering all endpoints. AJV-based validation integrated across the API to reduce runtime errors. A unified documentation portal accessible via /api-docs with interactive Swagger UI. This approach aims to improve developer experience, ensure type safety, and maintain backward compatibility while providing a robust, automated solution for API documentation and validation.
This project automates receipt processing and expense reporting using OCR capabilities of multi-modal LLMs to address the time-consuming nature of manual expense tracking. Users upload receipts into designated chat channels—each representing a specific event, time period, or trip—where the system validates the image, extracts structured data such as amount, date, and items, and categorizes expenses automatically. The processed data is stored persistently, allowing users to generate detailed spending reports in various formats (daily, weekly, monthly, yearly, or custom date ranges), filter by specific channels, or view overall spending. Additional functionalities include natural language query support, optional slash command integration to perform actions like showing receipt data. All designed to streamline financial tracking by minimizing manual input and enabling efficient, structured querying of expense data.
The goal of this project is to implement a feature where users can share multiple files in a single message, currently user can send only a single file at a time which is time-consuming process by implementing multiple file sharing in one single message would improve the user's experience and her/his productivity by saving time. By adding this feature it promotes smoother collaboration and enhances communication within organizations. DELIVERABLES :- 1. Being able to share multiple files in one message in channels, threads or rooms. 2. Users Can also add Description to the File which he/she is sharing. 3. Can View Files selected with name and size of the file. 4. Multiple files can be shared and can also delete if wrongly shared . 5. Users can also add the file if they forgot to add it before.
As Generative AI technology is improving and being implemented in various applications, I am interested in using it in Rocket.Chat. While we already have a Giphy App that can fetch GIFs from Giphy, I propose to create an RC app that can generate GIFs based on user prompts. The RC app will allow users to enter their prompts, wait for the generation process, and then use the generated GIF seamlessly anywhere. We will be using an open-source & self-deployed model to generate the GIF. To ensure the app can serve multiple users in parallel, we will use the concept of databases as Task Queues, to store the status of multiple GIF generations in parallel. Excited to see what people generate using this feature.✨🚀
The current mobile UI testing framework for the Rocket.Chat Mobile app, Detox, poses several challenges including flaky test results, steep debugging overhead, and limited cross-platform capabilities. This project proposes a complete migration to Maestro, a modern and actively-maintained mobile UI testing framework designed to deliver more stable tests, simplified test authoring, and enhanced developer experience. The primary objective of this proposal is to improve the reliability, maintainability, and clarity of UI testing for the Rocket.Chat mobile codebase by setting up Maestro, converting existing tests, expanding test coverage, and integrating the testing pipeline into GitHub Actions CI/CD workflow.