|
| 1 | +# Taxonomy and Landscape Workstream |
| 2 | + |
| 3 | +## Meeting — 2026-06-08 |
| 4 | + |
| 5 | +## Resources |
| 6 | + |
| 7 | +- [AI Summary](https://zoom-lfx.platform.linuxfoundation.org/meeting/97227615758-1780932600000/summaries?password=d5291d96-6895-43ea-96e6-0110e4c2f925) |
| 8 | + |
| 9 | +## Topics Discussed |
| 10 | + |
| 11 | +- The group reviewed the charter updates to refine the taxonomy schema definition, cross-workspace conflict resolution, and key success metrics. |
| 12 | +- We confirmed the adoption of the CNCF landscape tool format due to its widespread industry usage. |
| 13 | +- The team discussed the charter's deduplication efforts and refined tracking metrics for measuring document references and domain editor attestation. |
| 14 | +- We aligned on forming a core team consisting of active delegates from each working group to drive the taxonomy curation. |
| 15 | +- The group agreed that resolving high-level boundary definitions will be handled iteratively as a deliverable rather than hardcoded into the charter. |
| 16 | +- We discussed workflow setup and decided to convert existing terms into pull requests to ensure all terms follow the new approval process. |
| 17 | +- The team considered alternate meeting times due to scheduling conflicts and agreed to run a survey to find a better slot. |
| 18 | + |
| 19 | +## Decisions |
| 20 | + |
| 21 | +- We will adopt the CNCF landscape tool format for organizing our taxonomy. |
| 22 | +- We will form a core team composed of one or two active delegates from each working group to manage contributions. |
| 23 | +- We elected to treat high-level boundary definitions as an ongoing deliverable rather than embedding them directly in the charter. |
| 24 | +- We decided to reset the current terminology by converting all existing terms into formal pull requests to enforce our review process. |
| 25 | +- We will conduct a survey to determine a more accommodating weekly meeting time across different time zones. |
| 26 | + |
| 27 | +## Deliverables |
| 28 | + |
| 29 | +- High-level boundary definitions for cross-cutting concepts. |
| 30 | + |
| 31 | +## Action Items |
| 32 | + |
| 33 | +| Owner | Action | Due | |
| 34 | +|-------|--------|-----| |
| 35 | +| Junjie | Junjie will update the repository by converting existing taxonomy terms into pull requests for review. | TBD | |
| 36 | +| Junjie | Junjie will create GitHub issues for working group chairs to contribute their initial 10 key terms. | TBD | |
| 37 | +| Junjie | Junjie will coordinate with Christina to find a better meeting time for working group chairs. | TBD | |
| 38 | +| Junjie | Junjie will check with Alex to confirm Security and Privacy delegates and their meeting availability. | TBD | |
| 39 | +| Junjie | Junjie will send a survey to all participants to collect preferred meeting times. | TBD | |
| 40 | +| Gala | Gala will introduce the taxonomy workstream to the Workflow and Processing group and follow up with delegates. | TBD | |
| 41 | +| Julianna | Julianna will add her GitHub username to the repository to obtain write access. | TBD | |
| 42 | +| Amithash | Amithash will contribute missing terms like control plane and kill switch to the governance taxonomy. | TBD | |
| 43 | +| All WG Chairs | Working Group Chairs will review and approve the updated charter in GitHub. | TBD | |
| 44 | +| All WG Chairs | Working Group Chairs will nominate one or two active delegates for the taxonomy workstream. | TBD | |
| 45 | +| All Participants | Participants will start contributing to the taxonomy by creating pull requests for 10-20 key terms. | TBD | |
0 commit comments