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 is primarily focused on creating an interactive display of the carbon cycle forecast and data assimilation system of PEcAn. The main goal is to revive the site-specific R Shiny Forecasting and SDA dashboard that is no longer operational and broaden its scope to cover a larger number of sites. Additionally, the plan is to construct a new comprehensive dashboard that combines both SDA and Forecasting graphs. Moreover, the proposal also aims to establish an automated notification email system for the visualizations.
This project is to create a catalog of the OpenAPI definitions for the various Schema.org types. Also, providing a robust set of starting OpenAPI templates for helping developers to understand and develop new APIs using a design-first approach.
<p>The main objective of the project is to build a consistent API leveraging MNE-Python to perform connectivity analysis of neural time-series data, such as MEG, EEG and iEEG. The result would be “mne-connectivity” a Python3.6+ software package that allows scientists to explore connectivity based analysis using published algorithms with few barriers because it leverages the widely used open-source platform of MNE-Python.</p>
<p>NodeCloud is a <strong>NodeJs package</strong> that aims to provide a one-stop solution to use multiple cloud providers in a project. It provides a plugin for each cloud provider which will be used to communicate with respective cloud services. Currently, the nodecloud project has aws, azure, and gcp integrated with an auto class generator(<strong>Made using Typescript Compiler API</strong>). But for the digital ocean, this has not been implemented. Digital Ocean does not have any official SDKs but there are many third-party SDK's made by developers. Some SDKs are of no use as there are either definition files missing while some are not maintained.</p> <p>Under this project, I aim to implement the important functionalities of the digital ocean in a suitable SDK(If not present), <strong>Implement a code generation module for that</strong> and then use that SDK to auto-generate classes, assembled as <strong>do-plugin</strong> for the <strong>Nodecloud integration</strong>.</p>
<p>Industrial I/O subsystem, the home of Linux sensors, as Daniel Baluta rightly calls it, provides software support for sensors, ADCs, DACs, clock generators, etc. under the Linux kernel tree. The increasing demand for consolidation due to the bloom in fields of Internet of Things (IoT) and the Automotive industry requires increased efforts to provide kernel support for novel devices being manufactured at pace; this project, a small step in the similar direction, aims to implement an IIO driver for Analog Devices, Inc.’s (ADI) ADXRS290 gyroscope with support of IIO Channels, Buffers, Triggers and Events for both its pitch and roll axes.</p> <p>The ultimate goal is to:</p> <ul> <li>merge ADXRS290's compatible driver upstream to ADI's kernel tree</li> <li>deliver corresponding ABI documentation</li> <li>implement device-tree bindings for ADXRS290 in YAML</li> <li>exhibit a working example with the evaluation board on Raspberry Pi 3B, utilizing the SPI protocol.</li> </ul>
<p>The goal of this project is to improve internationalization (i18n) support in Godot. In particular, we wish to make the localization process simpler for users, and also enhance the existing system to support more features. Work includes:</p> <ul> <li>Building in-house tools in the editor to generate translation template (POT) files and smoothen some of the localization process for users.</li> <li>Adding extra functionalities to existing i18n system such as plurals support, context support and translators' comments generation.</li> </ul>
<p>The project aims to create tools that will simplify the manual process of switching between two architectures (crossgrading) and to make it a supported Debian feature.</p> <p>Two tools will be made to complete the crossgrading of a Debian installation: one to verify the system is ready for crossgrading, and another to complete and log the crossgrading process.</p>
<p>Terasology uses a desktop launcher to help users manage different game versions and tweak additional settings. The launcher is developed using JavaFX, but the mode of distribution of JavaFX has caused multiple issues for users. This project proposes to enhance the launcher while continuing the use of JavaFX and embedding a runtime to provide a hassle-free experience for end-users who don’t have Java installed.</p>
<p>Software License compliance is very important for any business/ OSS(open source software) nowadays which creates a need for more accurate license scanning. So, the aim of the project is to develop a new/improved license text scanner using different approaches so that one can generate an SPDX file and other copyright files with accuracy and thus the process can be automated.”</p>
<p>Hello. As a part of Google Summer Code of 2017, the main task that I intend to take up is to increase the number of the functions present in the <a href="https://github.com/JuliaAstro/AstroLib.jl" target="_blank">AstroLib.jl</a> package, chiefly by porting an extensive portion of the IDL <a href="https://idlastro.gsfc.nasa.gov/homepage.html" target="_blank">Astronomy User’s Library</a> procedures not present in the package.</p> <p>The project involves translating the code from IDL - <a href="https://idlastro.gsfc.nasa.gov/homepage.html" target="_blank">Interactive Data Language</a> - to <a href="https://github.com/JuliaLang/julia" target="_blank">Julia</a>, a relatively new high-level dynamic programming language designed to address the needs of high-performance numerical analysis and computational science. This will greatly increase the range of utilities present in the AstroLib.jl package, making it much more useful for users.</p> <p>A sample of what this project will entail can be seen through the following pull requests on Github - <a href="https://github.com/JuliaAstro/AstroLib.jl/pull/10" target="_blank">#10</a> and <a href="https://github.com/JuliaAstro/AstroLib.jl/pull/13" target="_blank">#13</a></p>
<p>The objective of the project is to improve accuracy of objects' descriptions generated by the RoboSherlock package in difficult environments. Glossy transparent objects can not be properly detected by off-the-shelf RGB-D cameras which use infrared structured light, like Kinect. Or as another example occluded object may be not properly classified or even segmented as one peace. So the goal of this project is to study and implement algorithms which will address such problems.</p>
HPX already has partial Tracy support and stronger integrations with tools like VTune and APEX, but tracing is still fragmented and largely thread-centric. This makes it difficult to understand how tasks actually behave, especially across suspension, resumption, and asynchronous dependencies. This project focuses on strengthening and extending Tracy integration in HPX by building on the existing hpx::tracing abstraction and expanding task-level instrumentation across key runtime paths. The goal is to make task execution easier to follow by improving lifecycle visibility, especially around suspend/resume behavior, and by adding initial causal signals (for example, future fulfillment and other synchronization events) to help explain why tasks resume. The work will also extend tracing to execution paths that currently lack visibility, such as fork_join_executor and continuation execution, and introduce scalable controls like filtering and sampling to keep tracing usable in fine-grained workloads. As a stretch goal, I will explore optional trace-context propagation across parcel paths to enable cross-locality correlation in distributed runs. The expected deliverables include integrated tracing hooks across core runtime components, improved suspend/resume tracing, better coverage of executor and continuation paths, benchmark-validated low-overhead operation, and clear documentation for both maintainers and users.
MWoffliner is a tool for scraping MediaWiki content into ZIM files for offline access, but its current architecture has significant maintainability and testability issues. The codebase suffers from singleton patterns preventing parallel execution, monolithic files, circular dependency cycles, code quality issues and tests that require full infrastructure that take a while to run. I'll deliver a comprehensive architectural refactoring that introduces dependency injection, breaks up monolithic files and singletons, implements storage abstraction for fast unit testing, restructures the directory organization, and optimizes the article processing pipeline all along with improved code quality. This refactoring will eliminate circular dependencies, enable tests to run without infrastructure, improve code modularity and architecture along with performance.
This would be an update of the existing Django shell that auto-imports models for you from your app/project. Also, the goal would be to allow the user to subclass this shell to customize its behavior and import extra things.
The project aims to seamlessly integrate JAX's jit and auto-differentiation functionalities into QuTiP, a quantum computing simulation library, enhancing its computational capabilities. Deliverables include cataloging JAX support in QuTiP functions, adding JAX functionality with clear documentation, designing interfaces for smooth integration, and creating example notebooks for practical usage. Emphasizing advanced applications and user-friendly interfaces, the project prioritizes example notebooks demonstrating quantum control optimization tasks, along with intuitive interface designs like decorator-based integration and hybrid solvers. This project not only improves QuTiP's efficiency but also serves as an educational resource, showcasing the synergy between cutting-edge quantum computing and machine learning techniques.
Bowtie is a meta-validator of the JSON Schema specification, giving users a way to use and compare implementations supported. Bowtie currently only supports validating instances against a given JSON Schema using the specified implementation and comparing implementations to one another on the basis of how correct an implementation is wrt the JSON Schema specification. This project primarily focuses on creating a performance tester for implementations and integrating it within Bowtie itself. This would allow implementations to be performance tested and also the comparison b/w the performance of implementations enabling performance optimisation of the various implementations giving users another dimension to compare different implementations on.
mesa is renowned as the premier Python framework for agent-based modeling, combining powerful functionality with ease of use. However, the framework's reliance on standard Python objects to represent agents poses scalability challenges, hindering performance as the number of agents grows. This limitation renders the execution of even modestly sized models, comprising a few thousand agents, impractical. The community has long requested a more performant version of mesa. While a refactor using Cython could address performance issues, it would introduce significant complexity and require users to adapt their methods to Cython, compromising Python's simplicity. The mesa-frames initiative proposes leveraging vectorized operations on dataframes, utilizing libraries such as pandas and polars, to enhance performance and scalability. This approach benefits from the optimized, out-of-the-box operations these libraries provide and their intuitive, well-documented APIs, which simplify custom agent creation.
Currently, the properties for the screen1 form contains a number of project project-wide properties such as App Name, Theme and many more. We want these properties separated from the component and maintained on a separate dialog on the designer view.
FreeBSD supports multiple architectures, file systems, and disk-partitioning schemes. Currently, there is a script named full-test.sh located in src/tools/boot/ that creates several of these environments but does not test all of them. The proposed idea is to rewrite the script in a language such as Python or Lua, which would allow for testing of all the architecture combinations supported in the first and second-tier support, and provide a report on any broken combinations and expected functionality. Additionally, providing Linux Boot support using Linux EFI shim(EDK) II for amd64 and arm64. If time permits, further exploration could be done to integrate the script into the existing build infrastructure (either Jenkins or Github Actions) to generate a comprehensive summary of the test results.
TiSpark maintains a com.pingcap.tikv/tikv-client module. It is a fork of the current official tikv-client legacy version. The difference from the current official tikv-client is that some TiSpark-specific enhancements have been added. This makes enhancements, bug fixes made for TiSpark tikv-client not affecting the official tikv-client and vice versa. We want to normalize the Java client and use the official one. Do not break original functionality and guarantee consistent behavior.
GNOME Network Displays uses Miracast for sharing displays and windows currently. This proposal plans to add support for Chromecast and allow users to cast their screens/windows, share local and remote videos, and play audio on Chromecast receiver devices.
The project proposes to implement the landing/home page for Pocket Paint, which will be a gallery kind of a view in which the user will be able able to see a preview of the images. This landing page will be the first view on opening the app and will allow the users to see all of the drawings that they have worked on or created with Paintroid and quickly select one to continue editing it or start afresh by creating a blank drawing. These images will also include .ora and .catrobat-image files as previews. The landing page will be similar to the one that has already been implemented in Pocket Code.
<p>As noted by SimonPoole, the current opening hours parser lacks a complete evaluator for its input opening hours. This project will center around building an evaluator to determine if an input of date and time translate to being opened or closed on the basis of an opening hours string, accommodating sunrise/sunset and holidays information. The evaluators will be in the form of a data structure resembling a compact calendar. The information on sunrise/sunset and holidays are taken externally, possibly using other open-source libraries.</p>
<p>My proposal has 3 parts <em>Making a Separate Repository and Refactoring Simulator Code</em>: The first part is refactoring of the simulator code base. For some time now, the CircuitVerse community has wanted to refactor the current javascript codebase (sample GitHub issues: #199, #110, #190). <em>Testing Simulator Code</em>: With bug fixes and new features being implemented by a growing community of circuitverse it will be essential to test Pull Requests before CircuitVerse admins and maintainers merge them. so the second part of my proposal is adding tests to ensure the basic functionality of the simulator. <em>Electron App</em>: CircuitVerse provides a platform to perform simulations on an online simulator that users don’t have to install, is lightweight and has a lot of features but sadly not everyone has unrestricted access to the internet. This can be one of the reasons why CircuitVerse’s maximum traffic is from developed countries with above-average or good internet connectivity like the USA(26%), India(11%), UK(6%) and Canada(4%). It would be a big step towards increasing accessibility to have an offline App. Hence, I propose the third part of my proposal: An offline electron app for CircuitVerse.</p>