Discover open-source organizations actively accepting contributors across GSoC, ESoC, LFX Mentorship, Outreachy, and more.
Showing 241–360 of 511 organizations
Browse projectsHyperledger
Hyperledger AnonCreds v2 takes the privacy-preserving features of AnonCreds v1 Verifiable Credentials to a new level. AnonCreds v2 adds support for newer, mature cryptosuites (including BBS+ Signatures), and for a number of important Zero Knowledge Proofs (ZKP) that enable an even better balance between verifiability and privacy. AnonCreds v2 also adds a crucial new, highly-scaled approach to ZKP-based credential revocation – a crucial element of almost all verifiable credential ecosystems. Called ALLOSAUR, this new scheme allows a single revocation registry to be created by an verifiable credential issuer that scales to support millions of credentials in a fast, low-data manner. Instead of sharing millions of credential revocation statuses (revoked or not), the scheme relies on the transfer of just a handful of integers between participants, enabling secure revocation without a verifiable credential holder from having to share a correlatable identifer for themself to the verifier. ALLOSAUR requires the creation of a new component in the verifiable credential ecosystem, the revocation manager, which is the goal of this Hyperledger Mentorship – to implement a scalable ALLOSAUR revocation manager. The implementation will at least be partially in Rust, with flexibility on the choice of languages/frameworks for the web service.
Hyperledger
Hyperledger Besu is an Ethereum client written in Java. Operators are a method of packaging, deploying, and managing a Kubernetes or an OpenShift application. This project aims for the mentee to design, build and test operators for Project Besu. The code to this will then become part of the Besu project and added to the code repository.
Hyperledger
Cacti provides modules, toolkit, and protocols to enable networks built on distributed ledgers to interoperate and carry out transactions spanning their boundaries, such as asset transfers, asset swapping, and ledger data communication. For ease of building DLT-agnostic protocols in Cacti, we need to build modules corresponding to various DLTs supported by Cacti that implement these core operators and expose them using a standard API. The goals of this project are as follows: 1. Design and build DLT-specific core operator modules for Cacti by leveraging existing Cactus or Weaver packages. This involves identifying building blocks of unique features in either, and integrating legacy Cactus and Weaver packages wherever they offer a common feature. 2. Design and implement a common DLT-agnostic API, following the OpenAPI standard, using which any DLT-specific core operator module can be invoked by application-specific business logic on-demand. 3. Add suitable API support within the common Cacti client API for ease of application development 4. Do a research survey of existing blockchain/DLT literature to identify a potentially exhaustive set of core operators any DLT network must possess (or harness) to interoperate with other networks.
Hyperledger
The Hyperledger Greenhouse, powered by the Hyperledger Foundation, provides several Business Blockchain Frameworks & Tools, some of which compose the state of the art private blockchains. In particular, Hyperledger Fabric is amongst the most famous permissioned blockchains; Hyperledger Indy tackles the first big initiative to promote decentralized identity support; Hyperledger Caliper is a comprehensive blockchain-testing framework; Hyperledger Quilt enables a specific type of blockchain interoperability - enables payments across any payment network — fiat or crypto - using the Interledger protocol. Cactus is a blockchain integration tool designed to allow users to securely integrate different blockchains, promoting blockchain interoperability. This way, Hyperledger Cactus aims to provide Decentralized, Secure, and Adaptable Integration between Blockchain Networks. Hyperledger Cactus is currently undergoing a major refactoring effort to enable the desired to-be architecture which will enable plug-in based collaborative development to increase the breadth of use cases & Ledgers supported. To fully explore Cactus’ capabilities, and to promote the project’s adoption, one needs several business logic plugins that realize cross-blockchain use cases (similarly to fabric-samples). Many are proposed on the whitepaper, but few are implemented.
Hyperledger
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.
Hyperledger
The goal of the project is to enhance the accessibility, consistency, and comprehensiveness of the Caliper documentation. This mentorship project aims to transition the current Caliper documentation site to utilize the common documentation template adopted by Hyperledger projects. This standardization effort will ensure a seamless user experience across Hyperledger documentation, facilitating easier navigation and comprehension. Furthermore, the project will focus on content improvement to ensure that the documentation covers all aspects of Hyperledger Caliper comprehensively, including installation, configuration, usage, and troubleshooting, with up-to-date and accurate information. The mentee can gain a wealth of knowledge and skills that are valuable not just for this specific project but for their professional development in technical writing, documentation management, and basic understanding of blockchain technology.
Hyperledger
This mentorship project aims to significantly improve the testability, test coverage, and robustness of the Hyperledger Caliper blockchain benchmark platform. Hyperledger Caliper is a blockchain benchmark tool that allows users to measure the performance of a specific blockchain implementation with a set of predefined use cases. The project will involve assessing the current testing framework, identifying gaps in test coverage, designing and implementing comprehensive test suites, and integrating best practices for testing to ensure the platform's reliability and performance. Expected Outcome and Deliverables - Comprehensive Test Suites: Develop and implement a suite of tests that cover all aspects of Hyperledger Caliper, ensuring high test coverage. - Documentation: Provide detailed documentation on the testing framework, test cases, and guidelines for future contributions to maintain test quality. - CI/CD Pipeline: A fully functional CI/CD pipeline that automates the testing process, ensuring that every contribution is thoroughly tested. - Contributor documentation: A detailed documentation about the internal working of Caliper components to facilitate future contributions.
Hyperledger
Today, most users adopt Blockchain in order to collaborate with each other, however, it is difficult to manage a large blockchain network because of multiple organizations and nodes. Hyperledger Cello is aiming to resolve the following challenges, 1) Facilitate creation of blockchain network, can help user without blockchain background to setup their network nodes quickly. 2) Cross organization communication, can connect blockchain networks among multiple organizations. This project targets to design and implement a practical operational system equipping with decentralized functionalities to solve above challenges, based on Hyperledger Cello code base. Learning Objectives 1) Work closely with community experts and developers to learn the open-source culture and skills; 2) Learn the advanced knowledge inside the blockchain and distributed ledgers; 3) Practice hand-on experience with web application design and implement. Expected Outcome Help design and implement the blockchain operation dashboard and api server.
Hyperledger
Blockchain is helpful for collaborative applications, however, it is difficult to manage because of the decentralized features. Another challenge is how to efficiently govern a blockchain network among various organizations. Hyperledger Cello is aiming to resolve the following challenges, 1) Facilitate creation of blockchain network, can help user without blockchain background to setup their network quickly. 2) Security, need to implement mechanism to protect key pairs. 3) Cross organization communication, can connect blockchain networks among multiple organizations. This project targets to design and implement a practical operational system equipping with decentralized functionalities to solve above challenges, based on Hyperledger Cello code base.
Hyperledger
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.
Hyperledger
The current existing implementation of Hyperledger Fabric with Raft consensus has many shortcomings such as transaction censorship and no mechanism to safeguard the network if a malicious leader gets elected. The network also has limitations on scalability which restrict the type of use cases that can be built such as real-time applications that use IoT devices. This impedes blockchain adoption and limits the type of applications and use cases that can be built on Fabric. The goal of this project is to build BiniBFT, a Byzantine Fault Tolerance consensus library for Hyperledger Fabric which provides end-to-end security, high throughput with low latency and high scalability so that Fabric can be applicable for distributed and decentralized day-to-day applications. Learning Objectives - Building and Integrating a BFT library with Hyperledger Fabric. - Understanding how BFT consensus protocols work and optimizing algorithms for better performance. - Developing an understanding of how DLT networks like Hyperledger Fabric work. - Exploring the different ways in which BFT protocols can improve the performance and security of Fabric networks.
Hyperledger
Designing an open wallet based on the DIDMan specification requires consideration of several key components. These include authentication, DID management, cryptographic operations, interoperability, user interface, security, and backup and recovery. The OpenWallet must have a secure authentication mechanism and support the DIDMan specification to manage DIDs, their associated keys, and metadata. The wallet must also support cryptographic operations, have a user-friendly interface, ensure security, and allow for backup and recovery. By adhering to the DIDMan specification, the wallet can ensure interoperability with other compliant systems and promote the adoption of decentralized identity technologies. Expected Outcome - The expected outcomes of designing and spec-ing an OpenWallet based on the DIDMan specification include developing a deep understanding of decentralized identity systems, gaining practical experience in implementation and cryptography, and prioritizing security and user experience. - Additionally, students can expect to learn about interoperability, open-source contribution, technical documentation, and real-world applications. - By achieving these outcomes, students will be equipped with the skills and knowledge needed to make meaningful contributions to the growing field of decentralized identity technologies.
Hyperledger
The project DRman aims to develop a standalone utility for Verifiable Credential Registries management. It includes functionalities like credential creation, verification, modification, and revocation, enabling easy management of the registry. The project has three significant aspects: DID Registry creation, member onboarding, and DID management. The project seeks to address migration issues by migrating the project from GitHub to GitLab to make it infrastructure-agnostic.
Hyperledger
The current existing implementation of Hyperledger Fabric with Raft consensus has many shortcomings such as transaction censorship and no mechanism to safeguard the network if a malicious leader gets elected. The network also has limitations on scalability which restrict the type of use cases that can be built such as real-time applications that use IoT devices. This impedes blockchain adoption and limits the type of applications and use cases that can be built on Fabric. n nThe goal of this project is to build BiniBFT, a Byzantine Fault Tolerance consensus library for Hyperledger Fabric which provides end-to-end security, high throughput with low latency and high scalability so that Fabric can be applicable for distributed and decentralized day-to-day applications. n nLearning Objectives n- Building and Integrating a BFT library with Hyperledger Fabric. n- Understanding how BFT consensus protocols work and optimizing algorithms for better performance. n- Developing an understanding of how DLT networks like Hyperledger Fabric work. n- Exploring the different ways in which BFT protocols can improve the performance and security of Fabric networks.
Hyperledger
The Fabric Token SDK allows developers to create token-based distributed applications on Hyperledger Fabric. While the Fabric Token SDK offers many features (i.e., configurable privacy, p2p transaction orchestration, atomic swaps, and audits,...), performance is yet another important aspect. The Hyperledger Caliper project is a blockchain performance benchmark framework, which allows the evaluation of blockchain solutions. How about using Caliper to benchmark token-based applications built on top of the Fabric Token SDK? The goal of this project is the design and the implementation of a Caliper plugin to evaluate applications using the Fabric Token SDK. This includes the creation of appropriate documentation and performance evaluation of sample applications. The project requires a solid understanding of theory and practice of software development using Golang and Node.JS, distributed systems, and performance benchmarking. During the project you will get hands-on experience with the deployment of Fabric networks, the transaction lifecycle, the Fabric Token SDK, and Hyperledger Caliper.
Hyperledger
Fabric Private Chaincode (FPC) leverages modern Confidential Computing technology, such as Intel SGX, to enhance the protection of chaincode and their data while executed at the endorsing peers. Client applications interact with their private chaincode via the FPC Client SDK, which is responsible to encrypt and authenticate the invocation arguments before being sent to the endorsing peers. However, the FPC Client SDK currently does not support the new Fabric Gateway API that simplifies the transaction flow for the clients. The goal of this mentorship project is the design and the implementation of the FPC Client SDK using the new Fabric Gateway API. This also includes the creation of appropriate samples and documentation. The project requires a solid understanding of theory and practice of software development using Golang, distributed systems, and security. During the project you will get hands-on experience with the deployment of Fabric networks, the transaction lifecycle, confidential computing technology.
Hyperledger
The task is to improve the documentation for DRMan, which aims to develop a utility for managing Verifiable Credential Registries. The core functionalities include creating, verifying, modifying, and revoking credentials, as well as managing DIDs. The project requires the creation of a DID registry for an organization, onboarding of members, and management of APIs needed to add/update/revoke access to DIDs or DID documents. The mentee is expected to use MKDocs to document the project and make it production-ready for future use.
Hyperledger
DLS consensus protocol is a BFT protocol that has been approved and hosted in the Hyperledger Lab to be integrated into Hyperledger Fabric for consideration as one of the ordering service BFT protocols. BDLS is an innovative BFT consensus algorithm that features safety and liveness by presenting a mathematically proven secure BFT protocol that is resilient in open networks such as the Internet. BDLS overcomes many problems, such as DoS attacks and the deadlock problem caused by unreliable p2p broadcast channels. These problems are all very relevant to existing realistic open network scenarios and are the focus of extensive work in improving Internet security. Still, it is an area largely ignored by most in mainstream BFT protocol design. Learning Objectives Consensus algorithm mechanism, Distributed messaging system, ability to integrate new consensus algorithm in the Orderer service of Fabric Expected Outcome BDLS consensus protocol is a BFT protocol that has been submitted for consideration to be integrated into Hyperledger Fabric as an ordering service.
Hyperledger
Current project targets privacy preservation developing modular tools for data sharing while envisioning the deployment of the necessary future blockchain and smart contract processes in Service Level Agreements (SLAs) evaluation. Service Level Agreements (SLAs) define the way that service and infrastructure providers are making available products to their clientele, for example, the dedicated agreements for Public Cloud Infrastructure As A Service. An SLA is an accurately defined contract involving the specified service level objectives (SLOs) and contractual guarantees that are promised to be delivered to clients by the providers of the service or infrastructure. Particularly, monitoring of SLAs determines whether a provider meets an SLA's contractual terms or otherwise breaches of the agreement unfold. SLA breaches lead to definite violations of the terms, namely SLA Violations, as described in the contract. Ultimately, contractual definitions and parameter values computations vary across different provider setups, e.g. Telecom, 5G, Edge, and Cloud. The main objective of the project is to develop privacy preservation through trusted execution environments, zero-knowledge proofs, or ring signatures for the corresponding transactional operations of SLAs assessment under a modular data sharing scheme on Hyperledger Fabric. The applicable deployment and engagement with such architectural elements of privacy leads the current project to preserve and secure data protection.
Hyperledger
Standards Working Group (Standards WG) of Hyperledger's Climate Action and Accounting Special Interest Group (CA2-SIG) has been working on developing an Anthropogenic Impact Accounting Ontology (AIAO). Climate accounting is currently the primary use case for AIAO. The ontology aims to enable interoperability between the plethora of impact accounting standards and methodologies in the market, allowing further development of systems such as a global climate impact accounting ledger. The WG has formulated an ontology comprising a current total of 46 classes and 11 primary axioms with several more axioms on the secondary and tertiary level. The core concepts are explicated on the Standards WG's wiki and encoded in an OWL file. During the 2022/2023 southern hemisphere's summer break the Nova Institute sponsored and hosted a mentorship programme that recruited three second-year ICT university students from South Africa to refine the OWL file, develop a Turtle parser and set up an MVP triple store for the ontology. The next steps towards operationalization of the ontology are aimed at developing the tools for interoperability between the AIA ontology and existing vocabularies in the field of impact accounting, starting with those from the climate accounting space. This will involve mapping the existing vocabularies and standards to the ontology, improving on the examples produced by the students; annotating existing climate impact data from selected case studies.
Hyperledger
The Hyperledger Foundation is seeking a mentee to assist the Hyperledger India chapter's student society in improving their new student chaptor society membership and onboarding, marketing, and technical deck development efforts. The mentee will help in organize developer events and conduct research to identify potential opportunities for increasing new student chaptor society member onboarding and developer engagement. The mentee will be responsible for analyzing the education space, monitoring social media platforms such as LinkedIn and YouTube, and creating technical and promotional materials for outreach activities. In addition, the mentee will work with the Lead, student chapter society to conduct market research and analysis on the latest trends in developer engagement strategies. The mentee will also contribute to the content calendar by posting on social media platforms regularly and monitoring analytics with the team to identify potential growth patterns and viable ideas.
Hyperledger
The data space approach aims at creating a data federation environment without the overhead of “enterprise” data integration. The concept of data spaces is gaining more and more importance, as this approach offers an opportunity for different stakeholders (data owners, including public bodies and municipalities, service providers offering AI-as-a-service algorithms , service consumers, regulatory bodies, etc.) to collaborate. There are several domains from eHealth to education where this kind of data/service federation is expected to have an important role in the near future. Blockchain is a natural candidate to support several aspects and steps of such collaborations. However, current initiatives do not really seem to fully exploit the possibilities of HFL (and its support for designing privacy-preserving applications with channels and Private Data Collection). The Eclipse Dataspace Connector, maintained by a coalition of European organizations, implements the International Dataspace Standard and also serves as a focal point of the Gaia-X. It is designed to connect multi-cloud environments and has an extension mechanism towards different cloud storage technologies. However, currently these extensions only support storage over designated cloud-based services, but do not offer consortial blockchain connection. The aim of the mentorship would be to develop an extension which support storing data over Hyperledger Fabric as data pane, relying on the Private Data Collection.
Hyperledger
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.
Hyperledger
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.
Hyperledger
Hyperledger Aries currently support only Hyperledger Indy blockchain. Verifiable credential(VC) and decentralised identifier(DID) standard & specification emerged in last few years. Trust over IP , Sovrin network, covid credential initiative are using Indy & Aries technology framework. Hyperledger Fabric general enterprise blockchain framework and most used Hyperledger project, latest Forbes Blockchain 50 report shows that 60% companies using Hyperledger Fabric for their enterprise grade blockchain. All the major cloud provides fabric as BaaS( Blockchain as a Service). Currently every identity/credential application using Indy/Aries stack to build W3C complaint VC & DID applications. There will be huge adoption and applicability of Hyperledger Fabric & Aries integration project. As per Hyperledger project governance there should be Hyperledger project interoperability to huge adoption of Hyperledger technologies. Mentee will learn: 1) Hyperledger Fabric Architecture & SDK/API 2) Hyperledger Aries Javascript framework 3) VC/DID standard and Application Expected Outcome Hyperledger Aries & fabric Wrapper or Aries will have support to use Hyperledger Fabric as Blockchain for storing credentials.
Hyperledger
This project aims to add interactive examples to fabric-python-sdk using jupyter notebook. The intern is expected to first understand the functionalities of fabric sdk (v0.8.1) and add missing functionalities of fabric 2.0 (e.g. wallet storage, etc.) to fabric sdk based on nodejs/golang sdk. Then, write jupyter notebook examples using fabric sdk and demonstrate functionalities of sdk. It provides new developers with better understanding of using fabric sdk.
Hyperledger
Introduction and Problem Statement: Many city councils want to know the voice of citizens whenever a change is implemented. Usually when a city approves a plan, there are always a small minority affected/opposing it.The city always wants feedback from the citizens on their decisions and they never have a proper channel to do so. Though the usage of online forums are common in developed and developing countries, its usually challenging to get public agree on a common platform as the platforms are controlled by individual companies/government bodies. Also, public is worried about privacy and safety of the platform. Further, there are also situations like some NGOs who host the platform have financial challenges and hence discontinue their services. Proposed Solution: In a distributed platform like Hyperledger, its possible to decentralize the ownership. This gets to a situation where the platform is by the people and for the people. Also, due to the immutable nature of the Hyperledger, there is one source of truth existing in the system. The Endorsement policies handle the privacy part and Certificate-Authorities provide safe and secure platform. When the Hyperledger components are shared among the NGOs/government/Universities/private-bodies, the ownership is distributed.
Hyperledger
Introduction Endorsement policy controls the approval of a proposal to be executed at various granular levels. In other words, this is the primary entity which is validated before a transaction is committed. Endorsement policy can operate at two different granularities: Namespace level: They can be set for the whole namespace. This is the default approach in which endorsement policies are specified in the chaincode definition, which is agreed to by channel members and then committed to a channel Individual key level: They can be set for individual state keys called private data collections. You can also specify an endorsement policy at the private data collection level, which would override the chaincode level endorsement policy for any keys in the private data collection. This would further restrict which organizations can write to a private data collection. Problem Statement This becomes complex to handle when operating at scale. Some use cases 1. Complex endorsement policy resolving for namespace level ones 2. Tracking Endorsement policies on large quantity Private data collections each having different endorsement policies 3. Resolving policy for a given object combining namespace level with overriding individual key-level ones.
Hyperledger
Fabric Private Chaincode (FPC) leverages modern Confidential Computing technology, such as Intel SGX, to enhance the protection of chaincode and their data while executed at the endorsing peers. Client applications interact with their private chaincode via the FPC Client SDK, which is responsible to encrypt and authenticate the invocation arguments before being sent to the endorsing peers. Currently chaincodes can be developed in C++ or Golang. The Hyperledger Labs CC-Tools library offers several features that facilitate the journey of learning, development and deployment of chaincode for Hyperledger Fabric in Golang. The goal of this mentorship project is the design and the integration of FPC as a destination for the code developed using CC-Tools. This also includes the creation of appropriate samples and documentation. The project requires a solid understanding of theory and practice of software development using Golang, distributed systems, and security. During the project you will get hands-on experience with the development of Hyperledger chaincode, the deployment of Fabric networks, the transaction lifecycle, and Confidential Computing technology. - Deep dive into Hyperledger Fabric, in particular, Fabric Private Chaincode using Confidential Computing, and the Hyperledger Lab CC-Tools - Experience an active open-source community - Mastering open-source workflow - Enhance your designing and implementing skills, testing, documentation, and project management
Hyperledger
Develop a command line utility that can create a secure DID Registry on Github or a Gitlab . On the Bash shell this utility will enable commands that makes use of Github or Gitlab API for doing basic CRUD operations on a GIT repository based DID Registry.
Hyperledger
While Hyperledger Indy has proven to be incredibly robust and more than sufficiently scalable to this point in its evolution and application, we think it would be useful to enable further scalability by adding the concept of Indy Read Replicas to the project. An Indy read replica is a copy of the ledger transactions from one or more Indy ledgers that can be used by clients that trust the replica. For this project, we will start from one of two existing, open source Indy "ledger browser" implementations that collect transactions from the ledger and maintain them in a database. A REST API will be added that provides replica clients with an HTTP version of the existing ledger API. Once a functioning Indy read replica implementation has been developed and tested, we will look at what optimizations can be accomplished to further lower the load on the ledger. For example, a new replica has to retrieve all of the transactions on the ledger, and, in the open source ledger browsers does so by do a read for all transactions starting at 1. Is there a good approach to getting a "trusted" batch of transactions to eliminate that startup load? To find transactions added to the ledger, the read replicas poll the ledger "anything new added?" Can that load be reduced by enabling a transaction "pub/sub" API that notifies read replicas of new transactions, perhaps even pushing them to the replicas. Lots of interesting design and implementation questions!
Hyperledger
Hyperledger Iroha has Smart Contracts from Hyperledger Burrow. It was done in internship project in 2019, then integrated into main Iroha code in version 1.2. Unfortunately integration does not integrate all Iroha commands and queries (currently only: TansferAsset and GetAccountAssets are integrated). So task is to integrate all commands and queries and also permissions. The mentee will be able to learn: 1) ways of integrating different projects from architectural point of view, 2) architecture of Iroha (1.x) and optionally Burrow, 3) work in true spirit of open-source, communicating with both Iroha and optionally Burrow community, joining calls and using other community tools, 4) writing documentation, so anyone in the community could use the results of their work, 5) ollowing rules and standards of open-source projects created by hyperledger, 6) Intern would get experience in virtual machines Expected Outcome Documented integration of all Iroha (version 1.x) commands, queries and permissions with unit tests.
Hyperledger
Hyperledger Cactus is a blockchain decentralised integration tool designed to allow users to securely integrate different blockchains started by companies Fujitsu and Accenture. Cactus has pluggable architecture which makes easy to integrate various blockchain by creating plugin, currently plugins for Fabric, Besu, Quorum are implemented. Cactus allows to transfer not only assets but also data between multiple blockchains. On the other hand Iroha (version 1.x) is great with asset management, and has functionality to store data, which makes those two projects a perfect fit! With this internship we will not only allow the interoperability between different blockchains but also create a system of Iroha networks that will also demonstrate the integration in examples easy to run by everybody. The mentee will be able to learn: 1) ways of integrating different projects from architectural point of view, 2) architecture of Iroha (1.x) and Cactus, 3) work in true spirit of open-source, communicating with both Iroha and Cactus community, joining calls and using other community tools, 4) writing documentation, so anyone in the community could use the results of their work, 5)following rules and standards of open-source projects created by hyperledger Expected Outcome 1) Documented, ready-to-use integration of Iroha and Cactus, 2) Documented example of integration between multiple (two and more) iroha's networks with Cactus, 3)Documented example of integration between Fabric and Iroha
Hyperledger
The task will be to implement a visual blueprint frontend similar to Blockly, Scratch, or Unreal Engine Blueprints for the Iroha Special Instructions smart contract language. Iroha Special Instructions (or ISI) are a composable smart contract language for Iroha v2 providing an opportunity to execute logic on-chain. In their raw form they represent a syntactical tree, which is not very convenient to write. We think that the structure of the ISI will perfectly match a visual blueprint language and therefore make developing Iroha v2 smart contracts more comfortable for everyone. The app to be developed should allow the user to compose ISI, potentially validating the correspondent types of outputs of each of the blocks. After the program of blueprints is composed, the app should provide a way to transpile the blocks into the file of raw ISI in their byte format. Potentially the app can also act like a client and submit the ISI directly to a Hyperledger Iroha network to be executed right away.
Hyperledger
Hyperledger Iroha has implemented set of commands and queries. In the internship's project for few Iroha's queries (GetAccountTransactions and GetAccountAssetTransactions and optionally GetPendingTransactions) should be added optional arguments e.g.: from and to to return transactions in the provided time range or in provided blocks range. Problem description Fetching transactions in Iroha can be from first account's transaction or from provided transaction hash. On the other bound transactions are limited by max number of transactions to fetch. So when it is necessarily to fetch transactions for a month: hash of first transaction needs to be stored in blockchain and number of transactions should be "guessed" -if too big it would take longer, if too small another query would be necessarily). It also requires few queries instead of one. The mentee will be able to learn: 1) architecture of Iroha (1.x) 2) work in true spirit of open-source, communicating with Iroha community, joining calls 3) writing documentation 4) following rules of open-source code of Hyperledger Iroha, creating automatic tests of code Expected Outcome Implementation according to description and plan of documentation and tests. Added possibility of running modified queries from iroha-python library.
Hyperledger
Hyperledger Quilt is a Java implementation of Interledger, a suite of open protocols and standards that allows payments interoperability across any currency - fiat or crypto. And Iroha is great with asset management, which makes those two projects a perfect fit! With this internship program we will not only allow the interoperability between different asset-carrying blockchains but also help create a system of Iroha networks that will only share some information, that is a requested feature.
Hyperledger
Hyperledger is a big project hosting different frameworks and tools. In Iroha team we've been working for some time now on integrating other projects into Iroha and Iroha into other projects. During that process, we've received good feedback and an important question: what can Iroha give other projects? To answer that, we've decided to mentor this project, including some research of different projects to create the most interoperable API solution and practical work with C++ code. We will try to derive a common subset of data model and executor interfaces from different HL projects in order to make the most compatible solution. Decoupling data model (commands and queries) will allow both reuse of it in different projects and easier work in case someone decides to change something in Iroha code itself (to customise it for their own project, for example, by easily plugging a new data model piece in). Some of the features might only be needed to some users, but not everyone.
Hyperledger
In some of the projects this year we've decided to focus on modularity and decoupling which makes a lot of sense when we talk about open source and interoperability. In our chats we receive questions about decoupling different components – some of the users would like to plug different modules in and out. To provide them with that option and make development easier and more secure, we would like to explore the option of following the example of the pluggable consensus in HL Sawtooth. In the best case scenario result, we will be able to reuse consensus modules from Sawtooth in Iroha and vice-versa in the future. So, overall, this project will increase HL projects interoperability and make Iroha more flexible.
Hyperledger
The Hyperledger Labs AIFAQ is an LLM ChatBot testable as a proof-of-concept. It replies to questions about Hyperledger standard documentation. The current version is a Google Colab Notebook which uses Gradio as GUI. This project proposes an implementation of a standard ChatBot GUI and the deployment of a prototype. Our end goal is to have a more usable system installed on a Cloud Server. Learning Objectives - Learn LLM background technology - Learn Javascript language and framework - Learn basics of Front-end development - Learn Cloud architecture and deployment - Learn how to create high quality documentation Expected Outcome and Deliverables - A Front-end component prototype - A simple container architecture - A good quality documentation
Hyperledger
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.
Hyperledger
The Solang Solidity Compiler is a new compiler project, which compiles Solidity to wasm or bpf. The compiler does not yet detect if a variable is used before it is assigned, or detecting that a value set is never used. For example: For example: contract test { function f(bool condition) public return (int) { int x; int y = 5; if (condition) { x = 102; } return x; } } This code has two problems: y is never used, and the value of x might be returned without it being given a value. In compiler theory this is done with reaching definitions. Solang already has an implementation of reaching definitions for the constant propagation pass, which will have to be generalized. Unused variables should be removed from the generated code. Secondly, implement a common subexpression elimination pass, which also uses the same reaching definitions implementation, to ensure subexpressions can safely be substituted. Learning Objectives 1) learn how to be a positive collaborator and contributor in an active open source project. 2) Learn how to work within the Hyperledger open source ecosystem and culture. 3) Understand smart contracts and the Solidity language 4) Gain a greater understanding of compiler optimizations and compiler theory Expected Outcome 1) Solang gives errors when undefined variables are used 2) Solang gives warnings when variables are not used, and removes them from the generated code 3) Solang does a common subexpression elimination pass
Hyperledger
Solidity is a language for Smart Contracts used by the Ethereum Solidity compiler. Solang is a new implementation of the Solidity compiler, which can target wasm on more blockchains. Solang is written in rust and uses a generated Solidity parser. Modern IDEs provide syntax highlighting, symbol definition, errors, warnings etc. This is often done via the Language Server Protocol. There are no good implementations of a language server for Solidity, however using the parser and resolver of Solang, this can change. The idea of this mentorship is to extend the Solang Compiler project so it can run as a language server, that implements the Language Server Protocol.
Hyperledger
Hyperledger Umbra is a Hyperledger Lab designed to run unmodified versions of our DLT platforms (e.g. Hyperledger Fabric, Hyperledger Iroha) under a simulated environment with software defined networking for the purposes of running experiments (e.g. scaling experiments, consensus algorithm development, etc) and security audits. Currently Hyperledger Umbra can run unmodified Hyperledger Fabric Docker images and execute a full Fabric network under simulation. Umbra is written in Python and has code for doing virtual network switches and connections. This project is to extend that code to allow for network fuzzing capabilities. The goal is to be able to introduce packet drops, packet delay, packet reordering, as well as unsolicited packets with random/known-bad data. The purpose it be able to test Hyperledger Fabric's resilience to general network "weather" and intentional attacks coming from the network.
Hyperledger
A growing part of our community is our partnership with academia. Hyperledger Fabric and other Hyperledger projects are being incorporated in to research and education in universities more and more all over the world. Hyperledger can aid the growth by preparing study materials, sample lab experiments and quizzes and tests that teach computer science students about distributed systems and consensus algorithms and cryptography. Hyperledger Umbra has streamlined the process of setting up a full Hyperledger Fabric network running on a single computer. It provides an ideal environment for students to learn Hyperledger Fabric administration as well as use it for running lab experiments and learning exercises. This mentorship is focused on producing a "classroom-in-a-box" for an introductory computer science course on distributed systems and algorithms that can be offered to universities that wish to use Hyperledger Fabric in their curriculum.
Hyperledger
Umbra has been developed in the past 2 years thanks to successful internship projects, its final target is the development of a platform for emulating blockchain projects and conducting academic research. This year the goal of the internship project is to unleash the full potential of Umbra, therefore running large scale tests added to chaos engineering mechanisms. The intern is going to work on mechanism that enable chaos engineering in Umbra, execute large scale tests in cloud providers (thousands of nodes), and present measurement reports of blockchain and infrastructure metrics. The goal is to enhance Umbra to a stable release, prove its full potential, and produce material to be reproducible by different academic institutions teach and perform research with the developed Umbra experiments. Expected Outcome Enhance Umbra source code, enable a stable experimentation environment for Umbra in cloud environments with large topologies (e.g., thousands of nodes), generate chaos engineering mechanisms in Umbra, capture the events in dashboards, and generate comprehensive reports detailing an Umbra experiment.
Hyperledger
For the past two years, the Hyperledger Umbra lab has been worked on by mentees to develop the capability of running the unmodified Hyperledger Fabric docker images under a simulated network environment for the purposes of doing experiments on running Fabric networks in a controlled way. At the end of last summer, Hyperledger Umbra achieved the initial goal of running Fabric networks under simulation. Hyperledger Umbra is useful for doing network-level security fuzzing as well as network scaling experiments and this mentorship is focused on designing and executing scaling experiments. Hyperledger Fabric networks are designed to scale up fairly easily, however nobody has actually tried scaling Hyperledger Fabric to many hundreds and thousands of nodes and done analysis on how it affects the characteristics of the distributed system such as time to reach consensus, time to run an election for block creation, etc. The mentee chosen for this project will work with their mentor to design a plan for setting up, executing, gathering and analyzing data, and reporting the results of scaling experiments run at different scales.
Hyperledger
The Hyperledger Web3j-android library is pivotal for developers integrating Android applications with Ethereum blockchain, leveraging the robust capabilities of Hyperledger web3j in a mobile context. Despite its critical role, the current state of web3j-android, last updated to version 4.8.8, faces challenges in coherence, functionality, and modern Android development practices. This project proposes a comprehensive update and restructuring of the web3j-android library to align with the latest Android development standards and Ethereum blockchain technologies. Learning Objectives - To establish a unified and coherent versioning and release strategy for web3j-android that aligns with web3j core releases, ensuring seamless functionality across platforms. - To enhance compatibility by updating the library to support the latest Android SDK versions, ensuring it meets modern app development requirements. - To refactor existing codebase for improving support and compatibility in Android context - To introduce comprehensive testing and documentation, providing a solid foundation for developers to contribute and leverage the library effectively.

Linux Foundation
The executable behavior of the RISC-V specification is encoded in UDB using a language called ISA Description Language (IDL). IDL is syntactically similar to C/C++/Verilog, but is both strongly and statically typed to eliminate ambiguity. This mentorship opportunity will involve the development and maintenance of IDL code in the database. Tasks could include writing a RISC-V extension in IDL (for example, the Vector extension), testing existing IDL using compliance tests, and fixing IDL bugs. Familiarity with a hardware description language like Verilog, design verification, and computer architecture are desirable.

Linux Foundation
"Caravan: Caravan is a framework that aims to provide CHISEL Designers with an easier way to create and integrate open-source bus protocols in their designs. It is a part of SoC-Now SoC Generator where this framework is the medium for connecting bus interconnects within the design for communication of core and devices. SoC-Now that accepts parameters and generates an entire SoC consisting of a Core with selective extensions and other configuration, devices which are selected via parameters and a Bus Interconnect that is used as the communication medium between the Core and the Devices, which is also selected by means of parameters. Currently SoC-Now contains the implementation of Wishbone and Tilelink Uncached Lightweight (TL-UL). Tilelink Uncached Heavyweight (TL-UH) TL-UH is the bus protocol standardized by SiFive that is an extension of TL-UL and contains additional operations such as burst and atomic operations."
Linux Foundation
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.
RISC-V
"The evolution of KVM (Kernel-based Virtual Machine) unit tests from a virtualization testing framework to one that also encompasses bare metal testing allows us to build a comprehensive unit test framework for Supervisor Binary Interface(SBI) in RISC-V. The need for a standalone, comprehensive unit test framework for SBI has become increasingly evident. Validation of the SBI specification has traditionally been intertwined with feature implementations across OpenSBI, KVM, and the Linux kernel. By establishing a dedicated unit test framework, we aim to streamline the identification and rectification of bugs early in the development cycle, thereby ensuring a robust and reliable specification for RISC-V's growing ecosystem. The RISC-V support along with a few SBI extensions got merged[1] recently, which enabled basic SBI extensions and SMP/EFI support in kvm-unit-tests for RISC-V. Expanding the coverage of both existing and forthcoming SBI extensions is critical to accelerating the development and adoption of the SBI specification. Besides generally improving kvm-unit-tests, tests for the following SBI extensions may be added: SBI PMU support Bare Metal testing using OpenSBI firmware Virtualization testing with KVM SBI Steal time extension support Virtualization testing with KVM SBI Debug Trigger extension Bare Metal testing using OpenSBI firmware Virtualization testing with KVM Any other extensions (SUSP, MPXY ?) CoVE related tests (time permitting)
Linux Foundation
Zowe docs consist of several high-level sections such as Getting Started, User Guide, Extending, etc. Due to the limitation of the Vuepress (current site generator) sidebar depth, the sidebar or navigation experience is not satisfactory. Also most open source docs now provide a three column layout and many other social functions such as Share. The goal is to provide a good and more industry-standard doc navigation experience for the Zowe doc site with better UI and functions that engage users. A new site generator can be explored. Details at https://github.com/zowe/docs-site/issues/1587
Cloud Native Computing Foundation (CNCF)
Inspektor Gadget is an eBPF tool and systems inspection framework for Kubernetes, containers and Linux hosts. A Gadget is an OCI image that includes one or more eBPF programs, metadata YAML file, and optionally, WASM modules for post processing. As OCI images, they use the same tooling as containers: building, pushing/pulling from OCI Registries. But today, Inspektor Gadget does not have good tooling for inspecting a gadget: the ig image inspect command just gives the gadget name, digest and creation date without further details. Expected Outcome: the ig image inspect command tells the architectures supported by the gadget, the layers included in the OCI image, the data sources with their fields, the eBPF parameters. Additionally, inspecting the eBPF module can provide the ELF sections, the eBPF maps and the disassembled eBPF bytecode annotated with the source when available.
Linux Foundation
Integrated Cloud Native (ICN) Blueprint (BP) family intends to address deployment of workloads at large number of edges and public clouds using Kubernetes (K8s) as resource orchestrator at each site and ONAP4K8s as service level orchestrator across sites. ICN BP is an end2end solution that provides a software stack integrating multiple layers of software such as Service orchestrator, Resource Orchestrator, Software and hardware accelerator plugins etc. Objective of ICN BP is to have single stack for Enterprise, Telco and IoT use cases. Major work items where the intern can help are – 1. Bug fixes and improving installation scripts 2. KUD integration, tuning, and adding new features 3. Maintaining current CI/CD systems 4. Integrating Cluster API into ICN local controller
Linux Foundation
APPLICATIONS ARE CLOSED. Please apply again in the Fall! We will post more information when it is available. Linux is the most widely used operating system in the world. The core software component of the Linux operating system is the kernel. Some of its roles include managing hardware interactions, virtualizing system resources, and enforcing security constraints. In effect, the Linux kernel powers almost all of the world's top supercomputers, android phones, and an innumerable variety of other computers. This course will introduce students to the Linux kernel development by focusing on device driver development, particularly character devices and the /proc and/sys interfaces. This will give students hands-on experience working with internal Linux kernel APIs for hardware access, memory management, DMA and interrupts, among other, and provide an overview of some of the core features and components of the kernel, such as scheduling, system calls, the boot process, and hardware description trees. Gaining an understand of the inner workings of the operating system and how to make changes to it will give students an invaluable perspective on how computers work behind the scenes, which will reveal a new layer of understanding to apply to any future software engineering practice. This is a new format of the following courses we created: https://www.uml.edu/catalog/courses/COMP/3085 or https://www.uml.edu/catalog/courses/COMP/5170

