[GRASS-dev] collecting grass (future) concepts

GRASS GIS GRASS GIS developer
1

Hi all,

from my personal point of view (as a relatively new/young GRASS
"power" user) I suggest to create a new GRASS mailing list (e.g.
grass-concepts, or grass-future, etc.), where developers and users
could discuss the new/modified GIS concepts for future version of
GRASS. E.g. idea concept like object-orientated and layer-orientated
data approach, full 2D-2.5D-3D-4D GIS implementation, and in the
future more technical issues (working on the new core libraries, core
programming language issue, etc.).

I hope that this mailing list (and of course GRASS-Wiki) might help to
collect and crystallize ideas about GRASS future. In any case GRASS
should build on the current versions and continue in "GRASS way of
thinking".

Would do you think?

Best regards, Martin

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

2

Martin Landa wrote:

Hi all,

from my personal point of view (as a relatively new/young GRASS
"power" user) I suggest to create a new GRASS mailing list (e.g.
grass-concepts, or grass-future, etc.), where developers and users
could discuss the new/modified GIS concepts for future version of
GRASS. E.g. idea concept like object-orientated and layer-orientated
data approach, full 2D-2.5D-3D-4D GIS implementation, and in the
future more technical issues (working on the new core libraries, core
programming language issue, etc.).

I hope that this mailing list (and of course GRASS-Wiki) might help to
collect and crystallize ideas about GRASS future. In any case GRASS
should build on the current versions and continue in "GRASS way of
thinking".

Would do you think?

Any special reason why we can't just have these discussions on the dev-list ? This has worked very well up to now, in my opinion.

Personally, I would prefer limiting the amount of mailing lists I listen to...

Moritz

3

Martin this is the list to discuss grass-concepts etc.
It is our experience that specialized mailing lists die
or don't get the participation they need to be useful.
That is why e.g. the GUI discussion was kept here
and sure enough it was useful to get everybody involved.
There is also wiki for grass future ideas and IRC chat can be used too.

Helena

On Oct 31, 2006, at 6:14 AM, Martin Landa wrote:

Hi all,

from my personal point of view (as a relatively new/young GRASS
"power" user) I suggest to create a new GRASS mailing list (e.g.
grass-concepts, or grass-future, etc.), where developers and users
could discuss the new/modified GIS concepts for future version of
GRASS. E.g. idea concept like object-orientated and layer-orientated
data approach, full 2D-2.5D-3D-4D GIS implementation, and in the
future more technical issues (working on the new core libraries, core
programming language issue, etc.).

I hope that this mailing list (and of course GRASS-Wiki) might help to
collect and crystallize ideas about GRASS future. In any case GRASS
should build on the current versions and continue in "GRASS way of
thinking".

Would do you think?

Best regards, Martin

-- Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

4

Martin,

This would be useful. There is already a GRASS-GUI list if you want to use
that.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

From: Martin Landa <landa.martin@gmail.com>
Date: Tue, 31 Oct 2006 12:14:57 +0100
To: grass-dev <grass-dev@grass.itc.it>
Subject: [GRASS-dev] collecting grass (future) concepts

Hi all,

from my personal point of view (as a relatively new/young GRASS
"power" user) I suggest to create a new GRASS mailing list (e.g.
grass-concepts, or grass-future, etc.), where developers and users
could discuss the new/modified GIS concepts for future version of
GRASS. E.g. idea concept like object-orientated and layer-orientated
data approach, full 2D-2.5D-3D-4D GIS implementation, and in the
future more technical issues (working on the new core libraries, core
programming language issue, etc.).

I hope that this mailing list (and of course GRASS-Wiki) might help to
collect and crystallize ideas about GRASS future. In any case GRASS
should build on the current versions and continue in "GRASS way of
thinking".

Would do you think?

Best regards, Martin

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

5

Helena Mitasova wrote:

Martin this is the list to discuss grass-concepts etc.
It is our experience that specialized mailing lists die
or don't get the participation they need to be useful.
That is why e.g. the GUI discussion was kept here
and sure enough it was useful to get everybody involved.

I agree with Helena.

Maciek

6

Hi,

