This document states the license file must be called 'LICENSE'
and the notice file called 'NOTICE'. In jakarta-commons the
convention used for the license file is LICENSE.txt. So my question
is, MUST the files be called 'LICENSE' and 'NOTICE' or will
'LICENSE.txt' and 'NOTICE.txt' suffice? Just
There's no quick answer; the question is, will someone who is making a
good-faith effort to follow the license not realize that the LICENSE and
NOTICE files are slightly differently named, and thus not follow whatever
related requirements are in the license. Even in that rare circumstance,
most o
Roy, Berin,
This document states the license file must be called 'LICENSE'
and the notice file called 'NOTICE'. In jakarta-commons the
convention used for the license file is LICENSE.txt. So my question
is, MUST the files be called 'LICENSE' and 'NOTICE' or will
'LICENSE.txt' and 'NOTICE.txt' suf
Roy T. Fielding wrote:
> http://www.apache.org/dev/apply-license.html
Thanks.
Has anyone developed more tools to assist with this? I know
that Adam and Antoine have done the relicense.py in the
committers CVS. Should that be mentioned at apply-license.html
We need another tool to determine the f
For those who have not seen it - there are some guidelines (thanks to
Roy!) on applying the 2.0 license to code at :
http://www.apache.org/dev/apply-license.html
Not just me -- thanks to Berin as well, for providing the first draft
and getting me off my butt to finish it.
Roy
Peoples,
For those who have not seen it - there are some guidelines (thanks to
Roy!) on applying the 2.0 license to code at :
http://www.apache.org/dev/apply-license.html
They have been very useful for us.
Cheers,
Berin
---
