<html><head/><body><html><head></head><body>Thank you Victor, Otto, Paolo and others for explaining the situation. Makes sense to me what you propose.<br>
<br>
Andreas<br><br><div class="gmail_quote"><br>
<br>
Otto Dassau <dassau@gbd-consult.de> schrieb:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px">Hi,<br /><br />I agree with Victors suggestion and his experience with the SAGA community.<br />I think their community is just too small to handle this, so we should start<br />our own project and tell them, that they are welcome to contribute. And it is<br />great to see, that we already have some people to work on it - thanks a lot<br />for your offers!<br /><br />I remember we also talked a while ago how to integrate SEXTANTE docs into<br />the qgis manual apart from the help tab within the modules. Here I would<br />also support the idea of having something extra, not directly part of the<br />manual. <br /><br />My idea for the SAGA module docs is:<br /><br />* it should be part of the documentation repository under <br /><a href="https://github.com/qgis/QGIS-Documentation/tree/master/source/docs">https://github.com/qgis/QGIS-Documentation/tree/master/source/docs</a><br />
<br />*
it should be written in RST with the same styles as the manual, so we<br />can integrate it in the build/update/translation/... processes, like all<br />other manuals<br /><a href="https://github.com/qgis/QGIS-Documentation/tree/master/source/docs/documentation_guidelines">https://github.com/qgis/QGIS-Documentation/tree/master/source/docs/documentation_guidelines</a> <br /><br />* speaking for the manual I would still like to have kind of an<br />introduction about SEXTANTE (we already have this) and then link to the<br />extra SAGA manual. As we did/do it for the INSTALL.rst in the qgis<br />sources, we could have this introduction as part the extra SAGA manual and<br />just integrate it into the main qgis manual as a chapter. This should be<br />no problem within the docs repo.<br /><br />* as a note for help pages from other applications, such as GRASS or GDAL,<br />we should just link to their web pages and integrate it in the SEXTANTE<br />help tabs as it is already don
e, I
think. It doesn't make sense to spend<br />more effort on this at this point. <br />They are usually not translated but very well maintained, e.g for <br />* GRASS -> <a href="http://grass.osgeo.org/grass64/manuals/index.html">http://grass.osgeo.org/grass64/manuals/index.html</a><br />* GDAL -> <a href="http://www.gdal.org/gdal_utilities.html">http://www.gdal.org/gdal_utilities.html</a><br /><br />So, I would love to see that we keep this interaction between the qgis<br />manuals and the SEXTANTE module help in mind. So we are free to mix our<br />docs as needed and people find a consistent (infra)structure, if they want<br />to contribute.<br /><br />Thanks <br />Otto<br /><br />Am Thu, 11 Jul 2013 09:51:39 +0200<br />schrieb Victor Olaya <volayaf@gmail.com>:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">Samuel<br /><br />Thanks for you contribution. However, those docs are generat
ed<br
/>directly from the source code and do not have much information. Of<br />course, they can be extended, but that means that the source code has<br />to be modified in SAGA....which makes it impossible for people who do<br />not know C++ to contirbute to the code, plus it would be the SAGA<br />people who would handle contributions. Considering that they are not<br />very active even in their own community and that they do not use<br />github but a svn repo (that is, no pull request that are made<br />easily...but patches...), I see that as a huge barrier.<br /><br />I prefer to have something external, RST-based, easy for everyone to<br />modify, and focused on how those algorithms should be used from<br />SEXTANTE. Let's be a little selfish on that. If we eventually have<br />good docs, I am sure the SAGA people will find the way of reusing our<br />docs and incorporate them in their structure. Then we can start<br />thinking about just taking them from upstream and coordina
te
with<br />them. Until that happens, let's keep things on our side to make it<br />easier.<br /><br />Thanks everyone for you help- I plan to write some instructions about<br />how to collaborate and maybe a list of algorithms that are more<br />priority than others<br /><br />I will keep you posted<br /><br />Thanks<br />Victor<br /><br /><br /><br />2013/7/11 Paolo Cavallini <cavallini@faunalia.it>:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">-----BEGIN PGP SIGNED MESSAGE-----<br />Hash: SHA1<br /><br />Il 11/07/2013 02:52, samuelmesa@gmail.com ha scritto:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">I managedthroughasmallPythonscriptto getsomethehtml<br />helpofSAGAinthesextantsyntax:<br /><br />Script [1]: <a href="http://paste.ubuntu.com/5863377">http://paste.ubuntu.com/5863377</a>/<br />Sextant html file [2]: <
a
href="http://goo.gl/Sr12A">http://goo.gl/Sr12A</a><br /><br />But there are some html files with errors due to special characters<br />such as "/, (,)" in command names.<br /><br />To test this help should only copy the folder in the path:<br /><br />/usr/share/qgis/python/plugins/sextant/saga/<br /><br />I hope this can be a small solution for the moment.</blockquote><br />Great, thanks a lot. This opens back the issue:<br />* should we write our own docs, or<br />* contribute back upstream (adding only docs for the things changed in<br />sextante, as Victor outlined)?<br />In the second case, how could we write the docs and send them?<br />All the best.<br />- --<br />Paolo Cavallini - Faunalia<br /><a href="http://www.faunalia.eu">www.faunalia.eu</a><br />Full contact details at <a href="http://www.faunalia.eu/pc">www.faunalia.eu/pc</a><br />Nuovi corsi QGIS e PostGIS: <a href="http://www.faunalia.it/calendario">http://www.faunalia.it/calendario</a><br />-----BEGIN PGP
SIGNATURE-----<br />Version: GnuPG v1.4.12 (GNU/Linux)<br />Comment: Using GnuPG with Icedove - <a href="http://www.enigmail.net">http://www.enigmail.net</a>/<br /><br />iEYEARECAAYFAlHeYacACgkQ/NedwLUzIr4k8wCfXHoqDfwB/0YEmO8fbQayAtpz<br />DtMAnjYCmxwx+2FPqyQTfGcqPw3Uxv0u<br />=fq89<br />-----END PGP SIGNATURE-----<br /><hr /><br />Qgis-community-team mailing list<br />Qgis-community-team@lists.osgeo.org<br /><a href="http://lists.osgeo.org/mailman/listinfo/qgis-community-team">http://lists.osgeo.org/mailman/listinfo/qgis-community-team</a><br /></blockquote><hr /><br />Qgis-community-team mailing list<br />Qgis-community-team@lists.osgeo.org<br /><a href="http://lists.osgeo.org/mailman/listinfo/qgis-community-team">http://lists.osgeo.org/mailman/listinfo/qgis-community-team</a></blockquote><br /></pre></blockquote></div><br>
-- <br>
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.</body></html></body></html>