Versions Compared

Old Version 1

changes.mady.by.user Ry Jones

Saved on

compared with

New Version Current

changes.mady.by.user Ry Jones

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

02/22/2023 Meeting Notes

Hyperledger Contributor Meeting Agenda

When: Wednesday, February 22ndApril 26, 2023 

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

...

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

...

  1. Quick review of where the codebase is today. The purpose of this meeting is around 1.X maintenance and enhancements.
  2. Contribution Ideas from those on the call, I will start with a few that we at Taekion have looked at tackling, but certainly enough - but some to get us talking:
    1. Making the TransactionCommitCache an LRU (We ran into issues with dependent transactions)
    2. Abstracting out the rust LMDB database functions into a separate crate and trait (sawdb)  - better abstraction where others can experiment with different database backends
    3. A rocksdb implementation of the sawdb trait for the merkle tree database - big performance improvement
    4. A mundane one, but important to understanding Sawtooth 1.x - documenting the network APIs (our work with the consensus API showed where that is lacking)
    5. I starting with some thoughts - but others are needed if 1.X is to continue
  3. Review of any high priority bugs or issues
  4. Housekeeping
  5. Volunteers to either help or track down someone who can help with questions that are on Discord or other sources . 
  6. Open discussion
  7. When should the next meeting be scheduled - in 4 weeks or sooner?

*************************************************************************************************************

Notes from February 23, 2023 meeting: (ANYONE can hit this doc and put comments on here 

Duncan from BTP discussed why to keep Version 1.X and not make it dormant

Shawn Amundson from Bitwise has not heard about the project potentially becoming dormant, but is the lead contributor v1.3 should be using lib sawtooth.

Kevin O’Donnell from BTP has several items to push to the v1.3 branch

Arun is just listening from the TOC perspective

Kevin is working with a set of V1.X for BTP 

Discussion around putting a lot of asynchronous discussion in Discord.  To be vibrant Discord needs to get more discussion and answering questions.

Are releases important or are you forking the branch?  

BTP does not care about the formal release but tagging is important to BTP. 

Recording: 


Attachments