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.
<h3>Goal</h3> <p>This project aims at fully implementing end-to-end encryption in matrix-python-sdk, following the official implementation guide and making use of the Python bindings already present in libolm.</p> <h4>Rationale</h4> <p>Currently, even though end-to-end encryption has landed in Matrix for over a year, only the three SDK upon which is built Riot on different platforms (JS, Android and iOS) ship with encryption. On desktop, this situation prevents writing clients, bots and bridges that can interact with encrypted rooms in any other language than javascript. Tackling this issue would benefit the matrix ecosystem by seeing more featureful projects emerge in a variety of languages (Python in this case). It also supports the Matrix long-term goal of having E2E encryption turned on by default in private rooms.</p>
<p>Integrated script editor in Godot lacks features found in editors like VS Code, Sublime, Emacs, etc. These editors are also more popular among developers and therefore are better to switch for usability. However, to implement core functionalities such as - Diagnosis, Registering custom symbols, jump to definition, etc a Language Server structure has to be adopted. For example, the client (say vs code) will communicate the godot language server to give desired result.</p> <p>Microsoft's Language Server Protocol (LSP) is flexible and powerful to implement these functionalities. It also supports many editors - VS Code, Atom, Sublime, etc. Hence, instead of writing complete extensions for each editor (client) using LSP servers can be reused while the client which is an editor extension has to be only re-written.</p>
<p>Signac is a data management framework named after the painter Paul Signac, whose colourful pointillist style resembles a collection of data "points". The signac framework is designed to help researchers design, manage, and execute computational studies. The core data management package signac helps users track data and metadata for file-based workflows (e.g. large molecular simulations) with features for searchability, collaboration, reproducibility, and archival. It stores the data in a JSON file using SyncedAttrDict and JSONDict classes. Currently, Signac uses SyncedAttrDict to store the statepoints and JSONDict to store the documents. In this project, the aim will be to unify the synced collection classes and improve buffering, synchronization and support to different data structures. Also, this project will deal with refractoring the statepoint loading to be lazy.</p>
This task involves various enhancements, such as: "Clone" Support for Edge Slide: An option for the Edge Slide tool which, when enabled, duplicates the corresponding edges first and then slides them. See RCS#2rcbbc, RCS#QDbbbc. Edge Flow: Adjusts the edge loop via spline interpolation such that it respects the flow of the surrounding geometry. See RCS#vddbbc. Loop Cut Curvature Preservation: Option added to loop cutting that when enabled places loop vertices on the curvature of the surrounding geometry with spline interpolation rather than with flat linear interpolation. See RCS#fSdbbc Expected outcomes: Additional loop-editing operators available in edit-mode. Skills required: Proficient in C++, Linear Algebra. Possible mentors: Campbell Barton, Tariq Sulley Expected project size: 350 hours Difficulty: hard
This project aims to develop a comprehensive Hamiltonian Library for QuTiP (Quantum Toolbox in Python). Currently, QuTiP users must frequently recreate common quantum system Hamiltonians from scratch, leading to redundant work and inconsistencies. The library will provide ready-to-use implementations of frequently used quantum systems like Jaynes-Cummings, Rabi, Dicke, and various spin-chain models. Key features include a standardised API, JSON serialisation for cross-platform compatibility, time-dependent parameter support, and LaTeX representation capabilities. The deliverables include a core Hamiltonian base class, at least 10 implemented quantum models, comprehensive documentation, tutorials, and full integration with QuTiP's existing functionality. This project will significantly enhance user experience and reduce redundancy in quantum simulations.
On the Cilium homepage (https://cilium.io), we want to document technical outcomes from using Cilium. Think of these technical outcomes as aggregating some of cilium features to achieve a high level technical goal. These are the current ones we have in mind: Zero Trust Networking, Network Automation, Distributed Firewalling, Cost and Carbon Savings, Multi-cloud Connectivity. Expected Outcome: A section of the Cilium website detailing these technical outcomes. This section on the website can include any supporting materials from the Cilium community i.e blogs, videos, talks, illustrations, etc. Recommended Skills: Technical Writing, some basic working knowlegde of Cilium or the willingness to quickly ramp up, Kubernetes, general familiarity with the cloud native ecosystem, basic React.js(the cilium webiste is built with Gatsby). Upstream Issue: cilium/cilium.io#492
<p>Visual Scripting Language is a part of Godot Engine that is fairly underdeveloped. But it still is a really powerful system which just needs to be properly improved for it to reach maturity.</p> <p>The idea is to add UI and UX changes to Visual Script Language that make it much <strong>less intimidating</strong> and allows for a much <strong>friendlier interface</strong> and has a <strong>Simplified API</strong> rather than being a GDScript with Nodes kind of a setup.</p> <p>Some ideas for improvement would be unifying the scripting graph, improve node quality and UI/UX changes to support the new features. Further, plans would be to ensure less breaking issues/bugs, and improving overall usability.</p> <p>An extended goal would be to work on the Group Nodes(VisualScript based CustomNodes) to allow for increased and simplified modularity.</p>
Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This internship focuses on significantly expanding the breadth and depth of Meshery Relationships across a wide array of technologies supported by Meshery. As Meshery continues to integrate with more cloud-native technologies (Kubernetes, public clouds, and all CNCF projects), there's a growing need to accurately model the intricate relationships between their components - vital for providing users with comprehensive insights and control over their deployments. Expected Outcome: - A multitude of new relationships defined both intra and inter GCP services. - Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
NeoRoo currently talks to DHIS2 through raw HTTP calls with no offline support, so if a nurse loses connectivity while entering baby data, that data is just gone. I'm proposing to integrate the d2 Android SDK as the primary sync engine and build a Flutter abstraction layer on top of it that works across both Android and iOS. The main deliverables are: a Pigeon-based platform bridge to d2 (Android) and DHIS2 REST API (iOS), an offline-first sync queue using Drift/SQLite with automatic retry, a server-wins conflict resolution system with a review log, real-time sync status indicators in the UI, background sync with battery optimization, push notifications for server-side changes, and a testing + monitoring toolkit. By the end, healthcare workers should be able to use NeoRoo reliably regardless of connectivity.
<p>Bayesian nonparametric (BNP) methods offer more modelling flexibility by relaxing parametric assumptions at the cost of more daunting theoretical underpinnings and challenging implementation. PyMC3 is a Python probabilistic programming library for fitting Bayesian statistical models using Aesara - formerly Theano - as a computational backend for Markov Chain Monte Carlo (MCMC) sampling and variational inference. While PyMC3 provides built-in tools for plotting, model checking and a wide selection of statistical distributions, it currently lacks support for Dirichlet Processes (DP), a BNP method first that is garnening much attention from the research community in the last two decades. My Google Summer of Code (GSoC) proposal centers around bridging this gap in the PyMC3 framework by building a submodule for DPs and DP-related methods and contributing notebooks that build upon them.</p>
RooFit uses RooWorkSpace to manage its models. Currently, the syntax to interact with RooWorkspace is completely different from Python syntax, which makes the code less intuitive & harder to manage. The project aims at making the interaction with RooWorkspace more Pythonic. Pythonization RooWorkspace is done in two main steps: 1.) Writing a C++ plugin for the RooWorkspace factory 2.) Writing Pythonizations This is followed by making unit tests, writing documentation & writing tutorial for the new Pythonic interaction. The deliverables for this project are: ● Develop a Pythonic alternative to RooWorkspace::factory() ● Pythonization of special operations of RooWorkspace along with support for creating Histfactory p.d.f.s using the JSON I/O ● Write unit tests to check the functionality of Pythonic code ● Make tutorials to demonstrate the usage of new functions in Python & improve documentation for HistFactory
DetectionMetrics is a toolkit designed to unify and streamline the evaluation of perception models across different frameworks and datasets. The older version i.e DetectionMetrics v1 provides objective performance metrics such as mean average precision and mean inference time for object detection models. Now DetectionMetrics v2 was introduced in which the previous version was redesigned with an expanded focus on image and LiDAR segmentation. Currently, DetectionMetrics v2 functions as both a Python library and CLI, focusing on the quantitative evaluation of image and LiDAR segmentation models, with plans to expand into object detection. It supports PyTorch and TensorFlow models, along with multiple public datasets. Its modular design allows easy integration of new models and datasets. This project aims to bring back the key functionalities from v1 that were lost while redesigning, build a GUI and set up a CI workflow.
<p>Despite being the go-to library for point cloud based computation, PCL can cause some friction to users due to its old-fashioned and sometimes inconsistent API and the lack of certain features. This proposal aims to introduce the following new features to the PCL library;</p> <ul> <li>GPU implementation of Iterative Closest Point (ICP) algorithm</li> <li>Implementation of Fast Resampling of 3D Point Clouds via Graphs</li> </ul> <p>As well as to refactor and modernize the library by means of;</p> <ul> <li>Introducing better type for point indices, thereby providing support for larger point clouds</li> <li>Introducing a fluent API for algorithms</li> <li>Modernising the GPU Octree module to align with the it’s CPU counterpart</li> </ul>
My project aims to enhance the GNU Octave Statistics package by implementing missing functionalities, specifically focusing on adding the missing ClassificationSVM classdef and ClassificationNeuralNetwork classdef. Support Vector Machines (SVMs) and Neural Network classifiers are powerful tools for classification tasks, and their absence in the current package limits users who require this functionality. By adding ClassificationSVM and ClassificationNeuralNetwork, I aim to improve the usability and completeness of the Statistics package, thereby increasing the user base and community satisfaction with Octave. During the Google Summer of Code period, I plan to complete the implementation of ClassificationSVM and ClassificationNeuralNetwork. I am excited to contribute to Octave, learn more about open-source development, and become an active member of the Octave community. You can follow the project using the following links: Blog: https://pallavpurbia.blogspot.com Github: https://github.com/XPT5OO1/statistics
Currently, dotty-cps-async does not support effect systems, hindering its further development. Additionally, there is no mechanism to automatically convert existing standard monads to effect system monads, resulting in increased boilerplate code. To address these issues, a macro will be used to assemble code-based effects to CpsMonad. Additionally, automatic conversion of existing monads to effect system monads will be developed using additional monad converters that will be implicitly applied. The outcome will be the ability to use effect system monads through the async[[X] =>> Monad[R, X]] syntax, facilitating easy composition of various effect systems. Furthermore, automatic conversion of existing standard monads such as Option, Either, List, etc., to effect system monads will streamline and enhance the user experience, reducing boilerplate code.
AI Tour Director reimagines geographic visualization as a cinematic experience by treating every tour like a film. There is a set of specialized agents that collaborate to transform a simple user prompt into an immersive tour. Creative Director, Production Designer, Writer, Auditor, and DOP make this magic happen. Each agent contributes to building a cohesive narrative, that is, from selecting locations and designing camera movements to generating narration and validating the flow. The system leverages modern AI and real-time geographic data to direct immersive tours on Liquid Galaxy, complete with synchronized visuals, subtitles, and multilingual narration. It further enables recording these experiences as high-quality videos and turns the exploration into shareable film-like content. The final deliverable is a modular agent-driven platform that blends storytelling, visualization, and open-source extensibility.
<p>DIRAC is a highly-scalable software used for accessing distributed resources from various distributed systems. DIRAC’s main contributor is LHCb and also its initiator. LHCb uses the different type of computing technologies in order to distribute and process the collected physics data and DIRAC is one the software which is used because of its scalability and the level of orchestration and monitoring it provides for the distributed resources which is the main requirement of the LHCb collaboration. Further, my task will be to upgrade DIRAC’s monitoring system further by assuring high-scalability as when the LHCb gets upgraded there can be an unpredictable type of data which needs to be molded easily by DIRAC for which we will use ElasticSearch which is one of the widely used NoSQL technology. With this, I will have to migrate the Service and Agent components and DIRAC's RequestManagementSystem and DataManagementSystem to support ES backend along with tests and documentation.</p>
This Google Summer of Code (GSoC) project aims to enhance the Open Food Facts Explorer by implementing new features, ensuring design consistency, improving backend API support, and elevating the overall user experience. The Explorer acts as a user-friendly portal where contributors can explore food data, contribute new information, and visualize relationships among food products. Throughout the summer, I will work on bringing feature parity with the main website by adding login flow, advanced search capability, image editing features, and more. Additionally, I will extend functionalities through the Open Prices integration, contribute to reusable web components, and enhance automation using GitHub Actions and Storybook. The project is divided into focused milestones to ensure consistent progress, including buffer periods for testing and documentation.
Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This internship focuses on significantly expanding the breadth and depth of Meshery Relationships across a wide array of technologies supported by Meshery. As Meshery continues to integrate with more cloud-native technologies (Kubernetes, public clouds, and all CNCF projects), there's a growing need to accurately model the intricate relationships between their components - vital for providing users with comprehensive insights and control over their deployments. Expected Outcome: - A multitude of new relationships defined both intra and inter Azure services. - Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
This project will build friendly automation tooling to support community translation of the p5.js reference documentation (including p5.js core and p5.sound). The p5.js reference (API documentation) is authored in English via JSDoc comments in the source code, and the website currently offers documentation in five languages (English plus Spanish, Simplified Chinese, Korean, and Hindi) . As p5.js evolves, keeping these translations up-to-date is challenging. The goal is to create GitHub Actions and workflows that do not automate translation itself (which requires human nuance) but instead assist volunteer translators. These tools will automatically track changes in the English “source” docs, flag or open tasks for updates in other languages, suggest new translation needs (for newly added APIs), and streamline communication with translation contributors.
Meshery Models are declarative representations of infrastructure and applications. Within these models, Relationships define how different Components (e.g., Kubernetes resources, Cloud services) interact and depend on each other. These relationships are crucial for visualizing, understanding, and managing complex cloud native systems. This internship focuses on significantly expanding the breadth and depth of Meshery Relationships across a wide array of technologies supported by Meshery. As Meshery continues to integrate with more cloud-native technologies (Kubernetes, public clouds, and all CNCF projects), there's a growing need to accurately model the intricate relationships between their components - vital for providing users with comprehensive insights and control over their deployments. Expected Outcome: - A multitude of new relationships defined both intra and inter AWS services. - Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
<p>digiKam is KDE desktop application for photos management. In digiKam, tags on photos are strongly supported for the sake of providing users with a natural workflow of searching and arranging photos in their collections. Since many of our photos contain faces, face tag has apparently emerged as an essential property for any photos management software, also with the fact that user has to tag thousand of their photos manually. Being aware of that, digiKam team has put a lot of efforts to develop face engine, capable of scanning photos and suggesting face tags automatically basing on pre-tagged photos by users. However, that functionality is currently deactivated in digiKam, as it is slow while not adequately accurate. Thus, this project aims to improve the performance and accuracy of facial recognition in digiKam by exploiting state-of-the-art neural network models in AI and machine learning.</p>
<p>Linear Programming (LP) based sparse learning methods, such as the Dantzig selector (for linear regression), sparse quantile regression, sparse support vector machines, have been widely used in machine learning for high dimensional data analysis. Despite of their popularity, their software implementations in R are quite limited. Our GSOC project aims to develop a new R package -- PaRametric sImplex Method for spArse Learning (PRIMAL), for the aforementioned LP-based sparse learning methods with the following two key features: 1) It provides a highly efficient optimization engine based on the parametric simplex method, which can efficiently solve large scale sparse learning problems; 2) Besides the estimation procedures, it provides additional functional modules such as data-dependent model selection and model visualization.</p>
<p>Radare2 has a very flexible console interface, including command line, different visual modes and Unix-like integration with other tools. But there are still a lot of things to be done, mainly:</p> <p>1) Unify similar code between all different modes</p> <p>2) Fixing Unicode support in RCanvas and Visual Panels mode</p> <p>3) Write a popup window widget for selection/autocompletion</p> <p>4) Add the table API/commands like it is done for graphs</p> <p>5) Add API and command for setting graph node background</p> <p>6) Show minigraph together with graph</p> <p>7) Radiff2 visual split-view mode</p> <p>8) Tests and documentation (r2book) for new commands</p>