![]() What is the change management plan and deprecation plan (if any) for the current chat communities?.What are the technical requirements for a migration?.What resources are able to be allocated to stand up any new chat platforms (or work through a migration plan)?.What support will be provided if we choose a chat platform that is not supported by the LFIT?.Ry: on the order of hundreds a month is OK. ![]() What is the Linux/Hyperledger Foundation willing to spend on a chat platform?.How do we keep chat channel choices visible and easy to find regardless of the platform or strategy we choose?.The others are not mentioned on the Hyperledger website.)(Ry: good point - I propose decision 0 is "should Hyperledger have an official chat platform?") (Ry: we already do - APAC is on WeChat, Iroha is primarily on Telegram, several community groups use Whatsapp, etc) (Tracy: We have one official chat for Hyperledger. Should the Hyperledger projects all operate on the same platform, or should they be allowed to choose a platform that best supports their community needs? Based on discussions in the TSC, we should not have multiple chat mechanisms within Hyperledger.What platform should Hyperledger focus its efforts on (Discord, RocketChat, other)?. ![]() Should Hyperledger have an official chat platform? Hyperledger needs to determine a way forward for its community chat channels by the end of the year to ensure the Hyperledger community can scale with the projects within it. The move to Matrix was met with challenges and abandoned. ![]() Hyperledger currently supports RocketChat for all of its community chat needs, but this technology is insufficient. Hyperledger Project documentation files are made available under the Creative Commons Attribution 4.0 International License (CC-BY-4.0), available at. Hyperledger Project source code files are made available under the Apache License, Version 2.0 (Apache-2.0), located in the LICENSE file. Hyperledger Fabric Issue Tracking (GitHub Issues) There’s always plenty to do! Check the documentation on how to contribute to this project We welcome contributions to the Hyperledger Fabric project in many forms. It's recommended for first-time users to begin by going through the Getting Started section of the documentation in order to gain familiarity with the Hyperledger Fabric components and the basic transaction flow. Information on getting started using and developing with the fabric, SDK and chaincode: Documentation, Getting Started and Developer Guides Please visit the GitHub issues with Epic label for our release roadmap. Unless specified otherwise, all releases will be upgradable from the prior minor release.Īdditionally, each LTS release is upgradable to the next LTS release.įabric releases and release notes can be found on the GitHub releases page. v1.4.x (maintenance ended in April 2021 with the delivery of v1.4.12).v2.2.x (maintained through December 2023).LTS release, and to the prior LTS release during periods of LTS release overlap. Important fixes will be backported to the most recent Additionally, certain releases are designated as long-term Releasesįabric provides periodic releases with new featuresĪnd improvements. Open source architecture Hyperledger Fabric is your starting point. Planning for theįuture of enterprise blockchain requires building on top of a fully-vetted, Hyperledger Fabric delivers a uniquely elastic and extensible architecture,ĭistinguishing it from alternative blockchain solutions. Intricacies that exist across the economic ecosystem. Implementations of different components, and accommodate the complexity and Hyperledger Fabric is a platform for distributed ledger solutions, underpinnedīy a modular architecture delivering high degrees of confidentiality, The Hyperledger Project Lifecycle document. Information on what Graduated entails can be found in For more information on the history of this project see the Fabric wiki page. This project is a Graduated Hyperledger project.
0 Comments
Leave a Reply. |