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 addresses the latency and response time variability issues in the hugegraph-server query engine by introducing memory management framework to it. Currently, the engine utilizes off-heap memory in most OLTP algorithms, but lacks the ability to control memory allocation per individual query, leading to potential out-of-memory (OOM) errors. The project aims to design and implement a unified memory management framework to address this limitation. This framework will include features such as lifecycle management of memory objects, memory capacity restrictions, and an allocator interface for efficient memory allocation and release. By implementing this framework, the project is expected to improve the stability and performance of the hugegraph-server, ultimately enhancing its usability and reliability for users.
<p>hydrus(Hydra universal server) is a python based tool to create hypermedia-driven REST-APIs. It uses Hydra(W3C draft) standard for creation and documentation of its APIs. This proposal aims to improve hydrus and extend its functionality. As we want to make hydrus reliable and complete, we will need to at least provide all the basic functionalities a Hydra-compliant API Documentation can describe. As we are planning to create a testbed in hydra-python-agent to test whether a server is Hydra compatible or not, it makes sense to first make hydrus compatible with Hydra so we can test it. So besides extending the functionality of hydrus, this project includes refactoring hydrus and making it completely compatible with Hydra specification.</p>
<p>Aim is to build all the portions of the FastAI.jl package, inspired by the fastai Python library, which will provide high-level components that can quickly and easily provide state-of-the-art results for tabular tasks, and provide low-level components that can be mixed and matched to build new approaches.</p> <p>This will include handling tabular data of all kinds of format, performing transformations on it if required, creating a model using best practices and entity embeddings, and being able to train the created model.</p> <p>All this will be done without compromising in ease of use, flexibility, or performance, due to the benefits Julia provides, along with the well designed three layered architecture.</p>
The aim of this project is to focus on patch-level classification tasks within the domain of whole slide tissue images. The approach involves utilizing pre-trained models as encoders and applying them to the task of patch-level classification. By leveraging pre-trained models, readily available on platforms like Hugging Face, aim to expedite the development process while maintaining high performance. The ultimate objective of the project is to integrate these pre-trained models into caMicroscope, providing users with a convenient tool for downloading and training models tailored to their specific tasks. Deliverables: - A documented method for training a classification model using a pre-trained or foundation model. - Implementation of this method as a set of software components. - Integration of the components with caMicroscope.
Implement MS-RDPEUSB protocol (client & server) in IronRDP with libusb backend and qemu-rdp integration. The goal of this project is to add USB device redirection support to IronRDP, the Rust implementation of the Remote Desktop Protocol. This enables client-attached USB devices (webcams, scanners, security keys, etc.) to be transparently accessed by applications running on the remote server. MS-RDPEUSB is a Dynamic Virtual Channel (DVC) extension that provides low-level USB packet redirection. Unlike high-level device redirection (like file system or audio), USB redirection transfers raw USB packets, allowing any USB device to work remotely without device-specific driver support on the client.
<p>To make printing easy for the users of desktop systems and mobile devices, a well designed print dialog should be there where a user can easily find right printers and right options to get the desired print. This project aims at implementing a common print dialog that will enable users to print documents easily. This project has a UI component which will be implemented in a major toolkit (GTK, Qt) and the backend component of this project is divided into three parts namely CUPS backend, IPP Backend and Google Cloud Print Backend. This project aims at implementing these modules. More specifically, implementation of Google Cloud Print backend will include designing and implementing a module along with proper documentation and tests.</p>
This project focuses on implementing an enhanced Model Context Protocol (MCP) and A2A communication framework for KubeStellar's Management Control Plane server. It builds upon the foundation MCP implementation to include advanced A2A coordination capabilities, distributed AI agent communication, and sophisticated context management for multi-cluster environments. Expected Outcome: A fully specified Model Context Protocol with A2A communication extensions, implementation of protocol handlers in Python for the MCP server, A2A communication framework enabling AI agent coordination, context management system for KubeStellar state information, serialization mechanisms for cluster state, protocol extension mechanisms for different AI providers, performance optimizations, and comprehensive test suite.
Current driverless print servers can be complex and resource-demanding in large part since they only run on full-scale operating systems like Linux. This project aims to port the different elements of OpenPrinting's printing stack (CUPS, libcupsfilters, etc.) to the Zephyr OS for simple future print server development on embedded devices. This will consist of systematically adding Zephyr modules and commits to the OS itself for each part of the printing stack. Importantly, Zephyr replacements and ports must also be used instead of the current Linux dependencies. This leads to further investigation into the capabilities of the Zephyr OS to support technologies such as Ghostscript and print buffering. Lastly, the stack must be tested on hardware to verify functionality and view benchmarks such as power consumption.
<p>This project targets at making Android app for vitrivr. Currently vitrivr has a web UI which is vitrivr-ng but it is not optimised for mobile use. vitrivr App will close that gap between vitrivr and mobile devices. Also this project will include adding/improving features of cineast like Spatial Retrieval and Add Media API. Spatial Retrieval will allow users to query on the basis of Location while Add Media API will allow users to add media directly from UI rather than writing commands on cineast server. Integrated with these, it will create a cohesive experience for mobile users which will allow them to query media from a huge server, collaborate with people or query media from own mobile device.</p>
The proposal deals with the problem of the creation of a kubectl plugin for Armada, the creation of the desired plugin will allow users to communicate with Armada via kubectl. The solution this proposal provides is that in order to create a plugin for kubectl we need the help of armadactl i.e. command-line utility for Armada through which users submit their jobs to the Armada server. To develop a plugin for kubectl, we first must develop a base plugin for armadactl in Go that performs basic tasks such as submission and cancellation of jobs, creation of queues, etc. After the necessary coding for the plugin is finished, we now distribute that plugin over at Krew so that it is globally accessible. Once it is distributed at Krew, a user can install this plugin as a kubectl plugin and can interact with the Armada server and perform the aforementioned tasks.
This project aims to enhance the course copying feature present for copying courses across the servers. Currently, when courses are copied between these platforms, crucial elements such as Timeline content are not included, posing challenges in reusing assignment plans. The proposed improvements will streamline the transfer process, enabling seamless migration of Timelines and other essential content across servers utilising pre-defined classes and methods. It would also allow non-admins to copy courses from Wiki Education Dashboard to Program and Events Dashboard. The current Dashboard mobile view presents challenges such as overflowing pages, non-responsiveness and design flaws, significantly limiting its functionality on small screens and hampering the overall user experience. This project also aims to resolve them.
<p>PostgreSQL is an object-relational database management system (ORDBMS), unlike MySQL which is a Relational Database Management System(RDBMS). It is easy to setup and install and offers support for both SQL and NoSQL. While there are pros and cons of both of these database management systems, it ultimately boils down to your requirements.</p> <h3>Why use PostgreSQL for OpenMRS?</h3> <p>As stated in the project description there are a large number of implementations who would like using PostgreSQL instead of MySQL. There is also another category who have already invested in PostgreSQL servers, where requiring them to install and learn another type of database server would not only be an unnecessary waste of their time, but also a wastage of computer resource.</p> <h3>Thus, this project aims to add PostgreSQL to the list of databases that OpenMRS supports.</h3>
<p>This project’s objective is to add an SSH proxy for the Cowrie (<a href="https://www.cowrie.org/" target="_blank">https://www.cowrie.org/</a>) honeypot. Currently, Cowrie emulates an SSH server using Python, and provides proxy functionality only for SSH exec commands, but no interactive terminal sessions. In this project we expect to implement the logic to <strong>forward SSH protocol messages</strong> from clients into backend SSH servers, thus allowing for <strong>full-fledged terminal sessions</strong>, and converting Cowrie into a <strong>high-interaction honeypot</strong>. Our proposal includes the addition of a <strong>backend management module</strong>, which will handle the virtual machines where commands received by the proxy are executed.</p>
This project focuses on enhancing and improving the Chaos Center code base, specifically redesigning the Chaos Workflow APIs to provide an enhanced user experience. The main objectives include refining the functionality of the Chaos Workflow and Workflow Run APIs, modularizing the chaos-workflow package into separate packages, and addressing security vulnerabilities and golangci-lint issues in the Chaos Center backend components. The project aims to deliver a more robust and secure Chaos Center platform, offering improved usability and performance for users. - Expected outcome: The outcome of this project will be improved functionality, security, and usability of the chaos workflow GraphQL APIs and chaos-center backend components through the implementation of new features, refactoring of existing code, and addressing of security vulnerabilities.
The NeoWarm swaddling device and NeoRoo mobile app have been developed to support Kangaroo Mother Care/Skin-to-Skin care for premature newborns and automatically collect vital signs information. The aim is to overcome the barriers to implementing KMC/STS and improve care for premature babies. The technology includes features such as automated monitoring of vital signs, alerts for abnormal readings, and shared goal-setting for education and discharge planning. To enhance the usability of the NeoRoo app, a participatory design study with A/B prototypes is being conducted, to improve the app's UI based on feedback. My rule is to implement the enhanced UI in Flutter and integrate the new UI with the DHIS2 backend server to ensure that the UI interacts seamlessly with the underlying logic and functionality provided by this server.
<p>Currently gatsby-source-plone plugin is unable to update,update, delete and create node after fetching data from plone site unless GatsbyJs development server is manually restarted or GatsbyJs site is rebuilt. This project plan is to enhance existing project "gatsby-source-plone" with features that allow "gatsby develop" development server to provide up-to-date instant live previews of pages that contain data from a Plone CMS source. Plone is an enterprise open-source CMS solution written in Python. The aim is to enhance "gatsby-source-plone" to provide a GatsbyJS development experience matching the experience provide "gatsby-source-filesystem" based plugins, which can create, update and delete nodes on from filesystem events.</p>
This project aims to develop a Text-based User Interface (TUI) framework for Dart, addressing the lack of a structured way to build interactive terminal applications in the language. While Dart excels in GUI development with Flutter, it lacks a robust solution for TUI-based applications. This framework will provide essential UI components, efficient rendering, and event-driven input handling, enabling developers to create modern, cross-platform terminal applications. Key deliverables include a modular TUI library with core UI components, theming support, optimized rendering, comprehensive documentation, and real-world examples. This project will expand Dart’s capabilities beyond mobile and web, making it a viable choice for terminal-based development.
Metaflow's metadata service returns unbounded JSON for every list endpoint. A single GET /runs on a production deployment returns megabytes of data the caller immediately discards. For AI agents, this is worse: a failure-diagnosis workflow generates 2,021 HTTP calls to check 1,000 tasks. This proposal adds cursor-based pagination and server-side tag filtering to the metadata service (prototyped in PRs #9 and #10, 65 tests passing), integrates pagination into the Python client SDK, and builds agent-friendly query utilities that, across five common agent workflows, collapse 11,828 API calls into 16. Server-side work is already prototyped. GSoC starts at hardening, not greenfield.
<p>loklak is free software hosted on loklak.org which provides message search results from twitter in json format. loklak is a complete search engine back-end solution with a json api. Loklak’s API can be used to build twitter clones and client alike, one of them being loklak.net. One of the main features that’s pending in such a tool is the ease of adding angular micro services and modularizing the existing application to run on micro services. Alongside the data store of loklak is magnificent and provides the ability to build IoT platforms using the loklak server. In this proposal I would like to enhance the service architecture of loklak.net and build a proof of concept IoT application demonstrating the capabilities of the loklak server.</p>
<p>Creating a Joomla 4.0 frontend template will be much easier by using an intuitive page builder. With this, users can desire the position of elements by a grid, buttons and drag'n'drop and select the information these elements should display. For a faster development the JavaScript framework Vue.js will be used, which provides a strong base for creating reactive components. The plan is to have one month for building the page builder and one for the implementation in Joomla. Final tests, integration and documentation is part of the third month. Years of experience in component, backend and frontend development helps to understand Joomla. Git and JS were part of past projects too. So let's give Joomla a page builder out of the box and give every user the possibilty to build customized templates.</p>
YCbCr is a color space used in video and digital systems to express color, where Y is the luma component and CB and CR are the blue-difference and red-difference chroma components respectively. This project aims to add YCbCr support to the Nouveau Vulkan driver (NVK), which opens the way for support for more applications and is also an important step towards Vulkan 1.1 compliance. Work on this project is split into 4 phases; first investigation and reading up the relevant parts of the Vulkan specification and the open-sourced NVIDIA hardware headers, second the actual implementation and coding, and finally the third and fourth stages being verification and review where I verify that the implementation is working and conformant, and fix any issues that pop up. All this would then be followed by a merge request implementing and enabling YCbCr support in the driver.
Vitess uses arewefastyet to automatically benchmark its codebase and ensure no performance regression is introduced. This tool benchmarks Vitess every day, and is used to visualize the results of those benchmarks. It is an important tool in the development cycle of Vitess and is used by its maintainers and adopters. Arewefastyet' website has changed quite a lot over the last year, we want to continue improving it by finishing the migration to TypeScript and by using Shadcn components. Moreover, we want to make the website responsive and have a proper Figma that serves as a reference for current and future contributors. Expected Outcome: The mentee is expected to produce a Figma with the design of the website that will be co-authored with the mentor. Re-vamp most of the pages using Shadcn and the design defined with the mentor at the start of the internship period. Add type information for all/most components using TypeScript.
In recent years, FOSSology's REST APIs have expanded significantly, enhancing user accessibility, flexibility, and automation. However, the development is not yet complete, prompting some users to resort to mocking WebUI access solely for information retrieval. With the development of FOSSology's new React UI also underway, robust support for REST APIs becomes imperative. This project aims to finalise the development of FOSSology's REST API by exposing any remaining endpoints, enhancing and upgrading existing ones to V2, increasing test coverage, and improving documentation. The approach involves a comprehensive review of each module to ensure the availability and exposure of required APIs for frontend consumption. These efforts will streamline development workflows, enhancing the overall usability of the FOSSology platform and facilitating the development of the new React UI.
Title: Generic Gizmo System for Graphite Problem: Graphite currently has 6 separate shape-specific gizmo handlers (Circle, Star, Polygon, Arc, Grid, Spiral), each with duplicated code for hover detection, drag handling, and overlay rendering. Solution: A unified, data-driven gizmo system with three components: Registry — Declarative mapping of node parameters to gizmo types Generic Gizmos — Reusable components (Slider, Dial, Angle) that work with any compatible parameter Manager — Auto-instantiates gizmos based on registry lookup Deliverables: 3 generic gizmo types (SliderGizmo, DialGizmo, AngleGizmo) All 6 existing shapes migrated to the new system Old handlers removed, reducing code duplication Developer documentation for extending to new nodes