[jira] [Commented] (EAGLE-373) Move Eagle document to Eagle source code control

["Julian Hyde (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/EAGLE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374076#comment-15374076 ] 

Julian Hyde commented on EAGLE-373:
-----------------------------------

In my experience keeping docs on a branch is tricky. (It is impossible to fix the code AND update the doc in a single patch.) I find it easier to put them in a sub-directory of the source code. Or you could create a separate git repo.

This issue must be fixed before Eagle graduates.

> Move Eagle document to Eagle source code control
> ------------------------------------------------
>
>                 Key: EAGLE-373
>                 URL: https://issues.apache.org/jira/browse/EAGLE-373
>             Project: Eagle
>          Issue Type: Improvement
>    Affects Versions: 0.5
>            Reporter: Edward Zhang
>            Assignee: Edward Zhang
>            Priority: Minor
>             Fix For: 0.5
>
>
> Today Eagle's document is maintained in https://github.com/eaglemonitoring/eaglemonitoring.github.io, it does not conform to Apache policy. We should move this into Apache git source control. The approach is to create a branch called document in https://github.com/apache/incubator-eagle/tree/document and put document into it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)