please let's keep the discussion here on grass-dev.
We have already too many mailing lists to follow.

Markus

On Tue, Oct 31, 2006 at 07:53:42AM -0700, Michael Barton wrote:

Martin,

This would be useful. There is already a GRASS-GUI list if you want to use
that.

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton

> From: Martin Landa <landa.martin@gmail.com>
> Date: Tue, 31 Oct 2006 12:14:57 +0100
> To: grass-dev <grass-dev@grass.itc.it>
> Subject: [GRASS-dev] collecting grass (future) concepts
>
> Hi all,
>
> from my personal point of view (as a relatively new/young GRASS
> "power" user) I suggest to create a new GRASS mailing list (e.g.
> grass-concepts, or grass-future, etc.), where developers and users
> could discuss the new/modified GIS concepts for future version of
> GRASS. E.g. idea concept like object-orientated and layer-orientated
> data approach, full 2D-2.5D-3D-4D GIS implementation, and in the
> future more technical issues (working on the new core libraries, core
> programming language issue, etc.).
>
> I hope that this mailing list (and of course GRASS-Wiki) might help to
> collect and crystallize ideas about GRASS future. In any case GRASS
> should build on the current versions and continue in "GRASS way of
> thinking".
>
> Would do you think?
>
> Best regards, Martin
>
> --
> Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *
>
>

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

--
Markus Neteler <neteler itc it> http://mpa.itc.it/markus/
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy

7

Martin:

> from my personal point of view (as a relatively new/young GRASS
> "power" user) I suggest to create a new GRASS mailing list (e.g.
> grass-concepts, or grass-future, etc.), where developers and users
> could discuss the new/modified GIS concepts for future version of
> GRASS. E.g. idea concept like object-orientated and layer-orientated
> data approach, full 2D-2.5D-3D-4D GIS implementation, and in the
> future more technical issues (working on the new core libraries,
> core programming language issue, etc.).
>
> I hope that this mailing list (and of course GRASS-Wiki) might help
> to collect and crystallize ideas about GRASS future.

Helena wrote:

There is also wiki for grass future ideas and IRC chat can be used
too.

futute development wiki page:
  http://grass.gdf-hannover.de/wiki/Development#Plans

Hamish

8

Hi all,

sorry for the late response.

First of all, thanks for your opinions.

The main reason why I suggested to create a new specialized mailing
list -- it is very difficult to find topic-orientated (e.g. concepts,
etc.) messages in grass-dev. On the other hand the better medium for
collecting ideas is the wiki.

BTW, there is lot of GRASS mailing list with (very) low traffic. Maybe
we should open discussion to decrease this number. Just idea;-)

Cheers, Martin

2006/10/31, Markus Neteler <neteler@itc.it>:

Hi,

please let's keep the discussion here on grass-dev.
We have already too many mailing lists to follow.

Markus

On Tue, Oct 31, 2006 at 07:53:42AM -0700, Michael Barton wrote:
> Martin,
>
> This would be useful. There is already a GRASS-GUI list if you want to use
> that.
>
> Michael
> __________________________________________
> Michael Barton, Professor of Anthropology
> School of Human Evolution & Social Change
> Center for Social Dynamics & Complexity
> Arizona State University
>
> phone: 480-965-6213
> fax: 480-965-7671
> www: http://www.public.asu.edu/~cmbarton
>
> > From: Martin Landa <landa.martin@gmail.com>
> > Date: Tue, 31 Oct 2006 12:14:57 +0100
> > To: grass-dev <grass-dev@grass.itc.it>
> > Subject: [GRASS-dev] collecting grass (future) concepts
> >
> > Hi all,
> >
> > from my personal point of view (as a relatively new/young GRASS
> > "power" user) I suggest to create a new GRASS mailing list (e.g.
> > grass-concepts, or grass-future, etc.), where developers and users
> > could discuss the new/modified GIS concepts for future version of
> > GRASS. E.g. idea concept like object-orientated and layer-orientated
> > data approach, full 2D-2.5D-3D-4D GIS implementation, and in the
> > future more technical issues (working on the new core libraries, core
> > programming language issue, etc.).
> >
> > I hope that this mailing list (and of course GRASS-Wiki) might help to
> > collect and crystallize ideas about GRASS future. In any case GRASS
> > should build on the current versions and continue in "GRASS way of
> > thinking".
> >
> > Would do you think?
> >
> > Best regards, Martin
> >
> > --
> > Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *
> >
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev

