TSCCall20260217

Hiero Technical Steering Committee Meeting

TL;DR: The TSC did not have quorum, so no HIP votes occurred. The primary discussion focused on improving Hiero documentation discoverability and proposing a more unified, AI-friendly docs approach (potentially a hosted platform with a hybrid “docs-in-repos, rendered centrally” model).

---

Details

Organization: Hiero
Date: Feb 17, 2026
Time: 10:00–10:32 AM ET
Recording: https://zoom.us/rec/share/Yak4W9gaGtbo59CEKFNE-ntS-1W5GkS5yyidKVaojVQT8FQXHMO-jPgiJGyK3DM.2VrgeR-I0yjxwLcu

---

TSC Attendees

• Hendrik Ebbers
• Stoyan Panayotov
• Milan Wiercx van Rhijn
• Georgi Lazarov
• Brandon Davenport
• Alex Popowycz

Guests

• Diane Mueller
• Keith Kowal
• Mike Cave
• (Chat participants)

---

Agenda Items

• Short overview of last TSC call
• Any Updates/Events from Communities or members?
• Reminder to attend public community calls + bring more activity into Hiero Discord channels
  • Public community calls: https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week
  • Discord channels: https://github.com/hiero-ledger#discord-communication-channels
• HIPs: https://github.com/orgs/hiero-ledger/projects/31/views/1?sortedBy%5Bdirection%5D=asc&sortedBy%5BcolumnId%5D=Status
• Any other business (AOB)

Guests

As every Hiero meeting the TSC meeting is a public meeting and everybody can attend it.
You can find all the information about the TSC meetings and all other Hiero meetings in our public calender.

Code of Conduct

As in every meeting we start with a short notice of the antitrust policy of Linux Foundation and an introduction of our Code of Conduct.

---

Meeting Summary

• Review of prior TSC meeting

  • Last TSC call recap:
    • The TSC voted to approve two HIPs.
    • The group began discussing ways to increase community engagement around HIPs (awareness, interaction, learning).
    • Jessica previously presented Hiero project goals for 2026 (also shared with maintainers); positioned as directional goals rather than hard milestones.

• Community updates

  • No community/member updates were raised during this meeting.

• Reminders: participation and Discord

  • Hendrik encouraged participation in public community calls and using Hiero Discord channels for questions and discussions across projects/SDKs.

• HIPs

  • No quorum was present; therefore no HIP votes could occur.
  • No HIP was scheduled for presentation in this meeting.
  • Keith shared status guidance:
    • One HIP (transcribed as “HIP 31 / HIP 1341”) was described as stable and ready for deeper review by the group.
    • HIP-1340 was described as still in flux, with additional tweaks expected before it is brought to the TSC.

• AOB: Documentation strategy discussion (primary topic)

  • Keith raised the question of whether Hiero should pursue a more unified documentation approach, while recognizing each repo can choose its own docs strategy today.
  • Observations and examples of the current “mixed bag” approach:
    • Legacy docs still exist on docs.hedera.com (hosted on Mintlify).
    • Some projects use traditional static-site tooling; others keep docs primarily in READMEs and folders.
    • Hendrik highlighted that docs.hiero.org exists as a starting point, but much project documentation is not discoverable from there.
    • Solo documentation and Python SDK documentation were cited as examples of differing structures and depth.
  • Key themes and viewpoints:
    • Discoverability and consolidation: Desire for “one interface” or at least a clear index/entry point that can guide users across fragmented docs.
    • AI-driven consumption: Keith emphasized that users increasingly consume docs through AI workflows and that hosted platforms may provide features (search, UX, AI tooling) that are difficult to replicate with open source stacks alone.
    • Hybrid model preference: Multiple participants aligned on a hybrid approach where docs live in repos (Markdown/MDX) but are rendered centrally into a more usable interface.
    • Pragmatism on commercial tooling: Hendrik noted Hiero already uses commercial tooling in other areas; a hosted docs platform could be acceptable if it avoids vendor lock-in and keeps source docs accessible in repos.
    • Need for guidelines / kit: Brandon and Alex suggested establishing best practices, criteria, and possibly an “out-of-the-box Hiero docs kit” to raise baseline quality while not forcing every project onto a single platform.
    • LFDT staff expertise: Diane suggested involving LF Decentralized Trust staff (David Boswell and Rye) who have deep documentation infrastructure experience.
    • Versioning considerations: Hendrik noted some projects (e.g., Solo) have versioned-doc needs, and a centralized approach must account for differing version/release realities across projects.

---

Key Decisions

• No formal decisions were made (meeting lacked quorum).

---

Prepared by: Brandon Davenport, Dir of Product, Hgraph