Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

track code license over time #110

Open
ltalirz opened this issue Mar 20, 2022 · 2 comments
Open

track code license over time #110

ltalirz opened this issue Mar 20, 2022 · 2 comments
Labels
2024 To be fixed in 2024 update enhancement New feature or request help wanted Extra attention is needed

Comments

@ltalirz
Copy link
Owner

ltalirz commented Mar 20, 2022

For an accurate historical analysis of license models, one should record the license of the individual codes as a function of time, rather than just stating the license that a code has today.

@ltalirz ltalirz added the enhancement New feature or request label Mar 20, 2022
@ltalirz
Copy link
Owner Author

ltalirz commented Apr 16, 2022

In principle, all metadata can evolve over time - we've already encountered the case for time-dependent query strings #114 (comment)

At the same time, recording time-dependent metadata will remain an exception and be introduced only where necessary (most metadata won't change over time).

This could be modeled by a schema like:

"code-name": {
  "query_string": "val",
  "license": "val",
  "updates": {
    "2020": {
      "license": "val-new",
      "query_string": "val-new"
    }
  }
}

where the value for 2021 would be obtained by recursively updating the top-level dictionary of the code with changes from all relevant years from the "evolution" key.

This probably means we should then pre-build the "rendered" version of the code metadata for each year.
This is not a big deal though - the current file has 40KB of text, so we'll be adding < 40KB*12 of memory.

Since the citation data for year X is retrospective, the changes for year X should reflect the metadata at the beginning of year X.

@ltalirz ltalirz added 2024 To be fixed in 2024 update help wanted Extra attention is needed labels Sep 10, 2023
@ltalirz
Copy link
Owner Author

ltalirz commented Sep 10, 2023

There have been a number of license changes since the list started in 2021: at least molcas, castep, amber, gromos, cpmd.
I suspect a few more might have changed from 2010-2021.

Edit: DIRAC switched to LGPL

Since we only record the latest license, we currently misrepresent the license trends at the ecosystem level (in particular, free/open licenses are actually growing more strongly than the current graphs would show).

It would be very nice to fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2024 To be fixed in 2024 update enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant