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 enhance the usability, accessibility, and responsiveness of the RUXAILAB UI while modernizing its codebase by migrating from Vue 2 to Vue 3. The solution involves redesigning the entire user interface, focusing on improved navigation flows, responsive layouts, and WCAG accessibility compliance. These designs will then be implemented using Vue 3 alongside Vuetify 3 as a component framework to accelerate development. Also, the project will systematically migrate the codebase from Vue 2 to Vue 3 using a phased approach with @vue/compat, methodically updating all major packages including Vue Router, Vuetify, Vuex, and Vue-i18n. The final deliverables include a fully migrated Vue 3 codebase leveraging the Composition API for better code organization, a completely redesigned user interface with intuitive navigation, responsive layouts, WCAG-compliant accessibility features, and seamless dark mode functionality.
The LibreOffice BASIC IDE currently offers limited code assistance, hindering developer productivity with unreliable completion, no object browser, and no inline help (parameter/quick info). This project will implement a modern, comprehensive code assistance system. This involves creating [1] a robust backend analysis engine to parse BASIC code (editor/libraries) and introspect UNO objects for detailed symbol information (types, scopes, signatures), and [2] an efficient knowledge cache. These components will power [3] user-facing tools including: an integrated Object Browser for API exploration, significantly improved context-aware code completion (Ctrl+Space and enhanced '.'), and helpful Quick Info/Parameter Info tooltips. The final deliverable will be these features fully integrated and enabled by default, delivering a significantly more productive and intuitive BASIC development experience in LibreOffice.
This ongoing “Sailing Downstream” project strives to transform the salient content from within the RISC-V Sail specification into a more accessible format, JSON, that downstream projects can easily and automatically transform into the content necessary to their project which is currently produced by manual effort. Project efforts and components span: - Adding to the RISC-V Sail specification information necessary for the various downstream projects. - Improving the RISC-V Sail specification so that the salient information can be easily identified and extracted. - Enhancing an existing Sail “JSON backend” to extract salient information completely and accurately and produce that information in a usable JSON format. As the end goal is to enable automatic adoption of changes, enhancements, and new content of the RISC-V ISA into downstream projects, efforts can be made to provide example implementations of such transformations to inform engagement with select downstream projects for adopting new automated processes.
WildBerryEye leverages edge computing (Raspberry Pi) and object detection (YOLO) to monitor pollinators like bees and hummingbirds. My project focused on developing a clean, intuitive, and responsive web-based interface to support real-time pollinator detection, data visualization, and system configuration. The final result empowers researchers and contributors to engage with environmental data in an accessible and meaningful way. Specific tasks: - Frontend Development: Continue development to enhance the user interface using React and CSS, ensuring a responsive and user-friendly design. - Backend Development: Expand functionality using Flask, focusing on efficient API endpoints and seamless interaction with the frontend. - Real-Time Communication: Implement and refine real-time updates between the frontend and backend to enhance system responsiveness. - Usability & Design Optimization: Research and propose improvements to the system’s usability, design, and overall user experience.
The Checkpoint-Restore Operator manages checkpoint retention well but has no way to create checkpoints automatically. This project adds a new CheckpointSchedule CRD and controller that triggers checkpoint creation through four mechanisms: cron-based time schedules, CPU/memory resource thresholds, Kubernetes cluster events (node drain, pod eviction, preemption), and pod annotations for application-level signaling. All triggers call the existing Kubelet Checkpoint API via the Kubernetes API server proxy. Deliverables include the CheckpointSchedule CRD, a CheckpointCreator that calls the Kubelet API, four independent trigger subsystems, a TriggerManager to coordinate them, a full controller-runtime reconciler, RBAC updates, unit and BATS integration tests, and sample configuration. Together with the existing retention policies, this turns the operator into a complete checkpoint lifecycle manager — admins declare both when checkpoints are created and how long they are kept, with no custom scripting required.
<p>In order to extent the available characteristic offered by the istSOS server, I propose the use of an open source Javascript library for the implementation of VistSOS: the istSOS Data Visualization Framework. The proposed solution shall allow users of the istSOS ecosystem to configure, customize and include a wide set of chart, bar, grid and map visualization types in their websites. The framework will offer complete support for the connection of the visualization widgets with multiple data-exchange formats like CSV, TSV and JSON. Considering the real-time nature of the data sources the framework will support the generation of real-time visualization widgets specially crafted to improve the readiness to display data of this kind. The framework shall be implemented with robustness, reliability and customization as its core development principles. Recommended practices for software development like Version Control Systems use and continous testing will be followed.</p>
<p>This project aims to provide an R interface to Ideogram.js, integrate it with bioconductor infrastructures and possibly provide an interactive whole-genome exploring tool combining with other visualization components.</p> <p>Ideogram.js is a JavaScript library for chromosome visualization. It can be used for interactive visualization of chromosomes of different species, showing cytobands, showing annotations along the chromosomes, showing position mapping (e.g. homology) between different chromosomes, etc.</p> <p>There is already a simple R interface to the Ideogram.js library at freestatman/ideogRam as a proof of concept. The main purpose of this project is to improve this interface and integrate it with bioconductor infrastructures (e.g. to support S4 classes like GRanges as annotation data).</p> <p>Moreover, the most important feature that the package may provide for static visualization is the ability to combine with other visualization packages to interactively exploring the whole genome.</p>
<p>This proposal details how I will be dealing with the project named <code>Productionizing bddashboard</code> . The main aim of my project is to <strong>create a testing framework</strong> of the Shiny application from <code>bdverse</code> that aids in visualizing biodiversity data, including but not limited to unit testing the UI and server, load testing, random testing, stress testing etc. For developing this framework I'll be working extensively with the <code>testthat</code>, <code>shinytest</code>, <code>pupeteer</code>, <code>crrry</code>, <code>gremlins</code> and <code>shinyloadtest</code> packages.Apart from testing, I'll also be responsible for <strong>finding the CI/CD pipeline</strong> solutions for our project after comparing and reviewing the available options out there. My final task would be to get our project (Shiny project) accepted into CRAN and eventually get a new and updated version of <code>bdverse</code> pushed out for public use.</p>
Problem: The current RocketMQ Dashboard suffers from outdated UI design, slow API responses, security vulnerabilities (e.g., plaintext passwords), and incomplete documentation. These issues hinder usability, performance, and adoption. Solution: I propose a comprehensive refactor to modernize the dashboard by: Frontend: Replacing AngularJS/Bootstrap with modular components (e.g., ECharts for dynamic charts) and fixing misaligned UI elements. Backend: Optimizing APIs via caching and async processing to reduce latency (e.g., topic queries from 30s to <1s). Security: Implementing Spring Security with BCrypt encryption, RBAC, and audit logs. Infrastructure: Updating Docker images and improving documentation with quick-start guides. Deliverables: Modernized UI with responsive design and interactive charts. Optimized APIs with reduced response times. Secure authentication (RBAC + audit logging). Updated Docker deployment and comprehensive documentation.
The AsyncAPI project, focused on enhancing event-driven architectures, requires stable and reliable website components, particularly the scripts used in its website. This proposal seeks to strengthen script stability through a robust unit testing and CI/CD pipeline, ensuring contributions are well-tested to reduce regressions and improve website reliability. The approach involves researching suitable JavaScript testing frameworks, followed by integrating the chosen solution into the AsyncAPI codebase with comprehensive test cases for all scripts. The project employs Jest for unit testing, utilizing its parallel execution and code coverage capabilities, and organizes test files in a structured tests folder for consistency. A CI/CD workflow using GitHub Actions will trigger tests on code changes, helping to catch regressions early. Key deliverables include fully developed unit tests for the specified folder, integration of the testing framework and CI/CD pipeline.
<p>The PEcAn (Predictive Ecosystem Analyser) project is an open source system for ecosystem modelling and forecasting. With huge amount of climatic and environmental data available, the PEcAn software tries to utilize it for providing users vital statistics and interactive visualizations for modeling and forecasting. Integration with Google Maps interface provides helpful information to the user and it becomes very handy to select a site. PEcAn already has an interface with Shiny (R) for visualizations and the main aim of this project would be to work upon the existing Shiny apps as well as developing other powerful visualizations to convey the right amount of information as well as clear understanding to the users on the platform. For me, an important component of this project is to understand what kind of visualization would give an intuitive sense to any user given the data and to present them in a very clear and effective manner. Otherwise, the user could not draw inferences that we want to show them. This is the most interesting thing I like and it is my motivation to work on this project to master this art of visualization.</p>
My project goal was to add DICOM file support to caMicroscope, a Whole Slide Image viewer. The viewer backend (OpenSlide) didn't support DICOM, so we needed a second backend. Surprisingly, before the coding period started, OpenSlide did get DICOM file support and this gave me the opportunity to tackle the bigger challenge of integrating BioFormats into caMicroscope. This would be extraordinary, as BioFormats is a Java library with no C wrappers available online. I started by refactoring caMicroscope code to use a single base Dockerfile which compiled OpenSlide. Then I made a Java wrapper and prepared its corresponding C caller. For this, I had chosen GraalVM C API, but once I found out about its level of performance and its requirement to achieve high code covergage first (for metadata collection), I rewrote it for Java JNI. To make it available to the two derivatives of our base image, I refactored this to be a separate project. We also needed to make this available to our Python image metadata server, so I wrote a wrapper in Python using cffi.
Teaclave currently lacks a mechanism for data providers to enforce policies on the data they upload, and also it cannot verify that the behavior of the uploaded function conforms to the expected rules. These two gaps leave the system vulnerable to exploitation by malicious actors. To solve the problem, verification should be exerted on the uploaded function so that its behavior that it strictly conforms to a prescribed policy. The standard formal verifier can be adopted (e.g., Prusti, Creusot) to formally verify the function's behavior. A set of deliverables as follows can be anticipated in the coming future. Milestones: Basic policies (e.g., addition, subtraction) of the data can be verified by Teaclave; Complex policies can be verified. Components: Verifier for the function code; Policy language adapters (adapt policy language to verifier); Policy language parser; Function source code converter (append policies to the functions). Documentation: The internal working mechanism of the verification; How to write policies for the data.
<p>The website would have a dynamic page for each port which would display</p> <ul> <li><p><strong>Port Information</strong>: Name, Description, Version, Maintainers (github and email), Dependencies, Long Description, Homepage, Installed Files etc.</p> </li> <li><p><strong>Installations Statistics</strong>: Number of installations, Installations vs Month, Installations vs Version for last 12 months, number of updates vs month.</p> </li> <li><strong>Build Data</strong>: Table of all builds(latest), Status of last build for all OS Versions, Build Reproducibility.</li> </ul> <p>The API would make the collection of data more powerful by extending its use beyond the web-app.</p> <p>Although these will be the main components of the app, yet there will be many other accessibility features like maintainer’s page, customisable table of all builds etc.</p>
<p>A large goal of both the SBOL and synthetic biology communities is to develop a useful and comprehensive workflow from experiment to publication. Many SBOL-compliant tools already exist which perform distinct and useful functions ranging from component design, modeling, composition, simulation, figure creation, storage, sharing, and publication. In 2016, ACS Synthetic Biology recommended that all authors submit genetic designs using SBOL. An example workflow for doing so was published in 2016 (Hillson), and each of the parts of the workflow can be fulfilled by extant tools, but the integrations between tools can be made more robust. For example, the SynBioHub service allows for storage and sharing of SBOL parts, VisBOL allows for creation of SBOL visual images from SBOL files, and iBioSim and SBOL Designer allow for creation and composition of SBOL parts. SBOL Designer and iBioSim allow for upload of parts to an instance of SynBioHub, but there are many opportunities to improve this workflow with authentication, security, and sharing capabilities.</p>
<p>CERNBox is a cloud storage synchronisation service for CERN users: it allows syncing and sharing files on all major mobile and desktop platforms (Linux, Windows, MacOSX, Android, iOS) aiming to provide offline availability to any data stored in the CERN EOS infrastructure. CERNBox is based on ownCloud, a cloud sync and share platform written in PHP following a Model-View-Controller architecture software pattern.</p> <p>This project aims to provide a prototype of a new web UI for CERNBox that will provide an immersive user experience. To achieve this, a milestone of this project is to provide offline manipulation of the data from the browser. The use case is that when a user goes offline in his browser, he could continue to work on the document and perform actions like renaming and browsing his files. Once network is re-established, the application will reconcile the changes in the browser cache with the server, offering a non-disruptive work environment for the end-user.</p>
rTorrent is a stable, high-performance and low resource consumption BitTorrent client. This GSoC project will replace the antique SCGI protocol with Websocket, which will allows real-time events, less serialization/transfer overheads, better security, etc. We will introduce uWebsockets into the rTorrent to make client can communicate with rTorrent via websocket protocol, client can subscribe some specific topics, once the event occurs, server will push the notification to client automatically; implement some callback function and bind to the events we care about, execute them when event occurs. For secuity and convenient reason, we will implement websockets over unix domain socket, which could be access restricted as a file, much efficient and safe than a TCP:IP port. There isn't a modern c++ websockets library that supports unix domain socket, we will add this important feature into uWebsockets, possibly by PR to office repo (if it will be accept) or personal fork.
The project aims to improve the visualisation tools for metagenomics data in the MGnify platform by identifying and using new technologies that can be used both on the website and in Jupyter notebooks. The goal is to enable researchers to easily compare taxonomic information from multiple studies for better interpretation and analysis of metagenomics data. Additionally, the project aims to streamline the process of user community contribution to MGnify Notebooks for improved accessibility and user experience. The project will be approached in three phases: research and evaluation of visualisation technologies, development of a Jupyter/observable notebook for comparing and visualising data from two studies, and integration of a JupyterLab extension to streamline the contribution process. The deliverables include a report on suitable visualisation technologies, a fully-functional Jupyter/Observable Notebook, and an integrated extension for user contributions. As a stretch goal, a component for the MGnify website that allows users to select multiple studies and launch a notebook for cross-study analyses will be developed.
<p>Schematics are a great way to understand electronic circuits, and specially when we are using high level descriptions, it becomes essential that we are able to portray what we have in mind. Automatic schematic generation will allow us to generate publication quality schematics directly from HDLs (verilog in this case).</p> <p>The objective is to take input a circuit desciption in json format (generated by yosys tools), and automagically create a schematic for it. The algorithm will run on the client side, so there will be no need to send data to server (thus no privacy concerns). Moreover interactivity with the generated circuit will allow it to be used as a great tool for learning circuits and HDL.</p> <p>I plan to implement the core algorithm as library which can be easily extended to work with a variety of cases like</p> <ul> <li>Combining it with simulators to perform interactive simulations</li> <li>Using it to create non-electronic schematics</li> </ul>
Kubernetes has recently moved its forensic container checkpointing feature into beta. This feature allows checkpointing containers within Kubernetes pods, and, with some additional steps, restoring them on a different node. This approach preserves active TCP connections of the container. However, workloads (e.g., web servers) with established TCP connections to the migrated container cannot make use of this feature, as the container IP changes after migrating to another node. This project implements a P4-based load balancer on the data plane that dynamically reroutes packets to the correct IP address after container migration. The goal is to make the migration invisible to the client, causing only a period of service unavailability, after which communication can be resumed without re-establishing the TCP connection. Deliverables of this project include a P4-based load balancer, control plane code for P4 runtime interaction, a minimal CNI plugin for Kubernetes integration, and performance benchmarks to demonstrate the system's effectiveness.
The Mission Support System (MSS) facilitates scientific flight planning in atmospheric science, but its existing mssautoplot CLI tool lacks user-friendliness, hindering widespread adoption. To overcome this, we propose developing a Graphical User Interface (GUI) for mssautoplot using PyQt5. This GUI will empower researchers by offering an intuitive platform to configure parameters like layers, resolution, and time steps visually, eliminating the need for complex command-line inputs. Additionally, it will support multilayering from multiple Web Map Service (WMS) servers, enhancing data visualization capabilities. Integration with the MSS UI will ensure seamless interaction, further streamlining workflow processes. Comprehensive documentation and testing using pytest will ensure reliability and usability. Overall, the GUI for mssautoplot aims to democratize access to advanced plotting tools, empowering researchers to efficiently analyze atmospheric data within the MSS ecosystem.
<p>Open Event Orga Application is a client-side application for Open Event API designed for Event Organizers. The app provides functionality to Create Events, Create Tickets, Check In Attendee, Scan QR Code, Sales Overview, User Authentication etc.</p> <p>To further increase app's performance, user experience and expand its horizon, the following enhancements are proposed -</p> <p>● Migration to MVVM Architecture.</p> <p>● Background Job Scheduling for Offline Support.</p> <p>● Implementing various core modules comprising Orders, Sessions, Call for Speakers etc</p> <p>● Analytics and check-in/check-out functionalities.</p> <p>This will be accompanied by adding the required REST API and resolving bugs in Open Event Server project.</p> <p>Best available and tested technologies will be used to implement the above enhancements and test them thoroughly to achieve high-performance.</p>
Today, most users adopt Blockchain in order to collaborate with each other, however, it is difficult to manage a large blockchain network because of multiple organizations and nodes. Hyperledger Cello is aiming to resolve the following challenges, 1) Facilitate creation of blockchain network, can help user without blockchain background to setup their network nodes quickly. 2) Cross organization communication, can connect blockchain networks among multiple organizations. This project targets to design and implement a practical operational system equipping with decentralized functionalities to solve above challenges, based on Hyperledger Cello code base. Learning Objectives 1) Work closely with community experts and developers to learn the open-source culture and skills; 2) Learn the advanced knowledge inside the blockchain and distributed ledgers; 3) Practice hand-on experience with web application design and implement. Expected Outcome Help design and implement the blockchain operation dashboard and api server.
SwitchMap-NG currently faces scalability challenges in distributed networks, including data loss due to unreliable connections and slow polling when monitoring thousands of devices. My proposed solution introduces a layered architecture: regional hubs will collect device data from edge pollers, buffer it locally during outages, and forward it to a central server. To improve performance, I’ll implement asynchronous polling, decouple frequent performance updates (e.g., every 5 minutes) from less frequent status checks (e.g., hourly), and introduce historical data tracking along with new device metrics like CPU, memory, and power usage. The final deliverables will include a fully containerized deployment alongside local buffering, complete testing, automated documentation. This will significantly improve the reliability, speed, and scalability of SwitchMap-NG, making it better suited for large-scale network monitoring and management.