Fetching the latest programs, projects, and workspace data.
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>
This document proposes a detailed architecture on how to implement the Audio Switchboard API. This idea enables numerous features, including translation layers and lightweight breakout rooms, as described in the idea page. This proposal introduces a metadata-based mechanism to manage audio streams. The implementation involves extending jitsi-meet to handle metadata, and Jitsi Videobridge (JVB) to handle signaling from senders and filtering requests from receivers. Senders attach metadata to their streams, such as spoken language or breakout room identifiers, while receivers specify criteria for the streams they wish to receive. JVB processes these inputs, filtering and forwarding only the matching streams.
The project aims to develop a comprehensive prompt editor within Rocket.Chat, facilitating seamless interaction between users and open source language models (LLMs) such as Mistral, Llama 2, and Phi. Key objectives include enabling free-flowing conversations, robust conversation history management, and seamless prompt sharing across external applications. The initial focus will be on implementing this functionality within the Rocket.Chat Web App and Electron platform.
AI Newsletter Generator and Publisher, aims to solve the challenge of creating engaging and informative newsletters for special interest groups; marketing and communications by the Rocket.Chat users communities. By developing this AI-powered app, users will be able to effortlessly produce well-crafted newsletters from raw content using advanced language models. The app seamlessly integrates with Rocket.Chat, allowing users to deliver newsletters.
<p>Integrate an Open Source speech to text engine to be used inside Rocket.Chat by users who prefer an On-Premise full-featured installation. There are many opensource speech2text engines on the market, like CMUSphinx and pocketsphinxjs, annyang, JuliusJS, Mumble, Voix JS, voice-commands.js and Artyon.js. The project includes a feature matrix comparison between those engines and the best one to be implemented in Rocket.Chat bundle, giving the UI the ability to click a button, record a message, send it to the text2speech engine and return the results to Rocket.Chat editing message box.</p> <p>Develop a voice recognition integration feature, by building a Settings pane to connect some of the well-known voice recognition and speech to text APIs on the market directly from within Rocket.Chat. By configuring API’s connection and usage attributes, and giving rocket.chat’s UI the ability to click a button, record a message, send to the desired API and return the results to Rocket.Chat editing message box.</p>
The Natural Language Bridge to Legacy Email project represents a groundbreaking solution to one of modern communication's most persistent challenges: The continued widespread use of legacy email alongside newer messaging platforms. Despite the evolution of systems like Rocket.Chat, email remains deeply entrenched in global workflows and communities. This project elegantly bridges this divide by creating a seamless interface that allows Rocket.Chat users to interact with email systems through natural language commands, bringing legacy email functionality directly into the Rocket.Chat environment. By leveraging advanced LLM capabilities, this integration will allow users to perform complex email operations without leaving their Rocket.Chat conversations. The app responds to natural language instructions, enabling email tasks to be completed with simple, intuitive commands that feel like conversational requests.
People love to listen to music together, for which they would like to start a video conference where they can enjoy music together with their friends and family. A music bot for Jitsi video meetings will serve this purpose. This Music bot will be extremely simple to use, while in a meeting, just copy the meet link to the bot window and start the bot. The bot joins the meeting as a participant and follows the commands. The bot will be controlled by writing simple English commands in the chat box like /play <songName>, /pause, /resume, etc. User can also use their accounts on music streaming apps with the music bot to provide them with high-quality ad-free music if they enjoy a premium subscription on their accounts.
<p>The goal for this project is to integrate chatbot platforms like Dialogflow and RASA with Rocket.Chat.</p> <p>These integrations are built to work with the Livechat module of Rocket.Chat. Livechat is a modern helpdesk application that helps connect a live-agent with a visitor so that the live-agent and answer visitor's queries.</p> <p>With these new Integrations of Dialogflow and Rasa, Rocket.Chat will now allow site visitors to interact with a Bot instead of a live-agent. These Bots would be developed and maintained on Dialogflow and RASA.</p> <p>This is a very common approach which most of the businesses use nowadays, where a visitor would first interact with a Bot. These bots can handle simple interactions like answering FAQ's for a business, to complex interactions like ordering an item. If these bots are not able to answer visitor questions, then the visitor would be transferred automatically to an online live-agent who can address their query.</p>
<p>This project aims to improve the existing Nextcloud integration within Rocket.Chat. Seamless authentication and improving the UI and UX of the file picker are the main focus.</p>
<p>Proposal for integrating <strong>Out of Office</strong> Settings into the Rocket.Chat codebase.</p>
<p>The Rocket.Chat Poll App is the go-to app for teams and channel members of any Rocket.Chat rooms for a rich interactive poll. It currently offers multi-voting and single-voting controls with confidential and open responses. The results are displayed in the form of a bar graph with an option to finish the poll. In this project, I plan on adding several new features to the Rocket.Chat Poll App and improving upon the existing ones to augment the user-experience and further the user-engagement achieved through the app.</p>
Rocket.Chat users across multiple time zones need a way to schedule messages for optimal delivery, enhancing global collaboration. This project will implement a native message scheduling feature by integrating a scheduling UI, a cron job to send messages at the designated time, and a contextual bar UI to view and cancel scheduled messages. It will also support scheduling in threads, improve error handling, and include comprehensive documentation and unit tests. The deliverables include a MongoDB collection for scheduled messages, APIs (chat.scheduleMessage, chat.getScheduledMessages, chat.cancelScheduledMessage), a cron job (sendScheduledMessages), scheduling and viewing/canceling UIs, thread support, error handling, documentation, and tests
The News Aggregation Rocket.Chat App is designed to deliver the latest news from various sources directly within the Rocket.Chat platform. This project aims to create an application that aggregates news from top websites like TechCrunch and BBC News, utilizing APIs or RSS feeds to collect data. The app will present news in a user-friendly format with complete configurability of sources and categories, ensuring users can customize their news feed according to their preferences. The project will implement logic to collect news, categorize it, and present it effectively within the platform. By enhancing the Rocket.Chat ecosystem, this app aims to offer users a seamless way to stay updated with curated news content without leaving the chat environment.
<p>Rocket.Chat has a remarkable internationalization effort. There are dozens of translation files across several apps, many of them with over 4000 translation strings. However, there's still a long way to go - some strings still lack translation, others need to be removed, etc. Currently, the translation process is entirely manual, making it even harder to manage that much information. To speed up the internationalization process, our goal is to build a tool that makes translators live's easier. We want to create a CLI app that helps in the translation process, answering questions like:</p> <ul> <li>Which strings weren't translated yet? </li> <li>Which strings are not mentioned in the codebase anymore? </li> <li>What is the translation progress for a given language?</li> </ul> <p>We want to make the actual translating easier, providing an interactive interface to add or remove translations. Our goal is to raise Rocket.Chat's translation standards - to ensure these standards are met, we'll build a CI scripts that checks for translation string usage in new contributions, ensuring every new translation string added to the codebase is listed in the translation files.</p>
<p>The project aims to improve/add the functionality of hot reloading during development, creation of templates for repeated code on the user end, and improve the overall experience of app development in the CLI tool used for the creation of apps within rocket.chat.</p>
Text embellishment plays a vital role in enhancing communication, fostering engagement, and making written content more impactful. This project aims to create a Rocket.Chat App that enables users to emojify or embellish their text messages using LLMs (large language models) and prompt engineering. The AI-generated text will be presented through an interactive message interface, with action buttons such as send, redo, edit, and copy, visible only to the user. Depending on the action button clicked, the user can send the message to the channel, regenerate the AI-generated message, edit the message, or copy it, respectively. This app adds a new dimension of creativity to enhancing communication within Rocket.Chat.