Skip to content

license: remove GPL-family package/runtime boundary for commercial intake #83

Description

@seonghobae

Problem

README/public-surface due diligence found that kaefa is not currently compatible with ContextualWisdomLab's no-GPL-family commercial intake baseline.

Current package metadata on protected development lineage declares:

  • License: GPL-3 for kaefa itself;
  • direct runtime import mirt (>= 1.27), a GPL-family dependency used throughout the numerical/model-fitting path;
  • additional direct R imports that require a complete current license/provenance inventory before any relicensing claim.

There is no root LICENSE file that independently grants Apache-2.0 or MIT. The repository's own outbound license and third-party runtime obligations must be resolved separately; a README or metadata edit cannot relicense dependencies.

Provenance boundary

DESCRIPTION identifies Seongho Bae as author/creator and Tae-Yong Yoo as thesis contributor (ths, ctb). Before changing kaefa's own outbound license, inspect git/file-level contribution provenance and confirm the rights needed for relicensing. Do not infer relicensing authority solely from current organization ownership.

Required outcome

Establish a commercially intake-compatible source and runtime graph without changing the scientific estimands merely to satisfy licensing policy.

Acceptance requires:

  • complete first-party contribution/provenance review sufficient for any Apache-2.0 or MIT relicensing decision;
  • complete direct/transitive runtime/build/vendored license inventory for the intended distribution model;
  • removal/replacement of GPL/LGPL/AGPL-family runtime, build, vendored, copied-source, and derivative obligations under the organization policy, including the current mirt boundary;
  • numerical regression/recovery evidence demonstrating that replacement estimation/item-fit/search behavior preserves the intentionally supported kaefa contracts;
  • package metadata and any root license/NOTICE files agreeing exactly with the resulting grant and attribution obligations;
  • R CMD check, fast/full tests, recovery tests, package/SBOM/provenance/security checks on the replacement graph;
  • README/docs clearly separating kaefa source licensing from third-party software.

Do not close this by suppressing license inventory output, treating GPL commercial-use permission as equivalent to the organization's no-GPL-family policy, or moving the same GPL implementation behind a process/container boundary without resolving the intake policy.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions