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.
I would like to volunteer to develop SSH Client/Server support for NuttX. I believe this is a highly valuable feature, as it would enable remote access to NuttX-based hardware in the field for maintenance and operational purposes. With SSH support, we could remotely interact with devices, trigger I/Os, manage peripherals, and perform diagnostics in a way that is conceptually similar to what we already do on Linux-based systems. Also, this is a great opportunity for me to develop my skills. The implementation would be based on Dropbear, a lightweight and complete SSH stack with a small footprint, which makes it well-suited for embedded environments. There is already a reference port available that I plan to use as a development guide: https://github.com/david-cermak/dropbear The project would be structured in the following phases: Initial study phase to assess requirements and dependencies, including evaluation of cryptographic library integration and system constraints. Review of existing ports for other platforms (for example, ESP-IDF) to understand architectural decisions and integration patterns. Porting of the required SSH client and server functionalities to NuttX. Testing, validation, performance assessment, and resolution of identified issues. Mentors: Alan C. Assis, acassis@gmail.com
While working with real-time systems, I observed that Flutter DevTools provides detailed visibility for HTTP requests but lacks support for persistent protocols like WebSockets. Once a connection is established, developers have little to no insight into message flow, latency, or connection lifecycle, making debugging significantly harder. This project aims to address that gap by extending the Dart SDK (dart:io, dart:developer, and the VM Service) to capture WebSocket frame-level and connection-level data. This data will then be integrated into the DevTools Network panel, following the existing HTTP profiling model to ensure consistency and minimal overhead. The implementation will include WebSocket instrumentation in dart:io, exposure of profiling data via the VM Service, and UI integration in DevTools to display messages, sizes, latency, and lifecycle events. If time permits, the same architecture will be extended to support gRPC traffic. By the end of the project, developers will be able to inspect WebSocket communication in DevTools with the same clarity and usability as HTTP, significantly improving debugging for real-time applications.
This project aims to address the inconsistency and redundancy found across customer-facing mobile applications built on the Mifos and Fineract platforms. Many of these apps share common screens and workflows, but their UI components are often rebuilt from scratch, leading to fragmented design, longer development times, and poor maintainability. To solve this, I propose to develop a unified, reusable UI component library using Jetpack Compose Multiplatform, ensuring compatibility across mobile, web, and desktop platforms. These components will be derived from shared workflows and designed according to updated design standards and guidelines developed in collaboration with our design lead. We will break down existing flows into base-level elements and reconstruct them into modular, scalable UI components. The deliverables will include: A set of core, reusable UI components built with Compose Multiplatform, shared design system with updated design principles and standards, Git-based repository to house the UI components and associated documentation, Sample screens and workflows implemented in a reference fintech app and documentation outlining how to integrate and update apps using the shared UI library.
We would like OpenCost to more effectively integrate with AI agents. To do this, we need to implement a Model Context Protocol (MCP) server to surface the information from the OpenCost API. This is a great opportunity to learn about MCP servers, and help us build an interface for AI agents to obtain reliable cost/usage information so that they can accomplish their business goals. Expected Outcome: We would like an MCP server integrated into OpenCost. This MCP server should support queries on allocations, assets, and cloud costs. The MCP server should support the full range of allocations, assets, and cloud cost query parameters. A demo video should be recorded showing an interaction with the MCP server, and used to obtain costing information in a conversational setting. In addition, integration tests must be created in the OpenCost Integration Tests repo that test all interactions with the MCP server.
<p>Sugarizer School Portal (SSP) is a Kubernetes based portal which provides on-demand Sugarizer Server Deployments. The proposed features include:</p> <ul> <li>A Sugarizer and Sugarizer Server Helm package (Sugarizer-Server Chart).</li> <li>Automated cluster database backup and restore facility.</li> <li>A Setup script to bring the Kubernetes stack up.</li> <li>A web interface for the Kubernetes infrastructure called Sugarizer School Portal Server (SSP Server), that could deploy on-demand Sugarizer-Server instances.<ul> <li>Role-based authentication with optional email verification based signup.</li> <li>Clients can request deployments from the web interface and admin to approve the deployment.</li> <li>The web interface allows creating/managing Sugarizer Server instances on the cluster.</li> <li>Automatically exposes the Sugarizer Server Instances onto a sub-domain to be used by the clients.</li> <li>The infrastructure uses MongoDB Replicaset as the database inside the cluster.</li> <li>Optionally dispatches Slack and Email notifications when the status of the deployment changes.</li> <li>Allow account creation in Sugarizer Server deployment directly from SSP Server.</li> <li>Displays SSP analytics on the dashboard.</li> <li>A Helm package for the SSP Server (SSP Chart).</li> <li>Deployment health checks.</li> </ul> </li> </ul>
Vitess is a distributed database system built on MySQL. Flags are widely used in Vitess for configuring components. As part of a major Vitess flag restructure, support for dynamic flag configuration was introduced. However, several Vitess components have not yet fully adopted this feature. This project involves modifying these components to fully integrate dynamic flags and performing additional flag-related refactors where necessary. Expected Outcome: Improved flag support across all Vitess components, ensuring consistent and flexible configuration management.
<p>I have decided to select the project, camel-minio - Component to store/load files from blob store(<a href="https://issues.apache.org/jira/browse/CAMEL-13934" target="_blank">https://issues.apache.org/jira/browse/CAMEL-13934</a>)</p> <p>Camel simplifies service integrations with an easy-to-use DSL to create routes that clearly identify the integration intentions and endpoints. Camel's out-of-the-box integration components are modeled after the Enterprise Integration Patterns cataloged in Gregor Hohpe and Bobby Wolf's book (<a href="http://www.eaipatterns.com" target="_blank">http://www.eaipatterns.com</a>). Camel allows you to integrate with quite a few protocols and systems out of the box using Camel components. Each component is highly flexible and can be easily configured using Camel's consistent URI syntax. In this project I`m going to add one more component to the camel components collection hopefully it will be a popular and widely used component.</p>
The Sugar Shell is the core desktop environment of Sugar and is responsible for activity launching, the Journal, the Frame, and system integration through DBus. The current Sugar Shell is built on GTK3, and several core components still depend on deprecated GTK3 APIs, which must be migrated to GTK4. This project focuses on the GTK4 migration of the Sugar Shell. The work includes replacing deprecated GTK3 APIs, migrating container and layout APIs to GTK4 equivalents, updating event handling using GTK4 event controllers, migrating styling to GTK CSS, and updating display and geometry handling using modern GTK4 display APIs. The migration will be done incrementally, component by component, starting with core components such as the Frame, Home View, Activity Launcher, Journal, Clipboard, and Control Panel. Each component will be migrated, tested in a running Sugar session, and submitted as small patches to ensure that the Sugar Shell remains stable and usable throughout the migration process. By the end of the project, the Sugar Shell will run on GTK4, core components will be migrated to GTK4 APIs, deprecated GTK3 APIs will be removed from migrated components, and migration documentation will be provided to support the remaining GTK4 transition work in the Sugar project.
<p>This proposal consists of the development of a compliance test suite for Reference API servers with validation and checks for URLs, status codes, correct response, checksum (to be used as the identifier) etc. This test suite to be used as a reference to facilitate Test Driven Development of Reference Servers. A Python client library along with an interactive command line interface tool to access Reference Server Data will be developed using TDD techniques. Finally, a complete system test suite comprising of various functional and system tests of client-server architecture will be used to test end to end compatibility of every Reference Server with every client.</p>
<p>Currently the open event frontend is implemented in Ember.Js. The plan is to shift the UI to React page by page.</p>
<p>WSO2 Identity and Access Management Server is open source popular identity and access management server throughout the world plus WSO2 Identity Server efficiently undertakes the complex task of identity management across enterprise applications, services, and APIs. For this project IS version 5.4 is used. Currently, WSO2 identity server is consisting of SOAP services and in near future, there will be REST API's which support for all functionalities and which is more effective. In current environment most It support for different user stores like LDAP, JDBC, and MySQL as primary and secondary user stores. with the having facility of creating a new user store the primary data which are saving to primary user store can be separated to different user stores as one for user details and other one is for user attribute (claims) details which can be accessed by providing user credentials and secrete.</p>
The Internet Printing Protocol (IPP) does not only support printing, but also scanning, as there are many printers which also have a scanner (multi-function (MF) devices). Both CUPS and the developer tool ippserver emulate IPP network printers but not IPP scanners and so they cannot serve as a server to share a local scanner. This task is about adding the scan server functionality. If you have a scanner connected locally (and it scans via SANE), share it as an IPP scanner, advertising itself and accepting jobs using the IPP driverless scanning standard. In contrary to SANE-based network scanning clients with any operating system, also phones or IoT devices can scan on your shared scanner. Also old hardware can be recycled to a modern MF device. This server software will be a so-called Scanner Application, a sample implementation of the future form of scanner drivers, easily packageable in sandboxed, distribution-independent package formats like Snap.
<p>JdeRobot is a software development suite for robotics, home-automation and computer vision applications. These domains include sensors (for instance, cameras), actuators, and intelligent software in between. It has been designed to help in programming such intelligent software. Details for the project: Project #5. Teaching Robotics: Translation of a Scratch program to ROS python components Scratch is a free visual programming language used in children's education, to teach them basic programming. It is composed of graphical building blocks (instructions) that must be visually connected to build the program. The idea here is to take benefit of our experience translating from a graphical description of a program in visual HFSM into a JdeRobot-ROS component to do the same with a different visual language, Scratch. The goal is to explore the use of Scratch with robots, both simulated or real, that JdeRobot-ROS allows and simplifies. We will start with simulated robots in Gazebo, despite with real robots will be the same as they use the same interfaces. This project expects to develop a new tool prototype that reads Scratch programs and translate them into ROS Python components.</p>
"Cockpit navigator" is a featureful File System Browser for Cockpit, which allows the user to remotely browse, manage, edit, upload, and download files on the server through the web browser. The project is about modernizing this plugin by following some new designs and rewriting the codebase to follow the standards specified by the starter-kit plugin. The project includes porting to React, adding tests, updating Patternfly, and much more.
The existing End-to-End (E2E) tests for the new React front end are hindered by low coverage and instability, compromising the reliability of the application. This project is dedicated to significantly improving E2E test coverage, ensuring comprehensive validation of the entire application workflow. By enhancing these tests, we aim to verify the seamless integration of components, ensuring the application functions correctly and reliably from the user's perspective.
The Karmada project consists of several components (e.g., controller-manager, scheduler, karmada-search, etc.), each accepting various command-line flags for configuration. These flags come from multiple sources: third-party dependencies (e.g., Kubernetes, controller-runtime) and custom flags defined by Karmada itself. During dependency upgrades or internal refactoring, flags can be unexpectedly added, removed, or modified, potentially impacting users who rely on specific configurations. This project aims to create comprehensive documentation and tooling to track and document all flags for Karmada's maintained components, establishing a baseline to detect and manage flag changes carefully. Expected Outcome: 1. Comprehensive flag documentation for all Karmada components (controller-manager, scheduler, karmada-search, webhook, aggregated-apiserver, descheduler, metrics-adapter, scheduler-estimator) 2. Automated flag extraction and documentation generation tool 3. CI/CD pipeline integration to detect and alert on flag changes 4. Documentation of flag lifecycle management (deprecation, removal)
<p>This project aims to focus on some of the primary goals the repo orcamap-react needs to support the visualization of hydrophones, orca calls, ships, sightings (can be weather, and ocean natural phenomena, too) and increasing the engagement of users with the feature to subscribe for further notifications. Developing different layers as a reusable component to onboard different data will be helpful to reuse them with other projects too (like orcasite and shipnoise).</p>
The component-model proposal merges and supersedes the Module Linking and Interface Types proposals. With this feature, WasmEdge can execute multiple modules wasm with Module Linking and and more flexible types with Interface Type.
<p>This proposal aims to implement an OAI-PMH component for Apache Camel. OAI-PMH is a protocol widely used in libraries and digital repositories across the world. This implementation will be extremely useful for final users working on data integration this domain.</p>
<p>Exporting chats is an easy way to save conversations into the disk, which can be archived or shared with outsiders. This feature will be handy for users who have millions of messages and can’t easily access the oldest parts of their messaging history. As Matrix also provides end-to-end encryption via the Olm and Megolm cryptographic ratchets, the process will include decryption of messages. I will be using matrix-react-sdk and matrix-js-sdk, which provide adequate functions and methods to communicate with the server, handle encryption and build a very feature-rich export tool.</p>
<p>Casbin is an authorization library. Its support for diverse programming languages, different access control models and the powerful adapters gains it the greatest popularity in the open source community. However, there are still lots of difficulties in utilizing Casbin at the frontend, especially applying it on the management of users’ accessibility to specific UX widgets. In the GSoC 2020, I wish to implement a friendly JS library (aka Casbin.js) and other supported facilities to extend Casbin to the frontend development. This project mainly includes a plug-and-play Javascript library that supports for seamless connection with server, auto page controlling and the corresponding components and plugins for modern frontend frameworks.</p>
The motivation behind this project is to extend and introduce a fully functional MCP server for pgmoneta. To achieve this ultimate goal, we have identified a set of subgoals that will transform the current implementation into a production ready system: Introduce Non-Blocking I/O for Intensive I/O Operations (e.g Backup). Architectural Abstraction refactoring via the Rig Framework. Production-Level Security & Authentication. Knowledge Retrieval via MCP Resources. Testing and Documentation