--
Markus Neteler <neteler itc it> http://mpa.itc.it/markus/
ITC-irst - Centro per la Ricerca Scientifica e Tecnologica
MPBA - Predictive Models for Biol. & Environ. Data Analysis
Via Sommarive, 18 - 38050 Povo (Trento), Italy

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

9

Hi,

here my candidates for merge/removal:

grassgui GRASSGUI mailing list
nvizlist List to discuss GRASS/NVIZ visualization tools
sqlgrass GRASS and SQL support

If you look at
http://grass.itc.it/pipermail/nvizlist/
http://grass.itc.it/pipermail/grassgui/
http://grass.itc.it/pipermail/sqlgrass/

you can see that they are basically unused. As a first attempt
we could simply remove them from
http://grass.itc.it/community/support.php
to not mislead people (who do not receive answers there).

Then I could close them for further subscription but leave
the archives alive.

Markus

On Mon, Nov 06, 2006 at 11:09:10AM +0100, Martin Landa wrote:

Hi all,

sorry for the late response.

First of all, thanks for your opinions.

The main reason why I suggested to create a new specialized mailing
list -- it is very difficult to find topic-orientated (e.g. concepts,
etc.) messages in grass-dev. On the other hand the better medium for
collecting ideas is the wiki.

BTW, there is lot of GRASS mailing list with (very) low traffic. Maybe
we should open discussion to decrease this number. Just idea;-)

Cheers, Martin

2006/10/31, Markus Neteler <neteler@itc.it>:
>Hi,
>
>please let's keep the discussion here on grass-dev.
>We have already too many mailing lists to follow.
>
>Markus

10

Markus Neteler wrote:

Hi,

here my candidates for merge/removal:

grassgui GRASSGUI mailing list
nvizlist List to discuss GRASS/NVIZ visualization tools
sqlgrass GRASS and SQL support

If you look at
http://grass.itc.it/pipermail/nvizlist/
http://grass.itc.it/pipermail/grassgui/
http://grass.itc.it/pipermail/sqlgrass/

you can see that they are basically unused. As a first attempt
we could simply remove them from
http://grass.itc.it/community/support.php
to not mislead people (who do not receive answers there).

Then I could close them for further subscription but leave
the archives alive.

+1

Moritz

Markus

On Mon, Nov 06, 2006 at 11:09:10AM +0100, Martin Landa wrote:

Hi all,

sorry for the late response.

First of all, thanks for your opinions.

The main reason why I suggested to create a new specialized mailing
list -- it is very difficult to find topic-orientated (e.g. concepts,
etc.) messages in grass-dev. On the other hand the better medium for
collecting ideas is the wiki.

BTW, there is lot of GRASS mailing list with (very) low traffic. Maybe
we should open discussion to decrease this number. Just idea;-)

Cheers, Martin

2006/10/31, Markus Neteler <neteler@itc.it>:

Hi,

please let's keep the discussion here on grass-dev.
We have already too many mailing lists to follow.

Markus

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

11

+2

2006/11/7, Moritz Lennert <mlennert@club.worldonline.be>:

Markus Neteler wrote:
> Hi,
>
> here my candidates for merge/removal:
>
> grassgui GRASSGUI mailing list
> nvizlist List to discuss GRASS/NVIZ visualization tools
> sqlgrass GRASS and SQL support
>
> If you look at
> http://grass.itc.it/pipermail/nvizlist/
> http://grass.itc.it/pipermail/grassgui/
> http://grass.itc.it/pipermail/sqlgrass/
>
> you can see that they are basically unused. As a first attempt
> we could simply remove them from
> http://grass.itc.it/community/support.php
> to not mislead people (who do not receive answers there).
>
> Then I could close them for further subscription but leave
> the archives alive.

+1

Moritz

