Explore Projects

This proposal outlines the development of an AI-powered Image Analysis App for Rocket.Chat. The project aims to introduce a feature that allows users to simply upload images, while the app automatically analyzes them using a multi-modal Large Language Model (LLM). The app will process images to identify locations, landmarks, points of interest, or event venues and retrieve up-to-date event and happening information from the internet. By integrating advanced image reasoning with real-time data retrieval, this solution enhances situational awareness and provides users with valuable insights. This proposal seeks to streamline information discovery, improve engagement, boost productivity, and elevate the overall user experience within the Rocket.chat ecosystem.

<p>This project aims to enable all the essential functionalities of Rocket.Chat to be accessed through any Alexa and Google Assistant device by creating and deploying a Rocket.Chat Google Action and an Alexa Skill to their respective stores.</p> <p>The main goals and improvements to be made for this term will be:</p> <ol> <li>Adding more functionalities to the backend to make the skill/action more practically usable and efficient.</li> <li>Improve the voice interface of the skill/action.</li> <li>Adding more functionalities to skill and action.</li> <li>Resolving existing bugs.</li> <li>Making it consistent across all languages.</li> <li>Finally deploying the skill/action to store.</li> </ol>

<p>Proposal for App: Bad-Words Filter. Rocket.Chat is Teams collaboration platform where people from different parts of world come together and collaborate. Some people can be toxic at times and can use harsh words against fellow members. This app can be helpful for Rocket.Chat platform for filtering bad-words.</p>

This project aims to enhance Kiwix's capabilities by improving its user interface for rendering YouTube channels & playlists. However, the current user interface lacks appeal. The goal is to revamp the UI to make it more visually appealing and user-friendly, thus enhancing the accessibility of educational videos and other content to Kiwix users around the globe.

<p>Search is a fundamental operation performed by Kiwix that helps users to find the content they want in a quick and efficient manner. Though it is highly functional right now with many more enhancements coming in libzim7, there are still some missing features and room for improvement. Namely:</p> <ul> <li>Drop wrapper structures from kiwix for performance and usability enhancements</li> <li>Improve relevant suggestion results and their snippets by optimizing Xapian implementation</li> <li>Introduce a versatile suggestion API that is able to work even in the absence of a Xapian index</li> <li>Make suggestion handling more stable in kiwix-serve and other sub-projects</li> </ul> <p>The project addresses these issues such that kiwix users can have an overall improved search experience.</p>

Setting a calendar event is a small, but important process in our day-to-day job. It can take some of your time when you want to set up another meeting if you 1) Already have a tight schedule; 2) Your coworkers are in different time zones; and 3) Have to switch back and forth between the calendar and the messaging app. Hence, this project aims to streamline the process using a scheduling assistant, that can create meetings or set up a reminder using a prompt. A slash command can simply trigger it through a messaging app (in this case, Rocket.Chat). The solution will involve a lot of large language models (LLM) experiments for the user prompt. Therefore, this project can act as a semi-research in which the result of LLM experiments can be used to approach similar cases.

<p>A full-screen composer that could be opened from the current composer to provide a larger area for text input or edition, good to send or edit large texts.</p>

<p>This project is about improving the UI/UX experience of kiwix-serve which is used to host library.kiwix.org and other local servers for hosting zim files. My main focus on this project will be to build a better search and presentation experience for users.</p>

There are many secondary goals for this project, but the main goal is to make the fuselage compatible with React Native. But also, we have figthing against the bundle size of the fuselage, and of course performance which is always a concern. Using the tamagui as a base, we can components that are compatible with both platforms, and in a efficient way.

<p>Currently, scrapers are used to generate ZIM files and contain code that is difficult to maintain. A new library called scraperlib is being developed to facilitate automated testing and code coverage of shareable code. The task is to rationalize the usage and maintenance of those by limiting them to their specificities only and move any reusable logic into the well-tested scraperlib.</p>

<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>

RocketChat UIKit Playground is a proposed Component playground that will allow us to build, test, and browse our UIKit components in isolation. When executed correctly, they make prototyping new experiences both easy and fast, thanks to the consistency they create. The playground should also allow developers to generate configuration by dragging and dropping components from the library. Deployed Here --> https://intvivek.github.io/RCplayground/

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.

The aim is to develop an attractive Rocket Chat Text TUI using bubbles and bubbletea go package. By using bubble and bubbletea the TUI can be made easy to understand and user friendly. To communicate with apis and database Integrating Rocket chat go SDK with minimal latency of SDK api calls. If required, developing separate api’s in the sdk for TUI specific use cases.

<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>

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.

