date:20210120

Re: [GRASS-dev] Should we use GitHub Discussions?

2021-01-20 Thread massimo di stefano

‘’’
 I think emails (and mailing lists) are awesome, but mailing lists are
increasingly seen as archaic and not accessible
‘’’

What about migrating our mailing list to mailman3?
The postorius interface looks modern and when integrated with hyper kitty,
allows an easy access to the list archives (including search and post
statistics).


My 2cents.


Il giorno gio 21 gen 2021 alle 4:32 AM Vaclav Petras 
ha scritto:

> Let me finally write some arguments for GitHub Discussions.
>
> First of all, I think it is a tradeoff, so I agree that the issues here
> are valid, at least to a point. My question now is if it is worth enabling
> GitHub Discussions anyway.
>
> As I mentioned earlier, people are asking for a web-based solution (see
> e.g. post from November on grass-user [1]). I think emails (and mailing
> lists) are awesome, but mailing lists are increasingly seen as archaic and
> not accessible. Nabble does not seem to cut it and it was even demoted on
> the mailing list for its link instability (which I think is a concern). It
> seems that if the Nabble situation would be fixable, it would be fixed
> already. Signup to receive all emails for a specific mailing list before
> posting a question is a big commitment, especially when people are using
> multiple software packages or are just trying out GRASS GIS. Is it clear to
> everybody they need to sign up before posting anyway? When you are already
> committed to GRASS GIS, they might not show stoppers, but when you are not,
> they certainly can be. Conclusion: If we want even the uncommitted users to
> ask questions, we need something which feels light, you already have an
> account there, and it does not require you to manage email filtering.
>
> There are already web-based forums, namely GIS StackExchange and
> StackOverflow proper where GRASS-related questions are being asked. This
> demonstrates the interest in the web-based Q platform, however when you
> look at the posts there, you see that it does not work that great. First,
> many of the original posts and consequently answers are actually not a good
> fit for that kind of platform - often a back and forth discussion is
> required. And perhaps more importantly, there are only a few GRASS power
> users answering there compared to mailing lists and comparing to how many
> people from the GRASS community have an account on GitHub. Conclusion: Even
> if we don't direct users to a platform and support that platform, people
> will use it anyway resulting in harm as questions are not properly answered.
>
> GitHub Discussions is a good web-based forum for three reasons, 1) GitHub
> is a platform we are already committed to, 2) devs, core+addon
> contributors, and bug-reporting users all have an account there, 3) a lot
> of potential users already have account there. The last point is especially
> interesting because not only that a lot of code-aware GIS users or
> scientists have an account there, but a lot of developers have an account
> there and we are very very interested in attracting developers.
> Developers/programmers need to combine multiple projects to create whatever
> they are creating. Asking them to subscribe to a mailing list in order to
> ask a question is exactly the reason why they will try their luck with
> another project. Conclusion: To attract more users, especially those who
> are developers, a GitHub-related service, such as GitHub Discussions, is
> needed and we are already on GitHub.
>
> As I mentioned in the initial post, I don't think enabling GitHub
> Discussions means closing mailing lists. I think it is important we have
> there is an option to ask a question, or even report a problem, without
> signing up for a proprietary third party service (it is bad enough we more
> or less require that for contributions). However, as there are people who
> see GitHub Terms and Conditions or a web interface as a barrier to post a
> question, there are people who see mailing list sign up for more inbox
> traffic, emailing, or attachment limitations as a barrier. The commitment
> needed for a mailing list, includes, perhaps surprisingly, an important
> group to reach that is the developers.
>
> Best,
> Vaclav
>
> [1] https://lists.osgeo.org/pipermail/grass-user/2020-November/081842.html
>
>
> On Mon, Jan 18, 2021 at 8:41 AM Markus Neteler  wrote:
>
>> On Sun, Jan 17, 2021 at 6:35 PM Brendan  wrote:
>> >
>> > Could posts on the mailing list automatically be posted on GitHub
>> Discussions and vice versa?  That's how the GRASS Nabble forums work right?
>> Those look great.
>>
>> If that would work, perhaps yes.
>>
>> Otherwise I'm with Moritz and the others who see the risk of
>> fragmentation etc.
>>
>> Markus
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
>

[GRASS-dev] Fwd: [Board] Fwd: Scheduling of the Joint OGC OSGeo ASF Virtual Code Sprint

2021-01-20 Thread Luca Delucchi

-- Forwarded message -
From: Angelos Tzotsos 
Date: Wed, 20 Jan 2021 at 14:40
Subject: [Board] Fwd: Scheduling of the Joint OGC OSGeo ASF Virtual Code
Sprint
To: OSGeo Board , ,
proje...@lists.osgeo.org , OSGeo Discussions <
disc...@lists.osgeo.org>

 Forwarded Message 
