EFWG 2022-03-31 Meeting

Meeting Schedule

Bi-Weekly at 8:00-9:00 am PST / 11:00-12:00 am EDT / 15:00 – 16:00 UTC / 17:00 - 18:00 CET
https://zoom.us/j/95389236256?pwd=RFErMm9SS0tBenA1Q0dSYlpXK3Bqdz09

Attendees

Steve Magennis
Carly Huitema
P Subrahmanyam
Eric Drury
Phil Wolff
Trinh Nguyen
Erran Carmel
Steven Milstein
Richard's iPad

Agenda Items

Welcome & New Member Introductions
Q1 Recap
Community Input & Discussion

Presentation Files

Recording

Meeting Notes

Welcome & Introductions

Notes

Q1 Recap

Inputs.

Speakers.

YouTube Channel w/ EFWG Presenter Series: https://www.youtube.com/channel/UC7gD2mHX_AXzkTHelj2nYEA
Riley Hughes
- Risk, Standards Paralysis, UX/UI, Governance were top four challenges of the ten.
- MVG
  - “Minimum Viable Governance" is an interesting and perhaps contentious topic (viable being the key concept to ponder).
  - The unstated part is the effort to understand and articulate what 'minimum' means in a particular context - this is tough. It seems to fit with agile development - iterate on building.
  - MVG = Lean Governance = governance that supports the functionality of the system for the users in either achieving the objectives of the parties within the ecosystem, OR managing risks to them achieving those objectives.
  - Governance as product & code vs governance as documentation.
  - Concern: “MVG" in the Agile construct is that governance is a difficult item to "fail early, fail often” test with iterations. Governance is also risk management and mitigation - and not just about how democracy exists in the system being governed.
  - We experimented with this in developing the Yoma GF - See the method here https://miro.com/app/board/uXjVOJ9nUnA=/?moveToWidget=3458764519852314046&cot=14 we are still researching some of this e.g. use of Domain Specific Modelling Tool as a product architecture if you treat governance as product & code
Accenture
- Adoption was wherever Accenture already had clients?
- The Accenture presentation was significant in terms of how the adoption was presented in terms of large sector adoption - probably because of multipliers of network effects happen better and to scale
- timing: Is governance developed as you start to notice challenges too late or at the right time? Equally, risks, functionality and context change all the time, governance needs to be able to adapt and develop in response to that.
- it seems like ecosystem boundaries change and depend on who is looking at the ecosystem.
- Disturbance. Governance failure has the potential for large downside, but of course not every failure in governance results in large downsides - understanding where 'thar be dragons' IMHO is the key. Governance in these systems consists of a human-controlled governance and algorithmic governance. One big and most challenging part of governance is the "evolving governance" aka the governance when things change or in crisis (like the DAO hack incident in 2016). https://www.coindesk.com/tech/2022/02/04/trons-justin-sun-accused-of-governance-attack-on-defi-lender-compound/. Governance has to be responsive and evolve. So instead of a "static" form it has to be dynamic.
Outputs
- Learning Pathways : https://wiki.trustoverip.org/display/HOME/Learning+Pathways+Taskforce
- Blogs / Posts: “Radio with Pictures” : https://trustoverip.org/blog/2022/03/02/radio-with-pictures/
- Ecosystem Directory : https://wiki.trustoverip.org/pages/viewpage.action?pageId=73896
- Resource Directory : https://wiki.trustoverip.org/pages/viewpage.action?pageId=19633443
How can we support or influence the Design Principles?

Community Input & Discussion

How do you want to spend one hour every other Thursday?
Who do you want to hear from?
What topics do you want to learn about?

Admin Reminder : remember to re-subscribe to new meeting calendar

If you want your name on the invite, reach out to Elisa Trevino (on slack), she will put your name in the calendar invite to make sure that the invite is sent out each time.

*** Next presentation *** eIDeasy - 14 April 2022

Space shortcuts

Page tree