[GRASS-dev] Should we use GitHub Discussions?

[Vaclav Petras]

Dear all,

What about enabling GitHub Discussions [1] on grass repo? Enabling is easy
[2], so the question really is, do we want them? They are for open ended
discussions, questions, etc. Right, like mailing list, but on GitHub. We do
get asked periodically for a web-based (as opposed to email-based) forum
which is what GitHub Discussions can fulfill. I'm not saying we should
abandon the mailing list, but GitHub Discussions may be easier for some
users, so it would open another avenue for people to ask or get engaged on
a platform we are already using anyway.

Best,
Vaclav

[1] https://docs.github.com/en/discussions
[2] https://docs.github.com/en/discussions/quickstart
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] PSC Election: Statement Stefan Blumentrath

[Stefan Blumentrath]

Dear GRASS GIS Community,

I am honored to be nominated for the GRASS GIS PSC.

Some of you may have read my name asking or answering questions on the user and 
developer mailing list. Fewer of you may have met me, e.g. at Community sprints 
in Bonn or video calls.
For those of you who do not know me: I learned GRASS GIS during my studies at 
the University of Hanover around 2000 (with GRASS 5.4). Being an environmental 
planner by education, I consider myself mostly as a "power user" with some 
"learning-by-doing" skills in Python. My focus has been on using GRASS GIS in 
applied ecology and my first contributions to GRASS GIS have been in form of 
AddOns[1] (r.connectivity, r.maxent.lambdas, v.rast.bufferstats, 
v.strds.timestamp). In 2018 I became a member for the core development team. I 
mostly contribute[2] to the Python code base or by discussing aspects of the 
development on the mailing list, github, or (virtual) meetings.

I use GRASS mainly on Linux for a broad range of analysis relevant in 
environmental research and advocate actively for the use of Open Source 
technology in that domain. In my work GRASS is often used in combination with 
other OSGeo tools, like PostGIS, QGIS, GDAL. So, as a PCS member - if elected - 
I will focus on the interoperability of GRASS GIS.

That said, I benefited a lot from my interactions with the great GRASS GIS 
community, so frankly being elected or not will most likely not have a major 
effect on my participation in the project one way or another. However, I would 
view it as an opportunity to "give back" though, by getting involved in the 
more administrative aspects of the project.

Finally, I also like to add that I have been very happy with the current PSC, 
and want to thank them for their work. Looking at the list of nominations I can 
already say that I will be happy with the next PSC too, whoever of the nominees 
gets elected. I am looking forward to future collaboration with the community 
in whatever formal role.

Cheers,
Stefan

1: Commits * OSGeo/grass-addons 
(github.com)
2: Commits * OSGeo/grass 
(github.com)
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Statement Martin Landa

[Martin Landa]

Dear GRASS community,

first of all I would like to thank Vero for nominating me for the next PSC term!

My GRASS story started around 2002 when I was studying at the
university. Later in the year 2005 when I started studying for my PhD
I used GRASS in my GIS and remote sensing lessons. It was fun, I
taught students how to zoom and pan in a map window by GRASS command
line tools like d.pan and d.zoom. It was an adventure:-)

In 2007 and 2008 I had a chance to work together with Markus Neteler
in Fondazione Bruno Kessler (thanks Markus for introducing me to the
GRASS community, it was a great time in Trento!). I started developing
a new generation of GRASS GUI which is called wxGUI. I became a core
wxGUI developer for several years. When I returned to my university in
Prague I continued in my GRASS mission. Plenty of students of mine
contributed to GRASS development under my supervision. Let me name
some of them - Anna Petrasova, Vaclav Petras, Stepan Turek, Matej
Krejci, Tereza Fiedlerova, Ondrej Pesek, Linda Kladivova and others. I
hope it was fun for them, at least the same as for me.