Subject: Re: Scheduling of the Joint OGC OSGeo ASF Virtual Code Sprint
Date: Wed, 20 Jan 2021 12:48:37 +
From: Gobe Hobona  
To: oapi-styles@lists.opengeospatial.org,
edr-api@lists.opengeospatial.org,
ogcapi-records@lists.opengeospatial.org, OGC API Maps SWG

, OGC WFS-FES SWG

,
ogcapi-common@lists.opengeospatial.org,
ogcapi-processes@lists.opengeospatial.org,
coverages@lists.opengeospatial.org,
ogcapi-tiles@lists.opengeospatial.org,
routing@lists.opengeospatial.org
CC: Martin Desruisseaux 
, Angelos Tzotsos 

All,

The Joint Virtual Code Sprint will be held on the 17th, 18th and 19th of
February 2021 starting from 07:00am EST until 05:30pm EST each day.

Please reserve the dates in your calendars.

The formal announcement is being prepared and will include a link to the
Registration page.

Regards,

Gobe

On 12 Jan 2021, at 13:21, Gobe Hobona  
wrote:

All,

The Apache Software Foundation (ASF), Open Geospatial Consortium (OGC), and
Open Source Geospatial Foundation (OSGeo) are currently planning a joint
Virtual Code Sprint to be held during the second half of February 2021.

The code sprint will cover multiple ASF and OSGeo projects, and OGC
standards. The code sprint is open to all participants in ASF, OSGeo and
OGC, even if you are not active members or contributors to the efforts of
the organizers.

To help us schedule the sprint, please enter your availability for the
sprint into the Doodle poll at https://doodle.com/poll/3ptyzi9vwfuak5bq

The Doodle poll will close on Tuesday 19th January 2021 at 17:00 EST.

Please feel free to forward this message to any colleagues that may be
interested.

Regards.

Gobe
__

Gobe Hobona, PhD MRICS
Director of Product Management, Standards | Open Geospatial Consortium (OGC)
Tel: +44 744 409 6781
ghob...@ogc.org   | ogc.org
  | @opengeospatial

-- 

 ___
Board mailing list
bo...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/board

-- 
ciao
Luca

www.lucadelu.org
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Should we use GitHub Discussions?

2021-01-20 Thread Vaclav Petras

Let me finally write some arguments for GitHub Discussions.

First of all, I think it is a tradeoff, so I agree that the issues here are
valid, at least to a point. My question now is if it is worth enabling
GitHub Discussions anyway.

As I mentioned earlier, people are asking for a web-based solution (see
e.g. post from November on grass-user [1]). I think emails (and mailing
lists) are awesome, but mailing lists are increasingly seen as archaic and
not accessible. Nabble does not seem to cut it and it was even demoted on
the mailing list for its link instability (which I think is a concern). It
seems that if the Nabble situation would be fixable, it would be fixed
already. Signup to receive all emails for a specific mailing list before
posting a question is a big commitment, especially when people are using
multiple software packages or are just trying out GRASS GIS. Is it clear to
everybody they need to sign up before posting anyway? When you are already
committed to GRASS GIS, they might not show stoppers, but when you are not,
they certainly can be. Conclusion: If we want even the uncommitted users to
ask questions, we need something which feels light, you already have an
account there, and it does not require you to manage email filtering.

There are already web-based forums, namely GIS StackExchange and
StackOverflow proper where GRASS-related questions are being asked. This
demonstrates the interest in the web-based Q platform, however when you
look at the posts there, you see that it does not work that great. First,
many of the original posts and consequently answers are actually not a good
fit for that kind of platform - often a back and forth discussion is
required. And perhaps more importantly, there are only a few GRASS power
users answering there compared to mailing lists and comparing to how many
people from the GRASS community have an account on GitHub. Conclusion: Even
if we don't direct users to a platform and support that platform, people
will use it anyway resulting in harm as questions are not properly answered.

GitHub Discussions is a good web-based forum for three reasons, 1) GitHub
is a platform we are already committed to, 2) devs, core+addon
contributors, and bug-reporting users all have an account there, 3) a lot
of potential users already have account there. The last point is especially
interesting because not only that a lot of code-aware GIS users or
scientists have an account there, but a lot of developers have an account
there and we are very very interested in attracting developers.
Developers/programmers need to combine multiple projects to create whatever
they are creating. Asking them to subscribe to a mailing list in order to
ask a question is exactly the reason why they will try their luck with
another project. Conclusion: To attract more users, especially those who
are developers, a GitHub-related service, such as GitHub Discussions, is
needed and we are already on GitHub.

