Published using Google Docs
Hyperledger Fabric SDK Working Group Charter
Updated automatically every 5 minutes

Fabric SDK Working Group Charter - Hyperledger Project

Introduction

A well designed SDK that can abstract the communication protocol details required to connect to a network of nodes running Fabric software is essential so that application developers can focus on the business problems. A well designed SDK would also provide a powerful API to the application developers while hiding the unnecessary complexities as well as any future protocol changes involved in interacting with the Fabric network. The purpose of the Fabric SDK Working Group is to define the specifications required to implement such a well designed SDK in any programming language.


Scope
        Fabric SDK working group is working towards creating the specifications that are applicable for “Fabric” project only.  This working group is not discussing specifications required for other projects in Hyperledger Foundation.

Work Products

The Fabric SDK working group will produce a document containing detailed API specifications for the following topics:

Collaborators

        Consists of team members from Fabric-SDK-Java, Fabric-SDK-PY, Fabric projects.

Process of the Group

The group is currently open to anyone who wishes to participate. There are frequent calls announced on the hyperledger technical and tsc mailing lists or any other medium that the TSC agrees on. There will be a chair or co-chairs depending on the work and availability of volunteers.

Transparency

  1. All meetings are open to public and will be conducted in a professional manner.
  2. Meeting minutes are posted at https://wiki.hyperledger.org/groups/fabric-sdk/fabric-sdk-wg


Amendments

Changes to this charter can be made if necessary by submitting a change request to the Hyperledger Project TSC and obtaining supermajority vote from the TSC members.

Disbanding

The group may be disbanded after the following conditions are met.

i) Fabric project reaches maturity and any changes in protocol to interact with Fabric network become minimal to none.

ii) Broad adoption of Fabric project by developer community providing evidence that SDK api is usable and developer friendly.