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.
Hyperledger Caliper is a general-purpose benchmarking tool with the goal of mitigating the aforementioned aspects of performance benchmarking. It allows the implementation/plug-in of custom workload behaviors to meet the diverse criteria of a wide range of business scenarios. Implementing a workload module for Caliper currently has some limitations and usability obstacles. The goal of the project is to provide means for defining complex workload behaviors in Caliper in a declarative manner, using solely/mostly configuration files. This should be accomplished with a general built-in workload module implementation that acts according to a configuration-based workload specification. Expected Outcome The mentee must complete the following tasks by the end of the internship: 1) Survey the workload definition capabilities of relevant workload generators/benchmark tools and typical workload requirements of relevant standards or existing workloads. 2) Specify/design a flexible and extendable YAML-based configuration schema for the declarative definition of complex workloads. 3) Implement a built-in Caliper workload module capable of generating requests based on the above configuration. 4) Thoroughly test the implemented module. 5) Provide developer and user documentation for the schema and the implemented module. 6) Port some of the Caliper microbenchmarks to the declarative schema as proof of concept.
OpenELB is an open-source load balancer implementation designed for exposing the LoadBalancer type of Kubernetes services in bare metal, edge, and virtualization environments. Currently, Currently, the allocation of OpenELB EIP pool and EIP can only be viewed and managed using command in the terminal. We hope to provide a simple web console to make OpenELB much developer-friendly. Users could manage EIP pool and EIP resources using web UI.
The Karmada dashboard has already implemented the management of resources in the control plane. Apart from that, we hope to implement the management of resources in the member cluster: once users add Kubernetes resources and the corresponding policy resources on the control plane, they can switch to the corresponding member cluster seamlessly, check the status of Kubernetes resources in the specific member cluster. Kubernetes dashboard is one of the most popular single-cluster management tools, which uses client-go sdk to communicate with the apiserver to manage resources in the cluster. A great deal of client-go related logic can be extended to muli-cluster easily, due to the karmada-aggregated-apiserver component and the compatibility design between Kubernetes resource and Karmada resoruces. So we hope to combine the Kubernetes dashboard with the karmada-aggregated-apiserver component to implement multi-cluster management in the Karmada dashboard. Expected Outcome: 1. Proposal for multi-cluster management base on karmada-aggregated-apiserver. 2. Tools to lift Kubernetes dashboard with specific version into Karmada dashboard repo, and implement management of resources in member cluster based on karmada-aggregated-apiserver. 3. Typical ui for member-cluster management: a. list/detail/delete/update action for deployment resources. b. log viewer for pod. c. web terminal for pod, which user can attach the running pod, and execute temporary commands.
Machine Learning is a big topic nowadays. WasmEdge already provides [a set of TensorFlow host functions](https://github.com/second-state/wasmedge_tensorflow_interface) to enable the ML inference in WebAssembly. However, these TensorFlow host functions are defined by us and they are just a Wasm function binding from the [TensorFlow C API](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/c/c_api.h). Here comes a standard, the [WASI-NN proposal](https://github.com/WebAssembly/wasi-nn) provides a new way to perform neural network inferencing by using a runtime-provided implementation that can leverage host native optimizations, CPU multi-threading, or powerful hardware devices such as GPUs or TPUs.
KubeArmor supports securing many environments ranging from Kubernetes, unorchestrated containers, bare metal and virtual machines. Our testing matrix however doesn't cover many of these completely. In this project, we plan to improve this coverage by introducing automated testing of some of these environments and improve the scenarios covered in some existing ones. These tests would be written using the Ginkgo framework and automated via GitHub workflows. The matrix we'll target can be found in the upstream issue. Expected Outcome: Improved test coverage; Standards for writing tests for KubeArmor; Stabilization of KubeArmor
Konveyor provides a unified experience of tools to help organizations modernize their applications at scale, transitioning them to Kubernetes and cloud-native technologies. Recently the Konveyor community began the development of a Generative AI approach for application modernization called Konveyor-AI. Konveyor AI accelerates application migration by discovering migration incidents in the source code and providing LLM-generated fixes in a diff view presentation. When proposed changes are accepted, it provides real-time updates on the number of incidents. The presentation side for this work is currently serviced via an IDE extension for VSCode. We aim to expand Konveyor AI by developing an IntelliJ plugin. Our first step involves integrating the static code analysis tool, analyzer-lsp, into the IntelliJ plugin. We plan to create a common module for interaction with analyzer-lsp, which can be used in multiple IDE plugins, starting with VSCode and IntelliJ. Currently, the IntelliJ IDE uses the Konveyor CLI tool, Kantra, for analysis and transformation, but we need to replace Kantra with analyzer-lsp to optimize real-time updates. Expected Outcome: Define and implement a new module or library to facilitate integration of analyzer-lsp into multiple IDEs. We will start with VSCode and IntelliJ to begin.
<p>Distributed tracing is essential for GenAI observability, but observing AI Agents differs fundamentally from observing microservices. While microservice traces focus on network latency and error codes, AI traces focus on the "reasoning process." The current Jaeger UI displays traces in a standard waterfall timeline, making it difficult to distinguish between logical "Tool Calls" and technical operations, and nearly impossible to read multi-paragraph prompts or view generated images. This project aims to transform the Jaeger UI into a first-class GenAI observability tool. When Jaeger detects a trace containing GenAI-specific metadata (following OpenTelemetry semantic conventions), it should automatically adapt its presentation to prioritize the "Agentic Flow."</p><p><br></p><p>Expected Outcome:</p><p><br></p><ul><li>Automatic "GenAI Mode" detection: detect `gen_ai.*` attributes and offer/switch to a specialized visualization mode</li><li>Agentic hierarchy with iconography: use distinct icons to differentiate span types (e.g., "brain" for LLM calls, "wrench" for tool calls, "database" for RAG retrieval)</li><li>Rich-media side panel leveraging ADR-0006 side-panel capability, with Markdown support for prompts and completions, pretty-printed JSON for tool inputs/outputs, and direct rendering of images/audio previews</li><li>Simplified "logical" view: toggle to hide infrastructure-level noise and reveal a clean, high-level reasoning flow</li><li>More compact table view of multiple traces on the Search page</li></ul>
In order to improve Thanos usage for users, we would like to define our APIs, both HTTP and gRPC, in protobuf/OpenAPI and expose the automatically generated documentation in the website. We also want to define the configuration of our components in protobuf. This would allow users to use tools for documentation, validation, type checking and even code generation to use our APIs efficiently. During this project we also expect collaboration with the Prometheus project to implement similar improvements on Prometheus' side. https://github.com/cncf/mentoring/blob/master/summerofcode/2021.md#port-the-prometheus-api-to-openapi. Optionally we would like to work on the index page on every Thanos component server that will expose those resources for easier debug.
Description: Now we have lots of new features, we need add more docs for them.
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.
Climate change is the biggest challenge of our time. We need all the help we can get to reduce emissions in every sector. Forest are particularly important as they can remove CO2 from the atmosphere. Moja global's software Full Lands INtegration Tool (FLINT) estimates greenhouse gas fluxes from land use. Progress means that emissions today are lower than the baseline, i.e. emissions we would have observed had we done nothing. A baseline requires predicting the rate of deforestation in case we had done nothing. So we need a formula linked to local proxies that predicts deforestation locally, but that can be aggregated to the level of a state, province or country without losing consistency. Proxies can be location of hamlets, roads, agriculture, recent deforestation, etc. Most approaches use social research and linear programming to develop an algorithm that predicts deforestation. This project proposes to develop the algorithm based on machine learning.
OpenHPC is accepting applications for a new mentorship program that aims to give students practical experience contributing to an open-source project and an opportunity to work with volunteers from the project’s Technical Steering Committee (TSC). OpenHPC is a software stack that aggregates a variety of software components ranging from administrative tools like bare metal provisioning and resource management to end-user development that span a range of scientific/numerical uses. If your interest is in the domain of high performance computing , scientific computing or cluster management, this might be the right program for you. This initial program will occur during the Fall of 2020 with future versions expected to occur during the summer. See our website for details and project ideas - http://bit.ly/ohcmentorship2020 . For questions feel free to email - mentorship@openhpc.community
The Yocto Project (YP) is an open source collaboration project that helps developers create custom Linux-based systems regardless of the hardware architecture.
Got a flair for helping other learn about RISC-V? Unlock your creative potential and make a global impact! RISC-V International invites you to join our vibrant, international community and play a pivotal role in boosting our support for individuals new to RISC-V. RISC-V International is looking for an individual willing to help the community and technical program managers in a variety of tasks. A good candidate will be an independent self starter who can create documentation, is an excellent researcher, with program management and content creation experience. See what its like to work in different departments of a Open Standard Project. Don’t miss this extraordinary opportunity to grow your skills and make a difference with this 30 hour a week, remote role. Apply now!
The goal of this summer mentorship is to continue enhancing the Testing chapter in the COBOL Programming course. Introduce CI/CD for COBOL application development using Jenkins. Update the course to gain value from the Zowe V3 release. This will ensure that we are able to provide our learners with the modern Devops Practices.
<p>Paladin is a programmable privacy solution for EVM blockchains. It provides a framework for deploying and working with private tokens and EVM-compatible private smart contracts for private, programmable on-chain logic such as atomic swaps.</p><p><br></p><p>See <a href="https://www.paladinprivacy.org/" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">https://www.paladinprivacy.org/</a> and <a href="https://lfdt-paladin.github.io/paladin/head/" rel="noopener noreferrer" target="_blank" style="color: rgb(9, 105, 218);">https://lfdt-paladin.github.io/paladin/head/</a></p><p><br></p><p>To work with Paladin tokens and private smart contracts applications typically use one of the existing SDKs - currently available for Go and Typescript.</p><p>There are users keen to build Java applications that utilize all of the Paladin privacy features in a performant, language-idiomatic way.</p><p><br></p><h3>Learning Objectives</h3><ol><li>Understand all the basic components and privacy patterns of Paladin</li><li>Understand the Paladin REST APIs and and their inputs/outputs</li><li>Review the existing SDKs to understand what feature-parity of a new SDK would look like</li></ol><h3>Expected Outcome and Deliverables</h3><ul><li>A Java SDK available as a published dependency for Java applications to consume</li><li>Request/reply and web-socket event-driven interfaces</li><li>A repeatable release process integrated with the current release pipeline</li><li>A high degree of test coverage of the new SDK</li></ul><p><br></p><p>Ultimately we are looking for a well designed SDK that feels natural to Java application developers to use, and makes use of current, idiomatic language features.</p><p><br></p><p>Lean more at <a href="https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/64" rel="noopener noreferrer" target="_blank">https://github.com/LF-Decentralized-Trust-Mentorships/mentorship-program/issues/64</a></p>
This mentorship focuses on extending the NucleusRV Core, a fully parameterized RV32IMFC core written in CHISEL, by implementing RVV v1.0 Floating Point Vector instructions. The core currently features partial RVV v1.0 support through its co-processor, Vaquita, which handles vectorized operations. This project presents a unique opportunity to dive deep into RISC-V vector extension, hardware designing with abstractions using CHISEL, and contribute to a cutting-edge open-source initiative. Problem/Opportunity Modern workloads increasingly demand efficient handling of vectorized floating-point computations, especially in domains like AI/ML, graphics, and scientific simulations. While Vaquita implements basic RVV functionalities, the absence of comprehensive floating-point vector support limits its applicability in these advanced use cases. Adding this capability will make the NucleusRV Core a more versatile and competitive RISC-V implementation, aligning with emerging industry needs.
The Mainframe Open Education Project seeks an enthusiastic and skilled individual to help elevate our program's visibility and engagement across social media platforms. This role involves devising and implementing effective strategies to boost our online presence and connect with a wider audience. Problems to be solved: To enhance and improve marketing & communication efforts by the program while helping align content to the intended audience and provide outside/in perspective. Deliverables: - Review of current marketing and communications materials & processes. - Review of current technical content to ensure it aligns with the intended audience (if mentee is not technical, partner with MOE Student User Group members to conduct the review). - 2 blogs on their experience with the project and OMP - A session title and abstract to potentially be delivered at an industry event if attendance can be arranged for.
Mailu is a simple yet full-featured mail server as a set of Docker images. It is free software (both as in free beer and as in free speech), open to suggestions and external contributions. The project aims at providing people with an easily setup, easily maintained and full-featured mail server while not shipping proprietary software nor unrelated features often found in popular groupware. Main features include: - Standard email server, IMAP and IMAP+, SMTP and Submission - Advanced email features, aliases, domain aliases, custom routing - Web access, multiple Webmails and administration interface - User features, aliases, auto-reply, auto-forward, fetched accounts - Admin features, global admins, announcements, per-domain delegation, quotas - Security, enforced TLS, Letsencrypt!, outgoing DKIM, anti-virus scanner - Antispam, auto-learn, greylisting, DMARC and SPF - Freedom, all FOSS components, no tracker included
This project aims to not only update and expand the instructional content and video resources available to the Hyperledger community but also to foster a mentorship relationship that can contribute to the mentee's professional growth and the overall vibrancy of the Hyperledger ecosystem. The mentor and mentee will collaborate to create a series of instructional videos covering a range of topics, including: - Updating the videos on the Hyperledger Participate page (https://www.hyperledger.org/participate/coding) - Understanding the contribution process, including how to submit issues, pull requests, and review processes. - Overview of the Hyperledger community structure, including Special Interest Groups (SIGs), Working Groups, and how to get involved. - Deep dives into specific Hyperledger projects, highlighting key features and contribution opportunities. - Best practices for successful community engagement and contribution. - Setting up a development environment for Hyperledger projects.
This task focuses on improving the LitmusChaos documentation by structuring and creating tutorials into Day 0, Day 1, and Day 2 workflows tailored for different users. Instead of documenting individual faults (which would require constant maintenance), the goal is to create user-flow-based guides that help users understand chaos engineering principles at different levels of expertise, from beginners experimenting with sample apps to advance users implementing chaos in real-world systems. Additionally, this task will involve tech doc improvements, fixing structural issues, removing duplicates, and ensuring a clear and intuitive documentation experience for the community Expected Outcome: - Structured Day 0, Day 1, and Day 2 tutorials for different user levels - Improved documentation clarity and reduced redundancy - Persona-based chaos experiment guides for real-world use cases
The Gateway API is becoming the standard for Kubernetes service networking, including ingress, traffic routing, and service mesh use cases. While Headlamp has built-in support for Gateway API resources, there is currently no integrated way to visualize and manage service mesh topologies, traffic flows, and policies. This feature aims to enhance Headlamp with a visual and interactive interface for understanding and managing service meshes built on the Gateway API. Expected Outcome: A Headlamp feature that enables users to: 1. Visualize service mesh topologies using Gateway API resources (e.g., Gateways, Routes, Services) 2. Overlay traffic flow data, latency, error metrics, and traffic policies (e.g., splitting, retries, timeouts) on the resource map 3. Leverage existing Headlamp Map and CRD extension capabilities for seamless integration 4. Documentation and possibly a demo video or blog post.
Many performance benchmarks are limited to single instance load generation (single pod load generator). This limits the amount of traffic that can be generated to the output of the single machine that the benchmark tool runs on in or out of a cluster. Overcoming this limitation would allow for more flexible and robust testing. Distributed load testing in parallel poses a challenge when merging results without losing the precision we need to gain insight into the high tail percentiles. Distributed load testing offers insight into system behaviors that arguably more accurately represent real-world behaviors of services under load as that load comes from any number of sources. Expected Outcome: Implementation of distributed load generation in Nighthawk. Integration of Nighthawk with relevant service mesh performance testing scenarios. Capability to invoke Nighthawk for distributed load testing through APIs and command-line interfaces. Implementation of reporting mechanisms for distributed load testing results.
[Kubescape](http://kubescape.io/) is a utility that can scan a Kubernetes cluster and report on its security posture. It can also scan individual workloads (e.g. YAML files) before they are applied. By creating a Kubescape admission controller, we will be able to combine the two, denying workloads into a cluster where it would reduce the security posture. - Expected Outcome: The Kubescape application will be extended and packaged to operate as an admission controller inside a cluster. The controller will be well documented, safe to install, and instrumented with logging and telemetry data to be able to diagnose problems.