[
https://issues.apache.org/jira/browse/CB-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262703#comment-13262703
]
Jukka Zitting commented on CB-6:
--------------------------------
To answer your question from above: Both the scripts and the Markdown files
should have source headers. The final HTML pages should too, but that's less
important since few people will be modifying those files.
The relevant sections from the source header policy page are:
{quote}
Q: Does this policy apply to documentation files included in a release?
A: Yes.
Q: What if my project includes its web site within a product distribution?
A: With few exceptions, all human-readable Apache-developed files that are
included within a distribution must include the header text. 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.
Q: What files in an Apache release do not require a license header?
A: A file without any degree of creativity in either its literal elements or
its structure is not protected by copyright law; therefore, such a file does
not require a license header. If in doubt about the extent of the file's
creativity, add the license header to the file.
{quote}
> Apache source headers in callback-docs
> --------------------------------------
>
> Key: CB-6
> URL: https://issues.apache.org/jira/browse/CB-6
> Project: Apache Callback
> Issue Type: Sub-task
> Components: Docs
> Reporter: Jukka Zitting
> Assignee: Ross Gardler
> Priority: Blocker
> Fix For: 1.7.0
>
>
> The callback-docs "codebase" should be updated to use the Apache source
> header as described in http://www.apache.org/legal/src-headers.html.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
