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.
Stochastic simulation is essential in computational biology and infectious disease modelling, but existing methods require a trade-off between accuracy and computational efficiency. While exact stochastic simulation captures dynamics in small populations, it scales poorly, whereas deterministic ODE models are efficient but fail to capture stochastic effects. The Jump-Switch-Flow (JSF) framework addresses this by dynamically switching between stochastic simulation and deterministic ODE integration based on population size. However, despite a mature Python implementation, R remains the dominant language in epidemiology and biostatistics, creating a significant accessibility gap. This project will develop rjsf, an R package that provides user-friendly functions for running the Python `jsf` library directly within R workflows via reticulate. Key deliverables include a core simulation function, S7-based result objects, diagnostic and visualisation tools, a comprehensive test suite, and a detailed vignette, with the goal of CRAN submission. As a stretch goal, the project will explore incorporating additional intermediate stochastic simulation methods to further enhance flexibility and performance. The resulting package will enable researchers and scientists to seamlessly integrate hybrid stochastic-deterministic simulation into their existing R-based modelling workflows.
<p>Last year, <a href="https://summerofcode.withgoogle.com/projects/5809403503575040" target="_blank">as a project under the Google Summer of Code</a>, I created <a href="https://github.com/p5py/p5" target="_blank">p5</a> --- a native Python implementation of the Processing API. The goal then was to combine Python's minimal syntax and pedagogical roots with Processing's high-level graphics API. While the <a href="https://medium.com/processing-foundation/p5-a-python-implementation-of-the-processing-api-5f05c62db23b" target="_blank">project was successful</a> and we <a href="https://github.com/p5py/p5/releases/tag/v0.3.0a1" target="_blank">released the first alpha as a Python package</a>, p5 is still missing some core parts of the processing API and needs better cross-platform support.</p> <p>The goal of this project is to fix existing cross-platform issues by changing the internal rendering engine to <a href="http://vispy.org/" target="_blank">VisPy</a>; fixing <a href="https://github.com/p5py/p5/issues" target="_blank">existing open issues</a>; and extending the API by adding image support, improvements to the <code>Shape()</code> class, and minor utility methods.</p>
The proposal outlines a comprehensive plan to enhance the model's accuracy and efficiency, coupled with new user interface (UI) integrations. First, the optimization of machine learning and statistical models will focus on Exploratory Data Analysis (EDA), feature reduction, feature engineering, and employing better imputation techniques for handling missing data. This will streamline the process and improve model performance. Additionally, fine-tuning a rule-based system will involve adjusting and normalizing feature weights, alongside providing users with tailored recommendations based on our analysis. Another key objective is the integration of new datasets. Currently, each dataset requires different handling, and by incorporating a new dataset, we aim to deliver more refined insights. To address data imbalance, techniques such as minority class upsampling and additional data generation methods will be applied. This ensures the model can better handle unbalanced data distributions. Fraud detection is also a critical focus, with plans to identify suitable datasets and initiate the development of robust fraud detection capabilities. Lastly, improvements in federated learning will be made to ensure data privacy and efficiency, allowing the model to learn from decentralized data without compromising individual data security.
<p>Educational institutions, open-source projects and private organizations have the need to create and maintain educational content such as classes, assignments, handbooks and onboarding material. This material is often stored as binary files and shared manually by email or extractable drives. This means that it often gets lost when people leave their organization, changes go unnoticed and error fixes take long to apply and share with the students. This makes collaboration very difficult for both the educators and the students.</p> <p>That's why <em>Courseware as Code</em> brings the good practices of <strong>DevOps</strong> and <strong>CI/CD</strong> into education. Using <code>git</code> for version control and <code>markdown</code> for formatted text, institutions will now be able collaborate and keep track of their educational content. Plus by using <em>Gitlab</em> <code>CI/CD pipelines</code>, new and novel ways of interacting with this content opens up.</p> <p>But building this workflow from the ground up is tough, especially for non-technical users. With a good template, clear documentation/tutorials and already implemented <strong>CI/CD</strong> pipelines, we plan to make it easy for any user to spin-up their own <em>Courseware as Code</em> implementation.</p>
The ZOO-Project is an SDI manager which gives the users the capability of building their own map and web applications using Map server as the Open Geospatial Consortium (OGC) services engine. It is an open-source implementation of the OGC's Web Processing Service (WPS) standard. WPS Interface Standard provides rules for standardizing how inputs and outputs (requests and responses) for geospatial processing services (eg. polygon overlay). WPS also standardizes how a client can request the execution of a process, and how the output from the process is handled. The existing ZOO-Kernel supports C, C++, and JavaScript implementations. With this project, the objective is to have the ZOO-Kernel passing all the tests for WPS 1.0.0 and 2.0.0 OGC ETS. During the GSoC the main focus is on making the WPS 2.0.0 test suite working properly. The async tests are still wrong currently and should be fixed, this will be done during the GSoC. The next and final step will be to get the WPS 1.0.0 test suite working and comprehensive enough to get the Test Suite or the ZOO-Project fixed. Moving from OGC API - Processes - Part 1: Core to WPS 2.0.0. can also be added as second step for the project.
This project aims to build a context-first AI infrastructure to improve how contributors, maintainers, and repositories interact in open-source development. I will design and implement a system consisting of a Skill Bot (for answering contributor queries using repository-specific knowledge), a Skill Updater (to convert maintainer discussions into structured, reusable documentation), and a PR Dashboard (to help maintainers analyze and manage multiple pull requests efficiently). These components will be connected through a shared knowledge layer, ensuring that AI assistance is grounded in real repository context rather than generic responses, while maintaining a human-in-the-loop approach for reliability and control. In parallel, I will work on XOps, a CI/CD-native infrastructure for programmable value transfer in open-source workflows. This involves building a reusable execution engine that enables secure, policy-driven payouts triggered by repository events such as PR merges. The system will support multi-chain execution, configurable policies, and auditable workflows, reducing manual accounting overhead and enabling scalable, transparent contributor reward systems. Together, these systems aim to improve contribution quality, reduce maintainer workload, and introduce a standardized, automation-first approach to both collaboration and value distribution in open source.
The Splash projection mapping software allows for controlling multiple video projectors together to build a single projection. It is able to adapt to virtually any real geometry, as long as the surface is diffuse. Its rendering engine is built using the OpenGL API. It currently runs on platforms capable of running Linux and handling an OpenGL 4.5 context, and has been tested successfully on x86_64 (with NVIDIA, AMD and Intel graphic cards) and aarch64 (with NVIDIA graphic cards). However to be able to: a) optimize it further and b) support more platforms (for example Raspberry Pi), it would be interesting to support more graphics API. To do this it is envisioned to replace direct use of OpenGL with an intermediate, multi-API rendering library. Work Done: 1) Investigating available rendering libraries and APIs supported by the Raspberry Pi 4. 2) Modifying Splash's OpenGL 4.5 code to work with OpenGL ES and thus the Raspberry Pi 4. 3) Merging the old OpenGL and the new OpenGL ES codepaths to allow one binary to run both. 4). Pulling out graphics code such that application classes are only responsible for application logic, they just use the provided graphics API specific implementation. 5) Rudamentary performance profiling. 6) Bug fixes to application and graphics code.
<p>Harbor CLI needs two foundational improvements this term. First, migrate the TUI from Bubbletea v1 to v2 and refactor the fragmented list/table/selection models into a unified `loadingtablelist` abstraction with consistent loading, pagination, and error states across all commands. Second, replace static credentials with an OAuth 2.0 Device Authorization Grant (RFC 8628) and OIDC login flow so users and CI/CD pipelines can authenticate against Harbor through their identity provider without long-lived secrets.</p><p><br></p><p>Expected Outcome:</p><p><br></p><ul><li>Bubbletea v2 upgrade and unified `loadingtablelist` model adopted across all list-style commands</li><li>harbor login --sso` device-code flow plus a non-interactive CI/CD path with short-lived tokens</li><li>Encrypted local token storage with automatic refresh and provider-agnostic OIDC config</li><li>Tests for TUI state transitions and a mock OIDC provider covering device flow and refresh</li><li>Updated docs covering the new TUI patterns and OIDC setup for common providers</li></ul>
The COVID-19 pandemic has increased awareness of hygiene risks associated with touchscreens, with reports indicating that 80% of people find them unhygienic. Touchless gesture-based intuitive systems can reduce transmission in public settings and workplaces, and offer a seamless and convenient experience. Touchless technology is expected to remain popular in various industries, such as retail, healthcare, and hospitality. In this proposal, I suggest developing an interactive web app using the Mediapipe Hands JS Solution API and simple human gestures to provide perfect contactless interactions with interfaces. The app will showcase an augmented transaction panel previewed on the screen, enabling users to perform essential CRUD operations of items through custom simple-to-use gestures, without physical touch. Both custom defined & pre-trained gestures from Mediapipe’s tasks-vision API will be utilized to classify gestures and trigger events on the interface. The project targets most platforms, primarily big screens, and may run on selective mobile devices with a camera module for input feed. All data taken via input video feed is deleted after returning inference and is computed directly on the client side, making it GDPR compliant. Once completed, the Web App will be uploaded to Codepen and/or deployed on Vercel.
The project focuses on improving the functionality and usability of key components in the Eventyay platform, specifically the talks, tickets, and video modules and integrating them into a cohesive, unified system. The goal is to streamline event management by ensuring consistent user experience, reliable data handling, and simplified admin operations. Work includes fixing existing bugs in the ticketing and talk modules, refining attendee and speaker management flows, and aligning data models across tickets, sessions, and users. The contributor will optimize database interactions, implement input validation and error-handling mechanisms, and enhance admin interfaces to allow efficient management of attendees, speakers, sessions, and video resources from a single dashboard. Additionally, integration tests will be written to ensure system stability and prevent regressions during development. The contributor will also provide updated documentation reflecting the improved workflows and interfaces. These efforts aim to create a maintainable, scalable platform that supports a seamless experience for both event organizers and attendees. As part of the ongoing development process, the project also includes maintaining the documentation for the unified platform. This involves ensuring that the deployment of documentation works correctly, keeping it up to date with recent changes in the system architecture, and revising content as needed to reflect new features and workflows.
cBioPortal hosts 400+ cancer genomics studies whose clinical metadata is wildly heterogeneous — treatment fields alone have 24+ variants. The mentor's team built MetaHarmonizer, a 4-stage ML pipeline using sentence-transformer semantic matching and ontology resolution (NCIT, MONDO, UBERON), but it has no web interface, no audit trail, and no cBioPortal-ready export. This project wraps the pipeline in a production-ready curator dashboard: upload a raw metadata CSV, review and correct automated column mappings with confidence scores and top-5 alternatives, validate ontology term assignments, monitor quality KPIs, and export a cBioPortal-compatible TSV with a full JSON audit report. I have already built a working full-stack prototype (React + FastAPI) integrating the real SchemaMapEngine — processing 141 columns in 2.6 seconds — with 20+ REST endpoints, an on-demand LLM rematch endpoint, and an automated evaluation pipeline on the provided eval set. Deliverables: (1) production-grade backend with PostgreSQL persistence and role-based auth, (2) polished React dashboard with all needed curator pages, (3) formal ML benchmarking report, (4) CI/CD pipeline and (5) full documentation and cBioPortal deployment guide.
This project focuses on creating a comprehensive plugin marketplace UI for KubeStellar that enables users to easily discover, install, update, and delete plugins directly from the interface. The marketplace will provide a seamless user experience with intuitive navigation, detailed plugin information, and streamlined management workflows. Additionally, the project will implement advanced resource filtering capabilities throughout the KubeStellar UI, allowing users to efficiently search, sort, and filter various resources based on multiple criteria. Expected Outcome: 1) A fully functional plugin marketplace UI integrated into KubeStellar 2) Installation, deletion, and update workflows for plugins with visual feedback 3) Plugin categorization, ratings, and search functionality 4) Dependency management and compatibility checking for plugins 5) Advanced resource filtering system across the UI with support for multiple filter criteria 6) Filter persistence across user sessions 7) Responsive design that works across different device sizes 8) Performance optimizations to ensure smooth interaction even with many plugins/resources 9) Installation and Setup Guide integrated directly into KubeStellar UI with cluster readiness checker, guided installation wizard, and real-time error feedback and resolution flows
To improve user experience and remove the need for manual downloads and installations, this proposal aims to automate the Joplin desktop application's update process. The main objective is to make sure that, for users of Windows, Linux, and macOS, the app updates without any problems in the background, downloading and installing the updates automatically when the program restarts. Investigating real-time updates and creating plans for updating files that are already in use are secondary objectives. For application updates, the project will make use of Electron and electron-builder together with TypeScript and React. Using Electron's autoUpdater module to manage downloads and updates, setting up a background service for silent updates, constructing a non-intrusive user notification system, and ensuring flawless application restarts for updates are important tasks. There will be testing and documentation at every stage of the development process. The timeline spans 14 weeks, starting with initial setup and planning, followed by developing the background update service, implementing the automatic installer and notification system, integrating and testing the updates across all supported platforms, and addressing any unforeseen challenges. The final stages will focus on finalizing documentation, polishing the update mechanism for deployment, exploring live updates, and project wrap-up with mentor review and project submission to Joplin and GSOC.
The write operation in flash can only change bits in a specific way and the erase operation changes all the bits of a block to 1s. So to modify any bit the whole block needs to be copied to another memory, erased on the flash, and then copied again from the other memory with the change. Due to this “erase overhead” write operations may require copying a lot of data to modify a small amount. Most flash chips support multiple erase-block sizes and flashrom keeps a list of these sizes and ranges for all supported flash chips. Currently, flashrom tries these functions one by one and uses the same function until the operation is completed or an error occurs. Usually, the first function works correctly but this function erases the smallest erase-block so flashrom would have to use it multiple times to complete the erase operation on a large region, which could have been done more efficiently using functions using larger erase-blocks, thus resulting in a transaction overhead. If a large erase-block size to erase a small region is chosen it would result in a larger erase overhead. So the erase-block size should be picked according to the size of the region left to be erased. Also checking in advance to tell if the programmer supports the given erase function and then sorting the supported functions in order of the erase-block sizes can further help the function selection.
<p>FreeBSD has an audit subsystem which is responsible for monitoring a variety of security-relevant system events, such as user-logins, configuration changes, file system & network access. Although the audit framework is indispensable for security conscious organizations running FreeBSD servers, currently there is no tool to test its reliability and the intended behavior.</p> <p>The project aims to develop a regression test-suite, which will evaluate the audit framework for proper logging of most auditable system calls classified in TCP/IP & UDP sockets, File I/O, process control and device management, along with the semantics of audit trail's BSM/XML/ text output.</p> <p>BSM tokens can be obtained via synchronous I/O multiplexing on a special clonable device <code>/dev/auditpipe</code>, by configuring various preselection parameters for local mode auditing with the provided IOCTLs. Several <code>libbsm(3)</code> APIs and functions within the FreeBSD kernel can be used to analyze syscall tokens in the audit record. Finally, <code>kyua(7)</code>'s run-time engine will be used to automate regression testing of entire operating system at once, <code>audit(4)</code> included.</p>
Indexes are baskets of stocks with specific characteristic. They provide examples for diversification in investing to mitigate the volatility of portfolios. Therefore, many investors, including institutions such as fund managers, attempt to build their portfolios to track closely major indexes. However, the effort and the transaction cost for tracking the exact constituents of indexes is not negligible, especially for indexes of many stocks (S&P500). An approach to reduce the transaction cost in index tracking is the sparse replication strategy which tries to mimic the index return through a subset of its constituents. In this project, we implement this method through the point of view of mean-variance optimization, i.e., to minimize the tracking error as a quadratic utility function. We first replicate the study in (Shi, Shu, Tian 2020) "High-dimensional index tracking based on the adaptive elastic net". This means we will implement an algorithm for sparse index replication using optimization with adaptive elastic net regularization. By implementing a Python framework and exploring possible open-source optimizers, we aim to deliver to GeomScale community a new functionality of portfolio selection, which covers data parsing and preprocessing, backtesting with configurable parameters and automated fine-tuning of hyper-parameters. The next step is to test different ideas to improve this method and calibrate the hyper-parameters to fit the market condition.
<p>This project will make improvements on the project IBus-Braille that was successfully completed by a student under SMC. Hear IBus-Braille is an input method engine that work with IBus. It is a six key approach. letters f, d, s, j, k, l represent 1 2 3 4 5 6 of the braille dots respectively. By pressing f and s together will produce letter k and like. The project got a great acceptance from visually impaired people who uses languages with big character set.</p> <p>1 A core braille module that can be plugin to any web related requirement.<br> 2 Online IME Tool. 3 Braille input method Plugin for chromium 4 Braille input method Plugin for Firefox 5 Make 8-dot braille possible 6 Integrate IBus-Braille with Liblouis 7 Announce extra information through Screen Reader 8 Solve the dot 4 issue. 9 Add Facility to write direct Braille Unicode 10 Three to Six for disabled people with one hand 11 User Interface for Creating and Editing Liblouis Tables 12 Add support for more Indic Languages via liblouis</p>
Problem: Currently, resonance frequency-based HRV training is backed by robust scientific evidence, but it remains inaccessible to the masses due to the high costs of proprietary hardware and software tools. There is a need to bridge the gap between basic consumer wearables and professional open-source psychophysiological research. Solution: BreathState 2.0 solves this by evolving the existing mobile application into an active, multi-modal, clinical-grade biofeedback platform. This will be achieved by introducing cross-platform architecture (Mobile/Web/VR), integrating research-grade hardware (Vernier respiration belts), and porting Python-based professional analytics natively to the application. Deliverables: A multi-patient database architecture using Drift with CSV export capabilities. Cross-platform application builds supporting Android, iOS, and Web. Integration of Vernier GDX-RB respiration belts via BLE with Polar H10 synchronization. A full on-device NeuroKit2-to-Dart analytics engine (computing time-domain HRV, frequency-domain HRV, RSA, and Baevsky Stress Index). A real-time biofeedback dashboard featuring dual-axis waveforms and adaptive guided breathing. An immersive WebXR HRV visualization scene (breathing sphere) accessible via Meta Quest headsets.
<p>The Project includes :</p> <ul> <li>Designing and Implementing the Admin dashboard.</li> <li>Merging Admin and public templates following the WCAG norms.</li> <li>Adding breadcrumbs to navigate back and forth.</li> <li>Removing “Related Actions” & using Admin dashboard, Header menu for navigation to relevant entities, and bootstrap tags/badge at the bottom where it is necessary. </li> <li>Delete modal with entity’s name and denial for delete right if there are other linked entities. </li> <li>Implementing missing UI for nearly all Edit and Add pages via a proposed common unified design.</li> <li>About page.</li> </ul> <p>These improvements will allow administrators to publish and maintain the CDLI’s entities since options are presented hierarchically with keeping the administrators' workflows in mind. Also, the project aims to solve discrepancy problems by merging the templates and enhancing the UX. I have included some designs in my proposal for implementing the above tasks and will incorporate suggestions in design by its actual users at an early stage of GSoC. Once the Front end is done with the existing sass elements to unify UI with existing pages, then I will be checking for any Violations of WCAG using Axe Devtools and will reiterate the front end.</p>
Performance benchmarking distributed systems (such as DLTs) is a challenging task, comprising of multiple aspects, such as scalable workload generation, representative workload definitions, and comprehensive data analysis. Hyperledger Caliper is a general-purpose benchmarking tool with the goal of mitigating the aforementioned aspects of performance benchmarking: 1. It provides a flexible architecture to allow scalable workload generation. 2. It collects and reports results based on detailed client-observable execution traces. 3. It allows the implementation/plug-in of custom workload behaviors to meet the diverse criteria of a wide range of business scenarios. The flexible support of the aforementioned performance benchmarking aspects inherently makes the setup and configuration of a Caliper-based project cumbersome and error-prone: - The user must provide information about the system under test (SUT) in the form of a network configuration file. - The user must also specify the flow of the benchmark run in the form of a benchmark configuration file. - The runtime behavior of Caliper components can be influenced in detail through a configuration file. - As with most programming-related projects, a Caliper-based project should employ best practices to make its structure flexible and maintainable. The goal of the mentorship project is to deliver a Visual Studio Code extension that can help users perform the aforementioned tasks in an assisted and possibly automated manner.
Detection time and response time are the major critical accepts of all detection and response systems. Considering the vast amount of system logs collectors, network logs collectors and external IOC systems bring vast amounts of data to process within a short amount of time and uncover the anomalies. Although this process should not be flooded with false positive alerts which we identified as alert fatigue. Considering processing vast amounts of boundless stream data and doing a less false positive detection rate is a system engineering challenge that should stand side by side with cybersecurity expert knowledge. Building state of the art systems required several major components divisions. There are Data Sources (IDS, sys logs, net logs, firewall logs, files) , External intelligence (IOC, SIEM), Processing and detection unit(s) (batch or streaming processing, deployed ML/DL models) , Data storages (databases, flat files, object storages) and visualizations (index, dashboards). Recreating each of above divisions are equivalent to reinventing the wheel, therefore openXDR focuses intergaterabiltiy to work with available tools out there which leads users to use existing systems without hassle but with the power of detection and response time of openXDR. In general, it seamlessly integrates with any EDR, NDR, SIEM, or IDS through a modular integrated architecture.
<p>Enhancing the FOSSAsia Open Event Template to add new functionalities like</p> <ol> <li>Fixing app specific bugs (Random Force Close and similar errors), optimize app Performance, and Stabilization. </li> <li>Android Wear support by allowing the user to receive notification for the events he has bookmarked on his smartwatch and get the driving directions to the event. </li> <li>Enhancing the Map Activity by displaying all the sub events and allowing the user to navigate to the event from the app itself.The map will also show locations of nearby hotels and Airports. </li> <li>Adding features like ability to mark the attendance and rate the session. </li> <li>Enhancing the general UI/UX of the app by redesigning various parts of the app by following material guidelines and optimizing the UI for tablets. </li> <li>Adding an option to display recent G+/Twitter posts by the Speaker and the Organization, Session images and also the reviews given to an event by the attendees. </li> <li>Generate the apk without using Android Studio by adding an option in the app which asks for API URL, App name and icon and then generates a signed .apk. This can also be done using a web-app that uses the build-bot for generating the app.</li> </ol>
Haptics, as a multidisciplinary field, has applications within the Medical, Consumer and Entertainment domains, to name a few, and despite their widespread presence in our phones to provide the user with a vibrotactile feedback response (a subset of haptics), haptics have very minimally been explored by artists as a tool for authoring immersive arts. The proposed project aims to create low-cost affordable haptic devices with one or mutliple degrees of freedom and authoring tools for artists to implement into their artwork immersive haptics and interactive audio. In the near future, artists can then use the proposed toolkit to benefit from Haptic floors being deployed into immersive art spaces like the Dome at SAT. The authoring tools Feelix, a ”haptic authoring tool developed to support the design and integration of force feedback and shape change in user interfaces”, and ForceHost, a toolchain that uses the functional sound synthesis and processing programming language FAUST that compiles firmware for audio-haptic applications, will be extended for use with the DeformableHapticSurfaces, a work-in-progress and open-source toolkit for interactive multi-linear DoF deformable surfaces, to create and demo the proposed immersive haptic and audio interaction toolkit. Support for audio input will also be added into Feelix potentially with ForceHost as an input modality so that ForceHost developed tools can interface their audio with the Haptic floor.
Proposal Summary: The project aims to achieve two primary objectives: efficient and precise particle identification and the development of effective lossless data compression techniques for the CMS Experiment at the Large Hadron Collider (LHC). Efficient and Precise Particle Identification: Traditional particle identification methods involve complex algorithms analyzing data from the CMS detector. Recent advancements suggest using convolutional neural networks (CNNs) directly on raw detector images, known as the "end-to-end" approach, for streamlined processing and competitive identification efficiency. The project seeks to explore and enhance vision transformers (ViTs) for particle reconstruction, benchmarking against established CNN models. Development of Effective Lossless Data Compression Techniques: The CMS experiment generates massive amounts of data from particle collisions, posing challenges in processing and storage. Data compression techniques are crucial for extracting relevant information while reducing data volume for efficient processing and analysis. The project aims to develop innovative masked auto-encoders (MAEs) with vision-transformer-based encoders for efficient data compression, enhancing downstream tasks' performance. Overall, the project endeavors to contribute to advancing particle physics research by improving particle identification accuracy and optimizing data handling through innovative data compression techniques.