Explore Projects

Build an inspection module for debugging asynchronous streaming boundaries and streaming chunk latencies in modern React frameworks.

The OpenELIS organization currently relies on JSP (Jakarta Server Pages) for most of its pages but is gradually transitioning to a modern JavaScript-based framework, React.js. Many pages still use Java-based controllers and endpoints to dynamically update and display data on the front end. As part of this project, I will rewrite all Test Management Pages and their components in React UI, integrating them with REST API endpoints to fetch and render data. Additionally, I will migrate all Test Management Configurations, Management, and other operational pages to React.

OpenELIS Organisation is currently using JSP (Jakarta Server Pages) in overall pages it is slowly moving towards the newer javascript-based framework called React Js. Currently, a (n)number of pages use Java-based controllers and endpoints that dynamically change page data in the front end to show the results, outputs, and desired data. For this project idea, I will rewrite all the Admin Pages in the React UI, connecting the Rest API Endpoint with the rendering data to the front end. Also rewriting all the Admin Configurations, Management, and Other operational pages to React.

<h3>Scope</h3> <p>Project scope is to develop a React.js library of pedigree components that will meet the GA4GH standards. Library will be build of accessible components. On top of that, library will include a environment to run components and speed up the development process.</p> <h3>Features</h3> <p>Due to need of building tools from those components, library will provide an API to make it easier for developers to modify state of components from code level. Components are still accessible from library without any abstract layers or boilerplates so developers have freedom of choice, how to build their app.</p>

<p>MusicBrainz is aiming for a user experience overhaul. To keep design and development in sync, by thousands of contributors over the years, we need a design system in place. The goal of this project is to build this design system which will include, apart from assets and MusicBrainz design principles, reusable independent UI components written in React.js. Further, I will use React Storybook to build a component library which will allow users to browse through components, visualise different states of each component, and interactively develop and test components.</p>

The project's objective is to create adaptable web components utilizing UI frameworks like LitElement. These components will adhere to the Data Repository Service (DRS) API specifications established by the Global Alliance for Genomics and Health (GA4GH), ensuring compatibility and interoperability. The development process involves creating reusable Web Components with customizable designs, possibly leveraging techniques such as Design Tokens. These components will facilitate a user-friendly interface for the GA4GH Data Repository Service (DRS) and will eventually be integrated into the ELIXIR Cloud Component suite. Additionally, the project involves upgrading the DRS-Filer to align with the latest DRS API version (DRS 1.4.0), ensuring continued compatibility and functionality.

Volto is structured as a typical Redux-centered React application. The refactoring class components to functional components project is centered around using concepts of hooks to migrate class components to functional components and testing the refactored components with Cypress tests and Storybook to verify the UI is intact, after, all the tasks are delivered performing e2e testing.The lifecycle of the components should be preserved while watching out for edge cases and UX problems.Delivering appropriate documentation for the changes made.

The objective of this project is to create adaptable web components using UI frameworks like Microsoft's Fast. This will involve expanding the existing component suite and implementing design tokens to create a user-friendly interface for the GA4GH Workflow Execution Service (WES) and Task Execution Service (TES) APIs. The ultimate goal is to integrate these components into the Krini web portal, providing an intuitive and responsive interface to facilitate complex genomic and biomedical computations.

The proposed React Native SDK will expose React Native components with a similar functionality of the already known Jitsi Meet Native SDK classes. These Native SDKs are utilising a React Native Component at their core that exposes Jitsi’s functionality for native mobile apps. The React Native SDK classes will communicate directly with the existing core component using props and offer the customisation options known from the native SDK. The deliverables are: - A React Native SDK containing the complete functionality of the native SDKs - A test suite for the SDK - An API reference with examples

This project aims to create a Rocket.Chat App that acts as an AI Assistant Agent, improving onboarding and community management through a conversational interface. The app engages new users with a tailored chat, delivers a welcome message, shares server rules, and recommends relevant channels based on their needs all of which can be configured by admins. It also auto-assigns default rooms and allows users to perform common tasks like joining or leaving channels, inviting others, or using other app features without remembering Rocket.Chat slash commands , making servers more approachable for newcomers

This project builds a Gemini CLI extension that solves MCP's context bloat problem for Rocket.Chat developers. Current MCP servers expose an entire platform's API surface, meaning every agent session wastes tokens on hundreds of tool definitions the project will never use. The Minimal MCP Server Generator lets developers describe their use case in plain English and produces a production-ready MCP server covering only the endpoints they actually need. The generator goes beyond raw API wrappers by composing multi-step workflow tools: declarative step graphs that chain API calls, AI reasoning, conditional branching, and data transforms into single high-level operations. It supports two compilation targets: a standalone webhook + REST server that runs anywhere, and an Apps-Engine bridged mode for realtime event interception. The key deliverables include: a Gemini CLI extension with endpoint discovery, schema lookup, and project generation tools; a six-pass workflow validation pipeline that catches and self-corrects LLM mistakes before codegen; additive tool generation that adds new tools to existing servers without overwriting; protocol-level test generation via MCP Inspector; runtime hardening with endpoint allow-lists; and a PlatformProvider abstraction with a Mattermost dry-run proving the generator's portability beyond Rocket.Chat. This approach reduces token costs, fits within free-tier limits, and makes MCP-based Rocket.Chat development accessible to any workspace regardless of plan.

