On 15 Apr 2016, at 18:29, Francis Poulin <fpoulin@uwaterloo.ca> wrote:
Thanks. Because I wrote my doc in a latex file I will use pandoc to convert the doc to rst.
Aha, I see.
To make the update on github, I was thinking of using my firedrake installation folder. Is that a bad idea?
No, that's fine. You will want to make a new local branch to commit your demo changes in. Because you don't have write access to the firedrake repository you won't be able to push that branch to github. You can fork the firedrake repo and add your fork as a new remote, you'll then be able to push to that and open a pull request from there. If you go down this route, you should probably make sure to switch back to master once you're done, otherwise firedrake-update may get confused (it just tries to update your current branch and doesn't switch branches for you).
If yes I can git clone the master branch, create a new branch, push the changes, and let you guys look it over and see if it's up to snuff.
This is also fine (if you don't want to mess around with the existing installed repo). But not in both cases you won't have write access to the main firedrake repo (so you'll need to fork either way). If this could be explained more clearly somewhere in our documentation, please let us know! Thanks, Lawrence