The last review focused on three aspects:
Develop behind Web Assembly for future cross-platform adoption
Create Libraries, Data models, and SDKs to advance the development of supply chain applications
Context updated to move scope and solution details out of this section into the right sections
In the Solution section, the diagram shows the main deliverables
BB: We need a different name for this proposal. Abstract/goofy names is a powerful thing. Before this is approved, we need to come up with a name for this. Name proposed is Hyperledger Grid.
CF: Could the marketing committee help with name search and trademark?
CF: Still struggling with how this is a generic thing. Is this technology that could be consumed other by Sawtooth. A couple platforms are interested in adopting Web Assembly.
CF: We still have work to do to figure out what the APIs will look like.
KO: This is shooting to where the hockey puck is going. Web Assembly is where the public space is going.
CF: Codify the standards in software.
NG: Incubating projects are intended to work this out.
MB: There is a shape of the API and incubation will allow for hardening of the API.
MB and SD: Specificity and context is much clearer now.
SD: Dependencies currently list Sabre. Does that imply that this is also dependent on Sawtooth then? Need ABI layer on WASM. Uncouple this from Sabre and Sawtooth. By making it a separate project, we can ensure that this bias doesn't exist. We also want Sabre to grow beyond just Sawtooth.
SD: If in Burrow, I did not want to support Sabre and instead add a WASM interpreter, what would the gap be to support these APIs? Sabre does get/set state and the application API will support the get/set state. A lot of the direction of the project depends on who we can get involved.
HM: This is in between Composer and Indy in Scope. The updates to the proposal cleared this up.
NG: Can we take a vote on this yet?
MW: Is the architecture designed to provide a layer for other platform support? The intent is that code goes through a WASM interpreter, which would allow others to pick that up. How hard is it to make a shim for Sabre for other platforms. Three operations: get, set, and registration API would need to be implemented.
Vote with the caveat on naming going through the marketing committee - CF abstained, AL not present, all other TSC members approved.
Meetup groups in India were looking for help in connecting with others.
The Indian developer community is looking to have a better connection to the rest of the community.
India has one of the largest developer community
The intent is to nuture, encourage, and train folks in India for getting involved in Hyperledger.
Amol Kulkarni has signed up to chair the TWGI
There is a tremendous amount of curiosity and enthusiasm for blockchain technologies. Have people who want to contribute, but don't know how to.
Helping out with collaboration, technical exchanges, and tutorials. Act as a bridge. Provide mentorship.
NG: Maintainers of Indy would like to participate. We would like to have them.
BB: Regional WG is not intended to be a VPN into the larger community. We expect them to be involved in the community and to provide a local assist. Because time zone prevents people from participating, it might be worthwhile to have a volunteer who can feedback to the community in India.
VB: Gender diversity is lacking in this working group. What can we do to drive more participation?
SB: How do we integrate with the Community Architect team? What are the boundaries between these regional WGs and the Hyperledger staff? There is significant overlap. Promote the programs and events that are part of Hyperledger's global community. Using local communication tools, news is shared about what is happening. Work with the APAC team on how we bring this group in closer communication with The Linux Foundation and Hyperledger staff.
BY: States his support for this group and desire to help.
AK: Call for additional participants that have knowledge of the different projects.