contributing to the documentation #283
Replies: 3 comments 7 replies
|
At this moment, we are shifting from documentation in the OpenDA repository to documentation on docs.openda.org Could you point us to the information that you would like to update? |
|
Hi @carbonatezero. Nice to hear that you are willing to contribute! I See you have explicitly linked to the course material/documentation. To put is a bit in perspective. The course is a living document/set of model input. Every time a course is organised we select the relevant exercises, fix issues/update when needed. Hence the exercises that are included in openda_course.tex are used at the last course and should be the most up to date/work properly. For contributing I suppose you should be able to create pull requests which is easy for smal suggestions/updates or additions and we can always discuss things here at the discussion forum. |
|
Hi @carbonatezero. I think a slightly different approach is "The GitHub way" If you fork our repository on GitHub. (button at top of GitHub). You can make your improvements on a branch of your forked repository (thanks!). When done you can create a pull request from you forked repository to the master on our repository. (in our GitHub "Pull requests-> New Pull request and select compare across forks". That should work and if not, let me know. In case that does not work I can merge the changes from your forked repository. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello. I'm interested in contributing to the documentation of the OpenDA project and would like to help edit the files in the
docdirectory. In addition to the "contributing guidelines", what would be the best practice to do so?All reactions