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 deliver comprehensive, end-to-end non-uniform grid support for MethodOfLines.jl. Currently, basic advection schemes lack graceful error handling for ill-posed boundary conditions, and advanced high-order schemes (specifically WENOScheme) completely lack non-uniform method dispatch, leading to fatal compilation errors on irregular domains. The proposed solution utilizes Julia's multiple dispatch to route non-uniform grids to a newly developed, isolated mathematical weight calculator within the WENO module, ensuring zero breaking changes for existing uniform grid users. Key deliverables include refactored basic advection schemes with robust well-posedness validation, a native non-uniform WENO implementation featuring dynamic smoothness indicators and negative weight regularization, rigorous L₂ convergence tests, performance benchmarking, and comprehensive documentation to enable highly precise real-world physics simulations.
<p>This project aims at designing and implementing new features in Distro Tracker [<a href="http://tracker.debian.org/" target="_blank">http://tracker.debian.org/</a>] to better support Debian teams to track the health of their packages and to prioritize their work efforts. For this purpose, I will migrate the most important team-related features from PET [<a href="https://pet.debian.net" target="_blank">https://pet.debian.net</a>] to Distro Tracker, leveraging and improving Distro Tracker current code base regarding teams. Thus, as a final result of SoC, I expect to incorporate to Distro Tracker a set of useful data to help teams to see the health of multiple packages and better prioritize their efforts where it is most needed. It is worthing noticing that Distro Tracker is a general purpose service that is also used by Kali community [<a href="https://pkg.kali.org/" target="_blank">https://pkg.kali.org/</a>]. Thus, they also will be able to take advantage of the proposed improvements.</p>
<p>The Heavy Flavour AVeraging (HFLAV) group is responsible for collecting and combining measurements made at different High Energy Physics (HEP) experiments, at CERN and other particle physics laboratories, and combining them using robust statistical procedures.</p> <p>The HFLAV website provides a live snapshot of the latest data obtained from these latest publications. This project aims to improve the experience of users using the HFLAV website. These averages could be of greater value to the particle physics community if the accessibility, interactivity and visibility of the current website can be improved. Thus this project seeks to transform user interaction with HFLAV’s ‘Beauty to Charm’ averages.</p> <p>The plan to increase the accessibility is by redesigning the whole user interface, making it easier to find a relevant data point ( branching fraction) by the use of filters. As the old website is static, thus in order to make the site responsive to the user's input, the website will be refactored and the framework will be changed to Django. The application would be hosted using CERN's OpenShift service instead of the older EOS filesystem it was using.</p>
<p>An asymptotic expression typically contains exact terms and O-terms, for example n3 + 2n2 + O(n). The basic framework for this asymptotic ring is already implemented. The main aim of this summer of code project is to extend its functionality up to the point where asymptotic expressions with explicit constants are fully supported. In his book, “Asymptotic Methods in Analysis” on page 5, deBruijn calls it an “L-term”, but we will call it “B-term”. B_{20}(3z) is a B-term, which stands for an expression which is bounded in absolute value by 3|z| for |z| ≥ 20. Sometimes, in research, it is important to know from which values of the variable on the asymptotic expression has enough precision to decide wether it is larger than a given bound. This cannot be achieved by O-terms (because the unknown implicit constant might be very large). For example, the average number of comparisons of classical quicksort is 2n log n + O(n). When comparing with recent variants, such as dual pivot quicksort with average number of comparisons 1.8n log n + O(n), it is interesting to know how large the O-terms are in order to know when dual-pivot quicksort will be more efficient than classical quicksort.</p>
Optical Character Recognition (OCR) technology has revolutionized document digitization. However, existing OCR tools like Adobe Acrobat and Google’s Pytesseract, they struggle with historical documents due to variations in font styles, image quality, degradation, and layouts. Text recognition from centuries-old works poses a significant challenge due to the complexity of early non-standard print forms, handwritten text and manuscripts. Over the past year, transformer-based models have been fine-tuned to improve transcription accuracy, particularly for degraded and complex historical texts. Training on a diverse dataset that combines expert transcriptions and synthetic data has enabled better generalization across various typographical styles. Building on this progress, we aim to expand the dataset, to help the model finetune to handle handwritten documents as well. Fine-tuning on larger datasets incorporating diverse typographical styles both printed and handwritten and also implementing Language Modeling & Contextual Understanding for post-processing, allowing for contextual corrections based on 17th-century grammar to further enhancing the OCR accuracy. Additionally, we plan to develop and deploy a web or mobile-based annotation tool for historians, researchers, and institutions to validate and refine OCR outputs
<p>The Essential Care for Every Baby (ECEB) is an educational and training program, developed by the American Academy of Pediatrics, provides knowledge, skills, and competencies to nurses and doctors in low/middle-income settings so that they can provide life-saving care to newborns from birth through 24 hours postnatal.</p> <p>The aim of this project is to develop an Android mobile application, the ECEB Digital Action Plan, that is purposely built to provide clinical decision-support for nurses and doctors delivering essential newborn care interventions during the first day of life.</p> <p>This project aims to develop an ECEB Android Application with the following features-</p> <ol> <li>Time-stamping births to generate an essential newborn care clock for babies. </li> <li>Ability to track multiple babies at a time. </li> <li>Automated classification of babies health status, based on results from observations and assessments.</li> <li>Automated advice on the management of babies, based on their classification. </li> <li>Reminders/alerts to provide recommended essential newborn care interventions. </li> <li>If particular interventions are not delivered on time then the capture of information regarding why this essential newborn care was late or missed.</li> </ol>
<p><strong>MapMint4ME</strong> is an android application which allows its users to record alphanumeric data, photo and GPS locations. The data can be recorded even when there is no internet connectivity. When the user returns to a location with the internet connectivity, the data is uploaded to the database. MapMint4ME is very close to <a href="http://mapmint.github.io/userguide-fr/index.html" target="_blank">MapMint</a> web software which is built on the <strong>ZOO-Project</strong>. The <a href="http://zoo-project.org" target="_blank">ZOO-Project</a> is an SDI manager providing the capability to built map and web applications.</p> <p>In this project, I plan to <strong>add audio and video data recording</strong> facility to MapMint4ME. The main idea is to <strong>include SOS input support to MapMint4ME</strong> which will <strong>enable recording of sensor data directly within the app</strong>. The sensor data will be obtained from the sensors embedded on the Android platform. This project will help lots of GIS users, geologists, geographers <em>et cetera</em> who wish to retrieve data from remote areas (where it is not possible to reach) by accessing sensor data directly through the app. Certainly, more functions with extended capabilities could be added in future. I believe that by following a strict timeline as mentioned in the proposal, I will be able to finish the project successfully.</p>
ROOT's TMVA( Toolkit for Multi-Variate Analysis ) has SOFIE (System for Optimized Fast Inference code Emit) which offers a parser capable of converting ML models trained in Keras, PyTorch, or ONNX format into its own Intermediate Representation, and generates C++ functions that can be easily invoked for fast inference of trained neural networks. It is currently implemented for CPU inference along with a SYCL implementation. This project aims to explore different GPU stacks (such as CUDA, ROCm, ALPAKA) and implement GPU-based inference functionalities in SOFIE. Although there exist CPU implementations, working with HEP applications, need for GPU inferences become important. We will be writing optimized GPU Kernels for various operators such as RELU, GEMM, CONV2D, etc. that SOFIE already has for CPU implementation. Testing and experimenting which tech stack (such as CUDA, ROCm, ALPAKA) will be best aligned with SOFIE is our first goal. After getting to know about the pros and cons we can decide which one aligns with our goal. Our next aim would be to integrate all operators for GPU implementation in a incremental fashion ensuring each operator gets enough testing for edge cases. Once we have done basic implementation, we move on to optimizing thread-block config by using tools like Nsight for maximum performance. Once we have implemented our operators for the GPU stack, there is a need for performance benchmarking against popular frameworks like Pytorch/Tensorflow. Last part of the project would be extensive testing and benchmarking memory usage and execution time. I would end the project with proper documentation on how exactly to implement and scopes for further improvements.
<p>Training of High end Deep Learning Models takes a Long time to Train, Hours, Days and Even Weeks. So, as a Developer/researchers it slows down the creativity and implementation cycle. The Whole Idea of Transfer Learning provides a nice solution where a model trained on a similar dataset can be trained partially or fully, on the custom dataset, yielding similar result. TFHub is a platform by Tensorflow where pretrained models are shared, so that developers and researchers can use transfer learning on these models. In this Project I'll be working on the following tasks:</p> <ul> <li>Implement Tensorflow Hub sample for Cloud TPU</li> <li>Convert ShuffleNet from ONNX to TF Hub Module</li> <li>Implement and Train ESRGAN(Enhanced Super Resolution Generative Adversarial Network) from Scratch (<a href="https://arxiv.org/pdf/1809.00219.pdf" target="_blank">https://arxiv.org/pdf/1809.00219.pdf</a>)</li> <li>Implement GAN Distillation to compress ESRGAN (<a href="https://arxiv.org/pdf/1902.00159.pdf" target="_blank">https://arxiv.org/pdf/1902.00159.pdf</a>)</li> <li>Add Support for SavedModel 2.0 Functions in saved_model_cli</li> <li>Add Sample Notebook demonstrating usage of ESRGAN TF Hub Module</li> <li>Create proof of concept Video player for real time video frame Super Resolution (using "distilled" ESRGAN)</li> </ul> <p>Github: <a href="https://github.com/captain-pool/GSOC" target="_blank">https://github.com/captain-pool/GSOC</a></p>
<p>Meshery Models are declarative representations of infrastructure, applications, and their relationships - the canonical artifacts through which Meshery understands and manages cloud native systems. Today, Meshery lacks a standardized, portable distribution mechanism for these models. OCI registries (Docker Hub, AWS ECR, GitHub GHCR, and others) have emerged as the universal artifact store for the cloud native ecosystem, and [ORAS](https://oras.land) (OCI Registry As Storage) provides the Go-native tooling to push and pull arbitrary artifacts to any OCI-compliant registry. This internship implements end-to-end OCI registry support for Meshery Models - from new Connection and Credential types for major registries, to ORAS-powered push/pull logic in the Meshery server, to a redesigned Registry page in the Meshery UI that gives users full visibility and control over their model artifacts across registries.</p><p><br></p><p>Recommended Skills: Golang, REST API development, React. Familiarity with OCI image specifications, container registries, or ORAS is a plus. Experience with Meshery or other CNCF projects is welcomed but not required.</p><p><br></p><p>Responsibilities:</p><p> - Design and implement Connection and Credential types for Docker Hub, AWS ECR, GitHub GHCR, and additional OCI-compliant registries within Meshery's existing connection framework.</p><p> - Implement Golang server-side logic using the ORAS SDK to push and pull Meshery Models (and their component schemas, relationships, and policies) to and from any OCI-compliant registry.</p><p> - Define the OCI artifact media types, manifest structure, and layer conventions used to package Meshery Models for registry storage.</p><p> - Enhance or rewrite the Registry page in Meshery UI to surface connected registries, browsable model artifacts, push/pull controls, and credential management.</p><p> - Write integration tests covering push, pull, and round-trip fidelity of Meshery Models across at least two registry backends.</p><p> - Document the new registry integration, artifact format, and UI workflows in Meshery's official documentation.</p><p><br></p><p>Expected Outcome:</p><p> - Meshery users can connect to Docker Hub, AWS ECR, GHCR, and other OCI registries using managed credentials and push or pull Meshery Models directly from the Meshery UI and `mesheryctl`.</p><p> - A well-defined OCI artifact convention for Meshery Models, documented and suitable for adoption by the broader Meshery ecosystem.</p><p> - A redesigned Registry UI page providing a unified, registry-agnostic interface for model artifact management.</p><p><br></p>
<p>The goal of the project would be to add support for PSIMI-TAB format to the admin tools of the DV-IMPACT database and allow the upload and download of PPI network data in the same format. Currently, the data upload can only be performed by the database admin. The objective is to create registration and user profile system that allows users to register and upload their own data independently without the need of the database admin to be involved in the upload process.</p> <p>The summarized goals would be:</p> <ol> <li>Create registration and user profile system that allows users to register and upload their own data independently.</li> <li>Add support for PSIMI-TAB format to the admin tools of the DV-IMPACT database.</li> <li>Add download PPI networks in PSIMI-TAB format to the frontend of DV-IMPACT database.</li> </ol> <p>The Project fulfills all these issues by:</p> <ol> <li>Creating a User Profile system type forum.</li> <li>Allow users to register, upload and download domain-peptide PPI data in the specified format.</li> <li>Modify the DV-IMPACT database present in the server to handle the upload to the admin tools in PSIMI-TAB format.</li> </ol> <p>Link to the evaluation task: <a href="http://dvimpact.herokuapp.com/" target="_blank">http://dvimpact.herokuapp.com/</a></p> <p>Github Repo: <a href="https://github.com/jajodiaraghav/DV-IMPACT" target="_blank">https://github.com/jajodiaraghav/DV-IMPACT</a></p>
The goal of this project is to enhance the Katib Experiment APIs to support various parameter distributions such as uniform, log-uniform, and qlog-uniform. This improvement aims to align Katib more closely with other hyperparameter tuning frameworks like Hyperopt, which offer a broader range of parameter distributions. Currently, Katib is limited to supporting only uniform distribution for integer, float, and categorical hyperparameters. By introducing additional distributions, Katib will become more flexible and powerful in conducting hyperparameter optimization tasks.
Expanding on Katie Chan's 2021 p5.js Showcase theme of The Love Ethic, the driving force of this project will be the theme of BONDS, but more specifically, how improved UI and accessibility can further BOND the creative code community. In previous years, outreach and accessibility updates have been core goals of the showcase, so this project aims to expand the possibilities of how outreach and accessibility can be achieved. Submissions will be encouraged to interpret the theme BONDS in their own ways, with emphasis on community, care, and thoughtfulness. As well, the ability to participate in and browse the showcase should not be hindered by one’s physical abilities, thus increasing accessibility will further BOND the community, especially in the parts of the community that are not as well represented. This project will deliver three stages of changes: the community approach, the support, and the narrative. The community approach will implement a hashtag and social media challenge to expand community discussion/bonding beyond the showcase launch date. The support phase will focus on tweaking specific functions to greatly improve UI and accessibility, as good design will open up the p5 community/showcase to underrepresented communities, such as the impaired. Lastly, the narrative phase will introduce the implementation of an "Explore" tab alongside of the current "Gallery" tab, which will encompass a digital gallery that allows viewers to freely explore the works and create their own narratives, adding more personality/personal voice to each submission.
Borg Collective is a well-known organization that offers a range of Python-based backup tools, including Borg, Borgmatic, and Vorta. Borg is a file backup tool that performs tasks like compression, encryption, authentication, and data deduplication. Vorta is a desktop GUI for Borg that operates in the user's taskbar and conducts backups in the background. It is officially supported on Linux and MacOS platforms, with its functionality on Windows currently being tested by the community. Borgmatic serves as a command-line interface (CLI) wrapper for Borg and is designed to help manage Borg repos, settings, and related tasks, including monitoring. I outline three significant projects aimed at enhancing the functionality, usability, and maintainability of backup solutions Vorta and Borgmatic. The first project focuses on Vorta, addressing critical code base issues through refactor, cleanup, and maintenance tasks.. The project aims to lay a robust foundation for future development endeavors by improving the quality, readability, and maintainability of the codebase. The second project aims to enhance the Exclusions tab in Vorta, introducing various features such as expanded exclusion patterns, alphabetical sorting, filtering options, and reinstatement of the Exclude-if-present feature. These enhancements aim to improve user experience and address community feedback. Finally, the third project focuses on Borgmatic, aiming to add support for dumping MySQL/MariaDB databases into directory format, which proved a more granular approach to managing and organizing backups, enabling easier navigation and selective restoration of database objects.
<p>Mission Support System (or short MSS) is a software that is used for atmospheric research flight planning by scientists and meteorological researchers. It is a tool that uses various sets of forecast data in combination with a web map service to analyze the data and place the waypoints for planning research flights accordingly.</p> <p>The present documentation of the Mission Support System client software covers the basic installation and offers a brief description of the use of the MSS client UI but lacks a vivid and lucid explanation of all the elements and features of the User Interface. The practical usage of the software has been lacking in the existing documentation. To enhance the user experience and to convey a deeper understanding about the practical usage of the software, I propose to create comprehensive and auto-generated video tutorials by a programming script that will be a helpful guide for the user.</p>
The project aims to add AAC via S/PDIF and Bluetooth passthrough support for all major OS specific audioservers to VLC as opposed to the current implementation where PCM data is passed through.
Idemix is a cryptographic protocol suite, which provides strong authentication as well as privacy-preserving features such as anonymity, the ability to transact without revealing the identity of the transactor, and unlinkability, the ability of a single identity to send multiple transactions without revealing that the transactions were sent by the same identity. More details here - https://hyperledger-fabric.readthedocs.io/en/release-2.2/idemix.html Current JavaSDK doesn't support to store Idemix credentials in Hyperledger Fabric Wallet. Objective of this mentorship program to support wallet to store idimix identities. - Ability to store Idemix Identity in a Wallet by using Fabric Gateway SDK for Java - Ability to store Idemix Identity in a Wallet by using Fabric Gateway Client API for Java - Ability to use the Stored Idemix Identity from a Wallet to fire transaction to the Hyperledger Fabric Network in both Fabric Gateway SDK for Java and Fabric Gateway Client API for Java - Write Unit Tests and Add Examples in fabric-samples Repository
Xrefer currently functions as an IDA plugin for static binary feature extraction. The goal of this project is to abstract Xrefer’s core functionality into a flexible multi-backend pipeline supporting static analysis on IDA, Ghidra and Binary Ninja.
<p>This project will add support for arbitrary CPU and RAM in the ComputeService on JClouds. Some providers do not have the hardware profiles concept and in the current implementation of ComputeService use workarounds to overcome that lack and provides a fixed configuration. This project will allow the user to specify CPU and RAM.</p>
The Cluster API is a Kubernetes project to bring declarative, Kubernetes-style APIs to cluster creation, configuration, and management. CAPG provides this Kubernetes-native declarative infrastructure for GCP. This project would focus on adding support for attaching GPUs to instances used for worker nodes in a Kubernetes cluster created by CAPG.
I aim to enhance the Sprocket VSCode extension by integrating advanced language features for the Workflow Description Language (WDL) through the Language Server Protocol (LSP). This includes implementing go to definition, go to declaration, references, rename, auto-completion to improve the development experience for WDL authors. As a stretch goal, I will extend support to other editors like IntelliJ IDEA and Neovim
<p>The goal of this project is to bring error recovery and streaming support in the graphql reference parser while maintaining the code readability, spec compliance and parser performance. This will enable this parser to be used by IDE like applications such as CodeMirror and GraphiQL. This project will also cover the migration of GraphiQL, GraphQL LSP server and CodeMirror Graphql to use the updated graphql reference parser.</p>
Description: In KubeVela's provider system, we can use our defined Go functions in CUE schema. The Go providers usually have a parameter and return. Fields in Go providers are the same as fields in CUE schema, so it is possible and important to support automatic generation of CUE schemas and documents from Go structs. Expected Outcome: Auto-generators of CUE schemas and docs from Go structs, the capabilities should be wrapped in vela cli command.
Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Gateway API resources are used to dynamically provision and configure the managed Envoy Proxies. Currently the implementation only supports Kubernetes clusters with IPv4 enabled, and not IPv6 Expected Outcome: The managed Envoy Proxy fleet can - Accept connections/listen on an interface that has an IPv6 address assigned to it - Can route to IPv6 pod endpoints/addresses