Update of the license text

[gblanke02]

After reviewing the license text of RInChI Richard mentioned that we have to update the copyright line of InChI to

Copyright (c) 2024 IUPAC and InChI Trust

Jan Holst Jensen proposed to move the content of the contributors file into the change log. That makes it clearer which version has got which contributions. -> TBD

[JanCBrammer]

After reviewing the license text of RInChI Richard mentioned that we have to update the copyright line of InChI to

Copyright (c) 2024 IUPAC and InChI Trust

We could tackle this along with #2.

Jan Holst Jensen proposed to move the content of the contributors file into the change log. That makes it clearer whch version has got which contributions. -> TBD

@gblanke02, is this related to the copyright line or should we transfer this to a separate issue?

[gblanke02]

Hi Jan, The second one is related to the contributors.txt file. Jan (Holst Jensen) made the proposal, to add the contributors to the chalnge.log file to make it clearer who helped with what version. While we have to follow up with any (actual) contributors for each release the change of the license note has only to be done once So, to me it makes more sense to split the 2 cases into 2 issues. Best wishes Gerd Von: Jan C. Brammer ***@***.***> Gesendet: Donnerstag, 28. November 2024 16:11 An: IUPAC-InChI/InChI ***@***.***> Cc: ***@***.***; Mention ***@***.***> Betreff: Re: [IUPAC-InChI/InChI] Update of the license text (Issue #70) After reviewing the license text of RInChI Richard mentioned that we have to update the copyright line of InChI to Copyright (c) 2024 IUPAC and InChI Trust We could tackle this along with #2<#2>. Jan Holst Jensen proposed to move the content of the contributors file into the change log. That makes it clearer whch version has got which contributions. -> TBD @gblanke02<https://github.com/gblanke02>, is this related to the copyright line or should we transfer this to a separate issue? — Reply to this email directly, view it on GitHub<#70 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AT3EDCMWGP3IMGVBY2TZYHT2C4XAJAVCNFSM6AAAAABSG7GJGGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBWGMZTIOJVG4>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>7