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

[Markus Metz]

Paolo,

you have not hurt anyone, you were annoying and arrogant, a behaviour
that is virtually absent from this mailing list, and I for my part do
not want to tolerate it. Anyway, continuing the thread this way is
fruitless.

This thread is about the QGIS SEXTANTE plugin. From a QGIS
perspective, it is just that, a plugin for QGIS with backends to a
number of analytical tools. From a GRASS perspective, this is a python
version of SEXTANTE with one binding (QGIS) and including a backend to
GRASS. I would like to see evolve python SEXTANTE into a more generic
python SEXTANTE where it is easy to add more bindings, as in java
SEXTANTE. I would also like to help improve the GRASS backend. In
order to achieve this, I try to get into contact with people who are
actually doing something on python SEXTANTE, i.e. the developers.

Ciao,

Markus


On Tue, May 29, 2012 at 11:31 AM, Paolo Cavallini <cavallini at faunalia.it> wrote:
> Il 28/05/2012 21:17, Markus Metz ha scritto:
>
>> 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.
>
> I'm more than happy to apologize if I have hurt the sensibility of anybody.
> However, I think there is some misunderstanding, let's try to clarify:
>
> -SEXTANTE has two versions now (which are like 2 different projects)
> -The QGIS version is still unstable, but is a much better software
> (cleaner design, different things, etc)
> -It would be great to coordinate both versions, but it has to be done
> manually. currently, Victor Olaya is putting time on the QGIS version and not in
> the gvSIG one, so they might get uncoordinated, which Victor do not see as
> a terrible problem, anyway.
> -SEXTANTE for gvSIG has more algorithms and is more prepared for that,
> while SEXTANTE for QGIS has more backends, and is better suited for
> it.
>
>> [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
>
> From the link I provided, you can easily find the source code at:
> http://plugins.qgis.org/plugins/sextante/
> so it should be, according to Victor choice:
> http://sextante.googlecode.com/svn/trunk/
>
>> [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]
>
> I really do not understand this (see above). What is Python SEXTANTE?
> Anyway, sending a link and "appropriating" code seems different acts.
>
>> [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]
>
> Bugs concerning the SEXTANTE QGIS Python plugin should be sent to:
> http://hub.qgis.org/projects/sextante/issues
> I do not see how this is "appropriating" anything.
>
>> [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).
>
> As I explained in a previous mail, Victor Olaya is the person who can best correct
> anybody on this. I took the liberty of talking on his behalf just because we are in
> close contact, and he has not subscribed to this list.
>
>> [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]
>
> Yes, "us" means QGIS. We (QGIS) already decided to integrate SEXTANTE into QGIS
> master as soon as code freeze is over (we are now releasing QGIS 1.8), so the
> distinction is blurred.
>
>> [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]
>
> Where do you find a generic python SEXTANTE?
>
> Having said that, if this still hurts, I apologize once more:
> http://www.youtube.com/watch?v=m7mIy97_rlo
>
> All the best.
> --
> Paolo Cavallini - Faunalia
> www.faunalia.eu
> Full contact details at www.faunalia.eu/pc