[
https://issues.apache.org/jira/browse/HADOOP-6775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871980#action_12871980
]
Doug Cutting commented on HADOOP-6775:
--------------------------------------
> So that future bylaws, release policies, etc. can reference it, packaging it
> with the site documentation could make things slightly easier...
We're able to refer to product documentation from the site with a relative link
to docs/current, and we're able to refer to site documentation from the product
documentation with links to http://hadoop.apache.org/.
A case I'm worried about is that if we, e.g., rename or remove one of these
categories, then released documentation would no longer make sense. The
definition of these terms seems like a part of the product documentation, not a
part of the project policy. How we apply and enforce the terms is a matter of
policy.
Most project policy has typically been documented on the wiki, not the website.
Should we change that?
> Update Hadoop Common Sites
> ---------------------------
>
> Key: HADOOP-6775
> URL: https://issues.apache.org/jira/browse/HADOOP-6775
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
> Fix For: site
>
> Attachments: api_classification.pdf, siteCLassification.patch,
> siteCLassification2.patch, siteCLassification3.patch
>
>
> Add documentation on our interface classification scheme to thew common site.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
