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.
There is a RISC-V Vector backend in OpenCV universal intrinsic, but the performance is very poor and only supported fixed vector size with 128 bit. The reason for the performance issue is speculated to be redundant instructions introduced by the wrapper class. And the fundamental problem is that the current design of Universal Intrinsic may not suitable for variable-size(size-less) architecture. So it would be nice to modify the API and implementation of universal intrinsics forvariable-size architectures. And the goal of this project is to optimize the current Universal Intrinsic for RVV, mainly including the following two points. 1. Reduce the overhead of using wrapper class and 2. Support for multiple VLENs The expected outcomes of this project is mainly including 1. a new Universal Intrinsic backend for RVV to opencv_core module 2. a new test cases (modify or add) and make it pass on QEMU
<p>My most favorite thing about Oppia is its Test-Driven-Environment. All these tests (FE, BE, E2E, Lint) will ensure that no new error or bug will be introduced into the system. Since Oppia is one of the most prominent open-source organizations, it needs rigorous testing and 100% coverage.</p> <p>Oppia’s frontend codebase can be broadly classified into four main categories.</p> <p>1.Components</p> <p>2.DIrectives</p> <p>3.Services</p> <p>4.Others</p> <p>We have a total of 205 components. In which, 163 components have 100% coverage. Partially covered components are 42. And finally, uncovered files are 0.</p> <p>We have a total of 203 directives. In which, 15 directives have 100% coverage. Partially covered directives are 188. And finally, uncovered files are 1.</p> <p>We have a total of 333 services. In which, 262 services have 100% coverage. Partially covered services are 71. And finally, uncovered files are 0.</p> <p>By excluding others category, we should thoroughly test and should achieve 100% coverage in components, directives, and service.</p> <p>My primary focus for this project is only unit testing. Although I'll be doing angular migration as an optional entity.</p>
<p>In today’s world, a lot of educated decisions are made using the information collected by robots and are aided by the inferences given by the software agents which make use of the information collected by the other machines and robots. One such crucial field, where the software agents can contribute is “Pedestrian and Vehicle Traffic Monitoring”, where they can help us identify the hotspots and conflict zones like Pedestrian Crossings, Traffic Signals, Traffic jams, etc. The aim of this project will be to achieve this by using detection networks and depth networks or localisation/pose estimation networks or by building upon the existing functionalities like “peopleCounter_SSDCNet” components already present in the robocomp repository. Through this, the information provided by machines like RGB cameras can be exploited maximally to make better decisions based on the density of people and vehicles present in an area.</p>
<p>EvalAI is a platform to host and participate in AI challenges around the globe. To host a challenge, challenge creation is one of the core features which is utilized by challenge hosts to create AI challenges. The idea is to use private GitHub repositories to host the challenge files instead of the zip file. The next step is to build and integrate a continuous deployment pipeline with GitHub so that for every new commit in the challenge repository, the changes are automatically reflected on the UI. We will also build support for tests so that new commits are fully tested before they are pushed to the live challenge hosted on EvalAI. The goal is to enhance the challenge creation experience for challenge hosts and set up a challenge on EvalAI by the challenge hosts involving minimal human effort from the EvalAI team.</p>
<p>This proposal concerns the addition of pose data extraction using OpenPose and the generation of posture and gesture embeddings to Red Hen’s pipelines for processing the NewsScape datasets, and posture and gesture search by example and similarity search to the vitrivr video information retrieval software. The focus is on reorienting some of the existing work towards similarity search in a pilot production environment. Embeddings for static body and hand poses will be created using Spatial (Non-Temporal) Graph Convolutional Networks using triplet loss. Candidates for illustrative gestures will be segmented based upon manually engineered features on skeletons from OpenPose and then embedded using Spatial Temporal Graph Convolutional Networks combined with triplet loss. Functionality for querying using a webcam will be added to vitrivr, and the embedding pipeline will be integrated into cineast</p>
<p>Linear extensions of partially ordered sets are fundamental in order theory and in algebraic combinatorics, holding high importance in the study of permutations and Young tableaux. Computing the number of linear extensions, in general, takes O(n!) time, given a poset of n elements. However, many efficient algorithms are known for certain large classes of posets. SageMath offers a single function to calculate the linear extensions of a poset. For even small posets, this quickly becomes impossible to use. The goal of this project would be to implement efficient methods of computing linear extensions of several important classes of posets, and introduce uniform sampling of linear extensions. This includes tree posets, d-complete posets, skew diagrams, mobile posets, and more.</p>
<p>Enable full application of Time-Frequency Analysis tools on Source Estimate M/EEG neurophysiological data by integrating <code>mne.SourceEstimate</code> objects with <code>mne.time_frequency.tfr</code> functions.</p>
<p>The <strong>Open Event</strong> Project offers event managers a platform to organize all kinds of events including concerts, conferences, summits and regular meetups. The various components support organizers in all stages from event planning to publishing, marketing and ticket sales. Automated web and mobile apps help attendees to get information easily.</p> <p>There are two major divisions of this project:</p> <ol> <li>Implementation of numerous features on the <strong>Open Event Server</strong> in order to make it feature complete. Some of the features that we aimed for were integration of <em>payment system</em>, <em>tickets</em>, <em>taxes</em>, <em>promo codes</em> etc. </li> <li>Integration of missing endpoints and related features on the <strong>Open Event Frontend</strong> and <strong>Open Event Orga</strong> app. Some of the features that we aimed for in the <em>frontend</em> were the implementation of <em>promo codes</em>, <em>notifications</em> while <em>tracks</em> and <em>speakers</em> endpoints were targeted for the orga app.</li> </ol>
<p>With Red Hen Lab’s Rapid Annotator we try to enable researchers worldwide to <em><strong>annotate large chunks of data</strong></em> in a very short period of time with least effort possible and try to get started with minimal training.</p> <p>Rapid annotator is currently a proof-of-concept rather than a finished product. This project aims to deliver a usable product by the end of Google Code of Summer. The <strong>final product</strong> would be a complete tool for fast and simple classification of datasets and an <em><strong>administrative interface</strong></em> for the experimenters where they can conduct their annotation runs. It broadly comprises of 3 steps, namely</p> <ul> <li>Uploading their datasets to setup the experiment.</li> <li>Assigning annotators datasets for annotation.</li> <li>Keeping a track of the annotation progress.</li> </ul> <p>The main aim of the pre-project phase is to do <em><strong>requirements gathering</strong></em>, analysis and <em><strong>designing</strong></em> the complete system architecture. The project phase will deal with implementing the architecture finally decided upon</p>
<p>The goal of the summer project is to revise the current implementation so that it can compute large frequency spectra efficiently. As a result, various inference can be carried on huge sample sizes at a reasonable computation cost. The idea is to track a small subset of entries in the full frequency spectrum and interpolate to recover the full AFS to proceed with integration for larger sample sizes. The key problem is how to recover the frequency spectrum accurately, so several experiments would be carried out to tune parameters and implementations. Also, a framework is expected to be developed for balancing the trade off between computational complexity and data recovery accuracy, that is, deciding which kind of data should be computed with approximation and which should be computed directly.</p>
<p>The project is about building a search engine for life sciences data based on Bioschemas.org . The data is scraped from all the relevant websites and indexed in Apache Solr for querying.</p>
<p>Currently, I/O operations are largely unmanaged, allowing a large number of them to be running concurrently, which increases the amount of random I/O performed by the disk. That can lead to poor performance. While GTask rate-limits the tasks, it cannot be assumed that GLib will always do that and thus Nautilus would benefit from having a mechanism to control the execution of its tasks. That, along with rewriting the operations in a more object-oriented manner will result in better performance and maintainability.</p>
<p>NTFS is a modern, elegant filesystem with support for many advanced features, such as fault tolerance, access control lists, hard links, data redundancy, journaling, transactions, the Common Log File System, compression, and encryption. It is the preferred filesystem for all Windows versions that came after Windows 2000.</p> <p>ReactOS still relies on the simple, limited FAT family of filesystems which are a holdover from the days of DOS. ReactOS has a driver capable of reading files from an NTFS volume, but this driver still lacks write support.</p> <p>My previous Google Summer of Code project improved the stability of the NTFS driver, and made significant advances toward write support. <strong>This project will continue adding write support and aims to make that support merge-worthy.</strong> This will be a major step towards ReactOS' goal of Windows compatibility, and it will be the kind of advancement end-users understand and get excited about. It will also open the door for the development of more advanced operating system features, like journaling and automatic fault-recovery. Having these features will aid development and make the operating system more practical.</p>
<p>The work proposed is to extend the already available, but limited SymEngine's Ruby interface. This project will greatly increase the computational capacities of the SymEngine ruby gem and add interfacing with other ruby gems for mathematical programming.</p> <p>Some of the proposed work are:</p> <ul> <li>Extending the C interface of SymEngine library.</li> <li>Wrapping up the C interface for Ruby using Ruby C API, including error handling.</li> <li>Designing the Ruby interface.</li> <li>Integrating IRuby with symengine gem for better printing and writing IRuby notebooks.</li> <li>Integrating the gem with existing gems like gmp, mpfr and mpc.</li> </ul> <p>At the end of the project, added features will include:</p> <ul> <li>Complex Numbers</li> <li>Floating Points</li> <li>Derivatives</li> <li>Substitutions</li> <li>Abs</li> <li>Series</li> <li>Polynomials</li> <li>Matrices</li> <li>Lambdify</li> <li>Parser</li> <li>LaTex printer</li> </ul>
I would like to volunteer to develop SSH Client/Server support for NuttX. I believe this is a highly valuable feature, as it would enable remote access to NuttX-based hardware in the field for maintenance and operational purposes. With SSH support, we could remotely interact with devices, trigger I/Os, manage peripherals, and perform diagnostics in a way that is conceptually similar to what we already do on Linux-based systems. Also, this is a great opportunity for me to develop my skills. The implementation would be based on Dropbear, a lightweight and complete SSH stack with a small footprint, which makes it well-suited for embedded environments. There is already a reference port available that I plan to use as a development guide: https://github.com/david-cermak/dropbear The project would be structured in the following phases: Initial study phase to assess requirements and dependencies, including evaluation of cryptographic library integration and system constraints. Review of existing ports for other platforms (for example, ESP-IDF) to understand architectural decisions and integration patterns. Porting of the required SSH client and server functionalities to NuttX. Testing, validation, performance assessment, and resolution of identified issues. Mentors: Alan C. Assis, acassis@gmail.com
Mifos Payment Hub EE is a payment orchestration engine that coordinates and routes payment transactions among core banking systems, switches, wallets, and external financial partners. The Payment hub exposes multiple APIs for payment initiation, status queries, partner integrations, and operational management, creating a large surface area for critical risks such as Broken or inconsistent authorisation across endpoints, replay or duplicate payment requests. This project will focus on conducting a comprehensive API security assessment of the Payment Hub API, with emphasis on the OWASP API Security Top 10 and real-world payment threat models. The goal is to identify, document, and help mitigate security vulnerabilities within the system’s RESTful APIs. This project will be centred mainly around: - API Surface Mapping, which deals with enumerating the APIs found in the PaymentHub and identifying the authentication flows, request headers and partner-specific parameters used. - Threat modelling deals with mapping the threats found to the OWASP category - API Penetration Testing focused on the OWASP API Security Top 10 - Tooling and Automation, dealing with developing custom scripts and reusable test cases - Reporting and Remediation, dealing with producing a detailed vulnerability report and providing fixes and mitigation to the different vulnerabilities found. By the end of the project, the following deliverables are expected: 1) A documented Payment Hub EE API threat model and API Penetration testing checklist 2) An automated or semi-automated API security test suite for reusing in other projects 3) A detailed vulnerability assessment report with remediation guidance will be provided to help developers make patches when needed and follow secure API Practices.
The Kolibri Design System contains resources for designers and developers building Kolibri products.KDS ensures accessibility, responsiveness, and cross-browser compatibility across all Kolibri products. Currently, Kolibri Studio relies on Vuetify 1.5.24 for multi-select dropdown functionality an outdated library that conflicts with KDS and blocks Studio's ongoing migration. This project builds a fully accessible multi-select dropdown on native KDS primitives, following the WAI-ARIA APG 1.2 combobox pattern and WCAG 2.1 Level AA from the ground up .Hence, replacing VAutocomplete instances in Studio and laying a foundation for an eventual KDS component.
Ultimate Alarm Clock is a cross-platform Flutter application that needs enhancement with advanced features to provide users with a more comprehensive alarm experience. This project aims to develop 12 key features including negative condition alarms that trigger based on inverse conditions, shared alarm notifications for coordinating wake-up times across multiple devices, timezone-aware alarms, Google Calendar integration, and smart home/IoT integration. Additional features include enhanced snooze customization, sunrise alarms that gradually brighten the screen, task lists for alarms, and advanced alarm insights. The implementation will follow a three-month development plan with regular deliverables, focusing on code quality through UI component standardization and reducing third-party dependencies. The end result will be a significantly enhanced open-source alarm clock application that goes beyond basic functionality to serve modern users' complex scheduling needs while maintaining a clean, intuitive interface across all platforms.
The field of computational biology depends significantly on mathematical modeling to simulate complex biological simulations, often involving solution of large systems of ordinary differential equations, which describe dynamic biological processes. Accurate and efficient numerical solvers are essential for these simulations to predict correct behaviour. LSODA (Livermore Solver for Ordinary Differential equations Automatic) is a well-established ODE solver known for its ability to dynamically switch between stiff and nonstiff methods, making it particularly suitable for biological models where stiffness can vary over time. However, LSODA’s widely used implementations are primarily in C/C++ and Fortran, creating a barrier for researchers working in Java-based environments. This project aims to bridge that gap by implementing a robust, optimized, thoroughly tested, and fully functional Java-based version of the LSODA algorithm within the Systems Biology Simulation Core Library (SBSCL).
This project proposes enhancing RTEMS’ In-Memory File System (IMFS) by introducing configurable memory allocators and improving bytes-per-block handling. By replacing hard-coded malloc/free with user-defined allocators, IMFS gains flexibility for constrained systems. Additionally, stricter validation of block sizes and support for larger blocks (1K–2K) will improve error resilience and scalability.
The goal of this project is to enhance the LicenseDB platform by integrating several important features including advanced database migrations, support for refresh tokens, and a notification system to notify users when a license is updated. In addition, it will require setting up a clean backend and fronted monorepo for simplified development. The improvements will ensure the platform is better, reliable, scalable, and more user-friendly.
Prerequisites: Ubuntu and ROS 2 development environment, no need for specialized hardware. Necessary programming skills: Familiarity with C/C++/Python, CMake, ABI/API. Difficulty level: Medium. Potential mentors: Tomoya Fujita Expected size: 100 hours to 150 hours. Expected outcome: A ROS 2 command line interface ros2cli with doctor sub-command and ros2_documentation. Detailed description: Currently, the ROS 2 doctor subcommand, ros2 doctor, is lacking a lot of useful information, such as ROS environment variables, RMW-specific environment variables, and configuration and service information (number of endpoints, QoS compatibility status, etc). This information is really important and useful for debugging issues with ROS 2, and would greatly improve our ability to support issues reported by our user community. In other words, adding this new information to our existing ROS 2 Doctor command would accelerate community communication and make bug reports much more precise! Aligned with ros2cli development, this project also targets the implementation of improved documentation on how to create an issue report with a new issue template. Reference pull requests: Add default github issue templates, add: get clients, servers info
KinFin is a powerful tool for protein clustering analysis, but its current command-line interface limits accessibility and ease of use. This project aims to develop an intuitive, standalone web-based UI that is also easily integrable with GenomeHubs, enabling researchers to visualise, explore, and analyse protein clustering data efficiently. The UI will include interactive visualisation such as taxonomic heat maps, phylogenetic trees, and cluster distribution plots. Additionally, users will be able to cross-reference results with external genomic resources like MolluscDB and Ensembl. Back-end enhancements will ensure seamless data retrieval and scalability, making KinFin more accessible and impactful for genomic research.