Action sheets are a very common UX pattern which are used to interact with quick actions and can be found in almost every mobile app . There are already multiple places where Bottom Action Sheets are used in Rocket.Chat app like the message actions menu. While there are also several other components like Server dropdown, Reaction Picker, Reactions modal etc. which have to be migrated to Bottom Action Sheets to improve the user experience. The main goal of the project is to redesign and add more features to the existing Emoji Picker, Reactions Modal and the other components, improving the overall user experience and then render them as Bottom Action Sheet.

API documentation plays a vital role in developers' workflow, serving as an essential reference for software integration and development. However, challenges such as outdated or inconsistent documentation frequently hinder efficient utilization. To address this, the proposed project aims to implement automation for API documentation generation leveraging a suite of tools including TypeScript Compiler API, openapi3-ts, Swagger, and OpenAPI specifications. This initiative seeks to streamline the documentation process, ensuring accuracy and consistency by maintaining only a single source-of-truth for the API Documentations.

Integrate Notion Via RC App prioritizes teamwork by enhancing collaboration for workspace users. Imagine having the power of two essential platforms, RocketChat and Notion, united as one, eliminating the need to switch between two platforms. Teams can Seamlessly Connect, Effortlessly Manage various Notion Workspaces, Share documents, and Even View Documents all within RocketChat. The real magic lies in Preserving your Important message inside the Notion Page, Structured within the Notion Database, ensuring vital discussions, decisions, and insights are never lost again, fostering alignment and inclusivity as everyone stays on the same page, even if they're not actively chatting. Whether it's brainstorming sessions, meeting notes, or shared links, find them all in one organized place. Plus, Create Comments on the Notion Page, view the Notion Database, and interact with relevant information.Welcome to a new era of streamlined collaboration, Where RocketChat and Notion work together seamlessly to fuel your team's success.

<p>The project aims to add the functionality of Service Accounts in the existing Rocket.Chat application. Service accounts will be an upgrade to regular user accounts, they will have a well-defined purpose. Regular users can subscribe to this account to get information regarding the context mentioned in the description of the Service account.</p>

<p>Currently, the Rocket.Chat.Electron desktop application has a wide range of useful features but I chose the project “Download Manager on Desktop App” because it would take the application even further and greatly improve user experience. On the web, we are comfortable with using the download managers built into our browsers which makes a download manager inside the web app a bit redundant. But this feature becomes desirable when we are using the desktop app.This improves the experience of the user in many ways, a few of which are briefly mentioned below:</p> <ol> <li>Track downloads made through the app. </li> <li>Track download progress of files.</li> <li>Search and filter for downloaded files based on the server that they are downloaded from as well as other attributes.</li> <li>Pause, restart or cancel downloads.</li> <li>Re-download cancelled or broken downloads.</li> </ol>

Today, with Ubuntu increasingly adopting Snap packages, Uyuni currently lacks support for managing these applications. This project proposes adding native Snap support to Uyuni, including install, update, remove, and channel management. By extending Uyuni’s capabilities to cover Snap, this work fills a key gap and ensures continued relevance for Ubuntu system management. I explored how Uyuni manages CVE audits and package upgrades for Ubuntu systems. Initially, Uyuni connects to client machines via SSH to install and register the Salt Minion. Once set up, all communication occurs through Salt’s remote execution system, eliminating the need for SSH. Salt gathers package data using grains, pillars, and custom modules, which Uyuni then compares to its centralized SUSE Manager database. For CVE auditing, Uyuni fetches security metadata (e.g., CVEs, OVAL data) from upstream sources like Ubuntu Security Notices and stores it in a PostgreSQL database. When Salt reports installed packages, Uyuni analyzes the data and generates patch or upgrade recommendations. APT repositories are mirrored into structured software channels, allowing clients to receive updates without direct internet access. Building on this workflow, I propose extending Uyuni to support Snap packages. While Snap lacks structured CVE metadata, we can implement a version-based upgrade system: Uyuni retrieves the latest Snap versions from the Snap Store and compares them to client versions reported via Salt, suggesting upgrades when newer versions exist. To support airgapped environments, we can pre-download .snap and .assert files on a connected system and distribute them through Uyuni’s software channels. Additionally, to manage storage and stability, Uyuni admins can choose which Snap channels (stable, beta, etc.) to mirror—defaulting to stable. Deliverables: Support Snap auditing, lifecycle management, airgapped environments, testing/validation, and user documentation in Uyuni.

Shardingsphere federated query engine provides support for SQL statements. In the GSoc period, I have to add support for more MySQL SELECT statements so that more SQL statements can be converted into SQLNode. This can be achieved by: 1- Analysing the SQL statement I have to add support of, 2-Figure out components & logic required , 3- Make changes in SQL federation engine optimizer files , 4- Optimize parser files , 5- Make changes in TEST files to ensure test is passing successfully. After the support for More SELECT statements queries is added, The users & developers will be benefitted by utilising more SELECT queries for MySQL .