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.
This project develops agent-accessible CLI tooling for the Julia Bayesian ecosystem, delivering three main components: DoodlePPL CLI for model validation, code generation, sampling, and diagnostics with structured JSON output, MCMCChains.js, a TypeScript npm library enabling MCMC diagnostics and visualizations in the browser and TuringCLI, a command-line interface for Turing.jl that provides machine-readable JSON outputs, with all three deliverables building upon and extending the GSoC 2025 work on DoodleBUGS.
<p>Adding a graphical interface for game library management, where games are displayed with cover art thumbnails, with options for grouping and filtering by publisher, engine, and other fields.</p>
<p>Differential equation models are widely used in many scientific fields that include engineering, physics and biomedical sciences. The so-called “forward problem” that is the problem of solving differential equations for given parameter values in the differential equation models has been extensively studied by mathematicians, physicists, and engineers. However, the “inverse problem”, the problem of parameter estimation based on the measurements of output variables, has not been well explored using modern optimization and statistical methods. Parameter estimation aims to find the unknown parameters of the model which give the best fit to a set of experimental data. In this way, parameters which cannot be measured directly will be determined in order to ensure the best fit of the model with the experimental results. This will be done by globally minimizing an objective function which measures the quality of the fit. This inverse problem usually considers a cost function to be optimized (such as maximum likelihood). This problem has applications in systems biology, HIV-AIDS study.</p>
<p>An app developed on Rocket.Chat App engine to integrate Google Calendar with Rocket.Chat. This can be used to create and manage personal calendar events. It can also be used to create public events which can be shared with multiple users and takes cares of reminders and notifications.</p>
Graph Neural Networks (GNNs) rely on message passing, traditionally implemented via a gather/scatter mechanism. In GraphNeuralNetworks.jl, this approach materializes dense feature matrices on graph edges, leading to severe memory bottlenecks and reduced performance as graph sizes scale. This project addresses this limitation by redefining message passing as non-materializing Sparse Matrix-Matrix Multiplications (SpMM). By treating the graph as a sparse mathematical operator, this project will unlock significant computational efficiency and memory savings on CUDA GPUs. The core objectives include integrating COO storage, upstreaming patches to CUDA.jl, and refactoring the GNNlib API. To ensure continuous momentum during upstream review cycles, the project features a secondary track focused on upgrading the Automatic Differentiation (AD) pipeline by fully integrating Mooncake.jl and Enzyme.jl, alongside expanding the ecosystem with new datasets and new tutorials / improved documentation.
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.
<p>The project titled "Integrated Personal Email Gateway" aims at facilitating users with an ability to reply messages by directly replying to emails they received whenever they are away. This allows them to interact with their fellows and provide support to the community even offline. Thus providing community with another great feature to boost communication.</p>
<p>By leaving tedious formatting to the machine, code formatters provide a substantial increase in engineering productivity and a consistent style across teams. Hence, this project implements a code formatter that can take a piece of Elixir code and format it automatically according to a standard style guide. It is very similar to tools such as <code>rustfmt</code> and <code>gofmt</code>.</p>
<p>End-to-End encryption is a highly important feature in chat clients, allowing users to talk to each other securely without fear of message interception or surveillance. The current implementation of OTR in Rocket Chat has a number of limitations, including no support for offline chats. In this project, I will improve Rocket Chat functionality by integrating the Signal protocol, which provides confidentiality, integrity, authentication, forward secrecy and asynchronicity, among other security features, with Rocket Chat.</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.
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 .
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
<p>I would like to implement support for the SMuFL music notation font standard, in order to give LilyPond access to the growing number of notation fonts that follow it. This is one of the organization's suggestions, but I intend to reverse the order of the listed tasks. First, I will add native support for SMuFL fonts (using the freely available Bravura font as a test case), and then I will make a SMuFL-compliant version of Feta. That way, the core task, which can stand on its own as an optional feature and will benefit LilyPond more, can be completed first in case I don't have time to make Feta SMuFL-compliant.</p>
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.
An AI-Assistant is developed to help developers understand the Rocket.Chat codebase better. This tool uses the existing knowledge base of the code to answer questions about the code structure and logic. It can answer specific questions about the code, create diagrams to explain things clearer, find relevant documentation, and even suggest ways to improve the code. This will help new developers learn the code faster and make the codebase overall better quality, easier to maintain, and more consistent. By helping developers understand the code better, this tool aims to make the Rocket.Chat development community more welcoming and productive.
<p>We will bring the ScummVM Director engine up to (MacroMind) Director 2 compatibility, with progress measured by <em>Spaceship Warlock</em>. Major tasks in this project include [1] making the render pipeline sprite-based (rather than per-frame), [2] compute score frames on-the-fly instead of caching them, so delta information is properly processed, and [3] using the new approach to improve sprite position calculation. Stretch tasks include rewriting transitions to support simultaneous sprite transitions, emulating the Mac UI elements that many games use, and understanding sprites with palettes.</p>
<p>Conflict-free Replicated Data Types (CRDTs) make the design of eventually consistent systems non ad-hoc and anomaly-free by formalizing the reconciliation mechanism of diverging replicas. Pure operation-based (aka op-based) CRDTs are variants of CRDTs that are generic and more efficient as they allow for compact solutions in both the sent messages and the state size. On the other hand, Lasp is a new programming model designed to simplify large scale, fault-tolerant, distributed programming using state-based CRDTs. It would be very interesting to implement the operation-based approach in Lasp and compare it with the currently implemented state-based approach.</p>
<p>XaoS currently cannot support very deep zooms because the 80-bit floating-point arithmetic used runs out of precision before too long. It should be possible to add arbitrary precision to XaoS using the MPFR library ( <a href="https://www.mpfr.org/" target="_blank">https://www.mpfr.org/</a>), or a different one if it is not fast enough to support real-time zooming. The second part of the project focuses on rendering very large size images to support high-quality output. Support for various colour profiles, batch output, cropping, and the cartesian grid will be added along with this. Additional improvements to XaoSjs and support for web compilation of XaoS will also be carried out.</p>
The primary aim of this project will be the refactoring of a domain specific language compiler to produce Svelte components rather than React Components, in order to enable the translation of components specified using minimal syntax to robust, secure and functional web applications at scale. Multiple components will be implemented using the new svelte framework , such as a video conferencing meet-your-mentor component, and a gsoc Leaderboard component which would allow for the gamification of contributions to the Rocket.Chat community. Finally, all components will be adapted to fully meet the pre-scaled “serverless” vision for the application, so components can be specified can be specified using terse syntax and transformed into full fledged applications at build time. All of this will culminate in the implementation of a functional Community Hub to be used for future summers.
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.
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.
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 ScholarLY 'annotate' module is a new tool, currently in a workable preliminary state, which extends the LilyPond music engraving software to add various implementations of textual annotations for collaborative workflows and the creation of critical editions. This project aims to improve functionality of the module within the LilyPond environment, and to extend the various outputs of those annotations. As such, the primary target features include triggering of score items from within annotations, ability to render score snippets in annotations, addition of new output file types of annotation logs (it currently supports plaintext and tex), ability to handle and export latex-ready footnotes, and the creation of a versatile LaTeX package (which does not exist yet in any state) for compiling the annotations (from the previously exported log) in LaTeX with customizable options for styling and distribution. Ultimately, 'annotate' offers a comprehensive functionality that hasn't yet been achieved in traditional/commercial softwares, and which will benefit a range of engravers from amateurs and individuals to professionals and group settings.</p>
-Project Description The current Botpress Connector allows users to easily connect a bot to a Rocket.Chat instance without any coding necessary. But the current design is limited to a single bot operating on direct channels. This decision was made due to privacy concerns of bots answering with sensitive data. This project aims to improve the functionality and usability without compromising privacy. This project consists of allowing multiple bots to be connected and operating on various use cases (channels, omnichannels and direct). It also aims to improve the UI by correctly rendering rich components (bots with interactive graphical capabilities). By developing these features we can not only focus on extending the Botpress Connector, but also on making these extensions a good foundation for other bot connectors -Deliverables Multiple bots can be configured with the Botpress Connector The Connector can inform which channels the bot is responding to The bot can answer on omnichannel, channels and direct When handling sensitive data, bots will respond with a direct message Rich components correctly render for the agent