As I mentioned in the initial post, I don't think enabling GitHub
Discussions means closing mailing lists. I think it is important we have
there is an option to ask a question, or even report a problem, without
signing up for a proprietary third party service (it is bad enough we more
or less require that for contributions). However, as there are people who
see GitHub Terms and Conditions or a web interface as a barrier to post a
question, there are people who see mailing list sign up for more inbox
traffic, emailing, or attachment limitations as a barrier. The commitment
needed for a mailing list, includes, perhaps surprisingly, an important
group to reach that is the developers.

Best,
Vaclav

[1] https://lists.osgeo.org/pipermail/grass-user/2020-November/081842.html

On Mon, Jan 18, 2021 at 8:41 AM Markus Neteler  wrote:

> On Sun, Jan 17, 2021 at 6:35 PM Brendan  wrote:
> >
> > Could posts on the mailing list automatically be posted on GitHub
> Discussions and vice versa?  That's how the GRASS Nabble forums work right?
> Those look great.
>
> If that would work, perhaps yes.
>
> Otherwise I'm with Moritz and the others who see the risk of fragmentation
> etc.
>
> Markus
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] 7.8.5 windows installer broken. How to find 7.8.4?

2021-01-20 Thread Helmut Kudrnovsky

>I think the issue I sent you earlier gives the most up-to-date info, so I
would subscribe to that issue to get >updates. I don't think we fully
understand the problem yet.

see https://github.com/OSGeo/grass/issues/1218#issuecomment-763959797

some more checks are needed about these files, mentioned in the comment, in
the standalone winGRASS installation path.



-
best regards
Helmut
--
Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3368: warnings and errors in compilation log

2021-01-20 Thread GRASS GIS

#3368: warnings and errors in compilation log
--+-
  Reporter:  hellik   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.4.5
 Component:  Compiling|Version:  svn-trunk
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  All
--+-

Comment (by nila):

 See !GitHub issue at https://github.com/OSGeo/grass/issues/1247 and
 related PRs.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #1910: GIS manager: allow dataset managing directly

2021-01-20 Thread GRASS GIS

#1910: GIS manager: allow dataset managing directly
--+---
  Reporter:  timmie   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:  7.6.2
 Component:  wxGUI|Version:  unspecified
Resolution:  fixed|   Keywords:  map management, layer manager
   CPU:  Unspecified  |   Platform:  Unspecified
--+---
Changes (by annakrat):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Closed, this can be all done now in data catalog.

-- 
Ticket URL: 
GRASS GIS 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] 7.8.5 windows installer broken. How to find 7.8.4?

2021-01-20 Thread Michael Barton

Thanks much. I will.

Michael Barton
School of Human Evolution  Change
School of Complex Adaptive System Science
Center for Social Dynamics & Complexity
Arizona State University

...Sent from my iPad

On Jan 20, 2021, at 7:16 AM, Anna Petrášová  wrote:




On Tue, Jan 19, 2021 at 3:48 PM Michael Barton 
mailto:michael.bar...@asu.edu>> wrote:
Could someone let me know if and when the windows installer for GRASS 7.8.5 has 
been fixed?

I think the issue I sent you earlier gives the most up-to-date info, so I would 
subscribe to that issue to get updates. I don't think we fully understand the 
problem yet.

Anna

Thanks
Michael

__
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: 
http://shesc.asu.edu,
https://complexity.asu.edu,
http://www.public.asu.edu/~cmbarton

From: Michael Barton mailto:michael.bar...@asu.edu>>
Date: Wednesday, January 13, 2021 at 6:57 AM
To: Anna Petrášová mailto:kratocha...@gmail.com>>
Cc: GRASS developers 
mailto:grass-dev@lists.osgeo.org>>
Subject: Re: [GRASS-dev] 7.8.5 windows installer broken. How to find 7.8.4?
Thanks much Anna
_
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: 
http://shesc.asu.edu,
 
https://complexity.asu.edu,
 
http://www.public.asu.edu/~cmbarton


On Jan 12, 2021, at 7:54 PM, Anna Petrášová 
mailto:kratocha...@gmail.com>> wrote:

Hi,

On Tue, Jan 12, 2021 at 7:13 PM Michael Barton 
mailto:michael.bar...@asu.edu>> wrote:
I just launched my spatial tech class today. Most people use Windows. I don't 
and and can't test it regularly, but haven't worried much about it because so 
many people do use it.

Nobody could get the standard Windows install to work for GRASS 7.8.5 today. It 
simply launched a console with a bunch of error messages apparently, for 
everyone. I'm getting someone to send a screenshot so I can file a report.

