User Tools

Site Tools



This shows you the differences between two versions of the page.

Link to this comparison view

Last revision Both sides next revision
groups:tsc:project-updates:sawtooth-2019-jan [2019/01/10 15:51]
clive boulton created from boiler plate to gather input.
groups:tsc:project-updates:sawtooth-2019-jan [2019/01/21 23:20]
Peter Schwarz
Line 2: Line 2:
 ===== Project ===== ===== Project =====
-//​Hyperledger Sawtooth Quarterly Update - Thursday, 17 January 2019 
-// created from boiler plate to gather input - cb //+Hyperledger Sawtooth [[]]
 ===== Project Health ===== ===== Project Health =====
-//**Required** Sum up the status ​and health of your project ​and the community ​in a few sentencesConsider this the TL;DR for the rest of the reportHow is your community doing health-wise? Are questions being answered? Are contributors acting appropriately?​ Are there new contributors showing up?//+ 
 +We released our 1.1 release last month. ​ New features included in this release: 
 +  * PBFT Consensus - [[​hyperledger/​sawtooth-pbft]] 
 +  ​Raft Consensus - [[https://​​hyperledger/​sawtooth-raft]] 
 +  ​Getting RUSTY: Continuing porting internal components from python→rust 
 +  ​Smart Permissions for Sabre: [[https://​​hyperledger/​sawtooth-sabre]] 
 +  ​Support ​and documentation for running in Kubernetes 
 +  * Extensive documentation updates 
 +  * The SDK (besides Python ​and Rust) have been split out into their own repos 
 +Blog content: 
 +  * [[https://​​blog/​2019/​01/​18/​safety-performance-and-innovation-rust-in-hyperledger-sawtooth|Safety,​ Performance and Innovation: Rust in Hyperledger Sawtooth]] 
 +  * [[https://​​blog/​2019/​01/​11/​floating-the-sawtooth-raft-implementing-a-consensus-algorithm-in-rust|Floating ​the Sawtooth Raft: Implementing a Consensus Algorithm in Rust]] 
 +  * [[https://​​blog/​2018/​12/​11/​making-dynamic-consensus-more-dynamic|Making Dynamic Consensus More Dynamic]] 
 +  * [[https://​​blog/​2018/​12/​07/​hyperledger-sawtooth-blockchain-security-part-three|Hyperledger Sawtooth Blockchain Security (Part Three)]] 
 +  * [[https://​​blog/​2018/​12/​06/​announcing-hyperledger-sawtooth-1-1|Announcing Hyperledger Sawtooth 1.1]] 
 +Additionally,​ added a FAQ to the Sawtooth Website: [[https://​]]
 ===== Issues ===== ===== Issues =====
-//​**Required** If there are any specific issues that the TSC should be aware of, or specifically address, then please call them out. If not, then it is helpful to state something like: "There are no issues at this time." When in doubt, it is better to include information or questions, rather than waiting.// 
 +Prior Issues
 +  * Disconnection between TSC and projects. Continuing to improve.
 +  * Maintainer access to project page managed by LF. Inconclusive.
 +  * Increase in PR backlog given increased submissions. No change.
 +New Issues
 +  * Sawtooth Next Directory feels like a separate project. ​ It does not conform to
 +the community norms.
 ===== Releases ===== ===== Releases =====
-//**Required** Regular software product releases are a sign of a healthy project. Reports should list the releases made since your last report, along with the release date of each. NOTE: If no releases were made, list the date of the most recent prior release.//+ 
 +  ​1.1 Dec 2018
 ===== Overall Activity in the Past Quarter ===== ===== Overall Activity in the Past Quarter =====
-//​**Required** Discuss briefly how active the project mailing lists and chat channels are. Are emails or user questions regularly read and responded to?  What technical changes is the project working on? Is there new development happening, or just bug fixes? NOTE: If activity is minimal, verify whether or not there are at least three active maintainers who can step in when needed, and include this information in the report.// 
 +  * Chat activity continues to increase
 +  * Developer chat has continued to move to rocket chat from private channels
 +  * listserv traffic remains light.
-===== Current Plans ===== +See community calendar [[​community/​calendar-public-meetings]] for occurrences ​of our
-//**Required** A healthy project will often be working towards a common goal, or have a shared understanding of what is being done next - even if individual contributors have their own "​itches"​What are the main features planned? What releases are planned? Are there any specific efforts or branches of development under way? This does not need to be described in technical detailConversely, if activity is minimal, discuss how the project plans to address that whether through seeking out new contributors,​ maintaining in a dormant but available state, or planning towards a move to a Deprecated (and ultimately End of Life) state.//+
 +  * Tech Forum
-===== Maintainer Diversity ​===== +===== Current Plans =====
-//​**Required** Please include the maintainers that were added since your last report. This information will allow us to track the diversity and growth of the maintainers of the project. NOTE: If no maintainers were added since your last report, provide the list of existing maintainers.//​+
 +Continuing development on:
 +  * The Python and Rust SDKs are being split into their own repos
 +  * Devmode Consensus engine is being moved to its own repo
 +  * Rewrite of remaining Python components in Sawtooth Core in Rust
 +  * Mobile SDK development:​ client SDK’s for both iOS and Android
 +  * PBFT Release
 +  * Sabre 1.0 as well as adding functionality around “Smart Permissions”
-===== Contributor ​Diversity ===== +===== Maintainer ​Diversity =====
-//​**Required** A healthy project should survive the departure of any single contributor or employer of contributors. Healthy projects also serve needs of many parties. Include information on the number of unique organizations currently contributing to the project. NOTE: The contributions do not need to be source code.//+
 +Maintainers are roughly evenly distributed across, Cargill, Intel, with T-Mobile on Next Directory.
-===== Additional Information ​===== +===== Contributor Diversity ​=====
-//​**Optional** Please provide any additional information that you feel would be useful for TSC to be aware.//+
- +  * Commits from 2018-10-1 to 2018-12-31: 420 
 +  * Committers from 2018-10-1 to 2018-12-31: 28 
 +  * Domains from 2018-10-1 to 2018-12-31: 6
groups/tsc/project-updates/sawtooth-2019-jan.txt · Last modified: 2019/01/24 15:10 by Peter Schwarz