Skip to content

Copyright notation inconsistencies #8

Open

Description

@merkys

Many thanks for switching to MIT license for InChI! I believe such change in licensing will benefit everyone.

While looking at what is on InChI GitHub repository, I noticed some licensing notation inconsistencies.

First of all, in the source released as v1.07-beta.3, a lot of source files still bear the old copyright notice:

* This library is free software; you can redistribute it and/or modify it
* under the terms of the IUPAC/InChI Trust InChI Licence No.1.0,
* or any later version.

In strict sense individual file copyright notices override the top-level copyright indication. Would it be possible to replace there notices with ones mentioning MIT, or removing them altogether?

Second, in the source released as v1.07-beta.3 there is a file INCHI-1-SRC/LICENCE.pdf with the old InChI license. The existence of such file creates some ambiguity over the true license of the source.

Third, other source releases such as v1.06 now bear the new license statement in LICENSE file. Assuming this does not mean that previous InChI releases are now relicensed, the existence of this file in the earlier releases may as well cause some confusion over the true license of the source.

Activity

  1. JanCBrammer commented on Feb 20, 2024

    @JanCBrammer
    Collaborator

    @merkys, thanks for the issue! We need to clean this up.

    • consistently license source files with MIT (see Parametrize version and file header #2)
    • remove obsolete references to previous license (e.g., INCHI-1-SRC/LICENCE.pdf)
    • correctly and consistently license legacy releases (v1.03 through v1.06)
  2. merkys commented on Feb 20, 2024

    @merkys
    Author

    Great, thanks for prompt response!

  3. JanCBrammer commented on Feb 20, 2024

    @JanCBrammer
    Collaborator

    Third, other source releases such as v1.06 now bear the new license statement in LICENSE file. Assuming this does not mean that previous InChI releases are now relicensed, the existence of this file in the earlier releases may as well cause some confusion over the true license of the source.

    @gblanke02, we need to decide if we re-license versions <= v1.06 with MIT or keep the original license.

  4. gblanke02 commented on Feb 20, 2024

    @gblanke02
    Contributor
  5. merkys commented on Sep 10, 2025

    @merkys
    Author

    I noticed that IUPAC/InChI Trust InChI Licence resurfaced in several places in v1.07.4:

    • INCHI-1-SRC/INCHI_API/demos/inchi_main/readme.txt
    • INCHI-1-SRC/INCHI_API/demos/mol2inchi/readme.txt
    • INCHI-1-SRC/INCHI_API/demos/test_ixa/readme.txt

    Does this mean these sources were intentionally relicensed under IUPAC/InChI Trust InChI Licence?

  6. fbaensch-beilstein commented on Sep 15, 2025

    @fbaensch-beilstein
    Collaborator

    @merkys Thanks for mentioning it, the license is now updated in these files.

  7. merkys commented on Sep 15, 2025

    @merkys
    Author
  8. fbaensch-beilstein commented on Dec 4, 2025

    @fbaensch-beilstein
    Collaborator

    @merkys, thanks for the issue! We need to clean this up.

    * [ ]  consistently license source files with `MIT` (see [Parametrize version and file header #2](https://github.com/IUPAC-InChI/InChI/issues/2))
    * [ ]  remove obsolete references to previous license (e.g., `INCHI-1-SRC/LICENCE.pdf`)
    * [ ]  correctly and consistently license legacy releases (`v1.03` through `v1.06`)
    

    @JanCBrammer anything we can tick here?

  9. fbaensch-beilstein commented on Apr 29, 2026

    @fbaensch-beilstein
    Collaborator

    @JanCBrammer reminder to have look ;)

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions