Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to follow English (master/HEAD) documents? #41

Open
henry0312 opened this issue Jun 13, 2016 · 5 comments
Open

How to follow English (master/HEAD) documents? #41

henry0312 opened this issue Jun 13, 2016 · 5 comments

Comments

@henry0312
Copy link
Contributor

We need to consider how to follow English documents.

@fchollet
Copy link
Member

Since Keras is in stable state after the release of 1.0, the changes to the documentation should be rare and limited. But there will be changes.

I can post an issue in this repo every time I notice a change happening in the English docs. But I might miss some changes occasionally.

@henry0312
Copy link
Contributor Author

I can post an issue in this repo every time I notice a change happening in the English docs.

Is there no problem if your work are increased?

@fchollet
Copy link
Member

fchollet commented Jun 14, 2016

Another solution:

  • create a new github repo
  • in the keras source, cd to docs/ and run python autogen.py
  • cp the resulting sources dir to the new repo and commit it
  • the new repo now contains the original English markdown files for the documentation. You can regularly update it, and use git diff to visualize what has changed in the English docs.

@henry0312
Copy link
Contributor Author

I hope we could automate these operations (in addition, posting the diff of documetns to github issue).

@fchollet
Copy link
Member

All of the steps above are bash commands. Automation is one script away.

On 14 June 2016 at 19:12, Tsukasa ŌMOTO [email protected] wrote:

I hope we could automate these operations (in addition, posting the diff
of documetns to github issue).


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#41 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AArWb1du1Q_b660gaxqWQB-ZuASW14XAks5qL196gaJpZM4Iz-Mw
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants