labs.hyperledger.orgLabs | Hyperledger

Labs Link Menu Expand (external link) Document Search Copy Copied Labs AI FAQ for Hyperledger Ecosystem Agora Aries Agent Controller Automated-Gateways Benchmarking Cross-Chain Bridges Blockchain Carbon Accounting Blockchain Explorer CC-Tools CCKit Cardea Documentation Template Electrodo.Docs Fablo Fabric Channeled Add-ons Gen Fabric Operations Console Fabric Operator Fabric Token Java SDK Harmonia Hyperledger Community Management Tools Hyperledger Fabric Chaincode Builder for Kubernetes Hyperledger Fabric Connector Hyperledger Fabric Operator for Kubernetes Hyperledger Fabric Smart Client Hyperledger Fabric SmartBFT Library Hyperledger Fabric Token SDK Learning Tokens Mosaique Open Enterprise Agent Operations Smart Contract for Hyperledger Fabric Orion Perun Private Data Objects Solang Playground Splice TDIDN Tempo Trusted Compute Framework Weaver DLT Interoperability YUI did:webs DID Method Implementation fabric-ansible-collection Archived Labs Aries SDK for Mendix Aries Wrapper For Fabric Avalon SDK Python BDLS Besu Operator Blockchain Analyzer Blockchain Automation Framework Blockchain Integration Framework Blockchain Verifier Business Partner Agent Byzantine-Config Chaincode Analyzer Citizens Pulse Convector Framework Cordentity Donor Milk Transparency and Traceability EasyDoser Ethercluster Fabex Fabric Docs CN Fabric Docs ML Fabric Machine Fabric Multi Channel Network Samples FireFly Gardener HL Starter Kit HyperFabGames Hyperledger Fabric Based Access Control Hyperledger Fabric Block Archiving Hyperledger Fabric Chrome Extension Hyperledger Fabric Consortium Management Hyperledger Fabric Haskell Chaincode Hyperledger Fabric Lightweight Client Hyperledger Fabric Private Chaincode Hyperledger Fabric WebAssembly chaincode Inter Carrier Settlements Karma Charity Foundation Platform Keyhole Fabric API Gateway Media Tracking Platform to Tackle Online Piracy MinBFT Minifabric Mir-BFT Modern Pharmacy Management NFT Auction App NFT Community Footprint Nephos Patient Consent Payments Performance Test Harness PerformanceSandBox Pluggable Hedera Consensus Service Proof of Elapsed Time 2 PubSub Interop SParts Sawtooth Healthcare ScoreX Sunyar fabric Topologies for Hyperledger Fabric TrustID Umbra University Course Fabric crypto-lib dancap eThaler fabric-chaincode-OCaml fabric-client-flutter fabric-server-node fabric-vms-provision microfab neferti private-transaction-families solang solidity2chaincode weft xcsi z-mix Hyperledger Labs Governance Hyperledger Labs Lab Proposal Document Maintainers Stewards This site uses Just the Docs , a documentation theme for Jekyll. GitHub Wiki Chat Hyperledger Labs Hyperledger Labs provides a space (i.e., GitHub repos) where work can easily be started without the creation of a project. Please refer to the Hyperledger Labs wiki page for additional information. Process to propose a new lab Fork the hyperledger-labs.github.io repository. Fill out the Proposal Template and save it into the labs subdirectory under the name of your lab, such as mynewlab.md. It is expected that your lab repository will have the same name so keep that in mind. In the Proposal Template, there is an entry for sponsor(s). Although not required, proposers are encouraged to seek a sponsor who can help them create ties with the rest of the Hyperledger community and ensure that the proposal is cogent and novel (in conception, proposed execution, or interested community). To find sponsors: use your connections to existing projects and ask maintainers, find working groups or projects with affinities to the proposed lab and pitch the project (good to have the template already filled out) in associated channels and/or mailing lists. The WG chairs emails, the maintainers contacts etc can be found on the wiki or github. Make personal appeals if you can. Every repository contains a MAINTAINERS file that lists the current maintainers with their contact information and you can reach them all by posting to the Maintainers list . Commit your changes with proper sign-off. This means that your commit log message must contain a line that looks like the following one, with your actual name and email address: Signed-off-by: John Doe john.doe@example.com Adding the -s flag to your git commit command will add that line automatically. You can also add it manually as part of your commit log message or add it afterwards with git commit amend -s . Submit a Pull Request. The labs stewards will then review your proposal. Like sponsors, stewards do not have a responsibility beyond this; ongoing work like contributing code or reviews is not tied to their role as stewards. In reviewing the proposal, the stewards make sure that the proposal is cogent and novel (in conception, proposed execution, or interested community). Bringing in an existing repository By default the Lab stewards will create a new repository for you to start from but if you have an existing github repo you would like to bring to your proposed lab you have the option to request for that repo to be reused instead. This is however only possible if every commit in your existing repo is signed-off so there is no DCO related issues. If that is not the case, you will need to bring your code by squashing all of your commits into a single first commit made against your new lab repo with your sign-off. License requirement All Hyperledger software must be made available under an Apache 2.0 license . This applies to Labs. Please, make sure to license all incoming code and new code accordingly, and ensure that all commits are made with proper sign-off so that no DCO related issue is introduced. Code of Conduct All Hyperledger community members must adhere to the Code of...