Skip to content

[Discussion] Switching to a copyleft license? #455

Open

Description

@Yue-Zhengyuan

With AI making it much easier to copy, translate, and build on existing code, switching future releases from MIT to GPLv3 or AGPLv3 could help keep more of that work available to the community. (This suggestion applies to all QuantumKitHub packages.)

Under MIT, someone can take our packages, improve them, and sell a closed-source version without sharing their changes. GPLv3 would require them to share the source when they distribute a version based on our code, while AGPLv3 also covers modified versions that people use over a network (e.g. some cloud simulation platform).

Others could still build commercial products, but users would retain the ability to inspect, modify, and share the covered code. That could help our work — and improvements built on it — remain a shared resource.

It wouldn’t guarantee contributions back to us or cover every independent rewrite, and existing MIT releases would remain available under MIT, but it would set a clearer expectation of sharing going forward.

For comparison, our friends working on YASTN and variPEPS use the GPL-3.0 license.

Activity

  1. Yue-Zhengyuan commented on Oct 16, 2026

    @Yue-Zhengyuan
    MemberAuthor

    I started to think about this when working on split-CTMRG (#441), which borrowed a few small numerical tricks (like where to add normalizations) from variPEPS. Their GPL-3 license will require me to adopt GPL as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions