2020-06-11 Status meeting notes

2020-06-11 Status meeting notes

Date

Jun 11, 2020

Attendees

  • @Vadim Reutskiy

  • @Sara Garifullina

  • @武宮誠

  • @Nikita Puzankov

  • @Egor Ivkov

  • @Kamil Salakhiev

Discussion items

Who

Notes

Who

Notes

@Nikita Puzankov

  • There are new PRs with permissions and event listeners

  • Updated Iroha contribution and presentations, e.g. README files

  • Prepared the README data for the CI 

  • Currently helping the internal team in terms of the design of the Iroha solution

  • There are some issues with the request from another team regarding the client for the Iroha. We need to refine their documentation.

  • I will proceed with the guide about building additional modules for Iroha

  • Today we proceed with the CI discussion together with the DevOps team

  • Proposed the documentation spellcheck automation RFC

  • Blocker: external requirements to the bridge implementation. When it will be ready, I can proceed with the improvements in the permissions

@Egor Ivkov

  • Merged the PRs with the Sumeragi refactoring

    • Moved network topology to the separate structure

    • Introduced module for messages

  • Continuing with the block creation timeout, which is the Sumeragi border case

  • Will proceed with TODOs in the Sumeragi implementation

  • @武宮誠 > In Iroha 1 there were many problems with the node sync. Currently, we are running the longevity stand, and we can start to create the one for Iroha 2.

  • Block sync is in our plans, I will take care of it as next big task

@Kamil Salakhiev

  • I finished the review of RFC about transaction tags and order.

  • Will be nice to get feedback from @武宮誠 about it

@Sara Garifullina

  • I am uploading video from Demo to Youtube.

  • I will proceed with the announcements about it

  • I will proceed with the documentation review

  • @Vadim Reutskiy > We need to have a meeting with Nikita in the aim to discuss the documentation structure and place

  • @Nikita Puzankov > We already have a discussion and decided to use docs.rs for the reference and Book MD as user-oriented documentation.

Action items

Make a decision about the documentation approach.