TSCCall20260224

Hiero Technical Steering Committee Meeting

TL;DR: The TSC approved creating a dedicated solo-docs repository to decouple Solo documentation from the Solo codebase and enable faster doc updates. The group also agreed to draft governance guidance for release/package naming and publishing namespaces, and received an update on 2026 mentorship program planning.

---

Details

Organization: Hiero
Date: Feb 24, 2026
Time: 10:00 AM ET (approx. 1 hour)
Recording: https://zoom.us/rec/share/kaYnWAqvJ8xMDZI_dDjk1j_YJhVYwAZge2vmVgL7l6vR7ZS4QgDdAeSUuL0N1pBb.NhVxJeAn5VcvD6eV

---

TSC Attendees

• Hendrik Ebbers
• Richard Bair
• Stoyan Panayotov
• Alexander Popowycz
• Georgi Lazarov
• Milan Wiercx van Rhijn
• Brandon Davenport

Guests

• Jessica Gonzalez
• Keith Kowal
• Diane Mueller
• Mike Cave
• Priyanshu Yadav
• Others (who did not appear in transcript)

---

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
• HIPs
• Discussion: HCS integration in HIP repository
• Discussion: Workflow to define namespaces of releases/packages for publishing
  • https://github.com/hiero-ledger/governance/issues/507
• Repository request: solo-docs
  • https://github.com/hiero-ledger/tsc/issues/286
• 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

• Recap of prior TSC call

  • Hendrik recapped a prior discussion on documentation practices across Hiero projects.
  • Keith clarified the recap: there is an action item for him to prepare a documentation-related proposal, but the solo-docs repository request is a separate, more targeted request.

• Proposal discussion: solo-docs repository

  • Keith presented the rationale for creating a dedicated documentation repository for Solo:
    • Current Solo docs are hosted at solo.hiero.org and are built with a Hugo/Docsy-style static site framework.
    • Keeping docs inside the Solo repo creates high friction for updates/review (long local build times and coupling doc updates to product releases).
    • The Solo “product family” is expected to expand (e.g., additional Solo components beyond the CLI), increasing the need for a centralized docs hub.
  • Questions and concerns raised:
    • Alignment with broader doc strategy: Alex emphasized avoiding decisions that might conflict with a forthcoming broader documentation strategy proposal.
    • Build/versioning implications: Hendrik asked how versioned docs and auto-generated sections would work if docs were split from the code repo, and whether splitting could worsen dependency on generated artifacts.
    • Repository/project consistency: Richard asked whether it was appropriate to add the docs repo if Solo were not part of Hiero; it was clarified that Solo CLI is already in Hiero.
  • Responses / clarifications:
    • Keith described the change as primarily relocating existing docs to reduce coupling with the Solo release cycle and lower contribution barriers.
    • The broader doc strategy discussion was framed as largely orthogonal to whether docs live in a separate repo; it is more about providing optional consistency in framework/look-and-feel across projects.
    • The group acknowledged there is no Hiero-wide “release train,” and that consistent doc UX could still be achieved even if docs originate from different repositories.

• Vote

  • The TSC voted to approve creation of the solo-docs repository as the documentation base for the Solo product family.

• HIPs

  • HIPs discussion was skipped (no HIP presenter present).

• HCS integration into HIP repository

  • Deferred due to absence of Michael Kantor.

• Publishing namespaces / release/package naming guidance

  • Hendrik introduced the need for governance guidance on publishing artifacts (naming, namespaces, avoiding conflicts) across ecosystems (e.g., NPM/Maven/etc.).
  • Consensus direction:
    • Establish clear naming rules/guidelines and maintain a central list of published artifacts to prevent naming conflicts.
    • Do not require TSC votes for every artifact/name change if it follows the documented guidelines; handle exceptions as needed.
  • Action item captured for Jessica and Hendrik to draft a document and bring it back to the TSC.

• AOB: Mentorship program planning (2026)

  • Jessica provided an update on efforts to apply for a 2026 mentorship program and shared candidate program ideas discussed in a mentorship meeting held Feb 23, 2026.
  • Topics mentioned included:
    • SDKs v3-related work
    • “Good first issue” management/support (noted as a leading idea internally)
    • HECA identity platform-related mentorship idea (pending maintainer outreach)
    • Web3j-related mentorship idea (pending community coordination)
    • A fifth topic being developed by Hendrik: smart contract event/log support for Hiero Enterprise Java
  • Discussion included:
    • Visibility and promotion channels for mentorship opportunities (LFDT newsletter, social channels, Hiero blog, Discord/public calls, and the mentorship platform itself).
    • Priyanshu shared perspective from prior mentorship experience: sustained mentorship over months increases contributor retention and long-term engagement.

• Process update: roles / contributor ladder

  • Hendrik noted the roles/teams/groups documentation was updated to add a “Junior Committer” role (between contributor and committer), intended to grant limited triage rights and improve scaling of “good first issue” work.
  • Hendrik also noted improvements to make nomination/voting processes for junior committers/committers/maintainers clearer in the document.

• Next meeting

  • Hendrik noted that Hart Montgomery (LFDT) is expected to join the next TSC meeting to provide an overview of LFDT and its projects (Mar 3, 2026).

---

Key Decisions

• Approved: Create the solo-docs repository (separating Solo documentation from the Solo code repository) to support the Solo product family and enable independent documentation updates.

---

Prepared by: Brandon Davenport, Dir of Product, Hgraph