Hi Christopher,
I'm sorry but I don't understand what you're asking, this project
didn't change licenses. It might contain some classes copied from
Apache2 projects, and some of its components use an ASL2 license (it's
split in independent modules), but no part of Hibernate ORM changed
license.
At best it's possible that your tool found some human error case of
some headers being misplaced and then fixed, but I'm not aware of such
a case.
Regards,
Sanne
On 20 August 2014 04:42, Christopher G Vendome <cvendome(a)cs.wm.edu> wrote:
Hello,
I'm a Ph.D. student conducting a study on Open Source projects hosted on GitHub with
respect to licensing considerations. Specifically, we are interested in understanding the
developer rationale for both picking and changing a license. We found your project:
"hibernate-orm" experienced the following license change to its files:
Apache:2->null:null LGPL:2.1+->null:null (if the change has a null:null value, it
represents no license or an unknown license as determined Ninka - a state of the art
license extraction tool. Also, patterns are split by a space). If you would be willing to
answer a short survey of 6 questions, please respond to the survey below. The answers are
strictly for research purposes that we plan to publish. We will keep responses private and
if quoted, we will not directly link you to any responses in the publication.
The survey link is:
https://wmsurveys.qualtrics.com/SE/?SID=SV_0qQEhAEp08bKEZf
We appreciate your time and thank you for your help understanding developer rationale
with respect to software licensing.
Regards,
Christopher Vendome
http://www.cs.wm.edu/~cvendome