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.
The goal of this project is to provide comprehensive documentation of the LALRPOP Parser, Intermediate Code Representation (ICR), and Code Optimization techniques utilized in Solang. Solang is a compiler for the Solidity Programming language, targeting the Ethereum Virtual Machine (EVM) and WebAssembly (Wasm) platforms. The documentation will encompass a detailed exploration of the parser's functionality, the structure of the intermediate representation, and various code optimization strategies employed within Solang. Additionally, we aim to propose improvements and enhancements to these components based on the latest research and advancements in compiler construction. Specifically, we will focus on suggesting advancements in error handling techniques, enhancing the ICR, and introducing more effective code optimization techniques.
There are many bugs being found in the Linux kernel by automated tools, yet not many people available to help fix these. This project will help the applicants choose bugs to fix, work through the problem found, and help get the issue resolved in the Linux kernel by producing a fix or working with the community on a fix. After the end of the project, the applicant will have a much deeper knowledge of many different areas of the Linux kernel and hopefully, many bugs fixed and many patches accepted.
There are many bugs being found in the Linux kernel by automated tools, yet not many people available to help fix these. This project will help the applicants choose bugs to fix, work through the problem found, and help get the issue resolved in the Linux kernel by producing a fix or working with the community on a fix. After the end of the project, the applicant will have a much deeper knowledge of many different areas of the Linux kernel and hopefully, many bugs fixed and many patches accepted.
Interested Interns: DO NOT apply through this platform. Due to a bug, it does not contact the Mentor. Please go to https://wiki.lfnetworking.org/x/EqsZB. Read the complete description. When you a ready to apply send your application documents to your Mentor(s) and mentorship@lfnetworking.org Selected interns will then apply here to finalize their paperwork. ODL CI/CD toolchain, as most of the LFN ones, is based on Jenkins which has developed new key features around Kubernetes not yet implemented by ODL (more generally LFN). As part of ODL IT modernization, the proposal here is to update our system by switching from agents running on baremetal or on virtual machines to containers running on a Kubernetes cluster. The clear first benefit is to make sure that resources are used effectively when testing our patchsets and when building our distributions. But, as important, it also enforces clean isolation between jobs and increase the capability to troubleshot the continuous integration issues more easily. It should be noted that this topic was also discussed during LFN Events in Anuket tracks and many projects could be very interested in these actions.
Update FDC3-electron to support FDC3 2.0 Certify FDC3-electron on FDC3 1.2 and 2.0 Release fdc3-electron into mainstream repositories (NPM) Include 3+ samples in fdc3-electron as default Point fdc3-electron to FINOS global directory if existing Work with FDC3 maintainers to “approve” fdc3-electron as reference implementation and link into fdc3.finos.org
There are many bugs being found in the Linux kernel by automated tools, yet not many people available to help fix these. This project will help the applicants choose bugs to fix, work through the problem found, and help get the issue resolved in the Linux kernel by producing a fix or working with the community on a fix. After the end of the project, the applicant will have a much deeper knowledge of many different areas of the Linux kernel and hopefully, many bugs fixed and many patches accepted.
Users have no ways to update log level of Volcano components now, which is difficult to track bugs especially in the production environment. Your task is to achieve it.
KubeArmor currently uses privileged mode for its daemonset containers. But it is not a good practice. Privileged containers are usually frowned upon. In many cases, specific admission controllers are deployed to not allow containers to be installed in privileged mode. It is best to not use privileged mode but to define specific capabilities for KubeArmor. The aim of the project is to analyse and reduce the system privileges required by KubeArmor, thereby reducing the potential attack surface.
Now Resource Interpreter framework enabled both built-in and customized interpreter, we are going to provide a way for people customize the interpreter by applying a configuration.
SODA API is an open source implementation of SODA API Standards for Data and Storage Management. The effort is to provide a common unified data and storage interface to store, run any data anywhere. This project implements the API Server, Different API services, utilities and more. The implementation will be based on the API standards from The SODA Foundation. It connects the application or client to the storage backends to do data/storage management seamlessly providing a platform and storage agnostic framework. Any application or client platform can implement the interface using the API specification to connect to API or implement northbound plugins to bridge their specifications to SODA API. Currently we support block and file APIs for key features of data management (provisioning, migration, fileshare, etc). for on-prem implementation This is one of the SODA Core Projects and is maintained by SODA Foundation directly. Provides the standardization for Data / Storage Management APIs. Currently we support block and file APIs for key features of data management (provisioning, migration, fileshare, etc). Working to add the storage management APIs. This is the key external interface to platforms, which can do a seamless integration with heterogeneous storage backends.
<p>The primary objective of this project is to analyze the role of mainframe platforms in achieving digital sovereignty and operational resilience within enterprise architectures. The mentee will evaluate the strengths and weaknesses of on-premise mainframe infrastructure compared to public cloud environments, specifically focusing on data residency, regulatory compliance (such as DORA), and resilience models. The research will explore how mainframes address critical sovereignty challenges, including third-party concentration risk and data access governance, where distributed systems may introduce vulnerabilities. Additionally, the project will assess the technical limitations of mainframe-centric strategies, such as skills dependencies, and provide a strategic analysis of hybrid sovereign architectures.</p><p><br></p><p>Deliverables: A whitepaper to be published under the modernization working group banner.</p><p><br></p><p><strong>Applications closing date: 25-Apr-2026</strong></p><p><br></p><p><strong>Mentee confirmation: 10-May-2026</strong></p>
Cello, as a decentralized BaaS, has been able to help users create blockchain networks and achieve channel management. Cello will help users to install, instantiate and test smart contracts. Learning Objectives - Work closely with community experts and developers to learn the open-source culture and skills; - Learn the advanced knowledge inside the blockchain and distributed ledgers; - Practice hand-on experience with web application design and implement; - Cultivate security awareness in software development process.
Magma is an open-source software platform that gives network operators an open, flexible and extendable mobile core network solution. Magma enables better connectivity by: Allowing operators to offer cellular service without vendor lock-in with a modern, open source core network Enabling operators to manage their networks more efficiently with more automation, less downtime, better predictability, and more agility to add new services and applications Enabling federation between existing MNOs and new infrastructure providers for expanding rural infrastructure Allowing operators who are constrained with licensed spectrum to add capacity and reach by using Wi-Fi and CBRS
This LFX Term 3 project will transform the KubeStellar Design System foundations (created in Term 2) into a production-ready implementation using Next.js (Nextra or Mintlify) and deploy it on Oracle Cloud Infrastructure. The project will deliver a unified design language across all KubeStellar interfaces, featuring immersive animations and interactive components that enhance UX while maintaining performance and accessibility. Expected Outcome: 1. Implement the complete KubeStellar Design System as a production-ready component library. 2. Build an interactive documentation site using Nextra or Mintlify. 3. Develop advanced 3D visualizations and micro-interactions using Three.js and animation libraries. 4. Deploy the design system and documentation to Oracle Cloud with enterprise-grade reliability. 5. Establish automated CI/CD pipelines for continuous deployment and semantic versioning. 6. Provide seamless integration paths for all KubeStellar interfaces (web UI, docs, CLI tools). 7. Ensure accessibility compliance while delivering visually engaging experiences.
Currently, Volcano will regard all pods as potential victims in rescheduling, which is not so reasonable in some scenarios. Your task is to implement a pod filter chain to support custom configurations.
Description: When deploying a multi-cluster resource one has to perform certain contortions such as providing a list of other clusters to each cluster. This places a dependency ordering on spinning up new clusters and a requirement for application operators to coordinate with cluster operators. Expected Outcome: Develop a prototype where each cluster only needs to reference a common service definition to discover peers without knowledge of the names or even number of other clusters.
There are many bugs being found in the Linux kernel by automated tools, yet not many people available to help fix these. This project will help the applicants choose bugs to fix, work through the problem found, and help get the issue resolved in the Linux kernel by producing a fix or working with the community on a fix. After the end of the project, the applicant will have a much deeper knowledge of many different areas of the Linux kernel and hopefully, many bugs fixed and many patches accepted.
Orchestrating and tracking the steps and cross-party messages of business collaborations is a key blockchain/distributed ledger technology use case. Several tools have emerged to support blockchain-orchestrated BPM (business process management); an important subset of these takes models of the cooperation, usually captured in the Business Process and Notation (BPMN) language and generate a process manager smart contract from the model. Most of the existing tools target Solidity, and all of them store the business process state in the clear, in the smart contract. This can be problematic even for Hyperledger Fabric – if the process state is not to be seen by the whole consortium, we must resort to the confidentiality toolbox of Fabric (multiple channels, private data collections, etc.). We argue that this is not absolutely necessary. Our prototype implementation already supports Hyperledger Fabric to some extent (originally, we focused primarily on Solidity/EVM). Specifically, we have an implementation of the crucial element, the commitment manager and proof checker chaincode. However, proper support for Fabric needs a number of further improvements – as contributions to our open-source solution, and this is the topic of this mentorship.
OPNFV Internship is for University or College students who are interested in contributing to the OPNFV project. Each intern will be working with a mentor in the OPNFV community to complete a project either in 3 months (full time 40 hours a week) or 6 months (part time 20 hours a week). This is a paid internship program and the internship project can start throughout the year (i.e. not just limited to summer in the northern hemisphere). As an open source project, each intern will work remotely from his or her location of choice. And, we welcome interns from anywhere in the world.
There are many bugs being found in the Linux kernel by automated tools, yet not many people available to help fix these. This project will help the applicants choose bugs to fix, work through the problem found, and help get the issue resolved in the Linux kernel by producing a fix or working with the community on a fix. After the end of the project, the applicant will have a much deeper knowledge of many different areas of the Linux kernel and hopefully, many bugs fixed and many patches accepted.
<p><span style="background-color: transparent; color: rgb(0, 0, 0);">The purpose of this project is to enhance the (</span><a href="https://openssf.org/projects/repository-service-for-tuf/" rel="noopener noreferrer" target="_blank" style="background-color: transparent; color: rgb(17, 85, 204);">Repository Service for TUF RSTUF</a><span style="background-color: transparent; color: rgb(0, 0, 0);">) implementation by tackling critical areas that would significantly improve its functionality, scalability, and ease of adoption. RSTUF is designed to manage content distribution efficiently using the TUF (</span><a href="https://theupdateframework.io/" rel="noopener noreferrer" target="_blank" style="background-color: transparent; color: rgb(17, 85, 204);">The Update Framework</a><span style="background-color: transparent; color: rgb(0, 0, 0);">), but it currently has areas where improvements in delegation flexibility, performance, testing, and documentation are needed. This project will allow RSTUF to handle larger and more complex scenarios, while providing an improved experience for both developers and adopters.</span></p><p><br></p><h2><strong style="background-color: transparent; color: rgb(0, 0, 0);">Goal</strong></h2><p><br></p><p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Add support for more signing schemes for hash-bin delegations under custom delegations: </strong><span style="background-color: rgb(255, 255, 255); color: rgb(0, 0, 0);">Enhance the flexibility of RSTUF’s delegation model to allow for more fine-grained delegation control</span></p><p><strong>TUF visualizer</strong>: Integration of a community-developed visualizer into RSTUF's deployment</p><p><strong style="background-color: transparent; color: rgb(0, 0, 0);">Improve documentation to facilitate easier adoption</strong><span style="background-color: transparent; color: rgb(0, 0, 0);">: Enhance the user-facing documentation to make it clearer, more comprehensive, and more accessible for new adopters, thus accelerating the onboarding process.</span></p>
Help us fight climate change through nature-based solutions! The Full Lands INtegration Tool (FLINT) is a platform for estimating greenhouse gas emissions at local, national and global scales. This project aims to improve moja global's documentation by building a community website and adopting consistent standards across our projects.
<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>