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>My project would re-implement the <a href="https://github.com/bundler/bundler-api" target="_blank">Bundler API</a> on the <a href="https://github.com/rubygems/rubygems.org" target="_blank">Rails app that provides RubyGems.org</a>. Bundler uses bundler-api to download dependency information about all the gems it is trying to install. This request for complex database queries, marshalling the output and everything else is quite CPU intensive and rubygem.org limited hardware infrastructure could not support it until now. With help of <a href="https://rubytogether.org/" target="_blank">Ruby Together</a>, hopefully we will make <code>bundle install</code> faster and more reliable for everyone.</p>
This project aims to improve feature parity between TruffleRuby and CRuby in places where full Ruby 3.0 feature parity has not been achieved, aiming at Ruby 3.0 pattern matching specifically.
Ruby uses garbage collection (GC) to automatically reclaim memory that was allocated by a program, but no longer used. Consequently, users do not have to manually manage memory, and can more easily avoid memory management issues such as memory leak. However, the program being executed must be stopped for the GC to run. Therefore the efficiency of the GC algorithm will affect the performance of the program. The project’s goal is to reduce the cost of GC when there are multiple fibers. Fibers are a memory efficient way to implement cooperative concurrency. Programmers control scheduling of the fiber instead of the operating system, making it possible to better allocate CPU resources. Ruby 3.0, released in 2020, added a Fiber Scheduler, which enables asynchronous behaviour in programs. Ruby’s GC scans through a program’s memory at various points during its execution, identifies which objects are no longer used, and removes them using an incremental tri-color mark and sweep algorithm and generational garbage collection. Improving the GC cost when there are many fibers will enhance the performance of Ruby programs, particularly asynchronous Ruby programs making use of fibers. Deliverables: 1. Reproducible test that triggers GC for fibers 2. Identification of GC bottlenecks for fibers 3. Reduction of bottlenecks compared to benchmark test through improvements to GC 4. Documentation of the above
<p><strong><em><a href="https://github.com/rails/web-console" target="_blank">Web Console</a></em></strong> is a debugging tool for the web apps built with Ruby on Rails. In order to debug, it provides an interactive Ruby session to the developers. The console is displayed in the current page of the browser, and its session stores context of running code of the web app. It allows us to debug the web apps interactively.</p> <p>This project aims to make a better user experience for Web Console as a whole, and the main focus is to support <strong><em>"auto-completion"</em></strong> feature, which is to help us typing commands speedy and quickly on the console.</p> <p>And also, this project is getting into ways to extend Web Console. The other goal of the project is to create <strong><em>"built-in commands"</em></strong> and its architecture, which makes Web Console more extendable, and it can open the door to yet another contributors.</p> <p>A point worthy of special mention is that the above features are working on the inner of console, and it basically does not need new things for the HTML view of Web Console.</p> <p>Details: <a href="https://github.com/sh19910711/google-summer-of-code-2016" target="_blank">https://github.com/sh19910711/google-summer-of-code-2016</a></p>
<p><code>gem owner -a/r</code> command is used to add or remove owners by an email. We will add options for adding/removing gem owners via Web UI. Additionally, we will make owner add/remove events notifiable, i.e. users can opt-in to receive email notification about ownership changes of a gem.</p> <p>We will also add a new flow for ownership transfers. Any gem owner <code>looking for maintainers</code> will be able to create <code>ownership request</code>. Any user can make an <code>ownership application</code> for any gem with less than 100,000 downloads and older than 12 months updated at time or gems which are marked as looking for maintainers. When a gem owner approves an <code>ownership application</code>, the requester would be added as an owner to the gem. These <code>ownership requests</code> will be searchable and listed on a site wide link.</p>
<h3>GSoC 2021 Proposal: Tests for debugger</h3> <h4>Overview</h4> <p>debug.rb is a replacement of the traditional lib/debug.rb standard library which is implemented by set_trace_func. New debug.rb has several advantages. However, it is hard to write test codes for them.</p> <h4>Proposal</h4> <p>This is a proposal to implement tests for a debugger based on deivid-rodriguez/byebug: Debugging in Ruby 2. Test codes for byebug consist of two parts. The first part is the test framework for test byebug. It extends minitest. The second part is tests for byebug using the test framework. It doesn’t test each method, but situations such as the existence of a breakline. I will implement test codes for debugger referring to them.</p>
Ruby 3 introduced Ractors, which allow true concurrency in the language. However, Ruby's stop-the-world Garbage Collector (GC) pauses all of the Ractors when doing Garbage Collection. This diminishes the efficiency of using Ractors. This project proposes to modify the Ruby GC to improve its performance with Ractors, ideally by having only one Ractor paused at a time. The idea is to investigate the ways in which the GC can avoid interfering with objects belonging to Ractors that it is not working on, which would allow these Ractors to continue unhindered during Garbage Collection. The final objective would be to have code for an improved version of Ruby's GC with measurable gains in efficiency.
<p>As mentioned in the listing for Bundler-related ideas, "Once an open source project has taken off and become popular and widely used, writing code and implementing new features has to take a back seat to accepting bug reports, assisting users, and ensuring that contributed changes work together without causing problems for a different set of users. This project idea basically consists of the chance to participate in the ongoing work of maintaining and administrating an extremely popular open source project. It will include triaging bug reports, updating documentation, managing fixes and features across multiple release branches, releasing new versions, and communicating with the public. This project is most suitable for students interested in continuing to work in open source, either as a hobby or a job, as they continue in their career as a software developer."</p>
Scarpe is a project designed to resurrect the shoes library using modern technology. This project aims to leverage an HTML/CSS/JS/RUBY stack to develop GUI apps, which can be deployed across various platforms.. The primary objective of Scarpe is to bring it closer to shoes by ensuring that all known examples run seamlessly. The project also aims to create comprehensive documentation and build an official Scarpe website to provide easy access to project resources. Furthermore, there are plans to make Glimmer lib UI an efficient secondary display service. Scarpe represents a significant opportunity to modernize the shoes library and bring it to a wider audience
Building modern Text User Interfaces (TUIs) often forces developers to choose between writing complex, low-level terminal sequence code or adopting restrictive, framework-specific solutions. This project addresses this fragmentation by bringing the universally beloved, declarative Shoes GUI DSL (via the Scarpe project) to the terminal environment, allowing developers to build complex CLI applications intuitively. The proposed solution leverages a robust, dual-language architecture. The frontend consists of a pure-Ruby DSL where developers define UI layouts and business logic. The backend is a custom-built, high-performance Rust rendering engine responsible for flexbox-like layout calculations, double-buffered differential rendering, and non-blocking event polling. These two layers communicate seamlessly in real-time through a memory-safe C-FFI (Foreign Function Interface) bridge, ensuring the Ruby VM is never blocked by terminal I/O. By the end of the project, the clearly defined deliverables are: 1) A Universal Low-Level TUI C-API: A standalone Rust rendering engine exposing a clean C-ABI, making it usable not just by Ruby, but by any FFI-capable programming language. 2) The scarpe-tui Ruby Backend: A complete mapping of core Shoes elements (stack, flow, button, edit_line, styling, and clipping) to the terminal grid. 3) An Advanced Showcase Demo: A complex, asynchronous CLI application (inspired by "Claude Code") featuring scrollable histories and bidirectional data flow, proving the framework's readiness for real-world production use. 4) Comprehensive Documentation and Test Suites: Ensuring maintainability and easy community adoption.
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.
<p>Ruby has no native ByteArray or ByteBuffer types, unlike Java. While it'd be great to have something like this in core Ruby, the next best place would be in the New IO for Ruby project, which provides a thin wrapper around Java NIO. The goal of this project would be to wrap Java ByteBuffers (particularly direct ByteBuffers) in a Ruby class that can also be implemented in pure Ruby which hooks into nio4r and can be used directly with nio4r's Java NIO backend.</p>
<p>This project would add a feature on the rubygems.org website to give an option on each gem web page to show a tree/DAG of all transitive dependencies needed by that gem. In one of the issues that lead to this project, a user talks about how some users download a gem based of it’s transitive dependencies and how they need to keep a mindmap of these transitive dependencies to conclude whether or not to use the gem. This project will help such users get a better idea of whether that gem is for them or not.</p>
<h3>Writing of RBS Files</h3> <ul> <li>Ruby is an extremely easy to use, syntactically elegant, dynamically typed language. </li> <li>Ruby announced the release of RBS, a syntax language to describe the structure of Ruby programs, with the release of version 3.0</li> <li>RBS is an extremely useful tool chain that can be used to run static type checks on your Ruby programs to prevent type mismatch errors to the maximum extent.</li> <li>This project mainly aims at providing RBS files for third party gems, integrating it with the RBS CLI so that Ruby developers can utilize these files to run type checks on their programs. </li> <li>This project also aims at fixing/improving the functionality of the current RBS tool chain, since RBS tool chain is a recent initiative undertaken by the Ruby Core Team.</li> </ul>
<p>The tool used in cBioPortal for network visualization is a powerful one with many implemented features. However, researchers and biologists are more comfortable with a simplified network view, which represents diagrams of curated The Cancer Genome Atlas (TCGA) pathways. With the aim to have a more attractive and intuitive tool for the biologists, PathwayMapper project was developed, which provides more intuitive pathway diagrams supported with cBioPortal’s rich data. For this project, I hope to help in implementation of a new version of PathwayMapper, which will include new features as well as making it more user friendly and easier to be used. Furthermore, I'd like to do the necessary integration to the portal pages such that PathwayMapper capabilities are more conveniently reachable to portal users.</p>
The current Integration Test coverage is still low. This project aims at extending and creating more Integration Tests to achieve a Test Coverage of at least 60% for the Back end Service and Controller Layer
This project aims to enhance the search capabilities within the OpenELIS system, particularly the Search Patient module, providing users with a more efficient way of retrieving patient information. We aim to integrate a Java search engine library Hibernate Search with an Apache Lucene backend, to index key columns such as patient ID, patient name and other relevant data, providing users a faster way to search results. This will also include the integration of fuzzy search capabilities which will allow for approximate matching based on similarity, wildcard search which will allow for specified pattern matching and range search which will allow for searching for values within a specified range.
<p>This project aims to extend Graphback by adding additional capabilities by building custom plugins. Plugins will provide Data Synchronization and Conflict resolution by optional integration with Debezium. Additionally, this project also aims to prototype an example application using the Graphback runtime with Debezium integration and deploy it using Knative.</p>
<p>Quarkus is a Kubernetes Native Java framework tailored for GraalVM and HotSpot, crafted from best-of-breed Java libraries and standards,which currently is fully supported by Maven build tool which in simple words is used for building and managing any Java-based projects. Gradle is another open source build system which presently isn't supporting all the extensions and core of Quarkus i.e it is in preview mode. To make Gradle support Quarkus completely, we need to have a fairly good understanding of Java and Gradle build tool system. Then studying and comparing the existing Quarkus Maven plugin source code and Quarkus Gradle plugin source code we realize where Quarkus lags behind in the case of Gradle. The points where Quarkus lags can be enhanced by comparing and replicating all the integration tests of Maven plugin for Gradle plugin to increase the overall test coverage for Gradle.</p>
<p>Bookbrainz lacks a feature which allows a person to make a collection of entities (edition, edition-group, work, author, publisher) for his/her future reference. This project is about introducing such a feature - User Collections.</p>
<p>Interactive Exercises for Turtle Blocks having illustrative examples and exercises for Turtle Blocks providing introduction to Programming in Logo with checkpoint based stages built across three difficulty levels: Easy,Medium,Hard covering exhaustive set of exercises starting from building basic shapes and figures such as square , rectangle to algorithmic challenges comprising proving Pythagoras theorem , making mirror images and congruent triangles .</p>
This project aims at adding an integration layer between OpenELIS Global2 and Odoo (OpenERP) in order to add support for Billing functionalities with the OpenELIS Order workflow. The goal of this project is to integrate OpenELIS Global2 with Odoo (OpenERP) to enable automated billing and financial management for laboratory services. This will ensure that when lab orders are placed in OpenELIS, invoices are automatically generated in Odoo, reducing manual data entry and improving efficiency.
By linking their Apple Music account with ListenBrainz, individuals are able to use ListenBrainz to play their music selections. The integration into BrainzPlayer allows for this capability. By utilizing a content resolver, we can match the MusicBrainz Identifier (MBID) to the Apple Music catalog, permitting users to transfer playlists to their Apple Music account.