Attendees
Guests:
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 min | Action Item Update - BLOG Updates and Approvals | ||
| 10 min | Actions Item Updates (10 min) Discussion Papers and Infographic Live Trademark Registration OIX MOU Graphics for Intro White Paper Hyperledger Workshop with ToIP Content APAC/Africa Regional Communication Meet-up Strategy | Judith Fleenor | |
| 20 min | Proposed Ideas from the EFWG (20 min) | Steve Magennis | |
| 10 min | New Topics (10 min) | Judith Fleenor | |
| 10 min | Open Discussion | All | |
| 1 min | Wrap up |
Judith Fleenor kicked off the meeting with our Antitrust policy and an agenda review. She provided updates regarding the LF Members Summit recap, Beyond Credential Exchange, Guardian Addendum BLOG - Lets Go Together and Discussion Papers; Captivating New and Solving Tough Problems that were all posted in November and December. She continued with the Happy Holidays - MEGA BLOG for review and approval. There was discussion regarding linking to Linux Foundation from the Happy Holidays - MEGA BLOG and the decision was made to unlink due to the nature of the blog. Steve Magennisrecommended we get this out as quickly as possible so that we can promote it as a "fun" spoof on the work we're doing. John Jordanrecommended we ensure we highlight the fact that this is a fun post to ensure we don't cause confusion.
Judith Fleenor continued announcing the up-coming blogs: Intro to ToIP and Design Principles, GSWG - three deliverable (posted after SC approval), OIX agreement (posted after SC approval) and GLEIF Public Review Launch - to be written by GLEIF (for approval Jan 7th meeting). She mentioned the details regarding the GLEIF blog post and public review. New info graphic are up on the website and we're encouraging folks to tweet and post about these. Judith Fleenorthanked Wenjing Chu for helping with the graphics for the Introductory WhitePapers. Judith Fleenor shared additional updates regarding Hyperledger Workshop still under development - ToIP content to be added, ToIP Branding Guidelines - Co-Branding of Deliverables (Example Yoma Governance Framework) and Cross Organizations Communications Collaboration. Judith Fleenoris awaiting the ToIP presented content for Hyperledger workshop, but mentioned registration is open.
Steve Magennis discussed EFWG proposed ideas: publishing case studies and maintenance related ToIP resources. Steve Magennis started with publishing case studies with the goal of creating a baseline of case studies that illustrate organizations who are structuring or currently running. He inquired with the Communication Committee how they feel about providing this baseline information and resources to help community members who are engaging with our ToIP Foundation within the EFWG. John Jordan mentioned that he believes this is a great idea and shared some personal experiences that help support why this would be beneficial from a government perspective. Steve Magennis mentioned the document will be relatively short and can be structured like a deliverable. Steve Magennis inquired about the process and John Jordan explained that the case study will be presented to Communication Committee and Judith Fleenor affirmed there would be a blog and case study that we could then publish on our website. Steve Magennis asked about the timeline for approval and Judith Fleenor shared the 7 day approval timeline.
Steve Magennis continued with the discussion regarding resources related to ToIP concepts and resources and consultants and fees. We don't want this to be perceived as us advocating for specific resources, but he wants to collect feedback and see what thoughts are with the committee to share with the larger ToIP community. Judith Fleenor inquired on where this list might live and Steve Magennis mentioned that initially it would be internal, but if it comes together well, we might be able to share on our public facing website so that we can illustrate resources within our ToIP community. Judith Fleenor asked the Committee for their thoughts and John Jordan referenced a vendor resources list and shared that Hyperledger currently has something like this. Wenjing Chumentioned that this is available, but it's merely an adoption based resources. He continued that since we're a Standards organization, we're a little more different from other groups. He continued with the question of what do we mean by resources? We don't have something to connect these resources. John Jordanmentioned the Linux Foundation landscape tool might be an option to illustrate what vendors offer what type of services. Wenjing Chumentioned using our four layer model to illustrate the resources, similar to what's illustrated on LF landscape. Phil Wolffmentioned we will need to budget for the work and getting the updates on our website. Wenjing Chuand John Jordanmentioned it's an open sourced resource and will likely be easy to use. Wenjing Chumentioned it would be on the EFWG to maintain the website updates. Judith Fleenorchimed in that we should encourage folks to be General Members to have their logo posted on our website. Judith Fleenor mentioned we need to identify how we identify the criteria for these potential members to ensure we've vetted them out before we promote them within our ToIP community. John Jordanmentioned we would need to encourage them to identify their specific attributes to help implement their logo within the landscape tool. Daniel Bachenheimermentioned he likes the idea to illustrate who the players are and where they fit in, but the challenge we may face is if they're contributing a lot to a sister organization and they're not a ToIP member but they're a leading provider in the space. We previously discussed publishing who/how this type of implementation in the past as a point of reference. Wenjing Chumentioned CNCF landscape illustrates the entire landscape, not just their CNCF members within the landscape. Steve Magennis mentioned it may be challenging to get approvals from all the various players, in order to get published. John Jordan recommended we look into this as it's a great potential resource to provide our community.
Action Items: