You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Hyperledger can help build communities by gathering people sharing a common interest in developing blockchain related software.

However, the only way to currently do so is to submit a HIP and launch a formal project in Incubation. This is a relatively heavy process which implies a level of endorsement by Hyperledger that is not suitable for cases where projects are immature from a code-complete, production-quality, or community building perspective, or experimental.

hyperledger-labs.github.io

Fork to get Started

Current Projects

Issue
Status

Motivation

Labs will

1) lower the pressure on the TSC to start new projects 

2) allow for work to be done within a legal framework that eases the transition to a project in Incubation in cases where this ends up being the chosen path for the lab.

In particular, this includes enforcement of the use of the Apache Software License and sign-offs on all contributions.

This new space will allow teams to experiment with new frameworks or new modules without the promise of stable code or MVP. It is a space suitable for innovation and testing of ideas. 

This new space will allow teams to experiment with new frameworks or new modules without the promise of stable code or MVP.

It is a space suitable for innovation and testing of ideas. 

--- ANS:  Im working on a test to ensure the code is stable before the push to lab repository.



Proposals

To submit a new proposal, please follow the process outlined at Hyperledger Labs. The lab proposal must meet the following:




  1. The scope of the proposed lab fits within Hyperledger's mission;




  1. The proposed name is appropriate (e.g., not too generic, confusing, or conflicting with other labs or projects, etc);

  • Here are my suggested Lab Names

    Hyperledger CLI StarterKit

    Hyperledger LearnersKit

    Hyperledger Microservices kit



  1. Proposers have a Sponsor (i.e. a maintainer of one of the Hyperledger projects, a TSC member or a WG chair);
---- ANS: based on our last call,  Primary sponsor would be Bobbi and Second sponsor would be Tracy

  1. Proposers need to be active members of the Hyperledger technical community (as defined in Section 4.a.ii of the Hyperledger Charter).
  • --- ANS :  I'm part of fabric contributor,  India chapter, LMDWG  team in Hyperledger Umbrella. Will that be considered as an active member proposer ...?






layouttitleparent

default

Lab Proposal Document

Labs

Lab Name

Enter the name of your lab here.

Short Description

Provide a short description of your lab. This will be used for the Github repository's description.

Scope of Lab

Enter the scope of the lab. This should include enough information to allow the Lab stewards to understand how it fits within Hyperledger's mission.

Initial Committers

Enter the Github IDs for the set of initial committers.

Sponsor

Provide the name of your sponsor. A sponsor is required and must be a maintainer of one of the Hyperledger projects, a TSC member, or a WG chair.

Pre-existing repository

If you currently have a Github repository that you wish to transfer to the Hyperledger Labs organization, please provide a link here. NOTE: Please refer to the README for additional information on existing repositories.

image2020-11-2_11-11-23.png


Hyperledger can help build communities by gathering people sharing a common interest in developing blockchain related software. However, the only way to currently do so is to submit a HIP and launch a formal project in Incubation. This is a relatively heavy process which implies a level of endorsement by Hyperledger that is not suitable for cases where projects are immature from a code-complete, production-quality, or community building perspective, or experimental.

Labs will 1) lower the pressure on the TSC to start new projects and 2) allow for work to be done within a legal framework that eases the transition to a project in Incubation in cases where this ends up being the chosen path for the lab. In particular, this includes enforcement of the use of the Apache Software License and sign-offs on all contributions.

This new space will allow teams to experiment with new frameworks or new modules without the promise of stable code or MVP. It is a space suitable for innovation and testing of ideas.

Examples of possible labs: projects too early for TSC approval as an incubator because there’s not a lot of code; demos; documentation examples; sample code from hackathons, research projects, etc.

Hyperledger Labs have similarities with the Apache Labs and the W3C Community Groups.

Proposals

To submit a new proposal, please follow the process outlined at Hyperledger Labs. The lab proposal must meet the following:

  1. The scope of the proposed lab fits within Hyperledger’s mission;

  2. The proposed name is appropriate (e.g., not too generic, confusing, or conflicting with other labs or projects, etc);

  3. Proposers have a Sponsor (i.e. a maintainer of one of the Hyperledger projects, a TSC member or a WG chair);

  4. Proposers need to be active members of the Hyperledger technical community (as defined in Section 4.a.ii of the Hyperledger Charter).

You can find all Hyperledger Lab approved proposals at https://github.com/hyperledger-labs/hyperledger-labs.github.io/labs. You can also look at the pull requests for all submitted proposals.

Archiving

Stewards are responsible for curating the set of labs, moving to an archives space (see below) those that become dormant or unresponsive for an extended period (6+ months), or are explicitly deemed by the committers to be deprecated/obsoleted.

Deprecated, obsoleted, or dormant labs (as defined above) will be moved to a GitHub org “hyperledger-labs-archives” that signifies that the lab is no longer maintained. Labs in the archives are read-only, and they can be moved back out of the archives, if there is interest in reviving them.

Repository

Communication

Mailing List






  • No labels