Thursday 04 June 2020 — 11:00-12:00 am EDT / 13:00 - 14:00 UTC
Thursday 04 June 2020 — 21:00-22:00 pm EDT / 01:00- 02:00 UTC
Mission and Scope
The scope of the Ecosystem Foundry Working Group is to facilitate a community of practice among governance authorities, implementers, operators, and service providers of Trust over IP Layer Four ecosystems. The WG will provide process guidance for the establishment and monitoring of new ToIP Layer Four ecosystem projects, whether hosted at the Linux Foundation or external to it. Other WG activities will include creating template RFPs for service providers, maintaining a list of affiliated Foundry Service Providers, identifying areas of collaboration and alignment between associated and/or disparate ecosystems, and where possible serving as a center of competence for the education and promotion of the role of ToIP Layer Four ecosystems.
Agenda
- Member Introductions
- 35 members were on the first call (see the recording for introductions)
- Mission and Scope
- Proposed deliverables and initial work items
- Logistics
- Mailing List
- Wiki
- Task Forces
- Chairs
- Meeting Schedule
Recordings
- Recording of the 04 June 2020 13:00 UTC meeting—35 attendees
- The second meeting (Friday 05 June 01:00 UTC) had a much smaller attendance and thus was not recorded
Meeting Notes
Attendees
- Karl Kneis
- Arjun Govind
- @Karla McKenna
- Oskar van Deventer
- sankarshan
- Jim St.Clair
- @Mike Vesey
- Todd Benzies
- Wenjing Chu
- @Markus Sabadello
- @Chaker Al-Hakim
- @Darrell O'Donnell
- @Zeev Arteevo
- Paul Knowles
- Ajay Jadhav
- Dan Gisolfi
- Drummond Reed
- @Eric Vinton
- Kalyan Kulkarni
- @Ken Adler
- @Lohan Spies
- Mark Scott
- @Mathieu Glaude
- @Matthew Boyle
- @Nicky Hickman
- @Phillippe Page
- @Sam Rookard
- @Sandeep
- Scott Perry
- Steve Magennis
- Steven Milstein
- @Natarajan Chandrashekar
Discussion items
Time | Item | Notes |
---|---|---|
20 mins | Member Introductions | |
10 mins | Mission and Scope |
|
15 mins | Proposed Deliverables and Initial Work Items | RFP Templates, Best practice docs, White papers, Web-site; Define website publishing process; what is an ec RFP templates and guides and existing best practice guides Thought leadership White Paper topics Wenjing: Study Comm WG overlap; need for collaboration, unified front; (avoid redundancy/duplication?) DReed: CWG: designed to coordinate all white papers, messaging across foundation and WGs, harmonize across all WGs; assist in sharing resources |
Logistics: Mailing List | Review of Mailing List sign-up process; Please subscribe to the mail list to join the Ecosystem WG. | |
Logistics: Wiki | Confluence Wiki review; all welcome to contribute; | |
Logistics: Task Forces | Option to establish task forces reporting to WG; mechanism available; task forces deliverables should have Github repo; suggest create Call to Action document for task forces (under development); all artifacts produced should be in Github for transparency | |
Logistics: Chairs | Call for volunteers for Chairs; DR: voting process different for each WG; depends if there are clear leaders; DG: volunteer chairs need to understand full scope of responsibility in terms of guidance to other projects. Chairs must be focused the community need vs individual projects. | |
Logistics: Meeting Schedule | Next meeting June 18 11am edt. The second repeating meeting at 9pm edt did not include any new members. We will postponed the redundant meeting until we have more representatives in that time zone. |
Action items
- Seeking input for handling proposed work items; send input to mailing list or post on wiki.
- Please propose new items for study, task forces, best practices, and existing resources
- Need to define what an Ecosystem is and establish practice guides. Need to understand business architecture and practices for procurement, design, build, and operation.
- Develop example use cases for discussion to bring clarity to the Ecosystem concept. All members welcome to send example Ecosystem use case slides for community review in the next call.
- Dan, Karl and Mike will meet before the next call to prepare Ecosystem example for community review.
- Review Proposed Task Force: Trust Over OpenID Connect 2.0 - Task Force: Trust Over OpenID Connect 2.0 (ToOpenID)
The following items were discussed in the free-form: