2023-10-30 Preparation for Community Review Meeting

Owned by Artun Gürkan
Last updated: Nov 02, 2023 by Nico Lueck
1 min read

 Date

Oct 30, 2023

 Participants

@Nico Lueck @Artun Gürkan @Meelis Zujev (Deactivated) @Oleksii Danyliuk @jarkkohyoty @Vladislav Todorov @Vasil Kolev

 

 Goals

  • Preparation for Community review which will be held on Nov 2, 2023

    • What to expect

    • Scope of the presentation

    • Responsibilities

 Discussion topics

  • Nico: We will go along with the Gitbook but there may be more.

  • We need to name this release.

    • 0.9 release

Decisions

  • @Nico Lueck will be the Moderator and decide when to start Q&A

    • Approximately presentation should take 45 min and 15 min Q&A in total

Presentation Flow

  1. Introduction @Nico Lueck (3 Min)

  2. Enter the sandbox Page @Nico Lueck (2 Min)

  3. USCT Demo/clickthrough with explanation - Which BBs are used (@Nico Lueck and @Vladislav Todorov for payment part and @Oleksii Danyliuk @jarkkohyoty Identification BB) (10min)

    1. Architecture

  4. DIY demonstration @Nico Lueck (10 min)

    1. RPC Layer @Vasil Kolev

    2. USCT @Oleksii Danyliuk

  5. DevOps/Infrastructure (@Nico Lueck @jarkkohyoty ) (5min)

  6. General Front-End Introduction - Construction Permit (@Priit Puru @Artun Gürkan) (10min)

    1. Follow Methodology - Service Design (@Artun Gürkan @Priit Puru )

  7. Outlook/Roadmap (3 min)

    1. High School Certificate

    2. Construction Permit

    3. RPC Backend

    4. Building Blocks: Consent iGrant.io. In 2024 Ukraine Platform of Registries

    5. Infra: Autoscaling, Operation and Maintenance Mode

  8. Fails and Learnings @Vasil Kolev (3 min)

    1. Sandbox Portal and respective User stories not reached @Nico Lueck

    2. BB Deployment not Automated

    3. Expectations without Specifications or Implementations (e.g. IAM)

    4. Missing BB specifications

    5. Missing building block implementations

    6. Difficult to install BBs with ongoing development

    7. Specification changes

    8. Specifications not well aligned between BBs

    9. Missing core BBs designed to work together as framework covering fundamental usecases

    10. Too big applications in place of BBs

  9. Q&A (10min)