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 aims to significantly enhance Mesa-Frames by building efficient and scalable data collection tools for large-scale agent-based simulations. The core focus is on developing a flexible framework that allows researchers to analyze simulation data with greater precision and lower overhead. One of the main components, the Stats Collection, will enable users to define exactly which statistics they want to track—such as mean, max, or count—helping reduce both memory usage and computation time. Another key feature is the Event Driven Collection, which records data only when predefined conditions are met. This ensures researchers capture meaningful insights while avoiding unnecessary logging and storage. To support even larger simulations, the project will also include integration with external storage systems like PostgreSQL and S3, allowing collected data to be streamed directly to disk or the cloud. In addition to these core improvements, the project will focus on performance optimization through lazy execution with Polars and better vectorization. Clear, modular documentation and a focus on usability will ensure Mesa-Frames remains an accessible and powerful tool.
This project extends Apache Airavata to support interactive development sessions on HPC clusters by integrating linkspan as a managed on-node agent. It addresses the gap by bringing interactive sessions under Airavata's existing framework for authentication, resource management, experiment tracking, and data movement. The proposed solution adds an Airavata mode to CS-Bridge in which users authenticate through Keycloak, discover resources through Airavata, and launch linkspan sessions as Airavata-managed jobs. Each session will be tracked as a first-class Airavata experiment with lifecycle state and recoverable metadata. On the backend, linkspan will be registered as an Airavata application with per-resource deployment descriptors, server-side workflow YAML generation, and an orchestration path for environment setup, job submission, and monitoring. The main deliverables are linkspan application registration in Airavata, interactive-session experiment tracking, new REST endpoints for session management, two minimal linkspan workflow actions for status and VFS reporting, Airavata mode in CS-Bridge, overlay-aware data movement integration, and an end-to-end tested and documented demonstration of the complete workflow.
<h3>Visualisation of the MOLTO-3BP Incorporating Matlab Python SDK</h3> <p>I am aware there are many applicants, thus I sincerely apologize and regret my delay but hope I can be given an assignment/evaluation test.</p> <p>I'm applying to the track for the visualisation of the MOLTO-3BP network as I am enrolled to start a graduate program in CS using distributed technology and am interested in the applications of orbital equations and computing problems.</p> <p>My motivation lies in my current interest for Backend and Frontend applications as I also work with a company managing their ML algorithms for data prediction in arbitrage contexts as lead analyst and developer for the Full-stack infrastructure to support such volume and structure the visualisation process for qualitative information (as quantitative is given by volume in this case). I am now interested in leveraging such skillset to perhaps a more researching-focused world in lieu of an economic speculative industrial motivator.</p> <p>I believe the 3BP is very interesting from a theoretical point of view and can be greatly improved with visual filter and newer GUI revamp to its already robust computational engine (orbital eq in the halo numerical model)</p>
refer notion site for better view : https://smart-rhubarb-c5c.notion.site/GSoC-2025-Proposal-Project-12-Empowering-Kubeflow-Documentation-with-LLMs-1c209ac9a7bd80e6941ee51ab6601c7c This project aims to build an AI-powered assistant for the Kubeflow ecosystem using Retrieval-Augmented Generation (RAG) and a long-context LLM. The assistant will index Kubeflow Github repository including, GitHub issues, and community discussions using a structured pipeline involving Feast (feature store) and Milvus (vector DB). It will support real-time queries through a FastAPI WebSocket interface and serve responses via KServe. Key deliverables include: End-to-end RAG pipeline integrated with Kubeflow Pipelines & Feast GitHub-triggered document ingestion and vector index updates LLM deployment and retrieval API with RBAC controls Evaluation loop using “LLM-as-a-Judge” Monitoring setup with Prometheus + Grafana Frontend integration with Hugo-based docs site This project will improve Kubeflow’s developer experience by enabling contextual, cited answers directly from its ecosystem.
The proposal outlines a high level plan to port the Hardsubx module to Rust. The proposal intends to port Hardsubx to Rust with the minimum amount of rewrites required while ensuring maximum memory safety through various stages. The final version of Hardsubx will have the exact same external interface as the old one. The live document is available in this url for feedback and changes: https://docs.google.com/document/d/1U9RqfbjfVNUkUYOBzT6yn1ANLGo_v58wtepslbQhtV4/edit?usp=sharing Edit: - Add support for tesseract cube engine for better performance in extracting burnt-in subtitles - Update subtitles for tests because the different tesseract engine will generate different subtitle files from before. Edit2: - add promising rust wrapper options for Tesseract, Leptonica, and ffmpeg Edit 3: - divide the timeline phases into mostly biweekly periods Edit 4: - add guarantees on subtitle quality in the deliverables - add contingency on LSTM replacing the current system. Now, in the experimentation period we need to determine if the computational tradeoff is worth it for using an LSTM. Edit 5: - add deliverables for first evals - add other possible commitments in the GSoC period
Apache HugeGraph's query engine relies on Java 11, TinkerPop 3.5.1, and Groovy 2.5.x, facing critical issues: the security sandbox depends on Java's deprecated SecurityManager and a blacklist already bypassed in CVE-2024-27348, while TinkerPop 3.5.x lacks 26 new Gremlin steps, GraphBinary, and JDK 17 support. This project will execute a phased upgrade to Java 17 + TinkerPop 3.7.x + Groovy 4, covering full TinkerPop API migration with custom Steps/Strategies adaptation, a security sandbox redesign from runtime blacklist to a three-layer compile-time whitelist defense using Groovy 4's @CompileStatic and AST Customizers with configurable enforcement modes (strict/warn/off), extension to PD/Store distributed modules, and performance benchmarking on the Twitter-2010 dataset. Deliverables include the upgraded codebase (PR), the new compile-time security sandbox, PD/Store module upgrade, a quantified performance benchmark report, full regression test reports, and a complete documentation set.
<p>One of advantages of document-oriented databases like MongoDB or Couchbase over RDBMSs is an ability to change the data scheme easily, fast and often. The traditional approach in RDBMS world involves doing an expensive ALTER TABLE operation, slow upgrade of an existing data, and stuff like this. This approach is often slow and inconvenient for application developers. To solve this issue PostgreSQL provides JSON and JSONB datatypes. Unfortunately JSONB has a disadvantage of storing all documents keys, which is a lot of redundant data. One possibility to to reduce JSONB redundancy is to use zson extension. It compresses JSONB documents using shared dictionary of common strings that appear in all or most documents. This approach has its limitations though. Particularly, since data schema evolves, the dictionary has to be updated from time to time. Also zson can affect the build-in mechanism of PostgreSQL of compressing data using PGLZ algorithm since this mechanism uses some heuristics to recognize data that compresses well. Thus sometimes zson can reduce the overall performance. The idea of this project is to create an extension that provides Thrift support which solves zson problem.</p>
<p>KDE has a vast web infrastructure. Some KDE websites have not been upgraded in a long time and use dated technologies.</p> <p>The first part of this project involves porting KDE's main website <a href="https://kde.org" target="_blank">kde.org</a> to Hugo - A Go based static site generator. This would allow for ease of development, faster load times and more security.</p> <p>KDE websites also currently use OpenLDAP and a PHP application to authenticate and manage users (<a href="https://identity.kde.org" target="_blank">identity.kde.org</a>). OpenLDAP is an old and complex method of authenticating and managing user identity and several modern approaches are available. Moreover many services do not support OpenLDAP authentication (Eg. discourse). One of the newer approaches is to use OAuth2. OAuth2 is a modern approach to authentication and fixes the various issues with LDAP. So, the project also involves migrating <a href="https://season.kde.org" target="_blank">season.kde.org</a> to OAuth and giving it a much needed visual overhaul at the same time.</p>
The Network Simulation Bridge (NSB) is a powerful co-simulation framework, but its current onboarding experience creates a barrier for new users due to fragmented documentation, absence of a clear “first success” path, and setup complexity. This project aims to design and develop a user-centric website that transforms onboarding into a structured and intuitive flow. The core focus is enabling users to run a working NSB example quickly through a quickstart-first approach, followed by progressive introduction of concepts, configuration, and simulator integration. The solution includes building a complete website with a guided Get Started system, reorganized documentation, and clearly defined learning paths, along with a progressive simulator integration strategy that begins with a simplified environment before moving to full simulator workflows. Key deliverables include a deployable NSB website with structured navigation, a guided onboarding flow centered on first success, unified documentation migrated from the repository, and tutorials with progressive learning pathways, validated through user testing and iteration. This project will reduce onboarding friction, improve usability, and make NSB more accessible to students, researchers, and developers.
With this proposal, my aim is to make Oppia's learner-facing pages more accessible by by learners having any form of disability. My suggested method involves two-fold approach. I'll start by addressing the accessibility issues (a11y) that have already been reported on the site. This will entail addressing difficulties with heading-related issues, focus management, colour contrast, and more. Many of these a11y issues have contributors associated to them. While I resolve the unassigned problems, I will be available to help any contributors who get stuck or require further support. Second, I'll utilise Lighthouse to evaluate every Oppia page that is intended for students, raising their accessibility scores to a perfect 100. Each learner-facing page's Lighthouse test audits will need to be examined in order to make the necessary changes. This will include adding alternative text for images, making sure header tags have the right semantic structure, and making sure aria-roles are contained by the appropriate parent. Also, in order to aid contributors in understanding the Lighthouse audit procedure and troubleshooting any potential problems that may emerge throughout testing, I will be adding guidance on how to debug Lighthouse tests to the Oppia documentation.
Rucio has proven its potential to be used for providing functionality to scientific collaborations to organize, manage, monitor, and access their distributed data and dataflows across heterogeneous infrastructures. What it needs is a revamped user-friendly UI. This will not only encourage existing users to get a feel of how Rucio continues to grow and reach new milestones, but also increase the adoption of the Rucio WebUI in general. The desired outcomes of my stint would not only involve a complete revamp of the existing UI by building a UI library of our own but also presenting users with a new & intuitive dashboard, keeping the core functionality of Rucio in mind. Rucio also supports multiple types of users and their specific workflows. The first task would involve migrating the WEBUI to a pure REST’ful architecture would require identifying and implementing new REST endpoints on the Rucio Server and developing a dynamic cross-platform ReactJS application capable of consuming the REST API directly. The second task is to improve the overall user experience for different users. The new dashboard would allow users to get a quick overview of relevant activity and provide quick access to frequently used functionalities.
This project aims to improve playlist management in ListenBrainz by making it easier for users to search, organize, and interact with their playlists. Currently, while some backend support exists, the user experience lacks intuitive features for managing personal playlists effectively. To address this, I plan to implement four main features. First, I will complete and enhance playlist search directly on the user playlists page. Second, I will introduce tag-based organization, allowing users to categorize and filter playlists efficiently. Third, I will add in-playlist track sorting options such as sorting by title, artist, date added, and shuffle. Finally, I will enable users to view their MusicBrainz collections as playlists and optionally save them within ListenBrainz. The project will involve backend changes such as adding new database tables and API endpoints, along with frontend integration using React to provide a smooth and consistent user experience. The final deliverables will include a fully functional playlist search feature, tag-based organization system, track sorting functionality, and MusicBrainz collection integration, along with tests and documentation for all components.
<p>Behavior Metrics comprises a wide range of robots with the pipeline completely set for various Deep Learning and Reinforcement Learning (RL) setups. With its main concern over the racing track, the Formula 1 (F1) setting solves the line following objective well. However, the presence of 2 separate pipelines for RL and DL is confusing to the users. The DL base works on the JDERobot app, while the RL base takes the privilege of gym-gazebo. These two bases are unable to communicate with each other. Also, the current framework does not leverage the full capabilities of testing scenarios and robots. Apart from line-following, F1 racing for autonomous maneuvers and drone racing has gained much popularity. Although these settings are highly derivative, it requires few significant changes in the control architecture and modularity wrt multiple robot settings. This project’s primary goal is to move towards more extensive support and documentation of Behavior Studio to suit the same RL environment or DL brain to multiple robots with continuous control integration. The advantages of such changes will make the framework more user-friendly and adaptive to various tasks and robot settings.</p>
Overview The middleware server in the CARE project, currently implemented in TypeScript, requires a rewrite in Django to enhance integration and maintainability within the existing ecosystem. The implementation includes a couple of steps Research Compatible ONVIF Packages for Python Identify and select Python packages compatible with ONVIF standards for interacting with ONVIF-enabled devices. Implement WebSocket functionality using Django Channels Utilize Django Channels to enable real-time transmission of vital data from various healthcare system sources. Integrate authentication mechanisms for HTTP requests and WebSockets Ensure proper authentication mechanisms for both HTTP requests and WebSocket connections from CARE and CARE_FE applications. Ensure Proper Typing Support Enhance codebase readability and maintainability by implementing type annotations throughout the Django middleware. Write Migrations to Align Tables with Django Models Create and apply Django migrations to modify existing database tables to align with Django model definitions. Deliverables A new django app which has all the functionalities of the existing typescript middleware Authentication for websockets and http requests Ensuring Proper Typing throughout the django app
Some of the most extreme and mysterious events in the universe like neutron star mergers, black hole accretions, and gamma-ray bursts are studied by the high energy radiations that they emit. Among all the brightness variations we can study in these sources, periodic and quasi-periodic oscillations are among the most interesting, because they can provide insights into the astrophysical processes in these objects. While the stingray package is a valuable tool for analyzing periodic data, its analysis of quasi-periodic data is limited by biases in frequency domain methods. To mitigate these limitations, a Gaussian process regression (a time domain method) can be used to model the time series for a kernel describing a QPO. Using Bayesian Inferencing, we can infer its parameters and assign them physical meaning related to the physics of the process and perform model selection between QPOs and alternative models. This can be used to reliably detect QPOs, and infer their physical properties. Such methods have already been implemented in recent papers (Huebner et al,2022), and the goal of this project will be to simplify their code and implement it in Stingray using the Tinygp library for the GP backend. It will also be accompanied by a tutorial and a demonstration on various datasets.
<p>Memory access is one of the most important operation done in modern processors thus it plays an important role in implementation of trusted execution environment. Recent secure processors and trusted environment encrypt memory contents to protect those important memory operations. However, sometimes just encrypting data is not enough since there are intelligent attackers who can see where the memory access goes to and infer where the real important data lies in. Those important data includes the private data, key, or OS fingerprint and else. These kind of attacks lead to concept of “memory obliviousness” to secure memory address itself. ORAM refers to Oblivious memory which can leverage obliviousness using specialized data structures and obfuscate memory access so even an attacker see or probe the memory access itself, he never learns about where important data lies on or even where the memory requests are headed to. Initially proposed by Goldreich and Ostrovsky, ORAM obfuscates memory access using random permutation, shuffling and encryption of contents. In this proposal, I’ll implement ORAM interface to support obliviousness on RISC-V’s trusted execution environment.</p>
<p>A support for Lua-scriptable syscall tampering and filtering will be added. It will be possible to inspect syscall arguments (including structures/unions of arbitrary complexity, given that their definitions are provided), passed both by value and by pointer (and write modified values back in case of the latter) using LuaJIT's FFI library or a compatible one (there are currently <a href="https://github.com/jmckaskill/luaffi" target="_blank">a standalone implementation of FFI library abandoned since 2013</a> and <a href="https://github.com/facebook/luaffifb" target="_blank">its fork by Facebook</a>).</p> <p>It will also be possible to perform fault/success/signal injection.</p> <p>A pull-style C API, as <a href="http://luajit.org/ext_ffi_semantics.html#callback_performance" target="_blank">LuaJIT's FFI documentation suggests</a> for minimizing context switching between C and Lua and thus maximizing performance, will be implemented, but a helper library written in Lua will wrap it to provide a convenient push-style one.</p> <p>Of course, everything added will be documented and tested well.</p>
Chaos Engineering is the discipline of experimenting on a system in order to build confidence in the system’s capability to withstand turbulent conditions in production, ref. https://principlesofchaos.org/, i.e. to induce errors on a system and see how it behaves. eBPF can be used to induce such errors on a system, it can change the return value of a kernel function, drop or modify network packets, etc. The goal of this mentorship is to implement a set of gadgets for Inspektor Gadget that helps causing system chaos. These are some ideas of the gadgets that should be implemented: - DNS: Drop/modify/add latency DNS requests and/or responses based on - The container or process performing it - The target URL - The DNS server - TCP/UDP: Drop network packets based on - Destination / Source IPs - Originating or destination pod or process - Simulate system call failures based on - Container or process performing the syscall - Syscall The gadgets should expose metrics with the number of times it induced failures, and possibly also provide notifications when those errors were induced. Expected Outcome: A set of gadgets with the above functionality should be implemented and merged on the upstream Inspektor Gadget repository. Those gadgets should include documentation and tests.
The Essential Care for Every Baby (ECEB) mobile application is designed to offer clinical decision support to healthcare personnel who provide essential care interventions for newborns. The project aims to improve the user experience, accuracy, and reliability of the app by revamping its user interface, improving the rule-based classification algorithm, resolving syncing issues on local storage and the DHIS2 rule engine, enhancing the app's functionality, and developing user manuals and training materials. The project will be implemented in four phases using Agile Development Methodology. The first phase will revamp the application based on UX changes, the second phase will improve the rule-based classification algorithm, the third phase will address DHIS2 rule engine and syncing issues, and the fourth phase will focus on documentation. The enhancements proposed in the design include making the application more accessible and user-friendly with more visual cues, legible fonts, and features that increase functionality. The goal is to ensure that healthcare workers in low and middle-income regions have essential knowledge, skills, and competencies to deliver life-saving care to newborns.
<h3>Background</h3> <p><a href="https://bd-r.github.io/The-bdverse/bdchecks.html" target="_blank"><em>bdchecks</em></a> is an infrastructure for performing, filtering and managing various biodiversity data checks using R. Data checks are a key to promoting biodiversity data quality. <em>bdchecks</em> offers various features for different types of R users:</p> <ul> <li>An interactive and user-friendly Shiny app for inexperienced R users.</li> <li>Full command line functionality for more experienced R users.</li> <li>Advanced R users can easily edit, add and manage their own collection of data checks, using one single YAML file and only two supporting R functions.</li> </ul> <p>Improving the quality of biodiversity research, in some measure, is based on improving user-level data cleaning tools and skills. Adopting a more comprehensive approach for incorporating data cleaning as part of data analysis will not only improve the quality of biodiversity data, but will impose a more appropriate usage of such data.</p>
The goal of this project is to add the JSON_* functions support in Select Handler mode. After the project, we can use json function with Columnstore in Select Handler mode. We can design and implement JSON functions. My implementation idea is as follows(take the JSON_VALID function as example): ● Related files and classes: define the relevant files required by the JSON_VALID function according to the specification of the SQL function definition in Columnstore 1. functor_json.cpp: According to the return value of the function, create new class Func_json_valid derived from class Func_bool. 2. func_json_valid.cpp: the JSON_VALID function is implemented here. Implement any other methods that behave differently from the default. 3. funcexp.{h,cpp}: in FuncExp::FuncExp(), add a new entry fFuncMap["json_valid"] = new Func_json_valid(). 4. CMakeLists.txt: Add any source files to build. ● Borrow and translate: 1. JSON_* functions are already implemented in MariaDB leveraging its own JSON format parser 2. The parser itself is couple files only library. Here is the main file. 3. So the next step is to read/understand this implementation and translate the code into Columnstore using the mentioned JSON format parser.
When tackling the challenge of detecting defects in high-resolution images, we encounter many challenges. One significant problem is the difficulty in training models effectively, primarily due to memory limitations. The process of down-sampling these images to fit within memory capacities leads to the loss of crucial information, which can result in the oversight of small yet significant defects. To overcome these issues, we can employ a strategy involving a tiled ensemble mechanism. In this case, images are split into smaller, manageable tiles. Each of these tiles is then processed using a separate model, specifically trained for that tile position. This strategy enhances localization and improves the detection of small anomalies, while also satisfying memory limitations. Anomalib currently has a basic tiler. However, the advantages of locally-aware models, like Padim, are diminished without the support of a tiled ensemble. To address this problem, we introduce a tiled ensemble implementation that preserves the advantages of local awareness while also enhancing overall performance. This approach aims to incorporate Anomalib's existing features, while simultaneously providing users the flexibility to tailor specific steps within our pipeline. All the while, we ensure that our approach remains memory-efficient.
Microcks (https://microcks.io/) is a cloud native, open source tool under CNCF for API and microservices mocking and testing. This project aims to enhance the [Microcks Hub](https://hub.microcks.io/) by updating the existing sandbox environment or adding new hub entries to mock key APIs IT industry leaders use. The goal is to make it easier for developers to test and prototype integrations with popular APIs like GitHub, Twilio, Stripe, or Salesforce using Microcks. Expected Outcome: Participants can choose to focus on one or both of the following aspects: 1. Update and Refresh the Existing Sandbox: - Improve the sandbox environment provided by Microcks Hub for existing mock APIs. - Ensure compliance with the latest versions of existing APIs. - Enhance documentation, usability, and deployment mechanisms. 2. Add New Hub Entries for Key Industry APIs: - Develop mock entries for leading APIs like GitHub, Twilio, Stripe, or Salesforce, but we welcome any ideas... - Ensure the mocks cover essential endpoints and realistic request-response pairs. - Provide detailed examples and use cases to support integration testing.
<p>Sugar has a lot of activities, with 250+ on GitHub, and more elsewhere. These have scope for improvement; bugs, features, updated human translations, and release. There are many activities which have not been maintained or updated for over a decade. It is important to port such activities from python 2 to python 3 along with porting them to Gtk+3. The support for python 2 is being withdrawn and the port to Gtk +3 to have a fully functional activity is important. Inaddition to that, the activity might require porting</p> <ul> <li>from GObject to GLib</li> <li>from GConf to Gio.settings</li> <li>from GStreamer Gst.Message.structure to get_structure()</li> <li>and porting to TelepathyGLib</li> </ul> <p>My project also includes adding feature improvements or fixing the features of the activity which are not working and fix display resolution issues. I will be collaborating with others to prepare activities for release and also test debian packages if needed. It is important to identify if the tracebacks are due to activity code, changes in versions of packages or due to difference in the test environment.</p> <p>So this project aims at making necessary changes to sugar activities to have at least 25 release ready activities.</p>