[FEATURE] Name "The LLMKube Authors" in copyright headers and LICENSE

Open
#2,565 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go

Research direction

Start by reading hack/boilerplate.go.txt and cmd/check-copyright with its tests to understand the required header form. Then update the listed notices in Go file headers, LICENSE, and charts/llmkube/README.md; preserve each Go file's year and avoid changing license blocks. Verify with the issue's git grep command and go run ./cmd/check-copyright -base upstream/main; completion also requires generated files to have no drift and make gate to pass. The issue says to wait until the current wave of open PRs has merged.

Written by the indexing model from the issue text.

Description

enhancement priority/medium size/medium

Feature Description

Name the copyright holder in LLMKube's file headers and LICENSE as "The LLMKube Authors", the form the Linux Foundation recommends and CNCF projects such as Crossplane use (Copyright 2023 The Crossplane Authors.).

Problem Statement

LLMKube's Go file headers read Copyright 2026., kubebuilder's default with the holder left blank: about 970 Go files, plus hack/boilerplate.go.txt and the chart README's License section. The LICENSE appendix names one person (Copyright 2026 Chris Maher), although the project now has contributors from many people and organizations. Ahead of the CNCF Sandbox application, the notices should name the project's authors collectively. Each contributor keeps the copyright in what they wrote; the notice just stops naming no one, or one person. One file already uses the target form: hack/kind-e2e-rbac.sh (# Copyright 2026 The LLMKube Authors.).

As a maintainer, I want the copyright notices to name the LLMKube authors so that the project reads as community-owned when the CNCF reviews it.

Proposed Solution

Decisions:

  1. Form: Copyright <year> The LLMKube Authors. Each existing file keeps its year; only the holder is added. No SPDX headers, no "All rights reserved", no change to the license block under the copyright line.
  2. Template and check: hack/boilerplate.go.txt becomes Copyright 2026 The LLMKube Authors., and cmd/check-copyright's copyrightLine requires that form for new files, with its tests updated (a new file with the old Copyright 2026. form must fail).
  3. Existing files: every Go file's header line Copyright <year>. becomes Copyright <year> The LLMKube Authors., by a mechanical rewrite of that one line only. The PR body shows the command, so a reviewer can rerun it and get the same diff. Generated files come out of make generate and make manifests with the new header and show no other drift.
  4. Other notices: the LICENSE appendix becomes Copyright 2026 The LLMKube Authors, and the chart README's License section (charts/llmkube/README.md) gets the same line. Historical plan documents under docs/superpowers/plans/ that quote the old header stay as they are.
  5. Commits: one commit for the mechanical header rewrite, a separate one for the template, the check, LICENSE and the chart README, so the hand-written part can be reviewed on its own.
  6. Timing: hold until the current wave of open PRs has merged. The rewrite touches nearly every Go file, and once the check changes, any open PR that adds a Go file fails it until that file's header is updated. The PR body lists the open PRs that add Go files at the time it is opened.

How to verify:

  • go run ./cmd/check-copyright -base upstream/main passes on the branch, and fails on a scratch file with the old form.
  • git grep -E '^Copyright [0-9]{4}\.$' -- '*.go' finds nothing.
  • make gate passes, with no regen drift.

Alternatives Considered

  • "Copyright Contributors to the LLMKube project": also an LF-recommended form, but "The LLMKube Authors" matches the one script that already uses a holder and what Kubernetes-ecosystem projects use.
  • Naming a company or person: cuts against the project being vendor-neutral, and copyright stays with each contributor either way.
  • Dropping the year: allowed by the LF guidance, but keeping it makes the check change and the rewrite smaller.

Additional Context

  • Related issues: #2298 (the year check), #2564 (third-party notices), both ahead of the CNCF Sandbox application.
  • Similar features in other projects: Crossplane's hack/boilerplate.go.txt and LICENSE appendix; the LF guidance at https://bestpractices.linuxfoundation.org/ip/copyright-notices.html
  • Workarounds you're currently using: none.

Priority

  • Critical - Blocking my use case
  • High - Would significantly improve my workflow
  • Medium - Nice to have
  • Low - Minor improvement

Willingness to Contribute

  • Yes, I can submit a PR
  • Yes, I can help test
  • No, but I can provide feedback
  • No, just requesting
Dominant language
Go
Stars
232
Forks
37
Avg merge
21h 42m
Merged PRs (30d)
244

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from defilantech/LLMKube

All issues in defilantech/LLMKube

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.