I also helped to migrate GRASS source code from CVS to Subversion in
2008 and recently to Git (GitHub). I became a core GRASS depeloper, I
contributed eg. to the vector library by adding support for PostGIS
Topology. I am also maintaining UbuntuGIS PPA and WinGRASS packages. I
was also several times involved in Google Summer of Code, I started as
a student (oh, it's so long time ago:-) and later became a mentor or
co-mentor.

It was always fun to meet my GRASS friends on code/community sprints,
oh, so nice social events! Such nice memories make me happier in these
days of social distance.

Unfortunately last year I didn't have so much time for contributing to
GRASS. It doesn't mean that I forgot about you - a great GRASS
community. GRASS still stays in my heart. There are nowadays many much
more active people than me who were nominated to PSC. It's a good sign
of a stable and mature GRASS community!

Martin

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS Elections 2020] Last call to update names and e-mail addresses in the voter's registry

[Chief Return Officer (CRO) - GRASS GIS election 2020]

Dear members of the GRASS GIS community,

The voting for the new PSC will begin on Monday 2021-01-18 at 12:00 UTC 
and will contiue until Monday 2021-01-25 at 12:00 UTC.


This is the last call for everyone to check that their names and email 
addresses are given, updated and correctly spelled in the lists below.


I will load these lists tomorrow evening (Central European Time). At 
latest on Monday 2021-01-18 before 12:00 UTC the registered voters will 
receive a token that will enable them to use the voting system.



Lists being considered:

https://github.com/OSGeo/grass/blob/master/contributors.csv

https://github.com/OSGeo/grass/blob/master/contributors_extra.csv

https://github.com/OSGeo/grass/blob/master/translators.csv

https://github.com/OSGeo/grass-addons/blob/master/contributors.csv

https://github.com/OSGeo/grass/graphs/contributors

https://github.com/OSGeo/grass-addons/graphs/contributors


Regards,

Hernán

Chief Return Officer (CRO)




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

Re: [GRASS-dev] minor tweak to new website

[Michael Barton]

Thanks
_
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 16, 2021, at 10:18 AM, Veronica Andreo 
mailto:veroand...@gmail.com>> wrote:

Hi everyone,

I just created a PR with the proposed changes:

https://github.com/OSGeo/grass-website/pull/244

best,
Vero

El sáb., 16 ene. 2021 02:34, Zoltan 
mailto:zolt...@geograph.co.za>> escribió:
Agreed, 'preview' is better.
Regards,
Zoltan

Sent from 
BlueMail
On 16 Jan 2021, at 02:17, Markus Neteler 
mailto:nete...@osgeo.org>> wrote:

On Fri, Jan 15, 2021 at 10:12 PM Michael Barton 
mailto:michael.bar...@asu.edu>> wrote:

 You are correct about the redundancy. I was trying to make the change as minor 
as possible. A somewhat better listing would be

 GRASS GIS 7.8.5 (current stable)

 GRASS GIS 7.6.1 (legacy) [change from “old”]

 GRASS GIS 7.9 (preview) [“development” is OK, but “preview” sounds more 
inviting for use]

I like the new wording.

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] minor tweak to new website

[Veronica Andreo]

Hi everyone,

I just created a PR with the proposed changes:

https://github.com/OSGeo/grass-website/pull/244

best,
Vero

El sáb., 16 ene. 2021 02:34, Zoltan  escribió:

> Agreed, 'preview' is better.
> Regards,
> Zoltan
>
> Sent from BlueMail 
> On 16 Jan 2021, at 02:17, Markus Neteler  wrote:
>>
>> On Fri, Jan 15, 2021 at 10:12 PM Michael Barton  
>> wrote:
>>
>>>
>>>  You are correct about the redundancy. I was trying to make the change as 
>>> minor as possible. A somewhat better listing would be
>>>
>>>  GRASS GIS 7.8.5 (current stable)
>>>
>>>  GRASS GIS 7.6.1 (legacy) [change from “old”]
>>>
>>>  GRASS GIS 7.9 (preview) [“development” is OK, but “preview” sounds more 
>>> inviting for use]
>>>
>>
>> I like the new wording.
>>
>> 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