[FEATURE] Name "The LLMKube Authors" in copyright headers and LICENSE
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
- Domain
- documentation, tooling
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
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:
- 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. - Template and check:
hack/boilerplate.go.txtbecomesCopyright 2026 The LLMKube Authors., andcmd/check-copyright'scopyrightLinerequires that form for new files, with its tests updated (a new file with the oldCopyright 2026.form must fail). - Existing files: every Go file's header line
Copyright <year>.becomesCopyright <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 ofmake generateandmake manifestswith the new header and show no other drift. - 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 underdocs/superpowers/plans/that quote the old header stay as they are. - 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.
- 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/mainpasses on the branch, and fails on a scratch file with the old form.git grep -E '^Copyright [0-9]{4}\.$' -- '*.go'finds nothing.make gatepasses, 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.txtand 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
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from defilantech/LLMKube
-
component/metal-agent documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
defilantech/LLMKube#2581 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
defilantech/LLMKube#2578 ·
Maintainers usually reply within 1 day
-
documentation helm priority/low size/small
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
defilantech/LLMKube#2420 ·
Maintainers usually reply within 1 day
-
component/metal-agent enhancement priority/low size/medium
Difficulty 4/5 3-5 days Newbie friendliness 48/100
defilantech/LLMKube#2597 ·
Maintainers usually reply within 1 day
-
[BUG] Docs and comments describe InsufficientMemory only as a start refusal, but a serving engine can now carry itPossibly taken @defilan-agent claimed this today. Openbug component/metal-agent documentation priority/low size/small
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
defilantech/LLMKube#2596 ·
Maintainers usually reply within 1 day
All issues in defilantech/LLMKube
Similar issues
-
☢️ Bug v3
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area/import-export area/projects concern/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
go-vikunja/vikunja#4455 · 1 comment ·
Maintainers usually reply within 2 days
-
Dependabot PRs no longer merge automaticallyPossibly taken @dwisiswant0 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
projectdiscovery/urlfinder#160 ·
Maintainers usually reply within 1 day
-
database
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
chnm/legal-modernism#450 ·
Maintainers usually reply within 1 day
-
tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day