rossant / ipycache

Defines a %%cache cell magic in the IPython notebook to cache results of long-lasting computations in a persistent pickle file
BSD 3-Clause "New" or "Revised" License
138 stars 35 forks source link

Clarify BSD license as BSD-3-Clause #41

Closed jakirkham closed 2 years ago

jakirkham commented 8 years ago

We were adding ipycache to conda-forge, but there seems to be a bit of confusion about the license. Is this intended to be BSD 3-clause?

cc @jochym

rossant commented 8 years ago

Thank you for your interest in ipycache. Unfortunately I don't have enough time right now to manage this project, would you be interested in getting commit access?

jakirkham commented 8 years ago

Thanks for asking. Though that seems like a better question for @jochym. Assuming you are amenable to this @rossant, do you have any interest in helping maintain ipycache, @jochym?

In any event, a clarification on the license would be nice. Though, to be honest, I have forgotten what the point of confusion was.

mbrukman commented 2 years ago

@jakirkham — was this already resolved previously, or is there still confusion over the license?

Per https://github.com/rossant/ipycache/blob/master/LICENSE.md, GitHub is classifying this as:

BSD 3-Clause "New" or "Revised" License

Are you asking that setup.py is updated to use a more specific SPDX identifier for the BSD 3-clause license vs simply the string "BSD" as it says now? Or are you looking for something else?

jakirkham commented 2 years ago

@mbrukman, sorry I don't really know. It has been a long time since this issue was opened and have unfortunately forgotten the context of the confusion

@jochym, is there anything remaining to do here from your standpoint?

jakirkham commented 2 years ago

Found this comment. Maybe this is helpful?

Updating this line to BSD-3-Clause would also help

In conda-forge the package has since been updated to list BSD-3-Clause as the license in the package metadata

jochym commented 2 years ago

Sorry for not responding.

  1. The license is BSD-3-clause, I believe. It should be as the original author selected.
  2. As for maintenance. I can adopt the package but cannot promise intensive development.
rossant commented 2 years ago

Sorry I haven't been closely following this discussion, but as the original author, I shall say I'm happy with the license being updated to match whatever is currently considered as standard practice in similar Python projects.

mbrukman commented 2 years ago

@jakirkham — re: s/BSD/BSD-3-Clause/ in setup.py — sounds good, will do shortly!

@jochym — FWIW, I've signed up to be a co-maintainer; you're welcome to join the party as well if you wish!

jakirkham commented 2 years ago

Thanks for all the work here @mbrukman ! 😀