Versions Compared

Old Version 4

changes.mady.by.user Victor Syntez

Saved on

compared with

New Version Current

changes.mady.by.user Victor Syntez

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Every Thursday (PT, ET, UTC) 5pm PT, 8pm ET, 12:00am UTC

See the ToIP Calendar for meeting info. You can subscribe to the mailing list at lists.trustoverip.org.

Recording

Link to the recording

Attendees

...

Main Goal of this Meeting

To launch community participation in the drafting of the Design Principles for the ToIP Stack document 

...

TimeAgenda ItemLeadNotes
10 min
  • Start recording
  • Welcome & antitrust notice
  • Introduction of new members
  • Agenda review
Chairs
  • Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
  • New Members:
15 minsBackground on Design Principles for the ToIP Stack documentDrummond Reed
20 minsDiscussion of the End-to-End PrincipleDrummond Reed
10 minsDiscuss volunteers for writing assignments for the next week
  • See Action Items
5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs

Screenshots/Diagrams (numbered for reference in notes above)

#1

Decisions

  • Sample Decision Item

Action Items

  •  Sample Action Item

Notes

  • Drummond Reed presented background on Design Principles for the ToIP Stack.
    • The main idea is to disassociate ToIP stack with Hyperledger Aries and bring definition of the stack under the ToIP Foundation.
    • As shown in the diagram on this page, the full definition of the ToIP stack will be split into three documents: Design Principles, ToIP Technical Architecture TSS and ToIP Governance Architecture TSS.
    • The Design Principles documents was started in December 2020, but was put on hold due to other important projects.
  • Following the question from P Subrahmanyam on what WG is responsible for the Design Principles document Drummond Reed clarified that:
    • It is a joint deliverable of both the Technical Stack WG and the Governance Stack WG because the design principles encompass the entire stack as a whole.
    • However in order for there to be a clear "home" for this Design Principles document, the Design Principles Task Force was chartered under the TSWG.
  • We reviewed the End-to-End Principle as an example of what the contents of a principle section should cover.
    • Drummond Reed volunteered to draft text for that section by next week's meeting.
  • We discussed length and agreed that each principle section should ideally be between one and two pages in length (including illustrations).
  • Victor Syntez suggested that we should think about using visual graphics, diagrams and images to illustrate principles to make them appealing to the broader community of readers. UN Sustainable goals were brought as an example of such images.
  • We agreed that our goal for the next meeting was to draft the first few sections and be ready to discuss them.

Decisions

  • Each section in the document describing a design principle should ideally be between one and two pages in length (including illustrations).

Action Items

  •  sankarshanand paulwill start working on the 'Introduction' and 'What are Design Principles' sections
  •  Drummond Reed will work on the 'End-to-End Principles' section.
  •  Victor Syntez will continue to work on other sections.