no need, here it is already:
https://github.com/OSGeo/grass/issues/1218

People were having trouble with 7.8.5 in OSGEO4W too. It did install but had 
problems running for some people.

In the meantime, is there someplace to get 7.8.4?

https://grass.osgeo.org/grass78/binary/mswindows/native/x86_64/

This is indeed a problem...



Thanks
Michael
_
C. Michael Barton
Director, Center for Social Dynamics & Complexity
Director, Network for Computational Modeling in Social & Ecological Sciences
Associate Director, School of Complex Adaptive Systems
Professor, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402
USA

voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: 
http://shesc.asu.edu,
 
https://complexity.asu.edu,

Re: [GRASS-dev] 7.8.5 windows installer broken. How to find 7.8.4?

2021-01-20 Thread Anna Petrášová

On Tue, Jan 19, 2021 at 3:48 PM Michael Barton 
wrote:

> Could someone let me know if and when the windows installer for GRASS
> 7.8.5 has been fixed?
>

I think the issue I sent you earlier gives the most up-to-date info, so I
would subscribe to that issue to get updates. I don't think we fully
understand the problem yet.

Anna

>
>
> Thanks
>
> Michael
>
>
>
> __
>
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Director, Network for Computational Modeling in Social & Ecological
> Sciences
> Associate Director, School of Complex Adaptive Systems
> Professor, School of Human Evolution & Social Change
> Arizona State University
> Tempe, AZ  85287-2402
> USA
>
> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
> www: http://shesc.asu.edu,
>
> https://complexity.asu.edu,
>
> http://www.public.asu.edu/~cmbarton
>
>
>
> *From: *Michael Barton 
> *Date: *Wednesday, January 13, 2021 at 6:57 AM
> *To: *Anna Petrášová 
> *Cc: *GRASS developers 
> *Subject: *Re: [GRASS-dev] 7.8.5 windows installer broken. How to find
> 7.8.4?
>
> Thanks much Anna
>
> _
>
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Director, Network for Computational Modeling in Social & Ecological
> Sciences
> Associate Director, School of Complex Adaptive Systems
> Professor, School of Human Evolution & Social Change
> Arizona State University
> Tempe, AZ  85287-2402
> USA
>
> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
> www: http://shesc.asu.edu, https://complexity.asu.edu,
> http://www.public.asu.edu/~cmbarton
>
>
>
> On Jan 12, 2021, at 7:54 PM, Anna Petrášová  wrote:
>
>
>
> Hi,
>
>
>
> On Tue, Jan 12, 2021 at 7:13 PM Michael Barton 
> wrote:
>
> I just launched my spatial tech class today. Most people use Windows. I
> don't and and can't test it regularly, but haven't worried much about it
> because so many people do use it.
>
>
>
> Nobody could get the standard Windows install to work for GRASS 7.8.5
> today. It simply launched a console with a bunch of error messages
> apparently, for everyone. I'm getting someone to send a screenshot so I can
> file a report.
>
>
>
> no need, here it is already:
>
> https://github.com/OSGeo/grass/issues/1218
> 
>
>
>
>
> People were having trouble with 7.8.5 in OSGEO4W too. It did install but
> had problems running for some people.
>
>
>
> In the meantime, is there someplace to get 7.8.4?
>
>
>
> https://grass.osgeo.org/grass78/binary/mswindows/native/x86_64/
> 
>
>
>
> This is indeed a problem...
>
>
>
>
>
>
>
> Thanks
>
> Michael
>
> _
>
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Director, Network for Computational Modeling in Social & Ecological
> Sciences
> Associate Director, School of Complex Adaptive Systems
> Professor, School of Human Evolution & Social Change
> Arizona State University
> Tempe, AZ  85287-2402
> USA
>
> voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
> www: http://shesc.asu.edu
> 
> , https://complexity.asu.edu
> 
> , http://www.public.asu.edu/~cmbarton
> 
>
>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
> 
>
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Should we use GitHub Discussions?

[GRASS-dev] Fwd: [Board] Fwd: Scheduling of the Joint OGC OSGeo ASF Virtual Code Sprint

Re: [GRASS-dev] Should we use GitHub Discussions?

Re: [GRASS-dev] 7.8.5 windows installer broken. How to find 7.8.4?

Re: [GRASS-dev] [GRASS GIS] #3368: warnings and errors in compilation log

Re: [GRASS-dev] [GRASS GIS] #1910: GIS manager: allow dataset managing directly

Re: [GRASS-dev] 7.8.5 windows installer broken. How to find 7.8.4?

Re: [GRASS-dev] 7.8.5 windows installer broken. How to find 7.8.4?

8 matches

Site Navigation

Mail list logo

Footer information