[GRASS-user] Report from ongoing GRASS GIS Community Sprint in Prague

[Markus Metz]

On Mon, May 28, 2012 at 6:02 PM, Paolo Cavallini <cavallini at faunalia.it> wrote:
> Il 28/05/2012 17:56, José Antonio Canalejo Alonso ha scritto:
>
>> we have put also a lot effort in SEXTANTE and in gvSIG/gvSIG CE. I like a lot these
>> projects and also QGIS and I think it's positiv to see both  (SEXTANTE-QGIS and
>> SEXTANTE-gvSIG CE) growing and sharing Knowledge.
>> The situation now is a bit confusing, but much better than 6 months ago:
>> http://sextantegis.blogspot.de/2011/11/kinda-goodbye.html
>
> Ola José.
> I do not think the situation is very confusing for SEXTANTE: the gvSIG plugin is
> stable, the QGIS one is under active development.

Now that the SEXTANTE plugin for QGIS has been demystified and
identified as a python version of SEXTANTE, this thread should IMHO be
moved to a more appropriate place like the SEXTANTE developers mailing
list [0]. QGIS is currently the testbed for the python version of
SEXTANTE, but I guess that there would be wider interest in a python
version, considering that python becomes ever more popular. As a GRASS
developer I want to offer my help to the SEXTANTE developers to get
the python SEXTANTE/GRASS interface in a usable shape. Currently it
seems to be intentionally broken because of the missing descriptions
and, more seriously, because some GRASS module settings were manually
changed from their defaults such that the SEXTANTE/GRASS interface
will not work for these modules. This applies only to python SEXTANTE,
not to java SEXTANTE. While on it (the blaming), I think it is time
for Paolo to apologize for his rude [1] comments [2][3][4][5][6][7]
earlier in the thread.

Markus M

[0] http://www.freelists.org/list/sextante-devel
[1] http://www.albion.com/netiquette/corerules.html
[2] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977385.html
the link is wrong, the original source code is at
http://code.google.com/p/sextante/source/browse/trunk/soft/bindings/qgis-plugin/src
[3] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977411.html
Paolo is appropriating python SEXTANTE as the QGIS Python plugin
called sextante. See [2]
[4] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977430.html
Paolo is again appropriating python SEXTANTE ("Please do nont send bug
reports concerning it to other bugtrackers.") as the QGIS Python
plugin called sextante. See [2]
[5] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977473.html
Paolo: "I can correct you :) " 1. Paolo was not addressed. 2. The
issue has been resolved, no need for any further "correction" 3. I,
not Paolo, gave an explanation and examples for the issue discussed
(there is a complete re-write of SEXTANTE in Python).
[6] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977489.html
Paolo: "... and join us". Paolo is not a developer of SEXTANTE, but
very active for QGIS. Therefore "us" does obviously not mean SEXTANTE
but QGIS. Paolo is again appropriating python SEXTANTE ("Please do
nont send bug reports concerning it to other bugtrackers.") as the
QGIS Python plugin called sextante. See [2]
[7] http://osgeo-org.1560.n6.nabble.com/Report-from-ongoing-GRASS-GIS-Community-Sprint-in-Prague-tp4977136p4977500.html
At this stage of the python version of SEXTANTE, the main objective
should be to get a stable version of python SEXTANTE. That is, a
generic python SEXTANTE, not just something that works for QGIS and
nothing else (with the SEXTANTE/GRASS interface not even working
properly, see main comment). Paolo is again appropriating python
SEXTANTE ("Please do nont send bug reports concerning it to other
bugtrackers.") as the QGIS Python plugin called sextante. See [2]