Hyperledger
Hyperledger Iroha 1 has a great set of commands and queries, but some useful commands and queries are missing. Iroha 1 blockchain can be the core of banking systems because it supports transactions, multiple currencies, etc. Nevertheless, advanced filtering of transactions is only partially available in Iroha 1, and it's necessary for banking systems. Currently, to filter transactions, we need to return many of them and filter with our code - it is much heavier for both Iroha's node and client application. During the internship project, queries should be extended with optional arguments. The mentee will be able to learn the following: - the architecture of Iroha (1.x), - work in the true spirit of open-source, communicating with the Iroha community, joining calls, etc. - writing documentation, - following rules of the open-source code of Hyperledger Iroha - creating automatic tests of code Expected Outcome - Implementation according to description and plan of documentation and tests. - Added the possibility of running modified queries from Iroha's client libraries. - Present changes during the Iroha bi-weekly meeting at the end of the internship.

Cloud Native Computing Foundation (CNCF)
Up to four versions of Istio are supported at one time, and so the documentation for each must be available. Our current site search is outdated and needs to be replaced, so that the search content only exists in the site search, and only fresh content is available on google.com. Expected Outcome: Working site search on istio.io, which lets you search for content for the currently supported versions.

Cloud Native Computing Foundation (CNCF)
Jaeger UI is built on React. While we are seemingly already on v18.x of React, the upgrade was not done across the board and some other dependencies are still lagging behind, e.g. `"@types/react": "16.8.7"`. It's also blocking upgrades of other dependencies. This project is likely to involve a substantial amount of code contribution, as certain upgrade require fixing the code to use the new APIs, and sometimes we may run into dependencies that are EOL and need to be replaced altogether. - Expected Outcome: Ideal outcome is to have _all_ dependencies upgraded to the latest versions (with the help of @dependabot) and fix all deprecation warnings during the build. But incremental progress towards that goal is also acceptable.
Linux Foundation
Monitor and troubleshoot transactions in complex distributed systems

Linux Foundation
Jenkins is an open source automation server. It provides thousands of plugins to support building, testing, deploying and automating virtually any project at any scale. Your donations help to keep the project going and to accelerate its evolution. More information about how we use donations: https://jenkins.io/donate/

Cloud Native Computing Foundation (CNCF)
K8sGPT is a tool for scanning Kubernetes clusters, diagnosing and triaging issues with the help of GenAI. It has SRE experience codified into its analyzers. These analyzers are critical for K8sGPT to perform its in-depth analysis. There are a few analysers that have either limited or absent unit tests. The goal is to introduce more unit tests which will reflect mocked problematic/misconfigured K8s resources and assure K8sGPT analysers can catch and identify those test scenarios. Expected Outcome: Introduce and enhance Test Coverage of K8sGPT's analyzers

Cloud Native Computing Foundation (CNCF)
kpm is a package management tool for KCL. kpm needs to refactor the local storage structure of the current dependencies to support storage of packages with the same name from different OCI registes and caching of the remote dependencies. Expected Outcome: The local storage structure has been designed in issue https://github.com/kcl-lang/kpm/issues/384, and the feature in issue need to be implemented.
Cloud Native Computing Foundation (CNCF)
KWOK (Kubernetes WithOut Kubelet) is a toolkit that enables setting up a cluster of thousands of Nodes in seconds. KWOK is currently being used by a number of projects for testing and performance. It is crucial that KWOK itself behaves consistently. The following tests are currently being considered: Unit Test, E2E Test, Edge Cases. Expected Outcome: Improved test coverage for KWOK.

