Skip to content

[HEALTH]: Hexa #2054

Closed
Closed

Description

@kfaseela

Archiving Checklist

  • TOC vote to archive passed

PRs

Mailing lists

  • Remove from staff list of maintainer emails list
  • Archive (lock) maintainers mailing list (groups.io)
  • Remove mailing list from maintainers@ mailing group

Send emails

  • Remove project (logo) from all slide decks (contact pr@cncf.io)
  • Remove project (logo) from event sites (contact events@cncf.io)
  • Remove from CNCF store (reach out to staff or email store@cncf.io)
  • Archive project in LFX Insights (move to archive in PCC - Email Formation team)

Other:

  • Remove from maintainers & project from service desk
  • Check with LF IT for any CI/CD or other infrastructure the needs to be removed
  • Check if any Copilot access need to be revoked

Project name

Hexa

Project Health Notification Link (issue, message to mailing list etc)

TBA

Concern

We’re checking in because, based on what we can observe publicly, Hexa appears to have very low / no recent activity across several common signals over the last year (2025-03-04 to 2026-03-04).

Supporting references:

Screenshots (to preserve what we’re seeing at time of filing):

  • Project stats have dropped off, no commits for the last 90 days:
Image

We want to record what we see and - most importantly ask:

  • Are you all doing ok?
  • How can the CNCF community / TOC help?

Prior engagement

No response

Additional Information

No response

Archiving Checklist (If project is determined for archival)

NOTE: Only applicable if the project opts to self-archive, or is initiated as a last possible option following a TOC vote.
To proceed with the archival checklist, add the level/archive label and assign: caniszczyk, mrbobbytables, idvoretskyi, jeefy, castrojo, krook

Details

Archiving Checklist

  • TOC vote to archive passed

PRs

Mailing lists

  • Remove from staff list of maintainer emails list
  • Archive (lock) maintainers mailing list (groups.io)
  • Remove mailing list from maintainers@ mailing group
  • Remove from cncf-maturity-level -projects@cncf.io (google groups)

Send emails

  • Remove project (logo) from all slide decks (contact pr@cncf.io)
  • Remove project (logo) from event sites (contact events@cncf.io)
  • Remove from CNCF store (reach out to staff or email store@cncf.io)
  • Archive project in LFX Insights (move to archive in PCC - Email Formation team)

Other:

  • Remove from maintainers & project from service desk
  • Check with LF IT for any CI/CD or other infrastructure the needs to be removed

