I was tempted to just edit the part on the compilation with Linux and make. However, if you just split the compiling section into subsections for compiling with windows and with linux and, then, with make and cmake, this would help speed-read the document.
Hey, you can fork the project, create a branch just for your wiki mods, push your changes there to test and then open a pull request to merge your modifications, if they are approved by the repo mods. Cheers!
Intriguing idea to collaborate with users and external developers effectively and efficiently.
However, I see that in GitHub the wiki documentation is handled differently from regular project files. In GitHub every forked project has its own wiki, and it looks like it is a separate git repository, for example https://github.com/DualSPHysics/DualSPHysics.wiki.git against https://github.com/DualSPHysics/DualSPHysics.git I can then create a wiki in my fork and for it only, which is indeed what I see happening with DualSPHysics own repository.
I am missing a way to pull local changes into the wiki git, considering that it is not tracked by the main project repository? Has anybody tried that out?
There is some 'magic' discussed in this Stack Overflow post at https://stackoverflow.com/q/10642928 . Which would be the preferred work around for DualSPHysics?
Otherwise the only solution remains that suggested above by @Alex
The link in the "ISSUES section of the repository" is https://github.com/DualSPHysics/DualSPHysics/issues If you open a new issue, having a GitHub account I presume, you get into a form like the image below, with wide possibility to document a contribution:
This seems to address the question asked at the top. I hope this will help users and developers contribute their insights to the description of DualSPHysics.
Comments
So only developers are now working on that...
However anything interesting you suggest can be included there.
Regards
@RCanelas and @whom-it-may-concern
Intriguing idea to collaborate with users and external developers effectively and efficiently.
However, I see that in GitHub the wiki documentation is handled differently from regular project files. In GitHub every forked project has its own wiki, and it looks like it is a separate git repository, for example https://github.com/DualSPHysics/DualSPHysics.wiki.git against https://github.com/DualSPHysics/DualSPHysics.git I can then create a wiki in my fork and for it only, which is indeed what I see happening with DualSPHysics own repository.
I am missing a way to pull local changes into the wiki git, considering that it is not tracked by the main project repository? Has anybody tried that out?
There is some 'magic' discussed in this Stack Overflow post at https://stackoverflow.com/q/10642928 . Which would be the preferred work around for DualSPHysics?
Otherwise the only solution remains that suggested above by @Alex
At the end of the wiki page itself, outside the index, at https://github.com/DualSPHysics/DualSPHysics/wiki#suggestions-and-errors-in-the-wiki, I found this
The link in the "ISSUES section of the repository" is https://github.com/DualSPHysics/DualSPHysics/issues If you open a new issue, having a GitHub account I presume, you get into a form like the image below, with wide possibility to document a contribution:
The 'contributing guidelines' linked to at the bottom of the form are at https://github.com/DualSPHysics/DualSPHysics/blob/master/CONTRIBUTING.md
This seems to address the question asked at the top. I hope this will help users and developers contribute their insights to the description of DualSPHysics.