Skip to content

CommunityCall20260820

Jessica G edited this page Aug 20, 2026 · 2 revisions

Hiero Community Call — 20 August 2026, 15.00 UTC

Call link: Zoom/Meet linkhttps://zoom-lfx.platform.linuxfoundation.org/meeting/97122675754?password=7eaa865a-2f17-4a7c-97b0-aff51933991c

Attendees

  • [name] — [affiliation]

Agenda

# Topic Owner Time
1 TSC candidate nominations — Sep 2026 election [name] 10 min
2 Committer ladder: growing junior committers, committers, maintainers [name] 10 min
3 Hiero Hackers: a lower-friction sandbox for ideas and repos [name] 10 min
4 Improving our OpenSSF Scorecard [name] 10 min
5 Improving our OpenSSF Best Practices badges [name] 10 min

1. How to nominate yourself or someone else as a TSC candidate

The Sep 2026 election nomination window is August 25 – September 8, 2026, for 2 Maintainer seats and 1 TSC-voted seat.

  • Nominations are submitted as a PR to the governance repo:
    • Directory: elections/nominees/sep-2026-election
    • Add one file named [Candidate-Name].md (spaces replaced with dashes), based on the directory's sample-nomination.md template.
    • The nominee must approve their own nomination — after review, they comment I approve this nomination. on the PR before it can merge.
  • For a worked example of the finished format, see the Sep 2025 election nominees (e.g. Alexander-Shenshin.md, Georgi-Lazarov.md, May-Chan.md).

2. PR governance: growing our junior committers, committers, and maintainers

We want to bring more people up the ladder across Hiero Ledger and Hiero Hackers. Three roles, each a step up in rights and responsibility:

Role Qualification (typical) Rights Nominated by
Junior Committer Regular activity over several weeks — create PRs, preliminary reviews, triage issues GitHub Triage: assign issues, label, mark duplicates, close/reopen Any Junior, Committer or Maintainer
Committer Quality contributions over ~3–6 months Create issues, create PRs, review PRs Any Committer or Maintainer
Maintainer Committer with a track record of project stewardship Drives roadmap/vision, runs community meetings, reports to the TSC, highest quality reviews Any existing Committer or Maintainer

All three go through a PR to the relevant config.yaml in governance, followed by a vote among existing codeowners on that project. Full detail: roles-and-groups.md and the committer/maintainer FAQ.

Discuss: Which active contributors on your project are ready to nominate right now or who is interested?


3. Hiero Hackers: build without the process overhead

Hiero Hackers is the community's low-governance sandbox — explicitly optimized for "speed and creativity, not process": no heavy branch protection, no required review chains, minimal ceremony. It's the right home for hackathon projects, demos, prototypes, sample apps, and tutorials that don't need (or want) the full Hiero governance model yet.

Getting your own repo there:

  1. Open an issue at hiero-hackers/governance.
  2. Include: the repo name, a short description, and (optionally) other people who should get write access.
  3. A maintainer creates the repo and grants write rights to you and your co-committers — no vote, no PR review cycle.

Discuss: Got an idea or experiment? This is where it belongs. Anyone want to walk through creating one live on the call?


4. Improving our OpenSSF Scorecard and Open SSF Best Practices

Our repos' Security & Scorecards dashboard tracks each project against the OpenSSF Scorecard checks — branch protection, code review coverage, dependency update automation, SAST, fuzzing, pinned dependencies, and more. Open SSF Best Practices Badge requires logging in and answering some questions.

Discuss:

  • Which repos are lowest-scoring right now, and why?
  • Pick 1–2 concrete, low-effort checks to fix before the next call.
  • Assign an owner per repo rather than leaving it as a group todo.

Clone this wiki locally