-
assigned issue to
plscott
Add license header to X3DOM-related css and js files
Issue #736
resolved
The css and js files in utils/x3dom/ need to have a license header added.
We could take the chance here to follow up on another discussion about using short license statements rather than including all the LGPL boilerplate.
Comments (14)
-
reporter
-
The license statement we currently use is correct according to the GPL howto. What is the reason for changing it?
-
reporter
@johannes_ring The lengthy boilerplate in every file is a bit annoying an unnecessary. In particular for demos, it obscures the point which is the actual code. @martinal suggested following the Jupyter approach, see for example top of https://github.com/jupyter/notebook/blob/master/notebook/log.py.
-
reporter
@plscott Have a think about what the right license is for the css and js code - I imagine LGPL isn't really appropriate.
-
reporter
@plscott Could you look at this? Would be good to sort it before the imminent release.
-
reporter
@plscott Could you make this a priority? We need to have the license sorted our before a release.
-
Let's just add our standard LGPL license for now and then later rethink our headers. We could make it even shorter:
Copyright (C) FEniCS. Licensed under the LGPL v3+. See LICENSE for details.@garth-wells
-
reporter
Is LGPL a suitable license for java script and css?
-
I'm not sure but lacking a good information on which is the best license for java script LGPL seems like the natural choice when it is distributed as part of DOLFIN.
-
-
reporter
@johannes_ring Good point - it needs to validate correctly.
-
- changed status to resolved
Fix issue
#736: Add license header to X3DOM-related css and js files→ <<cset 40632e981194>>
-
Fix issue
#736: Add license header to X3DOM-related css and js files→ <<cset 40632e981194>>
-
Merged in logg/fix-issue-736 (pull request #317)
Fix issue
#736: Add license header to X3DOM-related css and js files→ <<cset ee5424f5def5>>
- Log in to comment
