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>Apache Gora currently has support for JCache datastore which can be used with any JCache provider like Hazelcast. However JCache API does not expose details on data locality on how keys of data is distributed across the cluster. However Hazelcast IMap native api does expose these details and can be used to leverage data locality which is heavily useful to achieve performance gains in distributed processing. Hazelcast IMap datastore support is introduced to overcome these limitations in Apache Gora JCache datastore.</p>
<p>The aim is to build an open source Roku Channel Template that can be used by budding content creators to deploy on the Roku platform without too much hassle. Features like</p> <ol> <li>A good video playback experience (modern features like scrubbing with preview, etc)</li> <li>Visually pleasing and UX optimised home page</li> <li>Back-end support for recommendations</li> <li>Last played, custom settings</li> <li>"Activation” support - enabling paid subscriptions and custom feeds to channel</li> </ol> <p>will be the main focus.</p>
<p>Knative is a Kubernetes-based platform to deploy and manage serverless workloads. Eventing is a key feature for Serverless Computing. They deliver their information to a specified target to make a whole system interactive. The problem is that every kind of event cannot be treated as the same one in the Knative ecosystem because the shape of each event depends on its sources. Knative Eventing is designed to be consistent with the CloudEvents definition to keep interoperability. To make this happen, the Knative Eventing community already has several kinds of event type definitions such as GitHub, AWS S3, GCP Pub/Sub, etc.<br> This project aims to add two event types:</p> <ul> <li>an event source that is able to generate CloudEvents when a new container image is uploaded to Docker Hub.</li> <li>another event source that is able to generate CloudEvents on success/failure of Task/Pipeline and every step of a Pipeline created by Tekton CI/CD.</li> </ul> <p>Both components would help application developers focus on developing applications itself and make Serverless Computing more diverse.</p>
<p>This project focuses on implementing OpenCL support for Libavfilter, with other parts of the project (including scaling, color conversion and deinterlacer) being treated as optional improvements for FFmpeg.</p>
<p>Inkscape has basic support for CSS style sheet. Currently it can read and parse internal sheet. Aim of project is to extend its support by adding functionality and making it all-in-one solution for users.</p>
<p>Differential equation models are widely used in many scientific fields that include engineering, physics and biomedical sciences. The so-called “forward problem” that is the problem of solving differential equations for given parameter values in the differential equation models has been extensively studied by mathematicians, physicists, and engineers. However, the “inverse problem”, the problem of parameter estimation based on the measurements of output variables, has not been well explored using modern optimization and statistical methods. Parameter estimation aims to find the unknown parameters of the model which give the best fit to a set of experimental data. In this way, parameters which cannot be measured directly will be determined in order to ensure the best fit of the model with the experimental results. This will be done by globally minimizing an objective function which measures the quality of the fit. This inverse problem usually considers a cost function to be optimized (such as maximum likelihood). This problem has applications in systems biology, HIV-AIDS study.</p>
<p>The Proposal focuses on the improvement of App Inventor in the following aspects: Component Enhancements and Runtime Instantiation. Component Enhancement mainly targets the improvement in the features of components (ListView) so that the user can add more forms of information into the component. The Proposal focuses on the improvement of Listview so that after the final enhancements, the user can add Images and Text in the order they wish. Runtime Instantiation of Components enables the user to instantiate components by just using the blocks. This in turn gives the user, the ability to add components at runtime and instantiate them when necessary. This feature can boost the memory management in App inventor by assigning memory when needed. The proposal also marks the enhancement of file access. The app inventor currently doesn't support the access of External Storage in general. The proposal focuses on adding this feature so that many apps such as file managers can be made. Now, app inventor need not call an intent to access a file. Finally the proposal focuses on adding animation properties to the components so that the user is able to give a "Living" feel to their application.</p>
<p>After Meetup Everywhere was discontinued, Systers needed a Meetup app within the Systers Portal. This project was started last year but several features are yet to be added to it. This project aims at adding some extra features and completing the Meetup app.</p>
This project aims to improve the handling of transposed diffuse irradiance and optical loss modeling in the pvlib-python package. Currently, pvlib’s transposition models provide inconsistent output, with some providing only total sky diffuse radiation (e.g. isotropic), while others allow for outputting the isotropic, circumsolar, and horizon components. Due to this, the ModelChain workflow only allows users to define a single angle of incidence (AOI) model, and then applies the resulting incident angle modifier (IAM) to total irradiance, limiting physical accuracy. The proposed GSoC project will start by standardizing the outputs of diffuse transposition models already implemented in pvlib, introducing a consistent interface to return circumsolar, isotropic, and horizon components. Building on this, the project will extend ModelChain to support component-specific IAM calculations, enabling more accurate modeling of optical losses by distinguishing between direct and diffuse contributions. These enhancements will improve both the flexibility and accuracy of pvlib simulations while maintaining full backward compatibility. The project will include comprehensive testing and documentation to ensure reliability and ease of use.
Hundreds of BSM Lagrangians have been proposed in the literature, but translating them into validated FeynRules .fr model files is still a manual, time-consuming process. This project builds an agentic system inside the HEPTAPOD framework that automates this workflow. Given a BSM scenario description, the agent searches INSPIRE and arXiv, extracts Lagrangian terms into a typed schema, generates a syntactically correct .fr file using deterministic Jinja2 templates, and validates the output through HEPTAPOD’s FeynRulesToUFOTool and a downstream MadGraph smoke test. Every literature source, extraction decision, and validation outcome is recorded in an audit trail.
This project makes the ENTS (DirtViz) dashboard easier to grow with real field use. A lot of the UI is still wired together by hand in React, which gets painful when new sensors show up or when people want different views of the same data. The plan is to expose what can actually be plotted using live database information, mainly from the sensor table, so the app lists available sensor names, measurements, and units per cell instead of maintaining long static lists in the frontend. Power and TEROS data may still live on older storage paths for a while, so the catalog will need a clear, documented way to bridge those sources until everything lines up on one model. The headline user feature is a drag and drop dashboard: reorder panels, add or remove them, and keep layout in the URL so someone can share a view with a link. Saving layouts on the server can come later, once the client side layout behavior is solid and easy to reason about. For people comparing multiple cells, the work should also make loads feel snappier by avoiding strictly one after another requests where batching or parallel loads make sense, and by ignoring out of date responses when the selection or date range changes mid flight. After that foundation, there is room for equations for derived metrics with tight server side validation, plus CSV export of what is already on screen. Fancy per panel styling is a lower priority and might stay minimal. Overall this is steady refactoring of the existing Flask and React stack, not a from scratch rewrite, so current APIs stay stable unless an extension is clearly worth it.
B0Bot is currently a monolithic Flask application relying on synchronous, manual data ingestion and a single-pass LLM pipeline to retrieve cybersecurity articles. This current architecture creates significant bottlenecks: it requires manual scripts to update knowledge bases, scales poorly under heavy loads, lacks advanced reasoning capabilities, and delivers a generic "one-size-fits-all" news feed that ignores individual user preferences and behaviors.
As stated in the Mifos Forge, Users of Mifos have long had a need to have greater control and flexibility over creating loan and customer onboarding workflows that incorporate internal processes/steps as well as processes involving external systems. This project would center around creating an external integration with a workflow engine such as Flowable or jBPM using the Mifos X REST API as the glue. The auto-generated client library from the back-end enforces the contract between the workflow engine and the core banking system. The core banking and its REST API act as the glue. The result would be a UI-driven workflow engine to allow non-technical users to define these new custom workflows, where they could drag and drop the different steps of the process.
The goal of this project is to improve OpenCV’s imgcodecs module by reducing code duplication, enhancing performance, and improving format support. Deliverables: Modular and maintainable imgcodecs module. Faster, more efficient image I/O. Improved support for modern image formats and metadata. Robust and complete JPEG XL implementation with animation.
This project aims to complete the microservices infrastructure for FOSSology by continuing the work from GSoC 2021, with a goal to fully deploy FOSSology on Kubernetes. Over the past few years, multiple changes have been made to the codebase and the build system, requiring updates and integration strategies. Key deliverables include: - Reviewing and aligning the legacy GSoC Kubernetes setup with the current codebase - Completing pending work from pull request #2086 - Providing a fully working FOSSology Kubernetes deployment - Creating comprehensive documentation for Kubernetes setup - (Stretch Goals): Creating a single setup script, implementing health checks, and exposing usage/performance metrics This project ensures easier deployment, better scalability, and modern DevOps practices for FOSSology’s infrastructure.
The goal of this project is to develop an HR management module for the CARE system, streamlining employee management and automating leave and holiday tracking. The platform enables HR to efficiently manage employee records, process leave requests, securely handle document uploads, manage holidays, and allows employees to apply for leave and access their profiles and leave history.
D’s current JSON libraries (e.g., Phobos’s std.json) rely heavily on dynamic typing, which sacrifices type safety and performance—critical drawbacks for systems programming. For example, parsing JSON data into a generic JSONValue container forces developers to manually validate field types and existence at runtime, introducing overhead and error-prone code. This project addresses these limitations and enables type-safe JSON processing with constant memory by building higher-level functionalities on top of jsoniopipe, which exemplifies the language’s strengths in compile-time function evaluation(CTFE) and introspection.
The proposal outlines the development of an enhanced web application, IfcTester, for managing Building Information Modeling (BIM) project exchange requirements using IfcOpenShell. The current application lacks functionality and user experience improvements, which this project aims to address. It proposes a series of updates, including loading .ids files, implementing CRUD functionality for specifications and facets, upgrading the user interface, validating Ifc files, and potentially adding an XML editor. The proposal emphasizes on completing the half-built web app which allows viewing and minor editing of IDS files here: https://blenderbim.org/ifctester/ It focuses on finishing this web app, building features for more editing, drag and drop from a library of specifications, and adding and removing requirements.
In an era where cybersecurity threats evolve rapidly, the Open Web Application Security Project (OWASP) Bug Logging Tool (BLT) serves as a crucial line of defense, enabling the identification and management of vulnerabilities. My proposal aims to significantly enhance the OWASP BLT's effectiveness by integrating advanced AI capabilities, addressing the current limitations around bug reporting, triage, prediction, and user engagement. Deliverables: * A fully integrated AI chatbot for the OWASP BLT website. * An AI-enhanced bug report page with NLP support for detailed descriptions. * An automated bug triage system using machine learning. * A predictive analytics tool for future bug identification. * An NLP-enhanced bug search functionality. * A revamped user dashboard with updated design and features. * A user feedback loop mechanism with a voting system. * An improved Slack module with AI capabilities for bug management.
My proposal aims to make Sugarizer work well on different devices like web, mobile, and desktop in version v2. I'll analyze Sugarizer's current version and come up with a plan to adapt it for various platforms. Tasks include implementing remaining screens, creating a tutorial, porting Electron functionality, and testing on Android
<p>PyMC3 provides state-of-the-art tools to specify rich mathematical probabilistic models and algorithms to efficiently approximate the posterior distribution of such models conditioned on observed data. One such algorithm is the Sequential Monte Carlo (SMC) sampler which is capable of drawing samples from complex posterior distributions (e.g., multimodal distributions).</p> <p>In addition to traditional Bayesian inference, SMC can also be used to perform Approximate Bayesian Computation (ABC), which allows one to define models without a pure mathematical likelihood term, which is difficult to derive in many complex real world problems. To achieve this, SMC-ABC makes use of a “Simulator” function that is capable of returning simulated observed data given different unobserved parameters.</p> <p>This project seeks to extend the documentation, performance and flexibility of SMC and SMC-ABC sampling in PyMC3, to make it competitive with specialized libraries while remaining accessible to the large user-base of the PyMC3 library.</p>
<p>In the large majority of cases in DBpedia, it is not clear what kind of relationship exists between the entities. Instead of extracting the triples from semi-structured data only, we want to leverage information found in the entirety of a Wikipedia article, including page text. The goal of this project is to develop a framework for predicate resolution of wiki links among entities, specifically, we focus on the direct cause-effect relations between events. Our task then is to extract the cause-effect entity pairs (e.g., Peaceful_Revolution, German_reunification) from the wikipedia text. We combine the idea of using the seed data (e.g., the known cause-effect entity pairs) with training a classifier (e.g., a discriminative model--- LSTM ), so as to discover more cause-effect entity pairs from wikipedia text, which is known as distant supervised relation extraction. The procedures include the pattern matching, knowledge exploration, entity recognition, entity mapping, etc. Eventually, we aim to acquire more reliable causal relations between entities of DBpedia.</p>
<p>This project aims to build a program that end users can use as:</p> <ul> <li>Validating and reporting all possible parsing errors (in any) in the incoming markdown files.</li> <li>Auto generating Pretty markdowns for documentation purposes.</li> <li>Performing processing on top of parsed information like adding defaults, cross-references.</li> <li>Generating RDF like output (Turtle format).</li> </ul>
<p>OrcaSounds main objective is to educate and protect the orcas in the pacific. But in order to do that the website specifically the frontend needs to be optimized to keep users on the website and to make them willing to come back. Not only that but with the rise of users who use their phones to access a website;OrcaSound needs to be mobile accessible and also comply with the a11y requirements . In order to reach a wider audience and fulfill their business goals. My project would involve using the technologies of html,css , react , react-elements and javascript in order to improve the frontend.While working with the Ux team alongside this process. I want to create an attractive landing page that captures attention, organize the footer, create a blog post gallery and optimize them for SEO.</p>