>
> Markus
>
> On Mon, Nov 06, 2006 at 11:09:10AM +0100, Martin Landa wrote:
>> Hi all,
>>
>> sorry for the late response.
>>
>> First of all, thanks for your opinions.
>>
>> The main reason why I suggested to create a new specialized mailing
>> list -- it is very difficult to find topic-orientated (e.g. concepts,
>> etc.) messages in grass-dev. On the other hand the better medium for
>> collecting ideas is the wiki.
>>
>> BTW, there is lot of GRASS mailing list with (very) low traffic. Maybe
>> we should open discussion to decrease this number. Just idea;-)
>>
>> Cheers, Martin
>>
>> 2006/10/31, Markus Neteler <neteler@itc.it>:
>>> Hi,
>>>
>>> please let's keep the discussion here on grass-dev.
>>> We have already too many mailing lists to follow.
>>>
>>> Markus
>
> _______________________________________________
> grass-dev mailing list
> grass-dev@grass.itc.it
> http://grass.itc.it/mailman/listinfo/grass-dev

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

--
Martin Landa <landa.martin@gmail.com> * http://gama.fsv.cvut.cz/~landa *

12

[from GRASS-dev list discussion to reduce number of lists]

On Tue, Nov 07, 2006 at 04:36:42PM +1300, Hamish wrote:

Markus Neteler wrote:
>
> here my candidates for merge/removal:
>
> grassgui GRASSGUI mailing list
> nvizlist List to discuss GRASS/NVIZ visualization tools
> sqlgrass GRASS and SQL support
>
>
> If you look at
> http://grass.itc.it/pipermail/nvizlist/
> http://grass.itc.it/pipermail/grassgui/
> http://grass.itc.it/pipermail/sqlgrass/
>
> you can see that they are basically unused. As a first attempt
> we could simply remove them from
> http://grass.itc.it/community/support.php
> to not mislead people (who do not receive answers there).
>
> Then I could close them for further subscription but leave
> the archives alive.

this sounds like a good plan to me,

Hamish

Due to various positive feedbacks:

Done so. It is no longer possible to subscribe to above lists,
they have been removed from the Web site listing of mailing lists.
The archives are still accessible and searchable. I didn't
actively unsubscribe people but would just leave it as-is.

Markus

13

On Nov 6, 2006, at 3:06 PM, Markus Neteler wrote:

Hi,

here my candidates for merge/removal:

grassgui GRASSGUI mailing list
nvizlist List to discuss GRASS/NVIZ visualization tools
sqlgrass GRASS and SQL support

If you look at
http://grass.itc.it/pipermail/nvizlist/
http://grass.itc.it/pipermail/grassgui/
http://grass.itc.it/pipermail/sqlgrass/

you can see that they are basically unused. As a first attempt
we could simply remove them from
http://grass.itc.it/community/support.php
to not mislead people (who do not receive answers there).

Then I could close them for further subscription but leave
the archives alive.

yes, I think that is a good way how to close them, Helena

Markus

On Mon, Nov 06, 2006 at 11:09:10AM +0100, Martin Landa wrote:

Hi all,

sorry for the late response.

First of all, thanks for your opinions.

The main reason why I suggested to create a new specialized mailing
list -- it is very difficult to find topic-orientated (e.g. concepts,
etc.) messages in grass-dev. On the other hand the better medium for
collecting ideas is the wiki.

BTW, there is lot of GRASS mailing list with (very) low traffic. Maybe
we should open discussion to decrease this number. Just idea;-)

Cheers, Martin

2006/10/31, Markus Neteler <neteler@itc.it>:

Hi,

please let's keep the discussion here on grass-dev.
We have already too many mailing lists to follow.

Markus

_______________________________________________
grass-dev mailing list
grass-dev@grass.itc.it
http://grass.itc.it/mailman/listinfo/grass-dev

14

Markus Neteler wrote:

Hamish wrote

[from GRASS-dev list discussion to reduce number of lists]

Then I could close them for further subscription but leave
the archives alive.

this sounds like a good plan to me,

Due to various positive feedbacks:

Done so.

Good move.

Best,
Maciek