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>The Hiero ecosystem includes a growing number of diverse contributors, repositories, junior committers/committers/maintainers, pull requests, issues, discussions, and quality requirements.</p><p><br></p><p>To build a diverse ecosystem which generates high-quality code, maintainers need to spend a significant amount of time on repetitive coordination tasks such as checking contributor qualifications, validating pull request quality, un-assigning inactive contributors, closing stale issues, creating issues at different difficulties, and ensuring that repository processes are followed consistently.</p><p><br></p><p>We have demonstrated in some SDK repositories many of these maintainer tasks can be automated using custom GitHub action workflows and templates. However, the current setup is fragmented, difficult to customize and scale, and inconsistent across repositories. Different repositories may require different rules, but maintainers still need support to ensure they are working on the most important tasks, and developers need support to help them progress quickly and qualify to gain more responsibilities.</p><p><br></p><p>This mentorship project aims to design and build an automation framework and application for Hiero end-to-end maintainer workflows. The system should support configurable repository automation features that maintainers can turn on or off, depending on the repository context.</p><p><br></p><p>Example user on-boarding workflows:</p><ul><li>Checking contributors are humans</li><li>Checking whether contributors meet contribution requirements before assigning issues</li><li>Offering automatic issue assignment</li><li>Automatically assigning mentors for new contributors</li><li>Issue templates and documentations</li></ul><p>Example pull request review and quality workflows:</p><ul><li>AI issue planning</li><li>AI initial reviewing</li><li>Automated code quality, DCO, GPG, etc checks based on configurable quality requirements</li><li>Automatic review based on configurable quality requirements</li></ul><p>Example developer progression workflows:</p><ul><li>Automatic issue recommendations after a merged pull request to next available issues</li><li>Checking whether advanced contributors meet requirements to progress to JC/committer/maintainer</li></ul><p>Example issue management workflows:</p><ul><li>Managing stale issues or pull requests</li><li>Requesting help or feedback from specified teams based on labels</li></ul><p><br></p><p>A core requirement of the project is to ensure that this automation is reliable, consistent, secure, and scalable enough to be used across a variety of repositories inside Hiero (and one day optionally across LFDT).</p><p><br></p><p>The project should also define clear boundaries for what the automation is allowed to do, how maintainers configure it, and how users can understand or override automated actions when necessary.</p><p>The result should not just be a prototype for a single repository, but a hardened and reusable solution that can serve multiple Hiero repositories with different policies and maintenance needs. </p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/73" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/73</a></p>
<h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Purpose</span></h2><p><span style="color: rgb(0, 0, 0); background-color: transparent;">gittuf is a security layer for Git repositories, allowing for a security policy to be applied independently of the service the repository may be hosted on (e.g. GitHub, Gitlab, Bitbucket, etc…). The purpose of this project is to improve gittuf in several domains, such as functionality, usability, and ease of access for new users.</span></p><p><br></p><h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Goal</span></h2><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Improve gittuf's UI and UX</strong><span style="color: rgb(0, 0, 0); background-color: transparent;">: gittuf is currently driven primarily by a CLI-based workflow. The gittuf TUI is a work-in-progress UX improvement, where users instead interact with gittuf more akin to a traditional desktop program. The TUI is currently basic, and extending its functionality and improving its appearance so that it can be the primary way users interact with gittuf would be ideal.</span></p><p><br></p><p><strong style="color: rgb(0, 0, 0); background-color: transparent;">Enable temporary/time-limited approvals</strong><span style="color: rgb(0, 0, 0); background-color: transparent;">: There may be cases when a developer may need to exercise some discretionary authority and approve something in violation of the policy (e.g. a critical security patch at 4am may not be able to be approved by the full team required in policy). Adding approvals that will satisfy the policy for some duration of time (but not infinitely) would serve to improve this aspect of gittuf.</span></p><p><br></p><h2><span style="color: rgb(0, 0, 0); background-color: transparent;">Desired Outcomes & Deliverables (1-2 mentees)</span></h2><h3><span style="background-color: transparent; color: rgb(67, 67, 67);">Improve gittuf's UI and UX</span></h3><p><span style="background-color: transparent; color: rgb(0, 0, 0);">This project should result in gittuf featuring a polished, first-class TUI, as well as improvements to gittuf's UX in the CLI and API.</span></p><p><br></p><h4><span style="background-color: transparent; color: rgb(102, 102, 102);">Deliverables</span></h4><ul><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Substantial improvements to the gittuf TUI, both functionally and aesthetically.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Supporting documentation for how to use the updated TUI.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Appropriate tests and internal improvements needed to support the upgraded TUI.</span></li></ul><p><br></p><h3><span style="background-color: transparent; color: rgb(67, 67, 67);">Add functionality to gittuf to enable temporary/time-limited approvals</span></h3><p><span style="background-color: transparent; color: rgb(0, 0, 0);">Some changes in a repository may need to violate the policy (e.g. a critical security patch needing to be released at 4am, and only one developer is available to approve changes at the time).</span></p><p><br></p><p><span style="background-color: transparent; color: rgb(0, 0, 0);">A variant of this feature is to allow for changes to be submitted to a repository that must still be reviewed by someone else at a later time. These changes should not be consumed until they are reviewed, but should not necessarily pose a problem for the repository’s policy.</span></p><p><br></p><h4><span style="background-color: transparent; color: rgb(102, 102, 102);">Deliverables</span></h4><ul><li><span style="background-color: transparent; color: rgb(0, 0, 0);">A new feature that enables temporary/time-limited approvals in gittuf, as described above.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Supporting documentation for how to use this new functionality in gittuf.</span></li><li><span style="background-color: transparent; color: rgb(0, 0, 0);">Sufficient tests to ensure the proper operation of this new feature.</span></li></ul><p><br></p>
In order to have a better support of other AI/HPC platforms and GPU, it is necessary to enhance the integration with third-party operators and GPU support.
<p>The current HPX Parallel Algorithms do no support vectorization. This project aims at providing vectorization support to Parallel Algorithms with OpenMP as backend.</p>
Adding support for calculating and analysing spectra from atomic databases to RADIS and building a user-friendly Common API with ExoJAX for interacting with supported databases.
Enhancements for Kyverno Policy Exceptions including support for images and conditions. - Expected Outcome: A future version of Kyverno has enhanced support for its Policy Exception resource.
<p>libavutil is being expanded with a modern way of handling frequency transformation. The project aims to significantly increase the speed of this code on a selected architecture by writing the transformations in assembly.</p>
This project involves extending the Feral library to support more cloud providers, specifically Google Cloud and Vercel, in addition to AWS Lambda, as well as improving the existing support for AWS Lambda.
<p>Add web GL support for texture (u, v) coordinate mapping, add support for additional camera features, and fix bugs in the web GL renderer.</p>
Update the syntax highlighters adding support for macro statements, highlighting commas and parentheses, and support for variables. Also, add new snippets to test different aspects of the syntax highlighting grammar.
Tremor supports a number of other systems to connect one, yet one of the most widespread API's in the cloud world (S3) isn't yet supported. This is a chance to shine and build something many users will enjoy.
Refactor native debugger support for Linux x86, x64 and PPC64, and x86, x64 and AArch64 support for FreeBSD, OpenBSD and NetBSD along with automated testing. Improvements to the already existing Rizin debugger.
Looking forward to add new modules and improvise the module structure, redesign reports which having different format support, moving Sqlalchemy to Elasticsearch, modifying API routes and adding workflow feature support.
<p>Project proposal on issue#4813 about holding multiple SSH keys. As of now, ACS supports only a single SSH key to be added / reset on a VM. Here I propose a project on support of multiple SSH Keys.</p>
<p>Currently, Apache Beam Python SDK has already got support for Google Cloud Storage and Amazon Web Services S3. This project aims to add support for the Azure Blobstore filesystem to the Python SDK.</p>
<h3>Update OpenCV FileStorage</h3> <p>OpenCV FileStorage is very convenient while using C++. I'll update it and also add more features.</p> <p>Aim is to add base64 support, JSON support and other features for FileStorage.</p>
-fbounds-safety is a C language extension designed to prevent out-of-bounds memory accesses. Currently, upstream Clang provides partial support for some annotations such as counted_by. The proposal aims to extend the scope of the currently supported annotations and upstream missing ones.
<p>In this project, my focus will be on improving the snare's ability to clone and serve the pages. Also, I will add support for serving pages with TLS. On Tanner's side, I'll add Postgres support to help tanner maintain sessions for the long term.</p>
This proposal regards mapping histogram data to its underlying function; both of which can be represented as sequences and hence a transformer can and will be used to represent the mapping. This project involves both generating functions and histograms to use as a dataset and implementing and training a transformer to perform the mapping.
<p>This project will bring tab completion support to LuaRocks and any Lua project using the argparse command line parser. Support for generating completion scripts for popular shells will be implemented in argparse. LuaRocks will be updated to use argparse for command line argument handling.</p>
<p>Building a subtitle interface for the current video player. Popular formats of the subtitles would be supported along with multiple subtitles/captions for a single video. In addition to this, the user will be able to customize the subtitles/captions (If they want to, according to their own convenience). After this adding keyboard hotkeys support for the video player.</p>
Container Storage Interface (CSI) is a standard for exposing storage systems to containerized workloads on Kubernetes. The idea is to enhance a few CSI features(e.g. NFS, SMB) and also add e2e, sanity tests to cover those features, e.g. inline volume support, Windows support etc.
Extend the "Chart" functionality on the Study View Page by supporting additional types of charts such as line charts and area charts. Support chart toggle functionality to allow users to select different types of charts for the particular data set. Implement "group chart" functionality to improve UX for chart analysis.
<p>JavaScript Object Notation, in short JSON, is a very common human readable and structured data format. Unfortunately, GNU Octave still lacks builtin support for that data format. Having JSON support, Octave can improve for example it's web service functions, which often exchange JSON data these days.</p>