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: Getting Starter Kit into Labs | 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. | ||
ProposalsTo submit a new proposal, please follow the process outlined at Hyperledger Labs. The lab proposal must meet the following: | |||
| |||
|
| ||
|---|---|---|---|
| ---- ANS: based on our last call, Primary sponsor would be Bobbi and Second sponsor would be Tracy | Sponsors do not have a responsibility beyond this; ongoing work like contributing code or reviews is not tied to their role as sponsors. In reviewing the proposal, the sponsor(s) make sure that the proposal is cogent, and novel (in conception, proposed execution, or interested community). To find sponsors a. the proposers can use their connections to existing projects and ask maintainers b. 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. | Bobbi Muscara Sponsor / TSC committee Member Tracy Kuhrt TSC / Lab Stewart |
|
| ||
| layout | title | parent |
|---|---|---|
default | Lab Proposal Starter Kit | Labs |
Lab Name
Starter Kit ( Pick your experience)
Short Description
The ________________________ configurator tool developed under Shell scripting, for learners and developers who would like to learn Hyperledger frameworks with different Customized Configurations instantly.
Instantly you can create docker-compose templates. Product owners can leverage this tool at any point in time for prototypes.
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.
Hyperledger mission: fits in how? to allow easy of entry into .... Set up POC easily
Initial Committers
Enter the Github IDs for the set of initial committers.
- https://github.com/<user_id1>
- https://github.com/<user_id2>
- ...
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.
- https://github.com/<user_id> or Name (email@example.org) - Role (e.g., "Chair of the XXX workgroup")
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.
- https://github.com/<your_repo>
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:
The scope of the proposed lab fits within Hyperledger’s mission;
The proposed name is appropriate (e.g., not too generic, confusing, or conflicting with other labs or projects, etc);
Proposers have a Sponsor (i.e. a maintainer of one of the Hyperledger projects, a TSC member or a WG chair);
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
https://github.com/hyperledger-labs - Github Organization
Communication
Mailing List
labs@lists.hyperledger.org for general discussions on Hyperledger Labs (subscribe - archives)