Fetching the latest programs, projects, and workspace data.
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>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>
RubyGems.org currently lacks transparency into critical package registry events such as gem publications, ownership changes, and deletions, making it difficult to detect supply chain compromises or unauthorized modifications. This project proposes implementing a Merkle tree–based transparency log that records these events in an immutable, append-only structure. The log will provide cryptographically verifiable records that allow maintainers to detect unexpected changes and enable security researchers to audit the Ruby ecosystem.
<p><a href="https://github.com/ruby/rbs" target="_blank">RBS</a>, a type annotation language and tool for Ruby, is about to be bundled with Ruby 3.0. Gradual typing with RBS allows Rubyists to enjoy the benefits of static analysis.</p> <p>However, RBS is still a developing technology and its immediate applicability is somewhat unknown. In particular, it is an important task to verify and improve the practicality of RBS in Rails apps, where Ruby is typically used.</p> <p>I'll apply RBS and its related software to real Rails apps and examine their utility. <a href="https://github.com/soutaro/steep" target="_blank">Steep</a>, a static analysis tool that uses RBS, and <a href="https://github.com/pocke/rbs_rails" target="_blank">RBS Rails</a>, a tool that facilitates the use of RBS in Rails apps, will be targeted for the investigation. I aim to complement the implementation and improve its completeness until they reach a practical level.</p>
The project primary objective would be bypassing the current usage of the webview library in Scarpe, feeding directly the HTML and Javascript code to the browser running Ruby and Scarpe directly through WebAssembly. Having done that, the project would focus on bulding an educational playground for writing GUIs through Ruby directly in browser.
<h3>Cap'n Proto RPC implementation </h3> <h4> Project idea</h4> <p>There is already a decent binding of Cap'n Proto in github but it doesn't have RPC. My project consist in extending the existing code by adding a level one RPC implementation by wrapping the existing C++ official classes in ruby.</p> <h4>My proposal includes: </h4> <ul> <li>Risk management.</li> <li>Definition of optimal and sub-optimal solutions.</li> <li>Planning , milestones, and deliverables.</li> <li>The another items requested in "How to work with us".</li> </ul>
<p>In RubyGems.org website, we can search for any kinds of gems you want. However, most programmers use google or any other websites to look for gems which they want to use. So, who is using RubyGems.org? The answer is a beginner and intermediate for Ruby, who are not familiar with CUI but familiar with GUI. Therefore, I propose to add autocomplete and some functions which help GUI familiar people.</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
<p>Gem-web is a tool that capable of providing an interface that allows opening documentation, source code and website of a ruby gem. Integrating it on RubyGems CLI would make this feature available out of the box to all ruby users, improving their productivity, since there would have no need to search this information manually.</p>
<p>Dynamic languages trade some of the compile-time safety properties of statically typed languages for greater flexibility for a programmer to write correct programs that a static compiler would turn down as potentially faulty. There is a recent trend to integrate aspects of both disciplines, commonly by "adding types" to languages originally designed as dynamic.</p> <p>There has been interest in the Ruby community to explore such an approach: Yukihiro Matsumoto devoted his keynote at RubyConf 2014 to the potential implementation of static typing in the language. The topic is complex: a Ruby tightly corseted by types would not be true to the essence of the language.</p> <p>Under a gradual typing discipline, type annotations can be specified at will: interesting parts of the program can be given explicit types and their type safety checked statically. We propose an implementation of gradual typing in Matz's Ruby Interpreter, drawing inspiration from similar additions to other dynamic languages, with strictly optional type annotations consistent with Ruby's DRY and "lazy" philosophy and an evaluation of the practical usefulness of gradual typing.</p>
<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>
Developers using Ruby gems have no official way to know when a gem they depend on has a known security vulnerability. This project integrates vulnerability warnings into RubyGems.org by syncing the rubysec advisory database, implementing version-range matching via Gem::Requirement, and surfacing warnings on gem detail pages, search results, and a new public API endpoint — all with independent implementation to respect GPL licensing boundaries.
<p>Everything that worked with Bundler 1.0 still works with Bundler 1.11, all new features from 1.0 to 1.11 have been incremental additions, without removals or deprecations. Some feature ideas that break backwards compatibility are planned for Bundler 2.0 release.</p> <p>I plan to implement two features related to the first and only bundler security vulnerability, that allowed gems to be installed from a different source than expected. This includes some changes to part of the codebase that is fragile, complex and prone to bugs, to make it a drastically simplified version which would be more stable and easier to maintain.</p>
<p>This is to develop a plugin system for bundler which can be used to add features like CLI commands, new sources for ruby gems and hooks for lifecycle events without modifying the core bundler project. This can enable the community to customise bundler without messing with the core module and also can be used as staging area for future bundler features.</p>
<p>To increase the interoperability of the Galaxy Platform with GA4GH Cloud-compliant solutions, the goal of this project is to add support for the TES to the Galaxy and Pulsar. The runner would be implemented in Galaxy, would be able to convert the job requirements from Galaxy to the job script for TES, and would stage the job on TES remotely and actively manage the sent job until its completion. This would allow Galaxy to distribute the jobs across the TES computational Network. According to the TES specification, the Pulsar REST interface could be modified to bring standardization across the services.</p>
<p>vcf2fhir is a utility to convert VCF files into HL7 FHIR format for genomics-EHR integration. The utility currently converts simple variants (SNVs, MNVs, Indels), along with zygosity and phase relationships, for autosomes, sex chromosomes, and mitochondrial DNA. This project aims to enhance the utility by adding capabilities for the conversion of structural variants (e.g. insertions, deletions, copy number variants).</p>
<p>In this project we will work on the new CC systems (Beluga, Graham, Cedar, Niagara) and potentially mp2 trying to automate the setup of things like the account ID, meaningful default resources limits specific to each system, etc., in order to have zero configuration work done by users before being able to submit jobs. We will also work on creating some built-in safeguards against system abuse by novice users when they use this package. Documentation and tutorials will be easy to read and to understand and will be created at the same time the code is created in order to avoid delays in the delivery of the package. There will be use-case integration with PopSV, a package that could integrate this extension in order to demonstrate how easier this makes life for users of PopSV on CC systems. Time permits, we could potentially provide another software that could benefit from this e.g. SCones.</p>
The aim of this project is to make it easier to use MaveDB datasets for clinical use, as most of the MaveDB datasets are not annotated in a way that allows them to be combined with other genomic data. Datasets in MaveDB will be mapped to the human genome using the GA4GH Variant Representation Specification (VRS). This can be achieved by mapping sequences using alignment algorithms, transforming the results into VRS objects, and validating the results.
<p>The project aims to create a platform for hosting and sharing Vega and Vega-Lite visualizations. It will facilitate a user to save, fork and publish any visualization on the web. It is designed keeping in mind the user-benefits and covers everything from back-end to front-end with few new features. It will be integrated into the editor itself so that the user can conveniently make and share the visualization from the same place. This lowers the barrier to entry into the vega ecosystem.</p>
The goal of this project is to improve the navigability of the HTAN data standards in HTAN portal as well as in schema-visualization. To do this, we will add a 'Search field' on both applications, which would enable users to search through attributes efficiently and display required search results. For the first problem, we have 3 subtasks: adding a Search field to the Standard Page in HTAN portal, displaying search results in the Standard Page, and resolving the issues and bugs in HTAN Portal. To improve schema-visualization navigation, we have 3 subtasks: integration of the search field, incorporation of search filtering results with the existing Data Table, and resolving issues/bugs. Through GSoC, we will focus on these issues and solve them to improve the visualisation data standards.
Build WebGL spatial telemetry panels in Grafana for visualizing physical data center rack thermal sensor metrics.
<p>Making information easily accessible to people, when and where they need it. Part of a greater effort to make Sugar more welcoming and maintainable.</p> <p>Script for end-to-end migration of <a href="https://wiki.sugarlabs.org/go/Activities#Sugar_Activities" target="_blank">activity documentation pages</a> from the Sugar Labs wiki, to GitHub(and simultaneously <a href="https://github.com/godiard/help-activity" target="_blank">help-activity</a>).</p> <h7>Impact:</h7> <ul> <li>Reduction in maintenance efforts.</li> <li>User-documentation moved to help-activity could just be downloaded once, and then read whenever needed; eliminating the need to have persistent internet connectivity.</li> <li>Contextual-help ( <code>alt</code> + <code>shift</code> + <code>h</code> ) from within another sugar-activity could also be made available, when the documentation resides at help-activity.</li> <li>Developer-documentation of sugar-activities, if kept at same place with the source-code in its GitHub-repository; would help developers/maintainers (they could be read and updated easily; without visiting an external link to the wiki).</li> </ul>