[
https://issues.apache.org/jira/browse/DERBY-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464251
]
Jean T. Anderson commented on DERBY-2227:
-----------------------------------------
Here's more clarification because this can be kind of confusing....
We need to separate the issues of "source" from "built product" because the ASF
requirements are different.
The ASF source header policy [1] requires that a source file NOT have a
copyright statement in it; it should have the header specified in [1]. There
was a flurry of activity before 10.2.1.6 was released to update derby source
(DERBY-1377, DERBY-1422). The copyright goes into the NOTICE file instead.
The answer for [1]'s FAQ "What if my project includes its web site within a
product distribution?" covers all documentation (not just web site):
> Documentation, including web site documentation distributed with the release,
> may include the header text within some form of metadata (such as HTML
> comments) or as a header or footer appearing in the visible documentation.
So that's the *source file* policy.
For the built and distributed "product", things aren't quite so cut and dried
from my read. Look at the FAQ for [1]: "Does this policy also apply to content
displayed on our web sites?" The answer is currently "no". At some point, a
"terms of use" link might be added to web site pges.
ASF guidelines for how to form the copyright statement are covered in [2].
I don't think that a copyright needs to appear on each displayed page, but that
discussion might be better moved to DERBY-2237.
[1] http://www.apache.org/legal/src-headers.html
[2] http://www.apache.org/dev/apply-license.html
> Web Site - Add Checklist page for Doc updates for each release
> --------------------------------------------------------------
>
> Key: DERBY-2227
> URL: https://issues.apache.org/jira/browse/DERBY-2227
> Project: Derby
> Issue Type: Improvement
> Components: Web Site
> Reporter: Laura Stewart
> Assigned To: Laura Stewart
> Priority: Minor
> Attachments: docscheck.html, site.xml
>
>
> Create a list of items to check and update for each release for the
> documentation.
> This list should include copywrite info, dates/time issues in the Working
> with Derby
> See this thread:
> http://www.nabble.com/Proposal---New-page-for-%22Release-Checklist-for-Docs%22-to-Derby-Doc-Web-Pages-%28WAS-Re%3A--jira--Commented%3A-%28DERBY-2194%29-A-few-more-problems-with-Working-with-Derby-manual-tf2947889.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
