dpitt · dpitt · Feb 5, 2019 · Feb 8, 2019 · Feb 25, 2019 · Mar 14, 2019
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -0,0 +1,9 @@
+## Checklist for Hyperledger Lab Proposal PR
+
+- [ ] Read [README.md](https://github.com/hyperledger-labs/hyperledger-labs.github.io/blob/master/README.md) carefully
+- [ ] Make sure your changes are committed with the proper sign-off
+- [ ] Use the labs name as the PR title
+- [ ] Copy the short description of the proposal as the description of the PR
+- [ ] Remove this checklist section
+- [ ] Submit your PR and the labs stewards will review your proposal
+- [ ] Ask your sponsor to confirm sponsorship by stating so in a comment to the PR
diff --git a/.github/settings.yml b/.github/settings.yml
@@ -0,0 +1,14 @@
+repository:
+  name: hyperledger-labs.github.io
+  description: Hyperledger Labs
+  homepage: https://labs.hyperledger.org/
+  default_branch: master
+  has_downloads: false
+  has_issues: true
+  has_projects: false
+  has_wiki: false
+  archived: false
+  private: false
+  allow_squash_merge: false
+  allow_merge_commit: false
+  allow_rebase_merge: true
diff --git a/.gitignore b/.gitignore
@@ -1,2 +1,4 @@
 .DS_Store
-**/.DS_Store
+**/.DS_Store
+_site/*
+.jekyll-cache/*
diff --git a/CNAME b/CNAME
@@ -0,0 +1 @@
+labs.hyperledger.org
diff --git a/CODEOWNERS b/CODEOWNERS
@@ -0,0 +1 @@
+*       @lehors @tkuhrt @trbs @vipinsun
diff --git a/README.md b/README.md
@@ -2,25 +2,40 @@
 
 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](https://wiki.hyperledger.org/labs)
+the [Hyperledger Labs wiki page](https://wiki.hyperledger.org/display/labs)
 for additional information.
 
 ## Process to propose a new lab
 
-Fork the [hyperledger-labs.github.io](https://github.com/hyperledger-labs/hyperledger-labs.github.io) repository.
+1. Fork the [hyperledger-labs.github.io](https://github.com/hyperledger-labs/hyperledger-labs.github.io) repository.
 
-Fill out the [Proposal Template](https://github.com/hyperledger-labs/hyperledger-labs.github.io/blob/master/proposal-template.md)
+2. Fill out the [Proposal Template](https://github.com/hyperledger-labs/hyperledger-labs.github.io/blob/master/proposal-template.md)
 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.
 
-Submit a Pull Request.
+3. In the Proposal Template, there is an entry for sponsor(s). The sponsor(s) are responsible for reviewing the proposal. 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.
+
+4. 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`.
+
+5. Submit a Pull Request.
 
 The labs stewards will then review your proposal.
 
 ## Bringing in an existing repository
 
-By default the Lab stewards will create a new respository for you to
+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

diff --git a/_config.yml b/_config.yml
@@ -0,0 +1,17 @@
+title: "Hyperledger Labs"
+logo: "/hyperledger-logo.png"
+url: "https://labs.hyperledger.org"
+description: "Start here to propose a Hyperledger Lab"
+show_downloads: "false"
+has_children: true
+has_toc: true
+aux_links:
+  "GitHub":
+    - "//github.com/hyperledger-labs"
+  "Wiki":
+    - "//wiki.hyperledger.org/display/labs"
+  "Chat":
+    - "//chat.hyperledger.org/channel/labs"
+# Switch next two lines for local debugging
+# theme: just-the-docs
+remote_theme: pmarsceill/just-the-docs
diff --git a/favicon.ico b/favicon.ico
diff --git a/hyperledger-logo.png b/hyperledger-logo.png
diff --git a/index.md b/index.md
@@ -0,0 +1,55 @@
+---
+layout: default
+title: Labs
+nav_order: 1
+has_children: true
+has_toc: false
+---
+[//]: # (SPDX-License-Identifier: CC-BY-4.0)
+
+# 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](https://wiki.hyperledger.org/display/labs)
+for additional information.
+
+## Process to propose a new lab
+
+1. Fork the [hyperledger-labs.github.io](https://github.com/hyperledger-labs/hyperledger-labs.github.io) repository.
+
+2. Fill out the [Proposal Template](https://github.com/hyperledger-labs/hyperledger-labs.github.io/blob/master/proposal-template.md)
+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.
+
+3. In the Proposal Template, there is an entry for sponsor(s). The sponsor(s) are responsible for reviewing the proposal. 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.
+
+4. 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`.
+
+5. Submit a Pull Request.
+
+The labs stewards will then review your proposal.
+
+## 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](https://developercertificate.org/) 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.
diff --git a/labs/SParts.md → labs/archived/SParts.md b/labs/SParts.md → labs/archived/SParts.md
@@ -1,3 +1,8 @@
+---
+layout: default
+title: SParts
+parent: Archived Labs
+---
 # Lab Name
 
 SParts
@@ -21,4 +26,4 @@ Dan Middleton (dan.middleton@intel.com)
 
 # Pre-existing repository
 
-There is a pre-existing public repository available at https://github.com/Wind-River/sparts. We would copy over all the code except for the /apps directory. We did not initially use the git commit sign-off option and therefore need to recommit all the code to the new repo with the sign-off option. I recommend creating a new empty repo where we can re-commit the relevant pieces using the -s option. 
+There is a pre-existing public repository available at https://github.com/Wind-River/sparts. We would copy over all the code except for the /apps directory. We did not initially use the git commit sign-off option and therefore need to recommit all the code to the new repo with the sign-off option. I recommend creating a new empty repo where we can re-commit the relevant pieces using the -s option. 
diff --git a/labs/archived/blockchain-analyzer.md b/labs/archived/blockchain-analyzer.md
@@ -0,0 +1,28 @@
+---
+layout: default
+title: Blockchain Analyzer
+parent: Archived Labs
+---
+# Lab Name
+Blockchain Analyzer
+
+# Short Description
+The aim of this lab is to create a tool for visualizing and analyzing Hyperledger Fabric ledger from both operational and data-oriented aspects. It provides dashboards similar to Hyperledger Explorer, but it is applicable for data queries (e.g. medicine provenance, supply chain) as well.
+
+The user can inspect the data of multiple peers and multiple channels at the same time.
+
+A further goal of this project is to be suitable for any blockchain solution.
+
+# Scope of Lab
+
+Internship project ([Analyzing Hyperledger Fabric Ledger, Transactions and Logs using Elasticsearch and Kibana](https://wiki.hyperledger.org/display/INTERN/Analyzing+Hyperledger+Fabric+Ledger%2C+Transactions%2C+and+Logs+using+Elasticsearch+and+Kibana))
+
+# Initial Committers
+- https://github.com/salmanbaset
+- https://github.com/balazsprehoda
+
+# Sponsor
+- https://github.com/lehors - Member of Hyperledger TSC
+
+# Pre-existing repository
+- https://github.com/balazsprehoda/hyperledger-elastic
diff --git a/labs/archived/chaincode-analyzer.md b/labs/archived/chaincode-analyzer.md
@@ -0,0 +1,34 @@
+---
+layout: default
+title: Chaincode Analyzer
+parent: Archived Labs
+---
+# Lab Name
+Chaincode Analyzer
+
+# Short Description
+A static tool to check and detect potentially risky codes in smart contracts (a.k.a, chaincodes).
+
+
+# Scope of Lab
+The aim of Chaincode Analyzer is to provide the way to check whether the smart contracts includes potentially risky codes or not.
+The tool performs static analysis on chaincode source codes written in Golang and detects potentially risky parts such as generating random values, accessing outside of blockchain networks and iteration on map object.
+For more details of the tool and target risks:
+https://github.com/FujitsuLaboratories/ChaincodeAnalyzer
+
+In Hyperledger Fabric, developers can use general purpose programming languages, such as JavaScript, Golang and Java, to implement their chaincodes.
+Compared to using domain specific languages (DSLs) like Solidity of Ethereum, the efforts of implementing smart contracts are smaller since developers do not need to study new language for smart contracts.
+On the other hand, there are some pitfalls when developers use general purpose programming languages for implementing smart contracts.
+For instance, Solidity does not have a method to generate random value since it easily causes different states during nodes which execute the smart contract including random value generation.
+Different to Solidity, general purpose programming languages such as Golang typically have a method to generate random value. 
+Therefore, we think there are needs for a tool to detect such blockchain related potential risks quickly.
+
+# Initial Committers
+- https://github.com/kzhry (Kazuhiro Yamashita)
+- https://github.com/Chinlying (Ence Zhou)
+
+# Sponsor
+- https://github.com/hartm (Hart Montgomery) - Member of Hyperledger TSC
+
+# Pre-existing repository
+- There is pre-existing public repository available at (https://github.com/FujitsuLaboratories/ChaincodeAnalyzer) as explained above. We would like to copy all the code since we did not use sign-off option.
diff --git a/labs/cordentity.md → labs/archived/cordentity.md b/labs/cordentity.md → labs/archived/cordentity.md
@@ -1,3 +1,8 @@
+---
+layout: default
+title: Cordentity
+parent: Archived Labs
+---
 # Lab Name
 Cordentity
 

diff --git a/labs/crypto-lib.md → labs/archived/crypto-lib.md b/labs/crypto-lib.md → labs/archived/crypto-lib.md
@@ -1,21 +1,26 @@
-# Lab Name
-crypto-lib
-
-# Short Description
-A project for experimentation on creating shared cryptography modules for cross-project collaboration
-
-# Scope of Lab
-The purpose of this lab is to serve as an initial launching point for what will hopefully become a shared Hyperledger cryptography library.  We aim to use this lab to set up a code base and experiment with integrating cryptographic protocols between projects.
-
-See:  https://docs.google.com/document/d/1JtFT5L-82egj6shgGXzTsNAg6_UHuMheKfsst6NS_Xo/edit?usp=sharing
-for more details.
-
-# Initial Committers
-hartm
-
-# Sponsor
-Hart Montgomery
-(Many more, see the project proposal document).
-
-# Pre-existing repository
-No!  That's why we're starting a lab.
+---
+layout: default
+title: crypto-lib
+parent: Archived Labs
+---
+# Lab Name
+crypto-lib
+
+# Short Description
+A project for experimentation on creating shared cryptography modules for cross-project collaboration
+
+# Scope of Lab
+The purpose of this lab is to serve as an initial launching point for what will hopefully become a shared Hyperledger cryptography library.  We aim to use this lab to set up a code base and experiment with integrating cryptographic protocols between projects.
+
+See:  https://docs.google.com/document/d/1JtFT5L-82egj6shgGXzTsNAg6_UHuMheKfsst6NS_Xo/edit?usp=sharing
+for more details.
+
+# Initial Committers
+hartm
+
+# Sponsor
+Hart Montgomery
+(Many more, see the project proposal document).
+
+# Pre-existing repository
+No!  That's why we're starting a lab.
diff --git a/labs/archived/ethercluster.md b/labs/archived/ethercluster.md
@@ -0,0 +1,32 @@
+---
+layout: default
+title: Ethercluster
+parent: Archived Labs
+---
+# Lab Name
+Ethercluster
+
+# Short Description
+Ethercluster is an open-source design specification for building scalable blockchain infrastructure using the latest infra-as-code tools such as Terraform, Kubernetes and Docker containers. 
+The Ethercluster project is seen as an open-source alternative to using Infura by having control over a cluster of nodes that can serve as part of the developers decentralized-application architecture strategy.
+Website for Ethercluster is: https://www.ethercluster.com/
+Documentation for running custom Ethercluster: https://docs.ethercluster.com/
+
+# Scope of Lab
+Scope of the Lab is on the cloud devops infrastructure level of scaling blockchain nodes. Imagine having a scalable Kubernetes design specifications for Hyperledger Besu nodes, each running a separate network and running in multiple zones.
+Scope can also be for generating scalable Proof-of-Stake node architecture that can scale as a user wants to stake on more nodes.
+
+# Initial Committers
+- https://github.com/YazzyYaz
+
+# Sponsor
+- https://github.com/vipinsun - Vipin Bharathan (vip@dlt.nyc) - Founder of DLT.nyc
+
+# Pre-existing repository
+
+- Design specs: https://github.com/ETCCooperative/ethercluster
+- Docs: https://github.com/ETCCooperative/docs-ethercluster
+- Demo-Site: https://github.com/ETCCooperative/ethercluster-site
+- Terraform designs: https://github.com/ETCCooperative/ethercloud
+
+My main future goal with the design specs is to make a command-line application in golang that can auto-generate both the Terraform cloud design specs for ethercluster and then deploy Kubernetes architecture of Ethercluster inside those instances.
diff --git a/labs/fabric-chrome-extension.md → labs/archived/fabric-chrome-extension.md b/labs/fabric-chrome-extension.md → labs/archived/fabric-chrome-extension.md
@@ -1,3 +1,8 @@
+---
+layout: default
+title: Hyperledger Fabric Chrome Extension
+parent: Archived Labs
+---
 # Lab Name
 Hyperledger Fabric Chrome Extension
 

diff --git a/labs/archived/fabric-client-flutter.md b/labs/archived/fabric-client-flutter.md
@@ -0,0 +1,23 @@
+---
+layout: default
+title: fabric-client-flutter
+parent: Archived Labs
+---
+# Lab Name
+fabric-client-flutter
+
+# Short Description
+Hyperledger Fabric client for mobile devices written in Dart.
+
+# Scope of Lab
+The lab focuses on offline signing scheme as the frontend of Hyperledger Fabric that interacts with the fabric-server-node. The implementation of fabric-client-flutter is based on Google's Flutter framework for mobile devices.
+The lab implements [[FABN-895] Fabric SDK client signing](https://docs.google.com/document/d/1gj5XB7yS-pfjpvZEUQh5lBGSIE6aQemu8A69tAYQtTc/edit#heading=h.blytbnfrd23h) for the client side. It should be used for client keystore, signing, csr generation, client request and more.
+
+# Initial Committers
+- https://github.com/5sWind
+
+# Sponsor
+- https://github.com/dexhunter or dixingxu@gmail.com - Hyperledger Fabric Python SDK maintainer.
+
+# Pre-existing repository
+- https://github.com/5sWind/fabric-client-flutter
diff --git a/labs/archived/fabric-consortium-management.md b/labs/archived/fabric-consortium-management.md
@@ -0,0 +1,33 @@
+---
+layout: default
+title: Hyperledger Fabric Consortium Management
+parent: Archived Labs
+---
+# Lab Name
+Hyperledger Fabric Consortium Management
+
+# Short Description
+Chaincode based application to manage Fabric Consortium memberships
+
+# Scope of Lab
+Venders of Hyperledger Fabric network services can each offer their services to the customers,
+when customers use different vendors, they often have problems to join an existing fabric
+network due to lacking formally defined process and format of information exchanges. This
+project started by Hyperleder Fabric Interop Working Group(https://wiki.hyperledger.org/display/fabric/Fabric+Interop+Working+Group)
+has formally defined the organization join process based on the application chaincode and
+user interface so that each organization admins can easily locate new org join request,
+approve or disapprove the request and eventually allow a new organization quickly
+become part of a running fabric network.
+
+# Initial Committers
+Github IDs for the set of initial committers.
+- https://github.com/litong01
+- https://github.com/dpdornseifer
+
+
+# Sponsor
+- https://github.com/christo4ferris
+
+# Pre-existing repository
+- https://github.com/litong01/fabinterop
+