The ultimate goal of the project is to create a full-stack React component node module of the RocketChat application that would be fully configurable, extensible, and flexible for use. It will allow users to integrate RocketChat into their React web-based applications easily also providing an amazing developer experience while creating in-app chat applications.

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 goal of the project is to implement distributed tracing in order to trace individual calls between multiple backend components. The implementation can be broken down into the following stages: Infrastructure: Deploy an OpenTelemetry colector, and a Tempo tracing backend; Instrumentation: Instrument backend components in order to send events to the collector; Tracing: Stitch events together into traces by propagating trace context; Polishing: Iterate the generated events in order to improve the observability of the system; Documentation: Document how to deploy the required components, how to add/modify generated events, and how to visualize the data.

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>Over the years, Mozilla has shifted to using Taskcluster as its primary continuous integration system. Communication becomes essential between the various components when scaling the infrastructure. Mozilla uses Pulse to enable an exchange of information Mozilla’s systems. Pulse is actually a RabbitMQ server which uses AMQP ( and follows a Publish--Subscribe pattern). Taskcluster-events is a service that allows web clients to listen for pulse messages without RabbitMQ credentials and without the need for a TCP connection to the RabbitMQ server. However, currently, taskcluster-events is old and poorly designed, without protocol specification. This proposal aims to completely rebuild taskcluster-events from scratch, ensuring it is robust and free of major bugs / failures.</p>

<p>Currently, the process of generating the documentation is manual and it requires updating the docs every time there is a change in props. We can use document generator tools to generate documents effectively using scripts. Work on internationalization of documentation. Along with this make a Web App which showcases components.</p>

This project aims to develop an intuitive Message Timestamp Date Picker for Rocket.Chat, replacing manual timestamp code entry with a user-friendly UI component. Currently, users must manually type complex codes like <t:1732557600>, which creates friction and is error-prone for non-technical users. I will solve this problem by implementing a comprehensive system with three layers: Core Utilities for timestamp conversion and validation, UI Components creating an intuitive modal with selection options and preview, and Integration Layer connecting to Rocket.Chat's existing systems. Deliverables include complete timestamp utility functions, TimestampPicker modal with intuitive inputs, message composer integration, rendering system for displaying formatted timestamps, comprehensive testing, and documentation. The solution will support all timestamp formats across platforms, significantly improving user experience when communicating time-based information.

<h3>Implementation of Newsfeed (a social feature) in Rocket.Chat Server</h3> <p>This project adds a newsfeed for every user. In it, the users can follow other users. Whenever a user posts something in a public channel or does any public activity, it would appear in the newsfeed of all his followers with a link to the original post in the original channel. This would greatly help in discovering new conversations, increasing accountability of people in the organisation &amp; increasing many folds the time a user spends on RC</p> <p><strong>The most challenging part of creating the newsfeed is to make it scalable to support a large number of concurrent users (by using an adaptive follower/following relation model) and to benchmark the server performance in relaying the correct messages with filters. This is being done by using proper schema and proper database queries. Messages in newsfeed are fetched in real-time from messages stored for other channels.</strong></p> <p><em>Key Features:</em></p> <ul> <li>Support for Rich Message blocks</li> <li>Auto-summarization of messages to prevent spam in newsfeed</li> <li>Expandable embedded conversations</li> <li>Upvoting System &amp; Trending messages</li> <li>Group messages by origin user, date, channel etc.</li> <li>Integration with other projects</li> </ul>

<p>I will be adding and refining existing features to Firefox Devtools' CSS Grid Inspector tool. One major feature I will be working on is the grid outline tool. This tool allows for developers and designers to interact with a CSS grid layout highlighted by the CSS Grid Inspector. It gives users the ability to visualise grid cells, areas, positioning, and line names in an intuitive way. This feature will be shipped inside the new layout panel with Firefox Developer Tools.</p> <p>I initially implemented this feature as part of the Undergraduate Capstone Open-Source Program for an applied studies course during the Spring 2017 semester. Although it has come a long way, it still needs polishing.</p>

<p>Our React native implementation is relatively newer than its native counterparts hence lacks many of the important features and is more buggy. The aim here is to implement some of the important features that the application lacks, and also side by side replacing some legacy libraries with a new one to increase performance as well as user experience and last but not least resolving discovered as well as undiscovered bugs. I think the most important feature that app lacks is the ability to fully share files. It can right now download and view already shared files but there no way to upload a new one. Second, an important feature that really makes Rocket Chat standout from others are slash commands, It allows the user to do trivial actions, like invite a user or archive a channel in fewer tabs Third, add in app notification so user can be notified even when he is using app<br> And last but not least I will be redesigning the settings panel of app and adding new options to it like Licence and contact us</p>

<p>The aim of this project is to improve the Rust developer experience via the Rust Language Server by introducing few notable improvements. The scope includes supporting more workspace configurations (multiple targets and active crates) as well as popularly requested IDE features, such as implementing code action mechanism on the server side, e.g. used for refactoring or running specific tests, or improving diagnostic data required for better code navigation. Providing good out-of-box IDE experience will substantially help with widespread adoption of Rust and support writing not only quality self-contained libraries, but also incentivize writing advanced end-user oriented applications.</p>

<p>The Rocket chat team has been sincerely working on improving the Android App by regularly adding great features and making them available to users through updates on the Google Play store. Play store is a great platform for making the app available to all users but there are countries where play services are banned/not available. Hence there is a great requirement for other app hosting platforms so that people of these countries can also use Rocket.Chat apps. This problem can be solved by using F-Droid. F-Droid is a community-maintained software repository for Android. Apps hosted on Fdroid can be installed from the F-Droid website or client app without the need to register. Being a catalog of Android FOSS applications. It is available in almost every country in the world. Rocket chat legacy android client is recently replaced by React Native and needs to be updated on F-Droid, Apart from this there are few other features like integrating Fastlane in the android module and use it to run the existing jobs and create a new job to upload the build to play console Other features include Improving CI workflow and create jobs to generate separate builds for both Fdroid and Play store.</p>