Hyperledger Contributor Meeting Agenda

When: Wednesday, April 26, 2023 

9:00am to 10:00am  Eastern Time - New York

(UTC - 5:00) 

Location:

https://zoom.us/j/91526040244?pwd=TjExenBQSU9QYUFjSUMrTjg0MCtBQT09

Hyperledger Anti-Trust Policy

Hyperledger Code of Conduct


Attendees:

Kevin O'Donnell 

Shawn Amundson 

James Barry

Andrea Gunderson 

William Katsak 

Joseph Livesey

Mark Carroll

Ryan Roberts

Ry Jones 


Purpose:

To keep the Sawtooth 1.x line current and advancing with code and bug fixes. 

  1. Who should prepare the quarterly report - James Barry will with help from Shawn 
  2. Specific changes to discuss:
  1. Main Branch - tangible steps
    1. Go through main and identify the pieces that should be shifted to main
      1. Kevin and Shawn will work through pieces on Discord
      2. Shawn would like history in main
      3. Apply a patch to main or move certain items to 1.3 and rename it to main
  2. POET consensus  - should this be updated?
    1. Most projects are using PBFT
    2. Intel SGX is no longer used by the POET available today
      1. There are security issues within the current POET
      2. Reason it is still there lose the ability to handle forking consensus which is not being able to be tested
      3. Augrun is a consensus library that separates consensus code from implementation
        1. To keep researchers from implementing the entire stack
      4. Can POET be lifted into a new area and made more secure and maintainable?
        1. Can it be made a simulator only so people do not use it for production?
        2. Is the breakage Python libraries or Docker libraries?
        3. Joseph will take a look at cleaning up the code and documentation update - main working again with POET
    3. Is RAFT decommissioned? Make sure that it is sunsetted - 
      1. Go through the documentation and remove mentions
        1. James to clean through the documentation and clean up website 
        2. Make it official
  3. Long running testing
    1. Kevin to drop in code and update the long running test framework
  1. Bill Katsak will be releasing Hedera consensus so that a Public consensus is available for Sawtooth the private chain
  2. Find and identify additional developers working on Sawtooth and have them on this meeting and contribute

How to turn the end user experience into the documents?

Have some Rust code from the Python

  1.   Review of any high priority bugs or issues
  2. . Open discussion
  1. Listing out tools that are used within the project

https://docs.google.com/document/d/108b0LvennbRiXLLs8jHUE1X0gS7hC58y19Ku3hCPHw0/edit?usp=sharing


Recording: https://youtu.be/TDlGi3cK-ZI


  File Modified
No files shared here yet.

  • No labels

1 Comment

  1. James Barry

    Purpose:

    To keep the Sawtooth 1.x line current and advancing with code and bug fixes. 

    1. Who should prepare the quarterly report - James Barry will with help from Shawn 
    2. Specific changes to discuss:
    1. Main Branch - tangible steps
      1. Go through main and identify the pieces that should be shifted to main
        1. Kevin and Shawn will work through pieces on Discord
        2. Shawn would like history in main
        3. Apply a patch to main or move certain items to 1.3 and rename it to main
    2. POET consensus  - should this be updated?
      1. Most projects are using PBFT
      2. Intel SGX is no longer used by the POET available today
        1. There are security issues within the current POET
        2. Reason it is still there lose the ability to handle forking consensus which is not being able to be tested
        3. Augrun is a consensus library that separates consensus code from implementation
          1. To keep researchers from implementing the entire stack
        4. Can POET be lifted into a new area and made more secure and maintainable?
          1. Can it be made a simulator only so people do not use it for production?
          2. Is the breakage Python libraries or Docker libraries?
          3. Joseph will take a look at cleaning up the code and documentation update - main working again with POET
      3. Is RAFT decommissioned? Make sure that it is sunsetted - 
        1. Go through the documentation and remove mentions
          1. James to clean through the documentation and clean up website 
          2. Make it official
    3. Long running testing
      1. Kevin to drop in code and update the long running test framework
    1. Bill Katsak will be releasing Hedera consensus so that a Public consensus is available for Sawtooth the private chain
    2. Find and identify additional developers working on Sawtooth and have them on this meeting and contribute

    How to turn the end user experience into the documents?

    Have some Rust code from the Python

    1.   Review of any high priority bugs or issues
    2. . Open discussion
    1. Listing out tools that are used within the project