Page Comparison

...

1. Technical tasks / issues on Github 
   1. Contributor pathway: (for example: read this blog post, go to the list of good first issues, etc)
   2. Contributor persona: (for example: someone already familiar with Kubernetes)
2. Article in an online publishing forum such as Medium
3. Blogpost 
4. Deployment video
5. Custom digital badges?

WHAT IS A DEPLOY-A-THON ?

  A deploy-a-thon is like a hack-a-thon; however, instead of focusing on  building an application or a working piece of code, it is focused on deploying a network .

Deploy-a-thon : Pathways based on Personas : 

Persona : HL Fabric Developer / User / Operator  Operator  

• Start from Introduction > Familiarize on Key Concepts > Go To Getting Started > Configure Pre-requisites > Understand the HL Fabric configuration , charts and architecture > Get the HL Fabric configuration file specification done > Deploy the network and verify the deployment> Bring your network down > Setup again and Record a video this time with logical pause and explanations

Persona : R3 Corda Developer / User / Operator

• Start from Introduction > Familiarize on Key Concepts > Go To Getting Started > Configure Pre-requisites > Understand the R3 Corda configuration , charts and architecture > Get the R3 Corda configuration file specification done > Deploy the network and verify the deployment> Bring your network down > Setup again and Record a video this time with logical pause and explanations

Persona : HL INDY Developer / User / Operator

• Start from Introduction > Familiarize on Key Concepts > Go To Getting Started > Configure Pre-requisites > Understand the HL Indy configuration, charts and architecture > Get the HL Indy configuration file specification done > Deploy the network and verify the deployment> Bring your network down > Setup again and Record a video this time with logical pause and explanations

Persona : Quorum Developer / User / Operator

• Start from Introduction > Familiarize on Key Concepts > Go To Getting Started > Configure Pre-requisites > Understand the Quorum configuration, charts and architecture > Get the Quorum configuration file specification done > Deploy the network and verify the deployment> Bring your network down > Setup again and Record a video this time with logical pause and explanations

...

Social (staff to repurpose content from blog post)

Meetups:

• BAF + Indy: https://www.meetup.com/Hyperledger-Victoria/ – hosted by Stephen Curran
• BAF + Fabric: Hong Kong - connect with Julian
• BAF + Besu: Somewhere in Europe – Connect with Thomas and Vijay re suggestions about Europe locations
• Meetup blurb:

  • BAF is a new Hyperledger Labs project that is an automation framework to consistently deploy production-ready DLT/Blockchain networks on existing Kubernetes clusters. The BAF team is interested in speaking at a virtual meetup for around an hour to cover a project intro, talk about how to configure this for use with Indy and do a demo plus Q&A.

    We would want a 1 hour slot :
1. Introduction , need and architecture


    
2. Platform specific configurations

  • 
3. Live demo
4. Q&A. late July or early August.

    For more details: blog link

During Phase:

Social (staff to repurpose content from blog post)

...

Homepage mention (HL staff owns)

Post Phase:

Analysis metrics:

1. Number of new contributors (for a small enough set of new contributors it would be helpful to do a quick sketch of each person – who they are, where they work, why they are getting involved...)
2. Number of organizations contributing (this would need to come from discussions with the new contributors to learn more about who they are.  we could also combine this with the number above to see the number of contributors per organization to see how much internal interest and adoption there may be – is it just one person or many?)
3. Number of questions per week asked on the main communication channel – in this case the BAF chat channel (this would be a manual metric to gather but we'll look into something automated for going forward)
4. Website traffic on landing page and blog posts
5. Number of PRs on Github (And longer term it would be good to build a retention stat from this info to see if people show up and continue to contribute or drop off)
6. Number of community members attending planning call (this would also be a manual metric for now)
7. Possibly a social media metric about mentions for BAF
8. Note that usage and deployment metrics are challenging to gather with open source software so we are focusing on participation metrics

Blog post to recap results (written by BAF team)

...