Activity

  1. added
    needs-triageIndicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)
    kind/reviewItem related to a governance, tech, or other review
    on Mar 4, 2026
  2. kfaseela commented on Mar 4, 2026

    @kfaseela
    ContributorAuthor
  3. added
    triage/validIssue or PR is valid with enough information to be actionable
    and removed
    needs-triageIndicates an issue or PR that has not been triaged yet (has a 'triage/foo' label applied)
    on Mar 16, 2026
  4. added
    needs-groupIndicates an issue or PR that has not been assigned a group (toc or tag/foo label applied)
    on Apr 22, 2026
  5. 16 remaining items

  6. git-vote commented on Jun 13, 2026

    @git-vote

    Vote status

    So far 54.55% of the users with binding vote are in favor and 0.00% are against (passing threshold: 66%).

    Summary

    In favor Against Abstain Not voted
    6 0 0 5

    Binding votes (6)

    User Vote Timestamp
    abebars In favor 2026-06-12 16:52:28.0 +00:00:00
    chadbeaudin In favor 2026-06-09 15:48:22.0 +00:00:00
    chira001 In favor 2026-06-09 15:38:39.0 +00:00:00
    kevin-wangzefeng In favor 2026-06-13 2:19:43.0 +00:00:00
    kfaseela In favor 2026-06-09 16:01:03.0 +00:00:00
    salaboy In favor 2026-06-09 15:40:12.0 +00:00:00
    @angellk Pending
    @jrsapi Pending
    @mfahlandt Pending
    @jeremyrickard Pending
    @brandtkeller Pending
  7. brandtkeller commented on Jun 14, 2026

    @brandtkeller
    Member

    This issue pinged a few maintainers directly. My only outlier was public discoverability. hexa-org/policy-orchestrator#448 directly references this issue now.

  8. git-vote commented on Jun 14, 2026

    @git-vote

    Vote status

    So far 63.64% of the users with binding vote are in favor and 0.00% are against (passing threshold: 66%).

    Summary

    In favor Against Abstain Not voted
    7 0 0 4

    Binding votes (7)

    User Vote Timestamp
    abebars In favor 2026-06-12 16:52:28.0 +00:00:00
    brandtkeller In favor 2026-06-14 15:59:44.0 +00:00:00
    chadbeaudin In favor 2026-06-09 15:48:22.0 +00:00:00
    chira001 In favor 2026-06-09 15:38:39.0 +00:00:00
    kevin-wangzefeng In favor 2026-06-13 2:19:43.0 +00:00:00
    kfaseela In favor 2026-06-09 16:01:03.0 +00:00:00
    salaboy In favor 2026-06-09 15:40:12.0 +00:00:00
    @angellk Pending
    @jrsapi Pending
    @mfahlandt Pending
    @jeremyrickard Pending
  9. git-vote commented on Jun 15, 2026

    @git-vote

    Vote closed

    The vote passed! 🎉

    72.73% of the users with binding vote were in favor and 0.00% were against (passing threshold: 66%).

    Summary

    In favor Against Abstain Not voted
    8 0 0 3

    Binding votes (8)

    User Vote Timestamp
    @abebars In favor 2026-06-12 16:52:28.0 +00:00:00
    @brandtkeller In favor 2026-06-14 15:59:44.0 +00:00:00
    @chadbeaudin In favor 2026-06-09 15:48:22.0 +00:00:00
    @chira001 In favor 2026-06-09 15:38:39.0 +00:00:00
    @jeremyrickard In favor 2026-06-14 17:23:19.0 +00:00:00
    @kevin-wangzefeng In favor 2026-06-13 2:19:43.0 +00:00:00
    @kfaseela In favor 2026-06-09 16:01:03.0 +00:00:00
    @salaboy In favor 2026-06-09 15:40:12.0 +00:00:00
  10. lukaszgryglicki commented on Jun 18, 2026

    @lukaszgryglicki
    Member

    Removed from DevStats.

  11. angellk commented on Jul 6, 2026

    @angellk
    Contributor

    LFX Insights Activity Data (as of Jul 5, 2026)

    LFX Dashboard

    Signal Value
    Health Score 46
    Org Dependency 83%
    Contributor Dependency 58%
    Active Contributors (365d) 17
    Active Orgs (365d) 8
    Stars (365d) 7
    Forks (365d) 3
    Software Value $1.8M

    GitHub signals: 108 stars, 17 forks, 47 open issues. Last push: May 25, 2025 — over 13 months with no activity. Not archived. Already removed from DevStats (Jun 18, 2026).

    Assessment: Health score 46 is the lowest among active CNCF projects. 17 contributors and 8 orgs with 83% org dependency. No commits in over a year. Removed from DevStats. This project appears to meet the criteria for archival.

  12. angellk commented on Jul 6, 2026

    @angellk
    Contributor

    Commit Trend (last 12 months)

    Quarter Commits Trend
    Q1 (12mo ago) 0
    Q2 (9mo ago) 0
    Q3 (6mo ago) 0
    Q4 (last 3mo) 0
    Last 4 weeks 0

    ⚠️ Zero commits in the last 12 months. Combined with health score 46, 17 contributors, removal from DevStats, and last push May 2025 — this project meets archival criteria.

  13. chira001 commented on Jul 7, 2026

    @chira001
    Contributor

    note that the vote to archive passed : #2054 (comment)

    @riaankleinhans - we can proceed with archival.

  14. riaankleinhans commented on Jul 7, 2026

    @riaankleinhans
    Contributor

    @chira001 the project was achieved middle of June (PRs Linked above) I just failed to close the issue. Thank you for the reminder.

  15. moved this from Active Review & Discussion to Done in CNCF TOC Boardon Jul 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

gitvotegitvote/closedgitvote/passedkind/reviewItem related to a governance, tech, or other reviewreview/healthProject Health Reviewtoctoc specific issuetriage/validIssue or PR is valid with enough information to be actionablevote/nominationA nomination or call for nominations

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions