You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Meetings are every 2 weeks on a Tuesday at 9am EDT on the following zoom link: https://zoom.us/j/97104385554?pwd=OWJWMWVoZ0Nyai9BL3diMFMwSXlrdz09.  (see the ToIP Calendar for details)

Tuesday 17th May 2021

9am EDT = 14.00 London = 15.00 CET = 6am PT = 18.30 India, zoom link

Attendees  

Agenda

  1. Intro's and Updates
  2. Review Objectives
  3. Feedback from Compass Domain Modelling Exercise (Maha)
    1. Capture Rights, Responsibilities & Risks
    2. Capture Incentives
  4. AOB

Tuesday 4th May, 2021  

9am EDT = 14.00 London = 15.00 CET = 6am PT = 18.30 India, zoom link

Attendees  Lohan SpiesAamir AbdullahFrednand FuriasankarshanIain BarclayNicky Hickman Wesley Furrow, Will Abramson

Agenda

  1. Introductions & Updates
    1. Wesley Furrow: Generation Unlimited Prog Team in UNICEF NY, co-leading Yoma with Johannes.  Primarily focuses on partnership angle, but involved across the piece.
    2. Amir - Attorney & Teacher of law students
    3. Frednand - Based in Tanzania, member of Sovrin GFWG since 2018, leads consulting firm, audit perspective
    4. Iain Barclay, S/W background PhD student, experience w/SSI for AI and Data Sovereignty and some token work
    5. Will Abramson, PhD Student, working with Lohan on future platform development
  2. Review Scope, Principles & Purpose for Ecosystem Governance Framework.  Reviewed & updated, list of entities now agreed.
  3. Suggested approach to governance as product and code
    1. Reviewed proposed Agile Approach as viewed in this Miro Board
    2. Agreed to trial Sprint 1 using the Youth Experience as core user journeys to write governance for.
    3. Scope will be confined to governance that is required for functionality available end December 2021 (3 months post the completion of the GF V1)
    4. Here is a presentation that outlines the reasons for the approach and the proposed MVP which was delivered to the Ecosystem Foundry WG on 06/05/21

Kick Off Meeting - Mon Apr 12, 2021 9am – 10am Eastern Time 

https://zoom.us/j/97104385554?pwd=OWJWMWVoZ0Nyai9BL3diMFMwSXlrdz09 

Attendees: (Please add your name here)

Johannes; UNICEF work on Youth Agency in Africa.  Convener of Yoma

Iain Barclay Cardiff University, UK;  PhD studying - Applications of tech, SSI for last ~2 years, for UN SDG related impact.  Some work in IoT, used Evernym stack for birth registration trial in Kenya, but paper written about application.  Recently been looking at blockchain and tokenised value flows, recently transport - token used for incentives for behaviour change.  Also work on making AI scrutable

Zeljko:  S/W engineer, Hyperledger & ToIP member, SSI enthusiast

Lohan Spies:  DIDx SA -focus on Cyber Security, recently focus on SSI applications, acting as CTO for Yoma project

Kalin Niclov; Previously in Linux as SW Engineer, Head of Digital Currency at SICPA, ToIP founding members, recently also joined DIF, 2 foundations in identity and currency, SICPA secures all but 4 major fiat currencies and for most PP and ID Cards.  

Thiru: CTO - blockchain enthusiast, recently implemented 3 blockchain projects, SSI recent interest starting with tokens.  Experienced implementer.

Aamir Abdullah 

Frednand Furia

Agenda:

  1. Introductions
  2. Purpose & Principles review
    1. Vision, Mission, Values (Johannes) 
      1. Still working through Values with youth participants
    2. Purpose & Principles discussion
      1. Q4 we will start on SE / Legal entity established.  Both discussions on GF and future Yoma SE need to work in parallel.  Arrange specific sessions w/ SE team, bridging mechanism or interim solution for GA may be required  
      2. All to take time to review this document, add comments and suggested text before our next meeting.
      3. Make use of the Use Case Documents 
  3. AOB
  • Start Glossary document to define our language
  • Specify Layer 1 requirements rather than selecting specific Layer 1 utilities. (current investigation e.g. based on token requirements)
  • Token:  separate component related to token itself but the governance specifies rules, policies under which it will operate.



  • No labels