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.
<p>The name Scala comes from the word scalable, and true to that name, the Scala language is used to power busy websites and analyze huge data sets. Scala is one of the leading languages in implementation of big data systems. It is widely used in streaming data. Similarly, Python has become the language of choice for data scientists with its many high-quality scientific libraries. ScalaPy is that bridge which gives an opportunity to use Python libraries in Scala. Last year a new version of Scala was introduced. At the moment it is not released but Scala 3 brings many new features and changes. The aim of this project is to discover those new features and implement support for ScalaPy in Scala 3. ScalaPy will possibly help Scala 3 to become more popular among scientists and maybe this will be the core moment in combining data processing and data analysis worlds in Scala 3.</p>
<h3>Abstract</h3> <p>Tracing support with annotation-based traces is a promising approach to allow developers to get a view into the performance behavior of Ceph components. Past efforts have used the blkin library to instrument some parts of Ceph's codebase, and some plugins have been created to allow these traces to be visualized in Twitter's Zipkin platform.</p> <p>This project would add value to the Ceph community by extending the tracing capabilities and integrating the Zipkin visualizations in Ceph's continuous integration processes, allowing developers to quickly get performance information after changes or after testing particular scenarios.</p> <p>The objectives would be achieved by performing the following tasks:</p> <ol> <li>Have a well documented and modern implementation of an infrastructure that can generate and visualize tracepoints in Zipkin from Ceph. </li> <li>Integrate the infrastructure into CBT and Teuthology as well as anywhere else the Ceph Community is interested in having it.</li> </ol>
Currently, Talawa has three major software components which are talawa, talawa-api and talawa-admin. Among these, talawa-admin is a web-based portal and talawa is a mobile application whereas talawa-api provides access to user data and features. We also have talawa-docs, which is a website that contains most of the documentation and can be found at “https://palisadoesfoundation.github.io/talawa-docs/”. Currently, the documentation website is being powered by numerous Markdown files which are being rendered into a static website with the help of Docusaurus. The challenge is to find and implement a way to generate documentation (in the form of static HTML files) from comments within the files, which can then be hosted on the site used for documentation. This will enable the documentation to grow organically with the codebase. We target to automate the creation of our documentation using the content of our code repositories on our existing documentation website. This will give Palisadoes the flexibility to maintain its Markdown documentation and its website more efficiently.
GUI: In this part, we aim to build a new GUI for HNN, using the HNN core functions and open source practices, in the form of an ipywidget. Mimicking the current functionality and tutorials in the existing GUI, it will allow users to interactively set the experiment settings and get visualization results presented on the fly. Unlike the traditional HNN GUI, all these functionalities could be used within JupyterLab, making it convenient and friendly to those who prefer to use HNN on servers. This part will also benefit users that need to frequently adjust simulation settings and get real-time results but have little programming experience. CSD: Currently HNN-core provides APIs to record local field potentials from simulations while an API to turn these signals into source density signals is missing. In this part we will implement a series of mainstream algorithms to calculate the CSD and a visualization API that calls them in the backend to visualize the CSD.
Multigrid methods shape the method of choice when a self containing family of triangulations of a FEM discretization is at hand to achieve an optimal order solver. Optimal order meaning linear complexity in the number of DOFs, which is the same for the assembly of the associated linear system of equations, making this a completely astonishing and non-trivial result of the theory of multigrid methods. But also in applications this outperforms classical, algebraic based, solver routines when it comes to large scale simulations. Although, the flexibility of modern AMG implementations to not require any such structure of meshes, multirgrid methods remain of great interest not only in academia. So an implementation in the dolfinx framework should allow for versatile extensions and applications. To achieve this, multiple components of data structure associated with mesh, geoemtry and topology require close analysis and a fundamentally new feature, the necessary prolongation and restriction operators, need to be implemented. This process is split into multiple isolated, but chronologically dependent phases.
<p>PostgreSQL is a famous database management system, widely used by DBAs and with an open source license. There is a large community dedicated to developing and bug-fixing, intensely working through mailing lists.</p> <p>The Performance Farm is an useful way to test Postgres' functionalities while adjustments are being made, to analyse the efficacy of every change on different operating systems. To further support the community effort, this project has been extended building a database and a website on top of it, to make results easier to browse and display.</p> <p>To make this possible, a web application relying on Python has been built to interface server and client. The code provides a benchmark to collect test results, plus an API where they get stored and accessed from the website. The Performance Farm helps developers to understand the performance of different versions of the system, and users to check the functioning of their database, being helpful in terms of usability and accessibility of collected data.</p>
<p>SUSI is an Artificial Intelligence system which apart from having its own Android, iOS, web and IoT clients also offers an extended support for different bot platforms to get integrated. My aim is</p> <ol> <li>To contribute to the server (<a href="https://github.com/fossasia/susi_server" target="_blank">https://github.com/fossasia/susi_server</a>) side implementation of this project by implementing new servlets required and enhancing the existing ones.</li> <li>Implementing a client where users can manage all SUSI accounts (<a href="https://github.com/fossasia/accounts.susi.ai" target="_blank">https://github.com/fossasia/accounts.susi.ai</a>) related issues. Signup, login, change password, reset password, verify account, manage settings across different clients etc. </li> <li>Admin section for SUSI.AI</li> </ol>
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 Arctic sea is a framework for developing OGC services, clients and middleware sharing concepts for encoding and decoding of different formats and encodings, workflows and configuration. It is the backbone for OGC services, clients and middleware. One of the important components of the Arctic Sea framework is Faroe. Faroe is a configuration API currently featuring a JSON and a SQLite backend. It enables the injection and automatic configuration of settings of various types in classes, including a Spring BeanPostprocessor. It allows us to set properties for OGC services. The problem statement thus asks to create a web frontend to create, read, update and delete (CRUD) the JSON settings with a REST API on top of faroe API. I will try to develop a user-friendly UI for the same and make sure CRUD operations are carried out properly through UI, making it extensible and customizable. Also I’ll try to surely implement the optional extension mentioned in the problem statement.
Community-driven Drupal sites currently rely on reactive, manual moderation for spam and toxic content, which is exhausting and difficult to scale. This project introduces a proactive, real-time defense system by building a fully integrated AI Content Moderation module. The solution utilizes a decoupled ContentModerator service that intercepts form submissions on the client side using debounced JavaScript, providing users with instant, WCAG-compliant inline warnings before toxic data ever hits the database. On the backend, it employs a highly performant hybrid approach, checking local administrative keyword lists before securely querying external NLP models (such as Hugging Face) via Drupal's core HTTP client. Deliverables include a production-ready module featuring an intuitive Admin UI for AI provider and threshold configuration, bulletproof server-side validation fallbacks, and comprehensive site builder documentation.
<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>
The KServe Models Web App is a crucial front-end interface for managing ML models deployed through KServe, a core component of Kubeflow. However, the application has become outdated, with deprecated dependencies and technical debt. This project aims to modernize and enhance the app by upgrading its tech stack, resolving open issues, and implementing a robust CI/CD pipeline with GitHub Actions. Key improvements include regression testing with Cypress, model editing capabilities, and synchronization with KServe 0.14+. Additionally, the project explores migrating the app from kserve/kserve-models-web to kubeflow/kserve-model-ui for better integration. The deliverables include a stabilized, modernized codebase, improved user experience for ML engineers, and streamlined contributor documentation. This effort will reduce operational overhead, enhance usability, and support Kubeflow’s mission of making ML workflows simpler and more scalable.
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.
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.
This proposal aims to enhance the visualization system of Mesa, an agent-based modeling (ABM) framework in python, to make it more modular, user-friendly, and feature-rich. The project addresses two key issues in the current visualization system: clumped API design and difficulties in model sharing. The implementation plan is divided into two phases: 1) Phase 1 focuses on creating a more modular API for space drawing by developing AgentPortrayalStyle and PropertyLayerStyle components, separating agent drawing from grid drawing with a CoordinateMapper, and creating a unified SpaceRenderer class. 2) Phase 2 implements model sharing through links, upgrades the Altair visualization backend to match matplotlib capabilities and improves documentation. Deliverables include: a separate and intuitive visualization API, easy model sharing functionality, an improved Altair backend and comprehensive documentation. This upgrade will significantly improve the user experience for Mesa users.
<p>Open Posix benchmark suite (<a href="http://posixtest.sourceforge.net/" target="_blank">http://posixtest.sourceforge.net/</a>) is designed to test whether an operating system respects the standard of POSIX. It is an open source test suite with the goal of performing conformance, functional, stress, and performance testing of the functions described in the IEEE Std 1003.1-2001 System Interfaces specification. The test suite will be developed independent of particular implementations of the POSIX APIs. It is configurable to test any implementation by specifying include and library information. The purpose of this benchmark suite is the creation of tests that depend purely on POSIX APIs, thus leaving open the possibility of OS independence, although initial development is on Linux. NetBSD is one of these major stream operating systems. Thus, it would be cool if we can use this suite to test NetBSD, which also drives the evolvement of operating systems.</p>
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.
<p>Iridium is a satellite communication system, previously mainly used for satellite phone calls and remote control and tracking of scientific instruments or trucks. However, recently more and more lightweight modules were introduced to the market which allow for new applications in vehicles such as high-altitude balloons and miniaturised spacecraft.</p> <p>The goal is to improve the existing ground station coded for the MIRKA2-RX experiment and improving it to become a flexible and versatile platform that can be easily modified and fitted to the needs of an experiment. The current ground station already features the basic components needed for receiving data via the Iridium satellite but requires a lot of coding and understating of the code to use it in different scenarios. The suggested proposal would heavily focus on making the application useable to a wider audience by featuring config files for the GUI and the data protocols used as well as adding support for 3D visualisation of GPS data.</p>
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.
<p>Traditional rendering is based on the idea that light can be decomposed into three basic components: red, green and blue (RGB). In some areas this is a vast oversimplification of the physical reality; light exists on a continuous spectrum of wavelengths. Spectral rendering achieves better accuracy by taking that into account. The major drawback is that it cannot use widely available color data for surfaces such as photographs. The process of gathering usable spectral data is significantly more time- and resource-intensive.</p> <p>Spectral upsampling is the process of extrapolating spectral information from RGB color data. This is possible because, in practice, spectral reflectivities, which describe how a surface interacts with incident light on a wavelength-by-wavelength basis, tend to fit relatively simple patterns. The goal would be to add support for several newly published algorithms to Colour, a color science library for Python. With the rising popularity of spectral rendering, the library would greatly benefit from the work.</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>
My proposal tackles the critical challenge of making raw medical data safe to share on Bio-Block without destroying its usefulness for machine learning. To achieve this, I'm building a "zero touch" FastAPI ingestion pipeline that acts as an automated watchdog, seamlessly using Microsoft Presidio to scrub sensitive personal health information from text, DICOM files, and medical images before they ever reach storage. Because we still need this data to be valuable for AI research, I'm implementing flexible "Privacy Profiles" that allow the system to intelligently preserve general demographics rather than just blindly deleting every identifier. Finally, since highly anonymized data is very difficult to search through, I'm building a hybrid search engine that combines exact keyword matching (BM25) with context aware semantic search (ChromaDB), ensuring researchers can easily discover the exact datasets they need without running into redundant search results.
<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>
This project aims to scale QuTiP's HEOM solver beyond single-node limitations by integrating PETSc to distribute ODE integration across multiple MPI ranks on HPC clusters. HEOM can exactly simulate open quantum system dynamics, but propagating a full hierarchy of coupled auxiliary density matrices makes it brutally expensive — the current scipy-based single-process implementation hits a hard wall at hierarchy depth > 6 or larger Hilbert spaces. The core design challenge is partitioning the coupled density matrices across ranks without making inter-process communication the new bottleneck. The work covers profiling the existing solver, building the distributed path on PETSc's TS interface, correctness validation against the original solver, and scaling benchmarks across node counts and hierarchy depths — all without touching the existing solver or changing anything the user sees.