And per
> (1) We would slowly work to replace our existing license headers with
> this new standard license header. (Or, if possible, do a giant bulk
> replace of our existing headers for the 1.7.0 release)
The license:format plugin in the dspace-pom will facilitate this batch across
the enti
+1
We came up with the more concise format last year to reduce the amount of
commenting at the top of the files and to standardize the licensing includes
int he maven release process. The new dspace-pom projects assure that
licensing is always validated on all the files prior to release.
I wi
Hi Mark,
Good question.
I'm told the Fedora folks ran their license header solution (referencing
an external file) by lawyers at UVA a few years ago, and they were OK
with it.
Also, again note we are not suggesting any changes to either the DSpace
License or Copyright text. We'll still obvio
Have the Foundation's lawyers examined the proposed change and given
an opinion? or is there one already covering the Fedora practice?
Mechanical details are important, but ultimately the most important
aspect of copyright claims and licensure is whether they work in the
legal context.
If the lawy
All,
Just thought I'd bring this up while it's fresh in my mind. A few of us
in DuraSpace got into a license header discussion, and it made me
re-discover our current DSpace license header situation.
Most of our codebase still uses the policy of including the entire
license as a header in a s
