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.
The process of transcranial magnetic stimulation neuronavigation involves the generation of motor evoked potentials (MEP), which are detected and measured using electromyography. These MEP signals can be effectively represented through a color map projected onto the brain surface. This innovative approach enables real-time visualization of brain motor mapping, offering a dynamic and comprehensive understanding of neural activity during the procedure. Requirements: Computer with Windows, Linux or Mac OS installed. A source code editor, Python language and InVesalius libraries dependencies. Deliverables: Develop pipeline to receive motor mapping data using websocket Projection of motor mapping data, based on the neuronavigation position, in the brain surface GUI to define the color map preferences and customize the number of stimuli Coordinate communication between the websocket data receiver, projection module, and GUI.
This project aims to enhance the capabilities of neural-fortran, a parallel Fortran framework for deep learning, by implementing additional optimization algorithms. While the framework currently supports training and inference of dense and convolutional neural networks using stochastic and mini-batch gradient descent optimizers, more versatile learning and training from a broader range of problems and datasets require the use of other optimization algorithms such as RMSprop, Adam, and others commonly used in popular deep learning frameworks like Keras. The project will also require work on implementing, documenting, and testing these optimizers, which will broaden the applicability of neural-fortran and allow it to be used for a wider range of deep learning tasks. The successful implementation of these optimization algorithms will provide users with more flexibility and choice when training their models, ultimately improving the performance and capabilities of neural-fortran.
The noaa_coops package provides oceanographic data access but has critical gaps: large date ranges fail without pagination, no retry logic for rate limiting, and NOAA's Derived Products are inaccessible. I will implement: (1) automated pagination respecting product-specific API limits, (2) throttling-aware retry logic with exponential backoff, (3) complete derived product support via a new method, (4) metadata retrieval fixes for historic current stations, and (5) numpy 2+ compatibility fix. Deliverables include a strengthened noaa_coops package with merged PRs addressing each issue, comprehensive pytest coverage (>90% for new code) and updated documentation with clear examples. This will transform noaa_coops into a production-ready package that oceanographers can rely on for large-scale research workflows.
<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>
This project proposes an automated pipeline for ingesting, structuring, and semantically tagging federal Funding Opportunity Announcements (FOAs). The system aggregates opportunities from multiple sources, including the Grants.gov public API and NSF funding pages, combining API retrieval with web scraping to handle both structured and semi-structured announcements. Legacy FOA documents are processed using layout-aware PDF parsing to preserve reading order and extract key program information. The extracted records are normalised into a standardised JSON schema and enriched using a hybrid semantic tagging framework. Rule-based matching identifies ontology-aligned terms from controlled vocabularies, while sentence embeddings capture semantic relationships for more flexible tagging. The resulting structured dataset enables efficient discovery, search, and future grant-matching workflows.
The main objective is to integrate direct syntax support for parsing and emitting JSON, XML, and/or YAML formats in Vala. This will cut back the boilerplate code making it more user-friendly and efficient for developers working with these format languages. To solve this, I first plan to research how other languages implement these integrations. This will allow me to see best practices and common syntax used. At the same time, I will research how Vala currently parses and emits JSON, XML, and YAML formats. Lastly, out of the research, I will know how to properly integrate the format languages into Vala's compiler, which will allow for direct syntax integration. The overall deliverables consist of: 1) Research on how Vala and other programming languages handle JSON, XML, and YAML. 2) Syntax design and mock-ups. 3) Implementation and prototyping. 4) Testing, documentation, and code snippets
<p>P2PSP.org is a nonprofit organization that develops the P2PSP protocol, an application layer protocol designed for the real-time streaming of multimedia content over the Internet. I would like to contribute to the idea of <strong>Virtual Room</strong> this summers and be a part of the community. Recently I have been involved with a lot of real time applications .The hidden motivation behind choosing this project is mainly due to an application I recently developed, Latch for a hackathon. It is a Location based chat application, using Django as the primary backend server and Node.js for real time data handling. I already had an idea of developing a similar video based application which introduced me to WebRTC. I saw this project of Virtual Room in P2PSP, and the idea of an open source real time video streaming application fascinated me a lot. I believe that it could be very useful and can create an impact on the community.</p>
Thunar is a modern file manager for the Xfce Desktop Environment. It supports 3 types of views - List View, Icon View & Compact View. As a part of my project I will be adding the functionality of tree-like expansion of non-empty folders in the List View. Additionally I will be adding a feature to enable file highlighting in Thunar. This will enable the user to highlight their favorite/important files with the color of their choice. Xfce also offers a terminal application called Xfce-Terminal. My project also includes working on Xfce-Terminal to introduce Profiles. Currently all settings in Xfce-Terminal are global. I will be adding the functionality and feature set to allow users to create profiles, amongst which they can quickly switch between across tabs. This allows the user to have different settings on different tabs/windows and simultaneously work with them.
We propose to recreate the MIT IoTNet solution in silica. It is currently facilitated by mostly ARM processors and external (USB connected) radios. To do this modernization we are going to design a RISC-V solution that incorporates SDR. We are looking at the trade space now since we know there are some vendors that have products that might be ideal for us. However, we are looking specifically at GNU radio. The background for this project is substantially at https://tinyurl.com/mitiotnet In our first attempts we used TI Beagleboards and Pandaboards. For our next version we will use homegrown MIT Beaverboards and BU Terrierboards. We don’t anticipate having a chip design together soon, either through this effort or our ongoing research. But we may participate with a vendor who already has a board in the marketplace. This of course would depend on whether we could either put an (external) radio on a board or find a way to get our firmware onto the board.
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: 1. A multitude of new relationships defined both intra and inter AWS services. 2. Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
The project this document proposes is that of implementing the hash map structure described in high level detail in the article Hash Maps That Don’t Hate You (https://blog.toit.io/hash-maps-that-dont-hate-you-1a96150b492a), an elegant variation over standard open addressing hash tables that, instead of storing the Key-Value pairs themselves in the array backing the hash table, it stores indices into yet another insertion-ordered backing array. This allows us to have our cake and eat it too : we get insertion-order iteration while still maintaining most of the desirable performance guarantees expected from hash tables, with reasonable implementation complexity. Deliverables: A build of truffleruby with a Hash implementation as described in the article, supporting all standard Ruby Hashes operations (as of Ruby 3.1) and hopefully faster and\or more memory efficient than the current implementation of Hashes in truffleruby.
DBpedia, an ever-evolving repository of structured knowledge extracted from Wikipedia, has played a pivotal role in organizing information. Yet, its dependence solely on English Wikipedia limits its applicability in diverse linguistic environments. Our project seeks to rectify this by creating a DBpedia chapter sourced exclusively from Hindi Wikipedia. This endeavor not only ensures the continual enhancement and relevance of the Hindi ontology but also broadens its accessibility to a wider audience. Given the challenge of limited natural language processing (NLP) support for Hindi, a low-resource language, we will leverage the capabilities of Large Language Models (LLMs) to tackle multilingual text processing effectively. Through this effort, we aim to establish hi.dbpedia.org, a platform in Hindi, comprising a knowledge graph sourced from Hindi Wikipedia, a user-friendly web interface, and a SPARQL endpoint for seamless data querying.
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: 1. A multitude of new relationships defined both intra and inter AWS services. 2. Policy Contribution: For advanced interns, there may be opportunities to contribute to the Rego policies that evaluate and enforce these relationships.
To the existing Liquid Galaxy Controller on Google Play Store, I am: 1. Adding the voice functionality: For default POIs via AI generated voice mp3 files saved on storage. And using Text-To-Speech API by Android for providing voice functionality to AI generated places. 2. Adding the sound functionality: Adding sound effects for all the POIs belonging to a particular category using mp3 files saved on the local storage. Example: Bells sound for Cathedrals. 3. Improving the User Experience: Making the app responsive. 4. Removal of the Physical Beacon integration. 5. Adding AI support for context sensing perhaps using Google BARD(if published in the near future) or OpenAI ChatGPT. Example: Showing nearby places near Eiffel Tower. 6. Other additional AI integrations possible.
The Virtual Brain (TVB) is a brain stimulation platform. It offers tools for computing, simulating and analyzing functional and structural data of human brains. TVB provides a graphical user interface (GUI) for using its tools for studying human brains. The platform supports importing data into TVB like projects, data structures etc. Since TVB provides various tools for studying human brains the platform is also accessible through REST APIs. Goal of this project is to create a new package which will consume TVB REST services and perform operations on it. The new python client will have features like uploading data into a TVB, data encryption and validation, BIDS compatibility check etc. Users will be able to use this python client to interact with a remote TVB server without using an active GUI.
<p>CDLI has rich geographical and temporal data at its disposal. Currently, this information is not fully utilized. Although the data schema is being improved, there are significant challenges in exploiting the new relationships available.</p> <p>The proposed idea is to develop beautiful interactive visualizations of the search results using D3.js which will be displayed on the revamped website of Cuneiform Digital Library Initiative(CDLI) i.e.,<a href="https://cdli.ucla.edu/" target="_blank">https://cdli.ucla.edu/</a>. Altogether, a total of 5 different types of visualization will be developed and the one closest to the search filters will be displayed inside the Visualize tab, along with a dropdown option to toggle between different visualizations. Further, the developed visualizations will be made taking care of accessibility for differently abled users and device screen sizes.</p>
<p>CDI (Contexts and Dependency Injection) is an IoC (Inversion of Control) container, that is implemented in Apache OWB (OpenWebBeans). Even though there is an existing micro HTTP server that supports CDI capabilities in the Apache world (Meecrowave), it is not IoC centric and it has a lot more features than the basics. Furthermore, it is not runnable as a native executable – there’s always the big JVM necessary. The proposal is to build a much slimmer HTTP API and implement it in a project with CDI (OpenWebBeans) as the starting point and webserver components (Netty) on top. This can then be injected as a managed bean in the web application. It would be an even more minimalistic microserver and IoC centric. Making this then natively runnable as a native executable for Windows is delivering important work for future JakartaEE projects within Apache, that need to be turned into a native image (via GraalVM). At the moment, there is little to none such experience in the project.</p>
This project focuses on transforming Mogan STEM into a web-based, multi-user collaborative platform. Currently, the lack of a functional WebAssembly (WASM) version and real-time synchronization limits its use in modern collaborative research. To solve this, I will compile Mogan STEM using Emscripten, implementing a custom virtual file system to ensure stability. Furthermore, I will develop a real-time collaboration core based on Operational Transformation (OT) and WebSockets. This architecture allows multiple users to edit complex scientific documents simultaneously with "local-first" responsiveness and guaranteed global consistency. Deliverables include: 1. A stable browser-based version of Mogan STEM. 2. An OT-based synchronization server. 3. A complete end-to-end prototype supporting real-time multi-user collaborative editing.
<p>This project has three components:</p> <ul> <li>Behaviour Driven Development testing notions and ideas upon being weaved into Checkstyle’s existing test driven mechanism, shall provide ease of maintenance and prevent faults as we scale the project. This will help establish testing procedures that will be concise and abstract, to focus more on the desired functionality than going into the testing algorithm.</li> <li>With Google Truth’s new assertion framework, test verifications have become more clear, concise, flexible and readable. Migrating to Truth in Checkstyle’s tests shall be fruitful in terms of maintenance and flexibility.</li> <li>Pitest now supports a lot of new mutators which can enhance the quality of code and coverage we currently have in the project. Adding the relevant mutators shall be another task under this project.</li> </ul>
<p>Object tracking is the process of locating a moving object (or multiple objects) over time using a camera. It has a variety of uses, some of which are: human-computer interaction, security and surveillance, video communication and compression, augmented reality, traffic control, medical imaging and video editing.</p> <p>I propose to add object tracking modules in Julia either as a part of ImageFeatures.jl or as a standalone repository. Therefore, I propose to add the following algorithms:</p> <pre><code>1. Optical Flow Algorithms 1.1. Lucas-Kanade method 1.2. Farneback Dense Optical Flow method 2. Tracking Algorithms 2.1. Boosting Tracking 2.2. Multiple Instance Learning 2.3. MedianFlow Tracking 2.4. Tracking Learning Detection framework </code></pre>
I would like to participate in the project “Introduce concept of project in FOSSology” which can be founded in the idea list. The “project” is defined by: 1. a project ID (as primary key) 2. a project name 3. a root folder in Fossology 4. one or more Group IDs and associated access. 5. a URL / ID / Free field to link the project to an external tool The “project” concept is put by Nicolas Toussaint in the issue https://github.com/fossology/fossology/issues/1738. As described, it could be useful in many ways, such as gathering multiple uploads under the same umbrella, and making bulk changes to all uploads / sub-directories that belong to a given project. This project is like a web project. I need to modify both back-end logic and front-end pages. And the product of this project will be a new-version website that could support the operations on “project” level.
We propose to create a modular and composable library for variational inference and normalizing flow methods that emphasizes GPU compatibility and seamless integration with the Julia autograd ecosystem. The goal is to develop a user-friendly library that allows researchers and practitioners to easily construct and combine various components for variational approximation of general target distributions, without being tied to specific probabilistic programming frameworks or applications. Turing.jl's Bijectors.jl package offers an outstanding interface for working with normalizing flows; our project will build upon the foundation of Bijectors.jl to further enhance its capabilities and applicability. However, the current design of Bijectors.jl has several limitations such as lack of full GPU compatibility, lack of batch support, etc. Thefore, the main tasks of our projects are to address these limitations for Bijectors.jl, as well as developing the variational inference library.
RTEMS currently depends on third-party platforms like GitLab CI for static analysis, which introduces external dependencies and limits local customization. This project integrates CodeQL into the RTEMS workflow by providing a locally executable and customizable analysis setup. It includes a validated CodeQL configuration for the RTEMS codebase, an RSB recipe for automated installation, and tailored filters to suppress noise from generated and third-party files. Developers will gain tools to run predefined and custom security checks locally, generate SARIF-based reports, and track issues over time using automation scripts. Comprehensive documentation will ensure ease of adoption, and the modular design supports future CI/CD integration and rule expansion. This effort enhances code quality, developer independence, and the long-term maintainability and security of RTEMS
To improve the user experience of the KubeEdge official website, this project will focus on homepage design enhancements, the addition of new pages, and improvements to community resources. The goal of this project is to enhance the website's usability, increase user engagement, and attract more users to KubeEdge by enhancing training content and hardware compatibility support. Expected Outcome: 1. Design and optimization of the homepage, including design and code updates. 2. New page: Showcase for KubeEdge course videos, including design and code updates. 3. New page: "Hardware Compatibility" page, including design and code updates. 4. Design and optimization of the partner page, including design and code updates. 5. Optimization of community resources, improving documentation and onboarding experience to ensure users can easily get started and effectively use KubeEdge.