Project Health

  • Hyperledger Bevel continues to grow strong in terms of community interest.
  • It has a diverse global community with contributors from multiple organizations and geographies.
  • We are seeing new users joining and asking questions on discord. 
  • The project planning's have active maintainers and contributor participation.
  • The project has added hlf-operator (now called bevel-operator-fabric) as a subproject.


Required Information

Have you switched from master to main in all your repos? Yes

Have you implemented the Common Repository Structure in all your repos? Yes

Has your project implemented these inclusive language changes listed below to your repo?

  • master → main
  • slave → replicas
  • blacklist → denylist
  • whitelist → allowlist

You can optionally use the DCI Lint tool to make this a recurring action on your repo. Yes

Have you added an Inclusive Language Statement to your project's documentation and/or Wiki pages? Yes

Questions/Issues for the TSC

None at the moment.

Releases

New release v0.13, release draft change log - https://github.com/hyperledger/bevel/releases/tag/untagged-50adfdb2975c0129470e

Overall Activity in the Past Quarter

  1. Discussed and plan for Bevel v1.0 (Bevel redesign) - focusing on helm chart refactoring, documentation redesigning and operator integration - Roadmap Planning
  2. Roadmap groomed for Bevel release v0.14.0
  3. hlf-operator project became a project under bevel and renamed to bevel-operator-fabric 
  4. Cert-Manager option enabled with lets encrypt for TLS cert creation for bevel ambassador.  
  5. HL Besu and supplychain ref. app integration [WIP]
  6. Enable external chaincode as a service [WIP]

Current Plans

  1. Documentation redesigning - based on user persona (deployment specific) 
  2. Helm chart refactoring making it compatible with bevel-operator-fabric / other operators in future 
  3. HAProxy and Ambassador upgrade
  4. Complete release v0.14.0 targets - https://github.com/hyperledger/bevel/projects/85

Latest roadmap : https://hyperledger-bevel.readthedocs.io/en/develop/roadmap.html

Maintainer Diversity

The current maintainers to the project belongs from different geographies and organizations.

List of maintainers and their details are as follows -

Jonathan M HamiltonAccentureNorth America
Sownak RoyAccentureUK
Tracy KuhrtAccentureNorth America
Suvajit SarkarAccentureSouth Asia
Arun S MWalmartSouth Asia
Weihong OuWalmartNorth America


Contributor Diversity

https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fbevel/dashboard;quicktime=time_filter_3M

Our contributor strength has increased in this quarter compared to the previous quarter, which is great news!

Additional Information

N/A

Reviewed By

Submission date

$action.dateFormatter.formatGivenString("dd-MMM-yyyy", $content.getCreationDate())


  • No labels

3 Comments

  1. Suvajit Sarkar : Please note that project reports have been migrated to GitHub. Can you please submit a PR there? See https://toc.hyperledger.org/project-reports/#instructions-for-filing for more information.

  2. Suvajit Sarkar – I noticed in this update that you talk about some documentation redesign work.  If the Bevel team wants any help with that documentation work, I wanted to mention that in this year's Hyperledger Mentorship program we're including documentation projects and Bevel would be welcome to submit a proposal related to getting help with documentation.  That proposal could also include having someone create material for an upcoming Bevel workshop – perhaps when the 1.0 release comes out it would be a good time to have a workshop to show people how to use it.  For more about proposing a mentorship project, check out the wiki at: https://wiki.hyperledger.org/display/INTERN/Mentorship+Projects

    1. Yes, that would be great, would plan and propose the documentation work for the program.