Cloud Native Computing Foundation (CNCF)
Kagent is an open-source framework for DevOps and platform engineers to run AI agents in Kubernetes, automating complex operations and troubleshooting tasks. We have a few agents for kagents (Kubernetes, Istio, Cilium, Argo, Prometheus, Grafana etc) and would love to build more agents for other CNCF graduated or incubation projects so users can use conversation style to chat with the agents to either learn or troubleshooting or operating these projects. - Expected Outcome: Able to build at least 2-3 agents for CNCF graduated or incubation projects. Able to write a blog for the work and produce associated docs as well. Upstream Issues: - https://github.com/kagent-dev/kagent/issues/662 - https://github.com/kagent-dev/kagent/issues/664

Cloud Native Computing Foundation (CNCF)
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.

Cloud Native Computing Foundation (CNCF)
As a user, I want to be able to call arbitrary URLs via webhooks that are registered on Keptn events to interact with systems outside of Keptn. Therefore, I would like to use a templating mechanism to define payloads to be able to interact with external systems.

Linux Foundation
The mission of the KernelCI project is to ensure the quality, stability and long-term maintenance of the Linux kernel by maintaining an open ecosystem around test automation practices and principles.
Linux Foundation
The Linux kernel development uses a number of tools, checkpatch.pl, coccinelle scripts, sparse, etc. and these tools report certain findings. While the valid ones are addressed by the kernel developers, the invalid tool findings are manually assessed and not acted upon. Over time with addressing the valid findings, the proportion of invalid findings increase compared to newly appearing valid findings, as invalid findings of those tools are not marked and tracked over the various versions. Klever provides a Web UI to track false positive findings from static analysis tool. Extend Klever to allow to import findings from checkpatch.pl, coccinelle scripts, sparse, etc.
Cloud Native Computing Foundation (CNCF)
Kmesh now has an e2e testing framework, but it only covers some of the usage scenarios for key features. More test cases need to be covered to ensure the stability of key features. Expected Outcome: 1. e2e Test Cases 2. Documentation maintenance for e2e testing

Cloud Native Computing Foundation (CNCF)
Creating a Knative Kafka Broker requires developers to specify the number of partitions the backing Kafka topic should have, however, this is not an easy decision to make and it requires planning based on the expected load the Knative Broker could receive. This project aims to remove this configuration setting by having an autoscaler that is responsible to add or remove partitions based on the effective load the Knative Kafka Broker receives while preserving [ordered and unordered delivery features](https://knative.dev/docs/eventing/brokers/broker-types/kafka-broker/#configuring-the-order-of-delivered-events) for Triggers. - Expected outcome: A Knative Kafka Broker can be created without setting the number of partitions and the number of partitions for a topic backing the Knative Kafka Broker increases or decreases based on the observed load received.
Start with GSoC, European Summer of Code, Outreachy, or LFX — then drill into orgs.