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>In this project, We’ll create an HTTP library that uses cronet (Chromium’s network stack) under the hood providing better performance, access to modern features (like - QUIC) and being great at handling network uncertainty which is an everyday scenario for mobile apps.</p>
<p>Prometheus is one of the standard-bearing open-source solutions for monitoring and observability. As a Prometheus-as-a-Service platform, Cortex fills in all of these crucial gaps with aplomb and thus provides a complete out-of-the-box solution for even the most demanding monitoring and observability use cases. Currently all querying labels are indexed. This is IO operation and storage heavy. The idea is to reduce that.</p>
<p>Rust's procedural macros can be one of the more complicated and difficult to read sections of any codebase. A well-implemented and easy to use macro greatly improves a codebase by removing boilerplate code and user-facing complexity. My goal for the internship is to make the <code>ruma</code> macro crates readable and easy for newcomers to follow and add to. This will allow easier debugging and enable more people to review pull requests in the code-gen heavy crates. I plan to implement macro testing using <a href="https://github.com/dtolnay/trybuild" target="_blank">trybuild</a> or <a href="https://github.com/eupn/macrotest" target="_blank">macrotest</a> for both <code>ruma-events</code> and <code>ruma-api</code>. I will improve the error messages of the <code>proc_macro</code>s in <code>ruma-api</code> and <code>ruma-events</code> by using relevant spans and crafting helpful suggestions or examples to emit to the compiler, so the user knows exactly where and how to fix their code.</p> <p>The other goal of the project is to implement new code generation macros for the next breaking release version of <code>ruma-events</code>. The release will contain a major rewrite of how the event types are structured themselves and within collections. I will work on generating code for the new collection types and adapt existing code generation to the new API.</p>
<p>coala plugin for JetBrains IDEs that supports linting of files using coala right within the IDE. The plugin would provide a unified experience for the developer to keep their code files clean and readable, without ever leaving the IDE, and hindering the development workflow.</p>
<p>The project aims to add the functionality of Service Accounts in the existing Rocket.Chat application. Service accounts will be an upgrade to regular user accounts, they will have a well-defined purpose. Regular users can subscribe to this account to get information regarding the context mentioned in the description of the Service account.</p>
<p>The Webpack Dev Server is designed to make development of Webpack projects efficient, customizable, and possible on older browsers. During this project, I will introduce native WebSockets on the client and ws on the server as the new default Dev Server implementation, while also allowing the user to provide their own client-server implementation. I will improve upon API/CLI uniformity, which has made the Dev Server difficult for users to work with in the past. Finally, I will fully implement the Dev Server into webpack-cli, and I will create core Webpack features that allow the Dev Server to more easily interact with the Webpack Compiler.</p>
<p>Project aims at updating existing functions to make them compatible with Tensorflow 2.0 and adding new image processing operations to make the overall processing faster as in the earlier case image processing was done with other library and then the data is used for training.</p>
<p>The aim of this project is to investigate and propose a plan for <em>separation of Servo script crate</em>. Script crate lays in the core of the Servo and requires a large amount of memory to build. Large memory requirements make it impossible to build on 32-bit computers and slowdown development.</p>
<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>
<p>Free UK Genealogy will be launching a new project to expose genealogical information from wills and probate books. These books record the date and location of people's deaths, their occupations, and often the same information about the family members that executed the wills.</p> <p>In previous projects, all this material was transcribed manually by volunteers, as the source documents were handwritten. The probate books are different, however, in that they are printed and thus are accessible to OCR. We should be able to use OCR text to seed a database by parsing the text for names, dates, occupations, and relationships. We should also be able to use OCR bounding box coordinates to associate regions of a scanned page with an entry for presentation to researchers or for correction by volunteers.</p>
<p>The info program is very bare-bones (no fonts or images). On the other hand, the info program has a number of conveniences for browsing documentation, and the keyboard-centric user interface is very efficient.</p> <p>The main goal is to re-implement the user-interface features of the terminal-based info program (such as convenient keyboard navigation from a document), but in the context of a web browser displaying xhtml.</p> <p>The features of the info program that we would like to replicate in JavaScript include:</p> <pre><code>- Keyboard-centric UI - Fast, responsive UI - Index search </code></pre>
<p>TSP is a Ruby on Rails based application to manage the requests and reimbursements from travel help programs of free software organizations. Originally developed for the openSUSE Travel Support Program it was adopted recently by the KDE e.V. Travel Cost Reimbursement initiative.</p> <p>However currently its lacks some features and is less flexible. This project is about making the tool more useful for KDE e.V. and possible future adopters. The new features such as adding an event organizer to manage the events, a feature to send email to the event participants. It also include migrating the UI framework Bootstrap to the latest version and to move the DSL from the models to the configuration files.</p>
<p>Author of glutton have proposed some new functionalities to be added in Glutton, like:</p> <ul> <li>Spawn Containers</li> <li>Support of YARA</li> </ul> <p>I will make code for those functionalities. Furthermore I want to add the support for https MITM in Glutton and a management interface that can help the administrator to track the number of established connections or connections per services, so that they have control over their honeypot. Admins will also be able to terminate a specific connection, if it gets into too much mischief.</p>
<p>The main idea of the project is to define program repairs, which make the program closest to its oracle.</p> <p>Initially, we have a program, which is implemented in an incorrect way. We apply some fix options in the form of simple syntactic changes to it. Then, we run the same set of inputs on the oracle program and the repaired versions of the program. Using SPF and Green we calculate the percentage of the inputs for which the oracle program and the repaired program produce the same outputs. This percentage is the indicator of the quality of each fix.</p>
<p>Map/Reduce frameworks are getting more and more popular for big data processing (for example Hadoop). By utilising the unified and standards conforming API of the HPX runtime system, we believe to be able to perfectly represent the Map/Reduce programming model. Many applications would benefit from direct support in HPX. This might include adding Hypertable or similar libraries to the mix to handle the large data sets Map/Reduce is usually used with.</p>
circt-bmc can already prove when an assertion is falsifiable, but it does not yet produce the counterexample trace format hardware developers rely on for debugging. Today, users get a SAT/UNSAT result without a practical cycle-by-cycle waveform showing how the design reached failure. This project adds that missing debugging path. I will preserve meaningful signal identities before lowering, track the corresponding solver expressions across BMC timesteps, and evaluate those expressions against the first satisfying Z3 model. The implementation is intentionally staged: first a readable text counterexample for the failing prefix, then VCD waveform generation from the same trace data. The focus is the first-failure prefix (cycle 0 to the violating step), which delivers high user value with low integration risk and clean upstreamability. Deliverables: 1. Signal tracking and naming pipeline for user-relevant values (ports, externalized registers, selected internals where remapping is reliable). 2. A BMC trace runtime component that records per-step solver ASTs and supports model-driven trace emission. 3. Midterm milestone: first-failure text counterexample dump. 4. Final milestone: VCD waveform output for the same counterexample path, exposed through circt-bmc CLI flags. 5. Upstream-quality tests and documentation (IR-level + end-to-end regressions, including failing and no-violation cases).
This project aims to transform how analysts interact with threat intelligence data in IntelOwl by introducing a conversational AI interface. Currently, analysts must manually navigate dashboards, query APIs, and correlate results across different jobs and investigations. To solve this, I will integrate a privacy-preserving, self-hosted LLM chatbot using Ollama and a LangChain ReAct agent. The agent will be equipped with custom tools to query IntelOwl's internal REST API using natural language. Key deliverables include: 1) A new Django chatbot app handling WebSocket connections via Django Channels for real-time token streaming. 2) Ollama Docker integration with CPU/GPU auto-detection. 3) A native React chat component embedded in the existing frontend. 4) Custom LLM tools for triggering analyses and searching data models. 5) Comprehensive test coverage and detailed documentation for users and future maintainers.
To build a DJ application with two decks in Pharo, I will make use of three libraries: Phausto for audio file playback (at variable speed), equalization, and filtering. Spec for building a browser to visualize audio files in a folder together with their metadata, and to organize these files into playlists. Bloc for the visualization of audio waveforms and the rendering of UI widgets to control playback speed, pitch, levels, the equalizer, and filter cutoff and resonance. As a first step, Phausto will be used to load and simultaneously play two audio files, mixing them via the Phausto API. Once the audio engine is in place, a Spec application will be built to browse audio files and load them into either of the two decks. With the file browser complete, a conventional user interface will be added to control the mix between the two tracks and their equalization. The Phausto standard library will then be used to add a delay effect per deck. With the DJ application running, final polish can be applied in the form of BPM detection and track quantization, which requires implementing peak detection for audio files within Pharo. Deliverables: The Spec application with audio file browsing and audio playback will be delivered before the first evaluation. The audio visualization and UI built with Bloc will be delivered halfway between the first and final evaluations. Extra features (BPM detection and quantization) will be added and tested before the final evaluation.
The current OpenKruise Rollout implementation for Deployment progressive delivery mutates the updateStrategy to Recreate, creating a dangerous risk window: if the Deployment is not properly paused during rollout disable, removal, or controller crash, all pods could be simultaneously recreated, causing a service outage (ref openkruise/rollouts#305). This project implements a safer alternative by keeping the Deployment strategy as RollingUpdate and leveraging minReadySeconds and progressDeadlineSeconds to control the delivery pace. Updated pods remain in a "Ready but not Available" state, giving the Rollout controller precise batch-level control without the catastrophic failure mode of the current approach. Deliverables: 1. A new minReadySeconds-based progressive delivery implementation for Deployment in OpenKruise Rollout 2. End-to-end test suite covering normal rollout, rollback, controller crash recovery, and edge cases 3. Documentation for the new deployment strategy mode
RUXAILAB supports five study types but lacks focus group functionality. This project adds FOCUS_GROUP as a new study type under the Inquiry category, delivering structured session configuration with discussion guides, real-time multi-participant data capture via Firebase RTDB, manual thematic structuring, and NLP-assisted analysis through cost-tiered Python Cloud Functions. Core deliverables include the full focus group lifecycle - create, configure, run, capture, persist, and analyze - following the established Heuristic module architecture. Stretch goals include a LiveKit SFU integration for reliable video, sentiment-analysis-api integration for audio sessions, and a PDF report generator.
My proposal is to create and control computer-generated images of breast cancer tissues. I'll spend my first four weeks building basic models called VAEs that can learn what cancer looks like. Then I'll spend four weeks making better, sharper images using GANs. In my final four weeks, I'll try the newest technology called diffusion models to make the most realistic images. I'm using 400 real cancer tissue images that doctors have labeled from normal to severe cancer. My goal is to help train doctors and improve cancer detection systems by creating realistic fake images we can control. This matters because real cancer images are hard to get, and doctors sometimes disagree on what they see. If I succeed, my computer models will let users adjust how severe the cancer looks in an image, which could help with teaching and testing new cancer detection software.
Open Climate Fix recent Cloudcasting model is able to predict clouds movements very accurately but for end user it’s hard to see or visualize the results, this project aims to create a new dashboard similar to quartz-frontend that is already up and running, to visualize results from the cloudcasting model the dashboard will be build using Next.js and MapBox as base map layer, Sentry to log errors, and a minimal fastapi server written in python to preprocess zaar data and serve it to the frontend, this solution will be a proof of concept for the new MVP
Beacon is a cross platform mobile application made with Flutter for the frontend and supported by Node.js and GraphQL for the backend. It's a handy tool for planning and managing group hikes, offering features like tracking leaders location in real-time, showing routes dynamically, sending emergency alerts, and easily sharing locations. Using Flutter makes Beacon easy to use on different devices. By connecting with Node.js and GraphQL, it ensures quick updates and smooth navigation during hikes, making outdoor adventures safer and more enjoyable for everyone involved.
Project synopsis / summary: This project is dedicated to developing a set of automated tools and processes for extracting useful neuronal experimental data from datasets provided by the Allen Brain Institute, and converting these data into parameters that can be used for neuronal modeling on the NetPyNE platform, for comparison with cortical regions already validated by NetPyNE. The project flow is divided into the following steps: Data Collection: Automatically extracts data from the Allen Cell Type Database for specific cell types in the visual cortex, including electrophysiological properties, morphological characteristics, and gene expression patterns. The Allen Institute provides a powerful API that allows users to programmatically access and retrieve data. First through data cleaning, and then through data crawling to obtain data that is difficult to access in the API. In addition, domain-specific language models will be fine-tuned or trained using Google's Gemini model for subsequent data acquisition. Parameter Conversion: Develop tools(scripts) or design large language model prompts to automatically convert extracted data into a parameter format understood by the NetPyNE, such as .hoc or .swc format. Identify how to set reasonable default values for missing data. Model construction: Use the converted parameters to construct neural network models of relevant brain regions in NetPyNE. This includes defining neuron types, neuron connectivity, and synaptic interactions between neurons. Run Simulation: Run a simulation of the model in NetPyNE to simulate the brain's response to a specific input stimulus. Compare Results: Compare the simulation results with actual biological experimental data to verify the accuracy of the model. Intended set of deliverables: Automated Data Collection Tool. Parameter Conversion Script. Simulation Run Framework. Result Validation Report. Documentation and User Guide.