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 goal of the project is to implement Julia support for Cantor worksheet application with folowing features: command execution, variable management, syntax-highlighting, inline plotting and binding to existing wizards.</p>
<p>Orcus is an external filter library. The project is to implement missing code for style and conditional format and corresponding interface in Libreofffice Calc. The last and comparatively easier part is to replace the hard coded cell styles with the styles imported through Orcus.</p>
<p>Hyperspectral data is often used to determine what materials are present in a scene. Materials of interest could include roadways, vegetation, and specific targets (i.e. pollutants, hazardous materials, etc.). Trivially, each pixel of a hyperspectral image could be compared to a material database to determine the type of material making up the pixel. However, many hyperspectral imaging platforms have low resolution (>5m per pixel) causing each pixel to be a mixture of several materials. The process of unmixing one of these 'mixed' pixels is called hyperspectral image unmixing or simply hyperspectral unmixing. There is an R package for this purposes however, the already implemented methods N-FINDR and VCA make one crucial assumption: they assume the presence of pure spectra of all components are available somewhere in the data. Obviously, while this assumption is reasonable for some applications, other applications exist where this assumption should not be relied on. ICE algorithm does not need to have pure component spectra for the endmembers in the presented data. Vignettes are also required to provide datailed explainitaions of algorithms and examples.</p>
As the LLVM Flang frontend matures, a significant gap has emerged between compilation and diagnostic capabilities. Currently, LLDB does not provide native debugging support for Fortran. This project aims to address that gap by building the essential foundation for native Fortran debugging. The goal is to deliver a functional debugging stack that allows users to: Inspect Variables: Support for scalar variables, function arguments, and return values. Data Structures: Inspection of static arrays, character strings, and derived types. Visibility: Implementation of module and global variable lookups. Expression Evaluation: Enabling basic arithmetic and variable inspection via the print command. To achieve this, a new Fortran TypeSystem, a dedicated Language Plugin, and a DWARFASTParser to interpret and traverse Fortran-specific DWARF metadata are needed.
OpenROAD-MCP's adoption is limited by manual setup and the lack of production-grade deployment and validation workflows. This project delivers a complete Docker deployment story with GHCR publishing, cross-platform validation across Ubuntu, macOS, and WSL2, and a six-layer testing infrastructure covering integration tests against real ORFS flows, performance benchmarking, load testing, and memory profiling thus moving the project toward a reliable v1.0 release.
I aim to improve the Welcome page and create a walkthrough in JabRef. The walkthrough would: 1. Provide an overview of JabRef's core functionality 2. Ask users to select their user type 3. Configure software with sensible default settings based on user type 4. Demonstrate relevant features using a sample library The walkthrough would be personalized based on the user's selected type, helping new users understand the features most relevant to their needs. Additional walkthroughs may be implemented depending on if there is additional time.
Development and integration of the functionality for simultaneous control of two robots, aimed at applying dual-site Transcranial Magnetic Stimulation (TMS) in InVesalius (currently, support is provided for only one TMS coil attached to one robot). This feature is based on the existing implementation for the use of two or more coils, adapting it for multiple robots. The inclusion of this feature not only improves the speed, accuracy, and safety of the stimulatory process, but also enables the scientific exploration of interactive brain networks, by allowing concurrent, targeted TMS pulses to multiple brain areas.
The JupyterLab application relies heavily on plugins sourced from the Lumino project. Currently, all plugins load at startup, significantly increasing load time. The proposed solution is to enhance the extension configuration to incorporate entrypoints, akin to how VS Code manages extensions. This configuration will dictate when to load an extension based on various triggers, ultimately improving performance. Introducing main and side panel changes without manual coding will further optimize performance.
The proposal aims to develop a package manager for the Faust programming language, consisting of several components to enhance the development and sharing of Faust libraries. The proposed system encompasses: Central Repository on GitHub: Establishing a central repository on GitHub to store metadata for Faust libraries. This repository will serve as a centralized hub for developers to publish. GitHub App for Publishing Automation: Developing a GitHub application to automate the publishing process of Faust libraries to the central repository. The GitHub app will automate the submission of libraries, manage versioning, and generate documentation automatically to enhance accessibility and ease of use. Package Manager Application: Creating a package manager application designed to manage dependencies for Faust projects locally. The package manager will enable developers to efficiently integrate and manage dependencies within their projects, ensuring seamless integration of Faust libraries. Faust-hub Website: It will contain comprehensive information about Faust libraries available in the central repository. Faust-hub will provide a user-friendly interface for browsing, searching, and accessing Faust libraries, enhancing collaboration and community engagement within the Faust ecosystem.
While Unikraft may have the bare minimum implementation required to receive and process the information passed from Firecracker under the form of the Linux Boot Protocol structures, it is not able to boot through this protocol from more strict and proper environments such as QEMU, GRUB, U-Boot or any of the many open source bootloaders that speak this protocol. The main reason this does not happen is because the Unikraft bootable images are missing the Linux header. The first step will be reading documentation and familiarizing myself with the project. I would estimate that this step will take about two weeks. The Linux x86 Boot Protocol will be studied and questions will be asked towards the community and the mentor. Secondly, a step for planning ahead the workflow that will dictate the way I will work on the project (two weeks). By doing this, a schedule will be set in place that will help me always be on time. Design the structure of the external program to parse bootloader metadata and generate the Linux Boot Protocol header. Comparing the x86 header to the ARM64 one could highlight certain common traits that can be used to minimize the existent code. Finally, the coding period will start that will be summed up by taking feedback, discussing unforeseen problems, striving to meet deadlines. This will take approximately twelve weeks. At this time, the best course of action is to respect the planning done before and focus on integrating everything that can be picked from the UEFI script. The rest can be done after thorough testing and reviews from the community.
The Workflow Hardening of PEcAn project involves improving the existing integration testing framework by extending it to include a wider range of models, inputs, sites, and met within the integration tests, thus increasing system stability and ensuring more tests pass. It also involves improving the Status Board by adding more visualizations and fixing the existing issues.
In this project, I'll be building demos for TensorFlow Lite Micro, to be used in conferences and Machine Learning Courses. My plan is to build these projects: 1. Heart rate logger & Analysis Description: This project aims to determine the heart rate and SpO2 level from the raw data of a MAX30102 sensor 2. Activity detection Description: This project aims to determine & analyze the activity of a person using the IMU data. 3. Steps Tracking + Heart rate integration Description: This project aims to track a person’s steps and pace of walking using the IMU sensor and a heart rate sensor. 4. Steps Tracking - Integrated on shoes Description: This project aims to improve the accuracy of the project described above by fixing the orientation of the IMU sensor. 5. Gloves using Flex Sensors Description: This project aims to simulate a human hand in Unity, using nylon glove, flex sensors, and an IMU sensor. 6. Personal trainer for activities Description: This project aims to replace a human trainer for sports like badminton, hockey, cricket, table tennis, etc. 7. Shooting Game in Unity Description: This is a fun project using Gesture recognition in games. 8. Sleep & Snore detection & Alarm Description: This project aims to improve sleeping and waking up times using TinyML 9. Home Automation with Arduino Description: This project aims to automate home appliances with voice recognition and relay switches. 10. Pose detection Description: This project is intended to help correct the posture of a person by using an Arducam and a buzzer to alert the user. 11. A simpler Dum-E robot Description: This project aims to build a simpler version of Dum-E, from the Iron Man series. 12. Multiplayer Boxing Game Description: This is a fun project to integrate the glove described above into a web-based game. 13. A simpler Self-driving car Description: This project aims to build an RC car that is able to read signs and make decisions on its own
<p>The primary aim of this project is to make enhancements to Zulip’s REST API Documentation framework, which allows writing API Documentation based on the OpenAPI standard with built-in automated tests.<br> Major tasks include modifying the framework and testing to allow generating API pages directly from OpenAPI data and removing the redundant templates, and adding support for auto-generated API bindings by integrating different tools into the framework.<br> The docs will also be visually enhanced by improving the organisation and UI of /register and /events endpoints, and /api pages in general. This would include major design changes to the documentation pages to improve the overall user experience. Further, the OpenAPI data for currently undocumented /api endpoints will be added to improve the endpoint coverage by the docs.<br> This project would also involve fixing the currently open issues related to API Docs area, majority of which improve the testing of OpenAPI data, as well as making various API migrations with appropriate updates in OpenAPI data. Also, improvements would be made to the organisation of OpenAPI data and its testing/error messages to make it easier to maintain and work with.</p>
<p>Hybrid fuzzing is a term used to describe techniques in fuzzing which involve concolic execution to drive the fuzzing campaign through difficult-to-reach parts of the target program. In the academic world, this concept has received a lot of attention in the past few years and the results are promising. However, so far this technique does not seem to have escaped the lab yet, with many academic projects being difficult to use in practice. AFL++ and LibAFL are projects that aim to make cutting edge fuzzing research usable in the real world and in the same vein, this project proposes to make hybrid fuzzing more approachable by providing the necessary components to do hybrid fuzzing with LibAFL.</p>
<p>Google Protocol Buffers is a language-neutral serialization library. However Chapel support for Protocol Buffers has not been investigated. Nonetheless, there are a number of interoperability scenarios that would benefit from having such a feature. This feature is something that many other projects can build on - including calling Python from Chapel or creating a Chapel distributed in-memory key-value storage service.The protocol buffers compiler supports a few languages directly but also includes a plugin mechanism to generate code for other languages. These plugins can be written in the target language.</p> <p>The project involves the following:</p> <ul> <li>Create a Chapel library that works with basic Protocol Buffers functions.</li> <li>Implement a Chapel plugin for the protocol buffers compiler.</li> <li>Demonstrate this tool in an example integration using protocol buffers.</li> </ul>
<p>Bringing the 'maps' parameter with its full functionality to the TemplateData GUI editor to make it easier for the average non-technical user to modify the “Maps” parameter.</p>
<p>The Wayback Machine Extension is a powerful tool that collects and stores information about the search queries you make and the web pages you view to provide you with information about those pages and to help the Wayback Machine archive the Web. Driven by a powerful idea and an enthusiastic team, this extension has successfully been archiving the internet since 2017. The Wayback Machine Extension plays a significant role in providing people a way to archive and preserve the publicly available web pages and mapping the evolution of the World Wide Web.</p> <h4>This Project focused on Improving the Wayback Machine Extension by:</h4> <ol> <li>Enhancing the existing Search Box feature.</li> <li>Adding 'Fact Check' feature</li> <li>Adding 'Bulk Save' feature</li> <li>Re-defining the display of existing Contexts</li> <li>More enhancements:<ul> <li>Solving the existing issues to ensure full functionality</li> <li>Code optimization and improvement</li> <li>UI improvements</li> <li>Searching, inspecting and fixing bugs</li> <li>Interacting with users about issues and opportunities to make the app better</li> <li>Writing Tests</li> <li>Adding support for Edge</li> <li>Making the Internet a BETTER place to surf.</li> </ul> </li> </ol>
<p>The project aims to develop a <strong>Gitlab collection worker closely tied up with the Github collection worker using mapper files</strong> to bind the intended attributes of their API responses and the Augur schema. Gitlab worker holds the responsibility to fetch progressive data related to Issues, Commits, Merge Requests etc from GitLab using python-gitlab API on which metrics could be generated. Additional modules like <strong>Data Setter</strong> module and <strong>Schema moderator</strong> would be implemented to work as a common channel for both the workers to push the collected API response into the Augur Database or to change the Augur schema by <strong>editing the mapper files</strong>. Data Setter module will additionally hold the responsibility of implementing the duplicate management mechanism.</p>
<p>The Data processor Extension (created by Jaap) provides a user interface to create custom search screens and custom APIs. It saves time by removing the need for writing custom searches and custom APIs. Searches are compatible across different entities available across CiviCRM. Hence it is a handy tool for system administrator. My work over the GSOC period was to extend the functionality of the Data processor and add more features to the extension.</p>
<p>MapKnitter is based around the upload of images, the positioning of those images on a map, and the compositing of those images into map export formats. This project idea focuses on the systems for tracking changes on those images, collecting them into sets, storing image history, and other improvements which we hope will simplify and reconfigure the MapKnitter codebase.</p> <p>Mapknitter Synchronous Editing is a long-sought feature of MapKnitter is the ability to collaborate in real time on image upload and placement as if it were Google Docs. This will involve changes from the MapKnitter codebase to the Leaflet.DistortableImage front-end image distortion UI.</p>
<p>DIRAC is an open source interware platform whose roles are submission of jobs, the management of the data produced, to the orchestration of the distributed resources. It is a generic software, used and extended by several Virtual Organizations (VO).</p> <p>It monitors resources like computing, storage, catalogue resources, networks, information providers, file transfer services, message queues or databases services. Members of a VO can use a mask composed of services exposed by local resources. Experienced Grid administrators apply procedures for managing such services, based on their status, as it is reported by an ever-growing set of monitoring tools. When a procedure is agreed and well-exercised, a formal policy could be derived.</p> <p>For this reason, using the DIRAC framework is developed as a policy system that can enforce management and operational policies, in a VO-specific fashion.</p> <p>This project proposal offers :</p> <ul> <li>A reliable working implementation of a multi-VO Dirac Resource Status System (RSS).</li> <li>A base database access module for the RSS which would unify the SQLAlchemy frontend and also reduce code duplication.</li> <li>Remove sqlite3 from some RSS modules and port them to MySQL backend</li> </ul>
<p>This project involves the creation and refinement of a tool to create plots, using the <strong>Data & Analytics Framework APIs</strong> or graphql based on DAF data. This will be accomplished through <strong>python</strong> and its vast set of data science tools and libraries, such as <strong>matplotlib</strong> and <strong>mpld3</strong>, that have become an established standard in the data science field in recent years.</p>
<p>Over the years, Mozilla has shifted to using Taskcluster as its primary continuous integration system. Communication becomes essential between the various components when scaling the infrastructure. Mozilla uses Pulse to enable an exchange of information Mozilla’s systems. Pulse is actually a RabbitMQ server which uses AMQP ( and follows a Publish--Subscribe pattern). Taskcluster-events is a service that allows web clients to listen for pulse messages without RabbitMQ credentials and without the need for a TCP connection to the RabbitMQ server. However, currently, taskcluster-events is old and poorly designed, without protocol specification. This proposal aims to completely rebuild taskcluster-events from scratch, ensuring it is robust and free of major bugs / failures.</p>
<p>There exist several plotting libraries for Ruby, but none of them is as readily usable as either Matlab's plotting system or the Matlab-inspired Python Matplotlib. This lack of a matlab/matplotlib-compatible Ruby plotting library is Ruby's single biggest obstacle as a scientific library. The aim of this project is build Matplot lib in Ruby.</p>