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.
<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>
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.
This integration will bring the support of Figma right into Rocket.Chat using Rocket.Chat Apps. With the help of this plugin, teams can create new comments on Figma files, reply to comments, and get notified on different activities in Figma directly from Rocket.Chat. This will help in improving workflow and extending the functionality of the design system.
According to the state of JS ranking 2021, Vuejs has a 100% awareness rate which is coming from 99% from the previous year. This alone shows that there is an existing ecosystem of Vuejs developers and more developers will likely write Vuejs at a point in their career. So what point am I trying to make? Jitsi is a state-of-the-art video conferencing tool but doesn’t have an official Vuejs SDK to make integration seamless for Vuejs developers. Jitsi Vuejs SDK will provide a wrapper above the existing Javascript SDK. It will also expose the current implementation to the wide range of tools within the Vuejs ecosystem.
<p>According to an estimation, over 15% or one billion people of the total world population experience significant disabilities. These disabilities can be major or minor but the barriers in social and economic sectors for such people are the same. Even in the field of technology, people with disabilities are usually ignored. They find it tough to use websites and mobile applications. Considering such people a part of society and to make the live chat widget accessible to such people, I will implement a user-accessible mode. This accessible mode will help them to use the exciting features of the live chat widget.</p>
The Jitsi Videobridge (JVB) currently supports operational stats via JSON format. The Prometheus text-based format has become a more standard way of scraping metrics from services. The goal of this project is to add an additional REST endpoint which sends back operational stats in Prometheus format. The JVB will be able to be scraped via a Prometheus stats collector or via other scrapers which support this format. As proposed, a query on the local stats port to /prometheus should result in all general stats being dumped. Note: this project idea was proposed by the Jitsi team for GSoC 2022.
<p>The proposed project gives user the ability to create voice channels that would allow users to quickly enter and leave pre-existing voice calls from Rocket.Chat's own UI, enabling a more practical usage of audio features for team collaboration. Also adding the UI elements and integrating them with an established audio platform to handle calls.</p>
Open Rocket.Chat communities face a growing problem where new accounts join, flood multiple public channels with spam, and disappear before any moderator can respond. Current moderation is entirely reactive and manual, which is simply too slow for coordinated spam campaigns. This project builds a proactive, human-validated anti-spam system that monitors new users during their first 6 to 10 weeks and responds through a graduated restriction system called Moderation Levels, where every action is proportional, reversible, and requires admin approval before anything permanent happens. The system is built as a Rocket.Chat App on the Apps Engine with a seven gate detection pipeline running entirely in memory for speed. Gates catch exact duplicates via hash matching, polymorphic spam via cosine similarity, cross channel floods, rate flooding, rapid room spread, and phishing link campaigns. A four tier Moderation Level system escalates naturally with repeat behavior, from a friendly DM warning through posting cool downs to a permanent block that only lifts when an admin vouches for the user. The admin control layer includes a live dashboard, a full slash command suite, and AI powered on demand summaries so admins have everything they need to make confident moderation decisions without opening a single log file. Deliverables include a fully functional installable Rocket.Chat App covering the complete detection pipeline, a configurable Moderation Level system, a behavioral scoring engine, enriched admin notifications with message history, AI powered user analysis commands, a paginated admin dashboard built for scale, daily scheduled reporting, and complete documentation covering architecture, configuration, and known limitations.
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 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.
Playground 2.0 is an updated version of the Rocket.chat's Playground, which is an app development platform for creating custom apps and integrations. The new version includes several features to accelerate the development process and make it more visual. The first feature is the addition of an example section, which includes a collection of templates that can be used as a starting point for app development. This will save time and effort for developers who are new to app development and help them get started quickly. The second feature is the implementation of a project concept where multiple screens can be grouped, saved, and revisited at a later time. This will enable developers to work on different parts of the app separately and easily switch between them. The third feature is the use of the flow concept from https://reactflow.dev. This will allow each project to be represented as a flow, with each screen represented by a block. Actions can be connected to other blocks to visualise the app's lifecycle. This will make the development process more visual and easier to understand. The last feature is the ability to "compile the flow" and run it as a demo. This will allow developers to quickly present a mock or app to validate its usefulness. This will save time and effort for developers who want to get feedback on their app quickly. Overall, Playground 2.0 is an app development platform that makes the development process faster, more visual, and easier to understand. It includes several features that will help developers create custom apps and integrations quickly and efficiently.
The WebAuthn standard, now widely available on modern Android and iOS devices, enable convenient passwordless authentication satisfying 2FA (biometrics and "have device"). Frequently this involves scanning a QR code followed by unintrusive biometrics such as FaceID on iOS. This project aims to integrate WebAuthn in Rocket.Chat authentication to offer a passwordless, secure login experience. The implementation needs to be aligned with Rocket.Chat’s existing authentication system while ensuring backward compatibility with all existing login methods.
The Code Review Assistant app for Rocket.Chat addresses the common challenge of delayed code reviews, where pull requests often remain unattended for extended periods. This app intelligently analyzes the files modified in a pull request, examines the commit history of those files, leverages the CODEOWNERS file, and reviews past activity to identify the most relevant reviewers and does preliminary LLM review. By notifying only the most appropriate contributors, the app streamlines the review process. Integrated directly within Rocket.Chat, it provides user-friendly reminders and updates, LLM does the sanity review, enabling developers to stay informed and collaborate more effectively on code reviews.
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.
Build a mobile-first catalog of active scholarships, GSoC roadmaps, and interview preparation materials.
Build a dashboard that tracks contributor activity across GitHub repos — commits, PRs, issues — and gamifies the experience with badges and streaks.
Implement conflict-free replicated data type (CRDT) synchronization for synchronous multi-author document drafting.
<p>Chassis aims at defining open standards for various CSS/JS libraries and the web in general. The project aims to complete and deliver base styles for at least 5 UI components (e.g. tabs, modals, menus e.t.c) by the end of GSOC 2016. The project makes use of advanced SASS and JS for testing the components integration.</p>
<p>The Tails Server should provide a user-friendly way to start onion services that facilitate group collaboration, communication, and data sharing. See the <a href="https://tails.boum.org/blueprint/tails_server/" target="_blank">Tails Server Blueprint</a> for further information on the entire Tails Server project.</p> <p>During GSoC 2016, I plan to implement the basis of the Tails Server. It should be possible to use a GUI or CLI (I will implement both) in Tails to automatically install a service and set everything up so it is reachable as an onion service. It should be a generic solution which makes it easy to add many different services (web server, Etherpad, Mumble server, file sharing service, etc.), but I don't plan to add many of them during this project, because that might go beyond scope. I will instead use a simple web server serving a static page as a first service.</p> <p>The user should be able to choose:</p> <ul> <li>whether s/he wants to require client authentication (using HiddenServiceAuthorizeClient).</li> <li>whether the server's configuration and data and the onion service's keys and address are stored persistently (i.e. being restored after reboot) or not.</li> <li>whether the service is supposed to automatically start after booting Tails.</li> <li>whether it should allow LAN connections.</li> </ul>
Problem: Modern-day web browsers are pretty standardized and come with a certain guarantee that if a web page works in one browser, it will work in another web browser too except for a few minor cases. However, this is not true for email clients yet. The current state of the problem: The developer community is thus aligned to certain tricks and hacks to make sure the emails sent are properly rendered by these different email clients. There is no such package that solves this problem of creating responsive emails easily which can also handle cross browsers and clients compatibility issues. Proposed Solution to this problem: The end goal will be to implement a React-based component and utility methods-based lightweight library to provide a common interface for email building that users can install and use to build clean and responsive emails easily.
Create standalone Web Components for WCAG 2.1 AAA color contrast validation and palette generation.
Organisations such as the Royal National Institute of Blind People (RNIB) are currently manually adjusting appearance settings like staff size change, line thickness change etc. in Musescore to aid users with low vision, as these features are scattered throughout the software. This manual adjustment process consumes significant resources and bandwidth, posing challenges for effective access and use of the software by individuals with visual impairments. The idea is to address this issue by introducing a new settings feature in MuseScore. This feature will provide a list of standard accessibility profiles, such as normal, large, etc., each one customised to specific needs of users with low vision. These profiles will collectively update a set of appearance settings, including staff size, page size, and other relevant ones, to enhance accessibility for users with visual impairments.
<p>Since Scilab is an open source, various practitioners use it to simulate real-time applications and systems. However, Simulation cannot be achieved in zero time. Knowing execution time is a key to develop an accurate simulation in real-time areas. Precise measurement of execution time is important in area about life safety, such as military equipments, automotive and aerospace industries. As we known, Matlab has a Profiler function which could measure where a program spends time. By using Matlab Profiler, we could evaluate and improve performance of programs. What I want to do is to make a similar function for Scilab. We use Xcos to make models that have many blocks. In some cases, we want to know execution time of these blocks. A variety of literatures introduce the way of measuring execution time but they did not present directly time to users. Therefore, in this project, I will measure time and present time to users.</p>
Apache Kafka is a distributed event streaming platform that is very widely used to process and store data. This project aims to create a Swift Package that enables Swift developers to send and receive data in the Kafka ecosystem while also taking advantage of the new Swift Concurrency features. At first, this shall be achieved by wrapping an existing C library called librdkafka.