Re: [GRASS-dev] [GRASS-user] Mini project 2024: Third progress report

[Veronica Andreo via grass-dev]

Thanks for the report Linda!! And congratulations on the new family
member!! 殺

Greetings from the GRASS GIS family!
Vero

El lun, 22 abr 2024 a las 3:51, Linda Karlovská via grass-user (<
grass-u...@lists.osgeo.org>) escribió:

> Hello guys,
>
> I am sending my third progress report from working on the GRASS mini
> project called Easy command history navigation through the History browser
> panel. You can also access the detailed report here: [1].
>
> 1) What did I complete?
> I completed the PR [2] which enables storing more information about
> executed commands. Newly, commands are stored in JSON format and then
> displayed as the command info in the history pane. I also completed the
> relocation of the Export history button from the Console pane to the
> History pane (PR [3]).
>
> Besides that, I am working on [4] and [5]. The first PR creates a new
> button for setting the current region to the region used during the command
> execution. This PR is awaiting the final review. The second contribution
> adds time branching to the history browser tree and is currently waiting
> for the review.
>
> 2) What am I going to achieve for the next two weeks?
> I would like to merge both [4] and [5]. Subsequently, I plan to shift my
> focus toward visualization of command status. I plan to add icons in front
> of command nodes representing possible states (success, failed, in process,
> aborted). Regarding the status, it would also be nice to show the complete
> error text if a command fails. (Now there is “failed” written but no clue
> what happened).
>
> 3) Is there any blocking issue?
> No, it isn’t. I have just been much more busy the last two months since on
> the 19th of February, my two-member family expanded by one little guy, my
> son Vilem. So any work has gone kind of slowly over the last two months… 
>
> Have a nice week.
>
> Linda
>
> [1]
> https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/EasyCommandHistoryNavigation#Reportforweeks5and6
> [2] https://github.com/OSGeo/grass/pull/3365
> [3] https://github.com/OSGeo/grass/pull/3402
> [4] https://github.com/OSGeo/grass/pull/3421
> [5] https://github.com/OSGeo/grass/pull/3622
> ___
> grass-user mailing list
> grass-u...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>


-- 
Dra. Verónica Andreo
Investigadora Adjunta de CONICET
Instituto Gulich (CONAE - UNC)
Centro Espacial Teófilo Tabanera (CETT)
Falda del Cañete - Córdoba, Argentina
+54 3547 40 int. 1153
https://veroandreo.gitlab.io/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Proposal [Improve GRASS user experience in Jupyter Notebook]

[Veronica Andreo via grass-dev]

Hello Riya,

Welcome to GRASS GIS and thanks for sharing the proposal draft! I went
through it earlier this morning, and it looks really good :)
I'm looking forward to testing and using those planned new features!

Happy coding!
Vero

El mar, 26 mar 2024 a las 11:55, Riya Saxena via grass-dev (<
grass-dev@lists.osgeo.org>) escribió:

> Hello everyone,
>
> I am Riya, a pre-final year undergrad at the Department of Earth Sciences,
> IIT Roorkee. My interest in GIS stems from an Introduction to GIS course
> taught by Arun K. Saraf in my last semester.
>
> I started exploring GIS, which led me to GRASS GIS and ultimately to GSoC,
> which combined my interest in open-source and GIS. It is a perfect
> opportunity to spend my summers on (or even continue my M.Tech
> dissertation).
>
> Over the last few weeks, Anna guided me in writing my draft proposal.
> Please find it linked here: GSoC Draft
> . I would love to receive
> reviews from the dev community on my proposal.
>
> Looking forward to receiving your reviews.
>
> Regards,
> Riya
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>


-- 
Dra. Verónica Andreo
Investigadora Adjunta de CONICET
Instituto Gulich (CONAE - UNC)
Centro Espacial Teófilo Tabanera (CETT)
Falda del Cañete - Córdoba, Argentina
+54 3547 40 int. 1153
https://veroandreo.gitlab.io/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS GIS Community Meeting in Prague, June 14-19, 2024

[Veronica Andreo via grass-dev]

Dear all,

The GRASS GIS team announces its annual Community Meeting!!

Join us in Prague (June 14-19) to:
- Develop & Discuss: Code, docs, translations & integrations (QGIS, GDAL, R)
- Plan the future: Chart the project roadmap & tackle big challenges!
- Celebrate GRASS birthday & community achievements!

Get involved and support! We welcome in person and online participants!
You can sign up at:
https://grasswiki.osgeo.org/wiki/GRASS_Community_Meeting_Prague_2024

Sponsor us!
https://opencollective.com/grass/contribute

Shall you have any further questions, contact Vero Andreo at <
veroand...@gmail.com>

Looking forward to meeting you!
The GRASS GIS team
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS Teams on GitHub

[Veronica Andreo via grass-dev]

Hello guys,

Thanks for this discussion. I went through all of your explanations and
reasoning, and while I agree we have more repos and hence the need for more
groups, I do think the GDAL teams structure gives a much better image of
structure, unity and organization than our loose groups all over the place.
As Ondrej says perhaps not many people go and check the OSGeo teams, but I
think the image we show to the rest and to ourselves is still important,
and these little details do make a difference in my opinion.

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

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

[Veronica Andreo via grass-dev]

Markus, all,

Great! Thanks a lot!

Zenodo link works, but the doi link yields doi not found page... is it ok
for the resolver link to take a couple of days?

Vero

El mar, 20 feb 2024 a las 19:45, Markus Neteler via grass-dev (<
grass-dev@lists.osgeo.org>) escribió:

> Hi devs,
>
> On Thu, Feb 1, 2024 at 10:40 PM Markus Neteler  wrote:
> > We have accumulated a number of fixes in the past weeks.
> >
> > Here the milestone:
> > https://github.com/OSGeo/grass/milestone/24
>
> The RC1 release is now available, please test it:
> https://github.com/OSGeo/grass/releases/tag/8.3.2RC1
>
> The open issues/PR I have moved to a new 8.3.3 milestone. But let's
> focus on 8.4.0.
>
> And yay, the Zenodo bridge works again:
> Version 8.3.2RC1: https://zenodo.org/records/10685321
> DOI: https://doi.org/10.5281/zenodo.10685321 (resolver link will work
> in some hs from now)
>
> Hopefully no RC2 is needed.
>
> Thanks to all contributors,
> Markus
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - company
> https://grass.osgeo.org - FOSS
> https://neteler.org - freelancing & blog
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>


-- 
Dra. Verónica Andreo
Investigadora Adjunta de CONICET
Instituto Gulich (CONAE - UNC)
Centro Espacial Teófilo Tabanera (CETT)
Falda del Cañete - Córdoba, Argentina
+54 3547 40 int. 1153
https://veroandreo.gitlab.io/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Ideas

[Veronica Andreo via grass-dev]

Hi Maris,

Would you mind sharing more details on this idea? I'm afraid I was not able
to attend/hear the discussion about this welcome screen in Prague. I hope
though we do not end up with a new startup screen. It took so much time to
reach an agreement and finally remove it.

Vero

El jue, 15 feb 2024 a las 9:00, Maris Nartiss ()
escribió:

> Hello Anna, Vero.
> I added the welcome screen idea we discussed during our Prague
> meeting. I think it would be a good GSOC project as it is quite easy
> and at the same time will allow to understand if it is the way to go.
> Anna, would you be able to be a co-mentor as it is a GUI project? Or
> who else could be?
> Vero, your user-centric view also would be valuable.
> Please edit the wiki accordingly.
>
> Thanks,
> Māris.
>
> sestd., 2024. g. 3. febr., plkst. 06:34 — lietotājs Anna Petrášová via
> grass-dev () rakstīja:
> >
> > Hi,
> >
> > I created a GSoC Ideas 2024 page on grasswiki (as opposed to trac wiki,
> which I think we should be moving away from):
> > https://grasswiki.osgeo.org/wiki/GRASS_GSoC_Ideas_2024
> >
> > It's not updated yet, I plan to add more topics. If you want to mentor a
> topic, we can discuss it here.
> >
> > Anna
> > ___
> > grass-dev mailing list
> > grass-dev@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/grass-dev
>


-- 
Dra. Verónica Andreo
Investigadora Adjunta de CONICET
Instituto Gulich (CONAE - UNC)
Centro Espacial Teófilo Tabanera (CETT)
Falda del Cañete - Córdoba, Argentina
+54 3547 40 int. 1153
https://veroandreo.gitlab.io/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-user] GRASS-Wiki: new OSGeo-ID login method activated

[Veronica Andreo via grass-dev]

Thanks for taking care of this, Markus!

I just tested, all seems to be working.
Cheers,
Vero

El mar, 13 feb 2024 a las 15:09, Markus Neteler via grass-user (<
grass-u...@lists.osgeo.org>) escribió:

> Dear all,
>
> As of February 2024, we are happy to announce that the GRASS Wiki (
> https://grasswiki.osgeo.org/wiki/) is connected to the OSGeo
> authentication system!
> Many thanks to Regina Obe from OSGeo-SAC (
> https://wiki.osgeo.org/wiki/User:Robe).
>
> *What does it mean?*
>
> In order to keep spammers out of the system and to simplify the overall
> OSGeo login experience, the centralized OSGeo login method is also
> activated for the GRASS GIS Wiki.
> Please note that your current GRASS-Wiki username/password will no longer
> work here in favor of the OSGeo-ID already used elsewhere (OSGeo-Wiki etc.).
>
> *What do I need to log in?*
>
> As before, no login is required to read the wiki content.
>
> To edit the Wiki, you need to login with your OSGeo-ID (technically your
> OSGeo-LDAP account). If you do not have an OSGeo-ID yet, please register
> here: https://www.osgeo.org/community/getting-started-osgeo/osgeo_userid/
> .
>
> *What if I already have a GRASS-Wiki account?*
>
> The first time you log in to the GRASS-Wiki with your OSGeo-ID, your
> existing old user account will be merged with the OSGeo-ID. This should
> work automatically. If not, please contact me directly.
>
> Feel free to ask if you have any questions.
>
> Best regards,
> Markus
>
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - company
> https://grass.osgeo.org - FOSS
> https://neteler.org - freelancing & blog
> ___
> grass-user mailing list
> grass-u...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>


-- 
Dra. Verónica Andreo
Investigadora Adjunta de CONICET
Instituto Gulich (CONAE - UNC)
Centro Espacial Teófilo Tabanera (CETT)
Falda del Cañete - Córdoba, Argentina
+54 3547 40 int. 1153
https://veroandreo.gitlab.io/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC Ideas

[Veronica Andreo via grass-dev]

That would be cool Luca! eodag allows you to download different EO
datasets.

Do you think of a GSoC project idea to include eodag support for
i.sentinel.download, i.landsat.download and i.modis.download or as a new
module to download EO data in general? If you are willing to mentor, I can
be your second... mainly to test and make annoying questions :)

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

[GRASS-dev] Fwd: [OSGeo-Discuss] Developers are invited to the 2024 Joint OGC OSGeo ASF Code Sprint

[Veronica Andreo via grass-dev]

FYI :)

-- Forwarded message -
De: Tom Kralidis via Discuss 
Date: mié, 10 ene 2024 a las 13:10
Subject: [OSGeo-Discuss] Developers are invited to the 2024 Joint OGC OSGeo
ASF Code Sprint
To: OSGeo Discussions , 


Hi all: the 4th Joint OGC / OSGeo / ASF Code Sprint will be held
from 26-28 February 2024.  Full details on registration can be found at
[1] and [2].

As demonstrated in the past joint code sprints, this is a great
opportunity for cross-pollination of FOSS4G and standards in an agile/sprint
environment.

The OSGeo community is encouraged to sign up and participate!  Feel free
to add your project at [2].  Looking forward to seeing folks at this
upcoming sprint.

Thanks

..Tom

[1] https://www.osgeo.org/events/2024-joint-ogc-osgeo-asf-code-sprint/
[2] 
https://github.com/opengeospatial/developer-events/wiki/2024-Joint-OGC-%E2%80%93-OSGeo-%E2%80%93-ASF-Code-Sprint

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

Re: [GRASS-dev] Version DOI missing for GRASS 8.3.0

[Veronica Andreo via grass-dev]

Vashek, do you have access? Perhaps you can share credentials privately?

El mié, 25 oct 2023 a las 15:34, Markus Neteler via grass-dev (<
grass-dev@lists.osgeo.org>) escribió:

> Hi Peter, Vaclav, Vero,
>
> On Wed, Aug 16, 2023 at 3:34 PM Markus Neteler  wrote:
> >
> > Hi all,
> >
> > While I have indeed a script to auto-upload code/data to Zenodo.org
> > along with metadata stored in CITATION.cff, I don't remember who has
> > access to the GRASS GIS Zenodo account.
>
> This wondering... anyone?
>
> > This would be needed, otherwise it won't "join" the other releases
> > stored there under the meta DOI.
> >
> > Vaclav or Vero perhaps?
>
> Zenodo updates are still broken, see:
> https://zenodo.org/records/6612307
> and related.
>
> Markus
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - free data with free software
> https://grass.osgeo.org
> https://grassbook.org/neteler/
> ___
> 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] Send GRASS news to mailing list

[Veronica Andreo]

Hi Vashek,

Yes, it's a good idea to spread the news also via mailing lists

Vero

El vie., 1 sep. 2023 10:28, Markus Neteler  escribió:

> Hi Vaclav,
>
> Just a hint: the email limit can be lifted easily. Just post and I (or any
> other list admin) can approve it.
>
> Markus
>
>
> Vaclav Petras  schrieb am Fr., 1. Sep. 2023, 14:53:
>
>> Dear all,
>>
>> Having the very nice post about the meeting in Prague and others at the
>> GRASS website, I was thinking we should send this to the grass-user mailing
>> list too and maybe grass-dev.
>>
>> Given the mailing list emails have size limitations and may end up
>> potentially ASCII, I'm suggesting sending an email with a link to the new
>> item and the first paragraph of the news item to the grass-user mailing
>> list. So, the one for Prague, would look like this:
>>
>> 
>> Report of the GRASS GIS Community Meeting in Prague
>>
>> The GRASS GIS Community Meeting was held in the Czech Republic from June
>> 2 to 6 at the Faculty of Civil Engineering of the Czech Technical
>> University in Prague. The meeting was a milestone event to celebrate the
>> 40th birthday of GRASS GIS and brought together users, supporters,
>> contributors, power users and developers to celebrate, collaborate and
>> chart the future of GRASS GIS.
>>
>> Read more at:
>>
>>
>> https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/
>> """
>>
>> What do you think?
>>
>> Vaclav
>> ___
>> 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
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Invitation: Virtual toast for GRASS GIS 40th birthday

[Veronica Andreo]

Dear all,

Happy birthday GRASS GIS! 

Here's the link for *today's toast at 17:00 UTC*:
https://meet.jit.si/GRASSGIS-40th-bday-toast

Check local times:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023=7=29=17=0=0=485=207=37=25=204=197
.

See you there,
Vero

El mar, 25 jul 2023 a las 9:17, Veronica Andreo ()
escribió:

> Dear all,
>
> Our beloved GRASS GIS becomes 40 years old!
>
> Let's meet this *Saturday July 29th at 17:00 UTC* for a virtual toast and
> celebration 
>
> Some local times here:
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023=7=29=17=0=0=485=207=37=25=204=197
> .
>
> I'll share a link here shortly before the meeting.
>
> See you soon!
> Vero
> --
> Dra. Verónica Andreo
> Investigadora Asistente de CONICET
> Instituto Gulich (CONAE - UNC)
> Centro Espacial Teófilo Tabanera (CETT)
> Falda del Cañete - Córdoba, Argentina
> +54 3547 40 int. 1153
> https://veroandreo.gitlab.io/
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Invitation: Virtual toast for GRASS GIS 40th birthday

[Veronica Andreo]

Dear all,

Our beloved GRASS GIS becomes 40 years old!

Let's meet this *Saturday July 29th at 17:00 UTC* for a virtual toast and
celebration 

Some local times here:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2023=7=29=17=0=0=485=207=37=25=204=197
.

I'll share a link here shortly before the meeting.

See you soon!
Vero
-- 
Dra. Verónica Andreo
Investigadora Asistente de CONICET
Instituto Gulich (CONAE - UNC)
Centro Espacial Teófilo Tabanera (CETT)
Falda del Cañete - Córdoba, Argentina
+54 3547 40 int. 1153
https://veroandreo.gitlab.io/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] screenshots of old GRASS

[Veronica Andreo]

Perhaps Helena or MarkusN

The oldest I could find within the website repo are these:
-
https://github.com/OSGeo/grass-website/blob/master/static/images/gallery/history/grass32_tape.jpg

-
https://github.com/OSGeo/grass-website/blob/master/static/images/gallery/museum/grass421_tcltkgrass.png

Vero

El lun, 10 jul 2023 a las 19:21, Michael Barton ()
escribió:

> Has anybody got a screenshot of the CERL GRASS versions (1, 2, and/or 3)?
>
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: 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] [release planning] GRASS GIS 7.8.8

[Veronica Andreo]

El jue, 29 jun 2023 a las 12:33, Markus Neteler ()
escribió:

> Hi devs,
>
> On Sat, Dec 3, 2022 at 10:55 PM Markus Neteler  wrote:
> > On Sun, Jul 3, 2022 at 11:01 PM Markus Neteler 
> wrote:
> > > On Thu, Jun 16, 2022 at 2:13 PM Martin Landa 
> wrote:
> > > > Dear all,
> > > >
> > > > 7.8.8RC1 was released on May 14. There is one open issue [1]. Do we
> plan to release 7.8.8 anyway?
> > >
> > > Yes, we do asap.
> >
> > Well, some months have passed...
>
> And even more :-)
>
> > > > [1] https://github.com/OSGeo/grass/milestone/14
>
> Meanwhile no more open issues or PRs related to 7.8.8.
>
> This are the latest additions after RC3:
> https://github.com/OSGeo/grass/compare/7.8.8RC3...releasebranch_7_8
>
> Yet another RC or goto final?
>

+1 for final

Question to all: how much longer will we support the 7.8.x branch? We are
already in 8.3, so people has 8.0.x and 8.2.x to update to, no? Do we have
any policy on this matter?( ops, meanwhile I realized I have to update the
website... will do this weekend )

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

Re: [GRASS-dev] grass-dev Digest, Vol 208, Issue 4

[Veronica Andreo]

Hello Doug,

Yes, it's here: https://grass.osgeo.org/grass83/binary/mswindows/native/

Vero

El mié, 21 jun 2023 a las 9:30, Doug Newcomb ()
escribió:

> Will there be a rc1 standalone installer for windows?
>
> On Tue, Jun 20, 2023, 3:00 PM  wrote:
>
>> Send grass-dev mailing list submissions to
>> grass-dev@lists.osgeo.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>> or, via email, send a message with subject or body 'help' to
>> grass-dev-requ...@lists.osgeo.org
>>
>> You can reach the person managing the list at
>> grass-dev-ow...@lists.osgeo.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of grass-dev digest..."
>> Today's Topics:
>>
>>1. Re: [release planning] GRASS GIS 8.3.0 (Markus Neteler)
>>
>>
>>
>> -- Forwarded message --
>> From: Markus Neteler 
>> To: Sebastiaan Couwenberg 
>> Cc: grass-dev@lists.osgeo.org
>> Bcc:
>> Date: Tue, 20 Jun 2023 11:56:27 +0200
>> Subject: Re: [GRASS-dev] [release planning] GRASS GIS 8.3.0
>> On Tue, Jun 20, 2023 at 9:03 AM Sebastiaan Couwenberg
>>  wrote:
>> > On 6/20/23 08:46, Martin Landa wrote:
>> > > RC1 has been released 2 weeks ago. Is there anything missing in order
>> to
>> > > release 8.3.0 (what be nice to do for FOSS4G).
>> >
>> > Was there no announcement for RC1?
>>
>> Apologies, this fell off the radar due to heavy changes in the (now
>> automated) release management and travelling back from the Community
>> meeting.
>>
>> I have just sent the G8.3.0RC1 announcement.
>>
>> Kind regards,
>> 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
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] seeking GRASS example dataset for Germany

[Veronica Andreo]

Hi Michael,

There's this course that Martin taught in Jena with data for Jena and
Germany in general:
https://training.gismentors.eu/grass-gis-workshop-jena/index.html

Vero

El mié, 3 may 2023 a las 23:37, Michael Barton ()
escribió:

> I may be doing a GRASS workshop in Germany in a few weeks. While I can
> always use the standard North Carolina demo data, it might be more
> interesting to the participants to have a more local dataset. Does anyone
> have a nice dataset for Germany they could share with me with the range of
> raster and vector files similar to those found in the NC sample data?
>
> Thanks
> Michael
> _
>
> C. Michael Barton
> Associate Director, School of Complex Adaptive Systems (
> https://scas.asu.edu)
> Professor, School of Human Evolution & Social Change (
> https://shesc.asu.edu)
> Director, Center for Social Dynamics & Complexity (
> https://complexity.asu.edu)
> Arizona State University
> Tempe, AZ 85287-2701
> USA
>
> Executive Director, Open Modeling Foundation (
> https://openmodelingfoundation.github.io)
> Director, Network for Computational Modeling in Social & Ecological
> Sciences (https://comses.net)
>
> personal website: 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

[GRASS-dev] Fwd: [OSGeo-Discuss] GSoC 2023: Contributor Proposals Submission Started | Deadline - April 4th, 2023 1800 UTC

[Veronica Andreo]

FYI :)

GSoC Contributor proposal period has started!

Have a look at GRASS GIS ideas page for 2023 and get in touch if you are
interested: https://trac.osgeo.org/grass/wiki/GSoC/2023


-- Forwarded message -
De: Rajat Shinde via Discuss 
Date: jue, 23 mar 2023 a las 3:09
Subject: [OSGeo-Discuss] GSoC 2023: Contributor Proposals Submission
Started | Deadline - April 4th, 2023 1800 UTC
To: OSGeo-SoC 
Cc: gsoc-adminosgeo.org , OSGeo Discussions <
disc...@lists.osgeo.org>


Dear All,

FYI, the GSoC Contributor proposal period has started. This email is a
gentle reminder to the potential GSoC contributors interested in
participating in GSoC 2023.

*If you are a contributor interested in contributing to the geospatial open
source with OSGeo as an umbrella organization, then this is high time*:

   1. To go through the *OSGeo GSoC 2023 project ideas list* [1]. Make sure
   to check the list frequently, as it is being updated regularly with new
   ideas.
   2. *Contact the project mentors* via the Developers' mailing list or the
   community chat channels to discuss the project idea/ideas of your
   interest.
   3. Start working on the *proposal draft* and share it with the community
   as soon as possible to receive feedback and comments.

Please go through the GSoC Contributors/Students Guide [2] to get an
overall understanding of the problem. *From Google admins:
"GSoC Contributors who engage with their organization early (and often)
are more likely to be accepted and then succeed"*.

Remember to submit your proposal well in advance, so that you can make the
most out of the feedback from mentors and the community at large and refine
your proposal until the final deadline. Read the application instructions
here [3]. The same page contains all the info you need before taking
action, so please read it carefully.

Please note that the contributor application period starts *March 20, 2023
- 18:00 UTC* and all the student proposals must be submitted before *April
4, 2023 - 18:00 UTC*. Please don't wait for the deadline. Refer to the
GSoC Timeline
[4] for more details.

We are looking forward to working with you toward another awesome edition of
 GSoC! Good luck everyone!

Please forward this email to your developer and community mailing list.

Kind regards,
Your OSGeo GSoC Admins

[1]. https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2023_Ideas

[2]. https://google.github.io/gsocguides/student/
[3]. https://wiki.osgeo
.org/wiki/Google_Summer_of_Code_Recommendations_for_Students#Application_instructions
[4]. https://developers.google.com/open-source/gsoc/timeline
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Contribution for GRASS Community Sprint

[Veronica Andreo]

Hi Brendan,

Thanks much for your interest and willingness to join!! This is great news!
Also, as Vashek said already, we were indeed discussing about
enhancing/automating GRASS-QGIS integration, so your contribution will be
most welcome :)

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

[GRASS-dev] Announcing GRASS GIS 40th birthday community meeting, June 2-6, 2023, Prague

[Veronica Andreo]

Dear all,

The GRASS GIS team is organizing a *Community Meeting* with users,
supporters, contributors, power users and developers to celebrate *the
GRASS GIS 40th birthday!! *The Community Meeting will take place from *June
2 to 6, 2023*, at the Faculty of Civil Engineering from the Czech Technical
University in Prague, Czech Republic.

Keep an eye at this wiki for updates and details:
https://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Prague_2023

Everyone is welcome to participate and support us with donations! Looking
forward to meeting you!

Cheers!

Vero
(on behalf of the GRASS GIS PSC)

-- 
Dra. Verónica Andreo
Investigadora Asistente de CONICET
Instituto Gulich (CONAE - UNC)
Centro Espacial Teófilo Tabanera (CETT)
Falda del Cañete - Córdoba, Argentina
+54 3547 40 int. 1153
https://veroandreo.gitlab.io/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] update email in contributors.csv

[Veronica Andreo]

Hi Ivan,

Done in https://github.com/OSGeo/grass/pull/2888

Best,
Vero

El mié, 15 mar 2023 a las 0:37, Ivan Shmakov () escribió:

> It was brought to my attention that contributors.csv lists one
> of my emails that hasn’t been valid since early 2013:
>
> -,Ivan Shmakov,,Russia,1gray,yes
>
> Could it please be corrected to ?
>
> TIA.
>
> --
> FSF associate member #7257  http://am-1.org/~ivan/
> ___
> 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

[GRASS-dev] Fwd: [OSGeo-Discuss] GSoC 2023: OSGeo Accepted as Mentor Organization | Form for Mentors

[Veronica Andreo]

FYI :)

-- Forwarded message -
De: Rahul Chauhan via Discuss 
Date: dom, 26 feb 2023 a las 2:18
Subject: [OSGeo-Discuss] GSoC 2023: OSGeo Accepted as Mentor Organization |
Form for Mentors
To: 
Cc: , gsoc-adminosgeo.org ,
Ashish Kumar 


Dear All,

We are happy and elated to announce that OSGeo has been accepted once again
as a mentor organization for GSoC 2023.

   1. The list of accepted organizations is at [0].
   Our OSGeo GSoC 2023 application is available at [1].
   2. Please note the Potential GSoC contributors (Student + Professional)
   discuss application ideas with the mentoring organizations from Feb 22 -
   March 19, 2023. So, be ready to be flooded with queries by potential
   contributors in the coming period. :-)
   3. GSoC contributors will be able to register and submit their
   applications from March 20 -  April 4, 2023. All proposals must be
   submitted by April 4, 2023, at 18:00 UTC.
   4. *Mentors of the projects who have already updated their ideas in
   the OSGeo GSoC 2023 ideas list, kindly fill out the Google Form [2] so that
   we can start sending the invitations.*

We still have time for more projects to participate with ideas [3].
It is a good opportunity to:
• Add functionality to your projects.
• Attract more contributors participating in the projects, times they
become long-term contributors.

OSGeo projects, Incubating projects, and community projects are welcome.

*Note -*
If you are interested in joining the Organization Administration team and
have been involved with the OSGeo GSoC initiative in the past with rich
experience, please reach out to us.

[0] https://summerofcode.withgoogle.com/programs/2023/organizations
[1] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_Application_2023
[2] https://forms.gle/LWBMgA8ToL3RyL5v6
[3] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2023_Ideas

Stay tuned for further instructions on the next steps and be
prepared for another geospatial GSoC with OSGeo!

Yours,
OSGeo GSoC Admins
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.0

[Veronica Andreo]

Hi Markus,

El vie, 17 feb 2023 a las 15:25, Markus Neteler ()
escribió:

> Hi devs,
>
> After a long time of development and many, many improvements, it is
> time to release 8.3.0.
>
> Version scheme update: please note that we abandon the odd/even scheme
> and go for semantic versioning, i.e. 8.3.x comes after the 8.2.x
> series. See also the related RFC: Version Numbering
> (https://github.com/OSGeo/grass/pull/2357).
>

Just wondering.. Should we adopt an RFC that has not yet been merged nor
approved via motion? There's a list of tasks in the PR that still seems
incomplete and I see that Vashek moved the milestone of the RFC to 8.4...
I'm not trying to delay the release -either it is called 8.3 or 8.4, it is
overdue- but IMO we need to agree on the RFC, no? Shall I prepare a motion
and we approve a version 1 of the Version Numbering RFC?

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

Re: [GRASS-dev] RFC: variations of statistics in r.neighbors (and the stats lib)

[Veronica Andreo]

Hello Francesco, Markus

I find the possibility of getting statistics for only a certain fraction of
a neighbourhood really interesting and I like Markus' idea as it is more
general and allows for more use cases 邏 Count me in for testing ;)

Vero

El mar, 31 ene 2023 a las 15:48, Markus Metz ()
escribió:

> Hi Francesco,
>
> the proposed change to r.neighbors is interesting, but maybe too specific:
> you have introduced two new functions, and many more functions would be
> needed to e.g. get the filtered standard deviation or median.
>
> Therefore I suggest adding some filtering option to r.neighbors consisting
> of a filtering function and a comparison operator. The filtering function
> would be any of the currently supported neighborhood functions returning
> some value. The comparison operator would be one of gt, ge, le, lt (>, >=,
> <=, <). r.neighbors would then first get the result value of the filtering
> function, then set all values in the neighborhood to NULL that do not
> fulfil the condition "value  , then
> call the actual neighborhood operation with the filtered values. This would
> be more flexible, because the user can freely combine a neighborhood filter
> function with a neighborhood operation.
>
> Makes sense?
>
>
> On Wed, Jan 25, 2023 at 10:55 AM Francesco P. Lovergine <
> fran...@debian.org> wrote:
>
>> Hi,
>>
>> for some specific needs of a research project, I had to make a little
>> change to r.neighbors (the target version was 7.8.5 but that's not
>> essential).
>>
>> Essentially, the idea behind is computing first order statistics on
>> partial
>> populations as identified by selected quantiles (samples >= or <= of a
>> threshold value of quantile).
>>
>> For that, I introduced average_ge_quantile and average_le_quantile
>> operators modes.
>>
>>
>> https://github.com/fpl/grass/commit/6b83795b037c6645a32d6a525cfdee3cc65d521c
>>
>> (the html file is still not updated)
>>
>> I'm not persuaded this is the most elegant way of doing this kind of
>> things,
>> maybe it would be better using an option (as in the case of -w for
>> weighted
>> operations) to compute average and possibly other statistics. Even, one
>> could
>> think in general to other multiple ways of selecting population on the
>> base of
>> quantiles/percentiles of population in a window.
>>
>> Any hint/opinion/alternative/critic about that?
>>
>> All this in the remote hypothesis that a pull request could have sense
>> for such a kind of features.
>>
>> Thanks
>>
>>
>> --
>> Francesco P. Lovergine
>> ___
>> 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
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [Projects] [OSGeo in GSoC 2023] Call for Project Ideas - GSoC 2023 | Deadline - Jan 31, 2023

[Veronica Andreo]

FYI

-- Forwarded message -
De: Rajat Shinde 
Date: mié, 18 ene 2023 a las 12:32
Subject: [Projects] [OSGeo in GSoC 2023] Call for Project Ideas - GSoC 2023
| Deadline - Jan 31, 2023
To: OSGeo Discussions 
Cc: gsoc-adminosgeo.org , OSGeo-SoC <
s...@lists.osgeo.org>, 


Dear All,

Greetings! Wishing you all a very happy new year.

It is the time of the year to start preparing for OSGeo's participation in
the Google Summer of Code 2023 [1]. With the great success of GSoC 2022
projects [2], we are highly excited and motivated to invite the OSGeo
projects (Projects, Incubation projects, Guest Projects) to begin compiling
the project ideas for GSoC 2023.

In order to participate in proposing ideas as a project under the OSGeo
umbrella organization, you just need to send us (admins:  ) the URL for your project's GSoC ideas Wiki page. If you are
participating for the first time, then you may visit [3] for reference.


*Please remember that every idea should indicate:*

   1. A title
   2. Brief descriptions of projects that can be completed in ~175 hours or
   ~350 hours of your GSoC contributor’s time (and labeled appropriately)
   3. 3 Mentors' Details - Name, Email (Primary and Supporting mentors)
   4. For each project, a list of prerequisites, a description of
   programming skills needed, and an estimation of the difficulty level
   5. A test for the students to submit to your evaluation. The test aims
   at evaluating if the student is capable of the project, so please design
   the test having in mind the basic skills required to complete the project.

The organization application period starts *Jan* *23, 2023* and will be
open till *Feb 7, 2023*. So, we expect all the URLs by *Jan 31, 2022* (~12
days from now). Here is the complete GSoC 2023 timeline [4].

*Note*:
1. GSoC 2023 follows the new changes introduced with GSoC 2022. We
sincerely recommend going through the announcement mentioning new changes
[5].
2. If you floated ideas in GSoC 2022 but couldn't progress ahead, then it
is a great time to start working on those ideas again.

Thanks, and please forward the information to your respective project's
mailing list! Always waiting for further queries. :)

(PS- A call for contributors to the OSGeo project ideas with instructions
on interacting with projects will be sent soon, so please be ready for
welcoming new members to the community.)

Cheers,
Rajat for OSGeo GSoC Administration Team

[1] https://summerofcode.withgoogle.com/
[2] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2022_Results
[3] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2022_Ideas
[4] https://developers.google.com/open-source/gsoc/timeline
[5]
https://opensource.googleblog.com/2022/11/get-ready-for-google-summer-of-code-2023.html

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

Re: [GRASS-dev] Filter STDS by spatial index

[Veronica Andreo]

Hi Stefan

I'll test this weekend, would you mind providing us with a basic example to
test? Thanks a lot!!

Vero

El jue, 5 ene 2023 a las 11:01, Stefan Blumentrath (<
stefan.blumentr...@gmx.de>) escribió:

> Hi again,
>
> Please see:
> https://github.com/OSGeo/grass/pull/2725
>
> It uses east, west, north and south in the where statement to select only
> maps that overlap with a given spatial extent (e.g. the computatinal
> region).
> I would be happy to get a review of the PR, before proceding to eventual
> changes of module code...
>
>
> Cheers
> Stefan
>
>
>
>
> Gesendet: Montag, 26. Dezember 2022 um 17:31 Uhr
> Von: "Sören Gebbert" 
> An: "Stefan Blumentrath" 
> Cc: grass-dev@lists.osgeo.org
> Betreff: Re: [GRASS-dev] Filter STDS by spatial index
>
> Hi,
> i am not sure if this helps: some t.rast.* commands should support a where
> statement. Maybe you can use east, west, north and south in the where
> statement to select only maps that are in a extent that is build in the
> where statement?
>
> Best regards
> Sören
>
> Am Mi., 14. Dez. 2022 um 15:24 Uhr schrieb Stefan Blumentrath <
> stefan.blumentr...@gmx.de[mailto:stefan.blumentr...@gmx.de]>:Hei,
>
> I do have a use case where I would like to filter maps in a STRDS by
> spatial extent before e.g. t.rast.univar processes all registered maps.
> In particular, I want to process only maps from a STRDS that intersect
> with the current computational region.
>
> The reason is that the maps registered in the STRDS are collections of
> single scenes of satellite images or collections of smaller mosaics that
> cover only parts of the total extent of the STRDS.
>
> Currently, that does not seem to be supported by TGIS, and I see two
> options to address that:
> a) patch the scenes together with a given granularity (e.g. daily
> mosaics), leave GRASS GIS functions untouched and hope that there is some
> coverage for reasonable region settings. or:
> b) add a spatial filter to the "get_registered_maps"[1] function
> in abstract_space_time_dataset.py, and then subsequently flags to relevant
> modules that make use modified function...
>
> For b) I would think that the most efficient way to handle it would be to
> add a where clause like it was done for the semantic labels? In that case,
> it may make sense to add an index for north, south, east, and west too, no?
> Maybe also top and bottom...
>
> My main question, however is if my case is just a corner case, or does
> some sort of spatial filteing possibility make sense in general / more
> broadly...
>
> Any feedback is much appreciated, esp. before I evtl. start working on b).
>
> Kind regards,
> Stefan
>
> 1)
> https://github.com/OSGeo/grass/blob/main/python/grass/temporal/abstract_space_time_dataset.py#L1604[https://github.com/OSGeo/grass/blob/main/python/grass/temporal/abstract_space_time_dataset.py#L1604]
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org[mailto: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
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Filter STDS by spatial index

[Veronica Andreo]

Hi Stefan,

Sorry for my late response here... Yes, that sounds like something useful
to me, with collections of satellite images such a case/problem might be
pretty common. So, having the chance to select/filter only those scenes
(fully) covering the current computational region is a good addition in my
opinion.

Thanks Stefan!

Cheers,
Vero

El mar, 20 dic 2022 a las 5:53, Paulo van Breugel ()
escribió:

>
>
> On December 14, 2022 15:24:28 Stefan Blumentrath <
> stefan.blumentr...@gmx.de> wrote:
>
> Hei,
>>
>> I do have a use case where I would like to filter maps in a STRDS by
>> spatial extent before e.g. t.rast.univar processes all registered maps.
>> In particular, I want to process only maps from a STRDS that intersect
>> with the current computational region.
>>
>> The reason is that the maps registered in the STRDS are collections of
>> single scenes of satellite images or collections of smaller mosaics that
>> cover only parts of the total extent of the STRDS.
>>
>> Currently, that does not seem to be supported by TGIS, and I see two
>> options to address that:
>> a) patch the scenes together with a given granularity (e.g. daily
>> mosaics), leave GRASS GIS functions untouched and hope that there is some
>> coverage for reasonable region settings. or:
>> b) add a spatial filter to the "get_registered_maps"[1] function
>> in abstract_space_time_dataset.py, and then subsequently flags to relevant
>> modules that make use modified function...
>>
>> For b) I would think that the most efficient way to handle it would be to
>> add a where clause like it was done for the semantic labels? In that case,
>> it may make sense to add an index for north, south, east, and west too, no?
>> Maybe also top and bottom...
>>
>
>> My main question, however is if my case is just a corner case, or does
>> some sort of spatial filteing possibility make sense in general / more
>> broadly...
>>
>
> It seems a bit of a corner case, but in fact something I could use, of I
> understand it right.
>
>
>> Any feedback is much appreciated, esp. before I evtl. start working on b).
>>
>> Kind regards,
>> Stefan
>>
>> 1)
>> https://github.com/OSGeo/grass/blob/main/python/grass/temporal/abstract_space_time_dataset.py#L1604
>>
>> ___
>> 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
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS GIS twitter account

[Veronica Andreo]

Dear Jorge,

Thanks for letting us know. We'll explore if there's indeed a way to change
the email associated to the grass Twitter  account and follow the steps to
take over.

Best,
Vero


El lun., 7 nov. 2022 15:59, Jorge Cornejo  escribió:

> Is there anyone from GRASS that can officially take over this twitter
> account?
>
> I'm in the process of decommissioning my server and many websites and
> their associated email addresses will not be working anymore.  I plan to
> shut it all down by the end of this year (2022).
>
> If you guys could forward this to the appropriate individual will be
> greatly appreciated.
>
>
> *Jorge Cornejo*
> Phone: 8186136404
> <https://streaklinks.com/BRQRBBNiYkWhxs7DlgA-Ip6H/http%3A%2F%2Fvoice.google.com%2Fcalls%3Fa%3Dnc%2C%252B18186136404>
> Email: xch...@gmail.com
> Website: http://www.jorgecornejo.com
> Website: http://hackerspacela.org/
>
> <https://streaklinks.com/BRQRBBVXl5pkzkfUeAR0Dhjp/https%3A%2F%2Fwww.linkedin.com%2Fin%2Fjorgecornejo>
> <https://streaklinks.com/BRQRBBNvr5fI6BEyfwSxgvwQ/https%3A%2F%2Ftwitter.com%2FJorgeCornejo>
> <https://streaklinks.com/BRQRBBZWVpwaQehjlADHDint/https%3A%2F%2Fplus.google.com%2Fu%2F0%2F%2BJorgeCornejo>
> <https://streaklinks.com/BRQRBBNtLVJLzaHPPwjr_jb7/https%3A%2F%2Finstagram.com%2Farmandovronkass%2F>
> <https://streaklinks.com/BRQRBBNZGUBoBdMVWgTMwK_7/https%3A%2F%2Fabout.me%2Fjorgecornejo>
> Create your own email signature
> <https://streaklinks.com/BRQRBBNEhF3zEqU6JASFv_1H/https%3A%2F%2Fwww.wisestamp.com%2Fcreate-own-signature%2F%3Futm_source%3Dpromotion%26utm_medium%3Dsignature%26utm_campaign%3Dcreate_your_own%26srcid%3D>
> ‌
> ᐧ
>
> On Thu, Aug 3, 2017 at 12:28 AM Veronica Andreo 
> wrote:
>
>> Hello Jorge, Vaclav
>>
>> Would you add me too, please?
>>
>> Jorge, do you think it would be possible to change the profile avatar to
>> grass logo [0] instead of the old gui starting wizard? And the banner pic
>> for the grass splash screen [1], for example? And the red color in the
>> profile by grass green or the common blue/light blue one?
>>
>> Thanks a lot for your support!
>> and sorry for bothersome :)
>>
>> best,
>> Vero
>>
>> [0] https://grass.osgeo.org/download/logos/
>> [1]
>> https://trac.osgeo.org/grass/browser/grass/branches/releasebranch_7_2/gui/images/splash_screen.png
>>
>>
>> 2017-07-22 16:11 GMT+02:00 Markus Neteler :
>>
>>> (changing to a more appropriate subject line)
>>>
>>> On Sat, Jul 22, 2017 at 2:43 PM, Vaclav Petras 
>>> wrote:
>>> > On Sat, Jul 22, 2017 at 5:24 AM, Luca Delucchi 
>>> wrote:
>>> > years ago, Jorge Cornejo (CC'ed) created and used this account.
>>> However,
>>> > recently the automatic settings associated with the account was only
>>> > reposting some RSS reader with inappropriate content (from point of
>>> view of
>>> > GRASS and open source) - Jorge already solved that. Last week or so,
>>> he gave
>>> > access to it through TweetDeck and he can give it to you as well. With
>>> > TweetDeck, I can now tweet and also delete old tweets. However, I
>>> don't have
>>> > a full access to the account and can't change name, banner, add people
>>> to
>>> > TweetDeck, etc. (Jorge has).
>>> >
>>> > https://twitter.com/GRASSGIS
>>>
>>> Great, that some progress has been made here. Looking forward to the
>>> cleanup of the remaining issues.
>>> Thanks for your support, Jorge!
>>>
>>> Markus
>>> ___
>>> grass-dev mailing list
>>> grass-dev@lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>>
>>
>
> --
> Not Found
>
> The requested URL was not found on the server. If you entered the URL
> manually please check your spelling and try again.
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] hi

[Veronica Andreo]

Hi Daniel,

El mié, 3 ago 2022 a las 14:56, Daniel Torres ()
escribió:

> Hi guys,
> going back to the search feature in the Grass website. I've taken a look
> at the options in Hugo docs. I think it may not be the best approach to
> have a client based search as it will require loading big pieces of
> data...  in principle all pages, so loading ... all website pages + all
> manual pages  in a single page. Take this one for example:
> https://gist.github.com/cmod/5410eae147e4318164258742dd053993 ; using
> Hugo it creates a json from all pages and then in the search implementation
> it loads a js library and the json.
>

Well, this sounds similar to Nick's attempt here:
https://github.com/OSGeo/grass-website/pull/131. Have you seen that one?
When I tested it it was super fast too, but for some reason it was not
searching within the page. The link you point claims to be super fast, so
which would be the disadvantages then?


> Other options listed in Hugo's website are paid, like Algolia.
>

IMHO, paid options are not an option

>
>  So, maybe it would be better to just take the other approach of using
> Duckduckgo or google in the mean time?
>

If you prefer any of these, it's also fine. Which would be the
advantages/disadvantages?
In any case, I'd suggest discussing these in the issue, so it's all in the
same place :)

Thanks for taking over this! We really appreciate it!
Vero
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] hi

[Veronica Andreo]

Hola Daniel,

None of those at time, but you could open a new discussion in github
(though that is in the main grass repo...)

Vero

El lun., 1 ago. 2022 19:51, Daniel Torres  escribió:

> thanks Veronica, then I'll  try with the ones suggested in Hugo website
>
> (is there another communication method you guys use, like Slack, discord
> or something like kind of more direct or  quick questions and stuff? )
>
> On Mon, Aug 1, 2022 at 11:43 AM Veronica Andreo 
> wrote:
>
>> Hello Daniel,
>>
>> IIRC, I suggested using something similar to what wowchemy (former hugo
>> academic) has, but the path chosen was different. Paulo, also made a
>> suggestion, but I didn't have the time to try, honestly. I think it's all
>> in the PRs and probably this issue too:
>> https://github.com/OSGeo/grass-website/issues/19
>>
>> Vero
>>
>> El lun, 1 ago 2022 a las 15:55, Daniel Torres ()
>> escribió:
>>
>>> Thanks guys,
>>> I'm ok with starting on the website.
>>>
>>> About the search, in Hugo website they suggest a couple of methods
>>> https://gohugo.io/tools/search/ , have those been tried?
>>>
>>> On Sun, Jul 31, 2022 at 3:29 AM Veronica Andreo 
>>> wrote:
>>>
>>>> Hi Daniel,
>>>>
>>>> Welcome! Besides what Vashek pointed out, if you feel comfortable
>>>> starting with something for the website, we are missing a search engine
>>>> there. There were a couple of attempts in the past but none of them worked
>>>> fully as expected. Have a look at the PRs here:
>>>> https://github.com/OSGeo/grass-website/pulls
>>>>
>>>> Best,
>>>> Vero
>>>>
>>>> El sáb, 30 jul 2022 a las 23:46, Vaclav Petras ()
>>>> escribió:
>>>>
>>>>> Hi Daniel,
>>>>>
>>>>> Welcome. That sounds great. For Python, check this presentation I'm
>>>>> preparing for FOSS4G where are I describe how to do good PRs which fix
>>>>> coding standards and the load of tools which can be applied:
>>>>>
>>>>> https://wenzeslaus.github.io/code-quality-measures-foss4g-2022/#/45
>>>>>
>>>>> JavaScript at this point means starting with your own idea which may
>>>>> or may not be what you are looking for. Website is certainly one option.
>>>>>
>>>>> I would really like to see changes in the documentation (aka HTML
>>>>> manual pages):
>>>>>
>>>>> https://grass.osgeo.org/grass83/manuals/
>>>>>
>>>>> ...but that's certainly "bring your own idea." It likely involves some
>>>>> HTML and CSS design, but perhaps there is something more functional that
>>>>> can be done. An alternative to this is migrating to Sphinx first, but
>>>>> that's just a thought from the past.
>>>>>
>>>>> Now when I think about it, the full JavaScript checks in Super-Liner
>>>>> are not enabled, so that's perhaps a small JavaScript task to tackle 
>>>>> before
>>>>> starting a bigger project (that's up to you!).
>>>>>
>>>>> Let me know if there is any other info which would be helpful.
>>>>>
>>>>> Best,
>>>>> Vaclav
>>>>>
>>>>>
>>>>> On Sat, 30 Jul 2022 at 14:18, Daniel Torres 
>>>>> wrote:
>>>>>
>>>>>> Hi guys, I'm Daniel , I work as Front end dev. I would like to
>>>>>> contribute to the project, as I find it really nice. I have experience 
>>>>>> with
>>>>>> JS and front end stuff, but also with Python.
>>>>>>
>>>>>> Happy to contribute, but don't really know where to start. (Maybe
>>>>>> something on the website side?)
>>>>>>
>>>>>> Cheers,
>>>>>>   Daniel
>>>>>> ___
>>>>>> 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
>>>>>
>>>>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] hi

[Veronica Andreo]

Hello Daniel,

IIRC, I suggested using something similar to what wowchemy (former hugo
academic) has, but the path chosen was different. Paulo, also made a
suggestion, but I didn't have the time to try, honestly. I think it's all
in the PRs and probably this issue too:
https://github.com/OSGeo/grass-website/issues/19

Vero

El lun, 1 ago 2022 a las 15:55, Daniel Torres ()
escribió:

> Thanks guys,
> I'm ok with starting on the website.
>
> About the search, in Hugo website they suggest a couple of methods
> https://gohugo.io/tools/search/ , have those been tried?
>
> On Sun, Jul 31, 2022 at 3:29 AM Veronica Andreo 
> wrote:
>
>> Hi Daniel,
>>
>> Welcome! Besides what Vashek pointed out, if you feel comfortable
>> starting with something for the website, we are missing a search engine
>> there. There were a couple of attempts in the past but none of them worked
>> fully as expected. Have a look at the PRs here:
>> https://github.com/OSGeo/grass-website/pulls
>>
>> Best,
>> Vero
>>
>> El sáb, 30 jul 2022 a las 23:46, Vaclav Petras ()
>> escribió:
>>
>>> Hi Daniel,
>>>
>>> Welcome. That sounds great. For Python, check this presentation I'm
>>> preparing for FOSS4G where are I describe how to do good PRs which fix
>>> coding standards and the load of tools which can be applied:
>>>
>>> https://wenzeslaus.github.io/code-quality-measures-foss4g-2022/#/45
>>>
>>> JavaScript at this point means starting with your own idea which may or
>>> may not be what you are looking for. Website is certainly one option.
>>>
>>> I would really like to see changes in the documentation (aka HTML manual
>>> pages):
>>>
>>> https://grass.osgeo.org/grass83/manuals/
>>>
>>> ...but that's certainly "bring your own idea." It likely involves some
>>> HTML and CSS design, but perhaps there is something more functional that
>>> can be done. An alternative to this is migrating to Sphinx first, but
>>> that's just a thought from the past.
>>>
>>> Now when I think about it, the full JavaScript checks in Super-Liner are
>>> not enabled, so that's perhaps a small JavaScript task to tackle before
>>> starting a bigger project (that's up to you!).
>>>
>>> Let me know if there is any other info which would be helpful.
>>>
>>> Best,
>>> Vaclav
>>>
>>>
>>> On Sat, 30 Jul 2022 at 14:18, Daniel Torres  wrote:
>>>
>>>> Hi guys, I'm Daniel , I work as Front end dev. I would like to
>>>> contribute to the project, as I find it really nice. I have experience with
>>>> JS and front end stuff, but also with Python.
>>>>
>>>> Happy to contribute, but don't really know where to start. (Maybe
>>>> something on the website side?)
>>>>
>>>> Cheers,
>>>>   Daniel
>>>> ___
>>>> 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
>>>
>>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [OSGeo-Discuss] FOSS4G Community Sprint 2022

[Veronica Andreo]

FYI :)

-- Forwarded message -
De: Astrid Emde (OSGeo) via Discuss 
Date: dom, 31 jul 2022 a las 17:02
Subject: [OSGeo-Discuss] Less than a month to the FOSS4G Community Sprint
2022 - August 27th and 28th
To: OSGeo Projects , Announce <
annou...@lists.osgeo.org>, Discuss 


Dear FOSS4G community,

as you all know, in less than a month, between August the 27th and 28th,
the University of Florence will be stage for the gathering of the
developers, translators, power users and anyone interested in their most
important hands-on meeting of the year: the codesprint of FOSS4G 2022

This is a gentle reminder to add your name and project to this year's
wiki page:
https://wiki.osgeo.org/wiki/FOSS4G_2022/Community_sprint

The better we get an idea of the number of participants and the better
we will be able to organize rooms and supplies.

And remember, this year we invite seasoned community members to donate
time to guide new members through the setup of the development
environment or translation tools of their projects. Please state
availability in the wiki page.

We are looking forward to meeting you!

The Codesprint Organization Committee
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] hi

[Veronica Andreo]

Hi Daniel,

Welcome! Besides what Vashek pointed out, if you feel comfortable starting
with something for the website, we are missing a search engine there. There
were a couple of attempts in the past but none of them worked fully as
expected. Have a look at the PRs here:
https://github.com/OSGeo/grass-website/pulls

Best,
Vero

El sáb, 30 jul 2022 a las 23:46, Vaclav Petras ()
escribió:

> Hi Daniel,
>
> Welcome. That sounds great. For Python, check this presentation I'm
> preparing for FOSS4G where are I describe how to do good PRs which fix
> coding standards and the load of tools which can be applied:
>
> https://wenzeslaus.github.io/code-quality-measures-foss4g-2022/#/45
>
> JavaScript at this point means starting with your own idea which may or
> may not be what you are looking for. Website is certainly one option.
>
> I would really like to see changes in the documentation (aka HTML manual
> pages):
>
> https://grass.osgeo.org/grass83/manuals/
>
> ...but that's certainly "bring your own idea." It likely involves some
> HTML and CSS design, but perhaps there is something more functional that
> can be done. An alternative to this is migrating to Sphinx first, but
> that's just a thought from the past.
>
> Now when I think about it, the full JavaScript checks in Super-Liner are
> not enabled, so that's perhaps a small JavaScript task to tackle before
> starting a bigger project (that's up to you!).
>
> Let me know if there is any other info which would be helpful.
>
> Best,
> Vaclav
>
>
> On Sat, 30 Jul 2022 at 14:18, Daniel Torres  wrote:
>
>> Hi guys, I'm Daniel , I work as Front end dev. I would like to contribute
>> to the project, as I find it really nice. I have experience with JS and
>> front end stuff, but also with Python.
>>
>> Happy to contribute, but don't really know where to start. (Maybe
>> something on the website side?)
>>
>> Cheers,
>>   Daniel
>> ___
>> 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
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS birthday toast tomorrow, July 29th!

[Veronica Andreo]

Hello everyone!!

Tomorrow, the calendar marks 39 years of GRASS development! 邏 Let's
celebrate with some beverage and make a toast in an online meeting at 15
UTC (See local times here:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2022=7=29=15=0=0=48=25=207=197
)

Vashek will provide a link before the scheduled time! Keep an eye on the
mailing list!

See you tomorrow!
Vero

-- 
Dra. Verónica Andreo
Investigadora Asistente de CONICET
Instituto Gulich (CONAE - UNC)
Centro Espacial Teófilo Tabanera (CETT)
Falda del Cañete - Córdoba, Argentina
+54 3547 40 int. 1153
https://veroandreo.gitlab.io/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.2.0

[Veronica Andreo]

All fixed and tweet posted
Thanks Markus :)



El lun, 6 jun 2022 a las 13:46, Markus Neteler ()
escribió:

> Hi Vero
>
> Just edit straight in GitHub.
> This should work. Once done, ping me and I trigger the Hugo script on the
> server.
>
> Markus
>
>
>
> Veronica Andreo  schrieb am Mo., 6. Juni 2022,
> 13:39:
>
>> I merged Caitlin news yesterday, but I forgot to change the date in the
>> YAML heading of the file, which was planned for thursday, the day I weekly
>> post on twitter... So, the news is merged but does not appear in the
>> website yet and does not make sense to post about it... difficult day
>> yesterday, sorry
>>
>> Vashek, if you want to merge the release news then go ahead, I tweet
>> about that and on thursday, we do Caitlin post when it appears online.
>>
>> Vero
>>
>> El dom, 5 jun 2022 a las 1:06, Vaclav Petras ()
>> escribió:
>>
>>>
>>>
>>> On Sat, Jun 4, 2022, 5:07 PM Veronica Andreo 
>>> wrote:
>>>
>>>>
>>>> I had planned to merge Caitlin's news tomorrow and tweet about that on
>>>> Monday, so then we can post the release,
>>>>
>>>
>>> That works for me!
>>>
>>>> ___
>> 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] [release planning] GRASS GIS 8.2.0

[Veronica Andreo]

I merged Caitlin news yesterday, but I forgot to change the date in the
YAML heading of the file, which was planned for thursday, the day I weekly
post on twitter... So, the news is merged but does not appear in the
website yet and does not make sense to post about it... difficult day
yesterday, sorry

Vashek, if you want to merge the release news then go ahead, I tweet about
that and on thursday, we do Caitlin post when it appears online.

Vero

El dom, 5 jun 2022 a las 1:06, Vaclav Petras ()
escribió:

>
>
> On Sat, Jun 4, 2022, 5:07 PM Veronica Andreo  wrote:
>
>>
>> I had planned to merge Caitlin's news tomorrow and tweet about that on
>> Monday, so then we can post the release,
>>
>
> That works for me!
>
>>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.2.0

[Veronica Andreo]

Tweet drafted as well: https://trac.osgeo.org/grass/wiki/PSC/Marketing
(near the bottom).

I had planned to merge Caitlin's news tomorrow and tweet about that on
Monday, so then we can post the release, but we can shift the order if you
prefer.

El sáb, 4 jun 2022 a las 22:27, Vaclav Petras ()
escribió:

>
>
> On Sat, 4 Jun 2022 at 16:20, Martin Landa  wrote:
>
>>
>> standalone installer available for testing at
>>
>>
>> https://grass.osgeo.org/grass82/binary/mswindows/native/WinGRASS-8.2.0-1-Setup.exe
>>
>
> Thank you, Martin!
> ___
> 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] [release planning] GRASS GIS 7.8.8

[Veronica Andreo]

El vie, 13 may 2022 a las 13:09, Markus Neteler ()
escribió:

> Hi devs,
>
> Here the milestone:
> https://github.com/OSGeo/grass/milestone/14?closed=1
>
> it lists the following fix:
> --> Make: add -rpath to LD_SEARCH_FLAGS #2280
>
> which is relevant for the GDAL-GRASS driver, to avoid /etc/ldconfig.d/
> tricks.
> BTW, this driver has been moved to a separate repo, for easier
> maintenance and less burden to GDAL devs:
> https://github.com/OSGeo/gdal-grass/
>
> Hence I would suggest that I create 7.8.8RC1.
>
> Any objections?
>

No objection from my side
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 7.8.7

[Veronica Andreo]

El mar., 22 feb. 2022 16:52, Markus Neteler  escribió:

> On Mon, Feb 21, 2022 at 7:17 PM Markus Neteler  wrote:
> > On Mon, Feb 21, 2022 at 11:32 AM Sebastiaan Couwenberg
> >  wrote:
> > > On 1/20/22 23:43, Markus Neteler wrote:
> > > > On Tue, Jan 18, 2022 at 7:57 PM Markus Neteler 
> wrote:
> > > >> Given that also a lot of wxPython/Python 3.10 fixes have been
> merged,
> > > >> I suggest that I create the 7.8.7RC1 by tomorrow.
> > > >
> > > > Done:
> > > > https://github.com/OSGeo/grass/releases/tag/7.8.7RC1
> > >
> > > Will there be an RC2 or final release in the foreseeable future?
> >
> > There was not much feedback on RC1. This are the changes since then:
> > https://github.com/OSGeo/grass/compare/7.8.7RC1...releasebranch_7_8
> >
> > @Tomáš: do we need RC2 for this change?
> >
> https://github.com/OSGeo/grass/commit/7f6f550d79f603d8218fd224540d1f852cfcec7e
>
> He answered personally that not RC2 is needed for this change.
>
> > However, I'd like to see 7.8.7 final out asap.
>
> If there are no objections, I'll release 7.8.7 final tomorrow.
>

+1

Vero

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

[GRASS-dev] Call for ideas to post in social media

[Veronica Andreo]

Dear all,

Some of you might have seen that every week I post something on Twitter (
https://twitter.com/GRASSGIS - follow us and help with a RT if you don't
already ;-)) mainly as a way to show off GRASS new features, releases,
student projects, presentations at conferences, scientific publications,
new addons, etc. This has brought us +800 more followers in the last year,
increased our mentions, impressions and visits significantly (last month
our profile visits increased almost 400%). In the long term, I believe
increasing our presence and showing our software features is good for the
project.

To keep this running, we are collecting ideas and crafting threads here:
https://trac.osgeo.org/grass/wiki/PSC/Marketing#Upcomingpostsmayberecycledandpostedagain.

This upcoming week, I'll post about Caitlin's student grant and the
implementation of the temporal class within grass.jupyter. There are a
couple of other ideas there that need to be developed further, i.e., they
need content.

I'm calling here for help with those and for new ideas, screenshots, small
video tutorials, new addons, new features you would like to see published
in twitter to keep these weekly posts flowing.

Thanks much in advance! And thanks to those of you that eventually ping
with something cool to show :)

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

[GRASS-dev] RFCs on Python version and release procedure

[Veronica Andreo]

Dear all,

During our last PSC meeting (see minutes here [1]) we discussed the Python
language version that we should support and clarifications were made to the
draft RFC. Furthermore, the draft RFC for release procedure was also
mentioned as a way to adopt feature freezing and avoid last minute
backporting of new features that, if not properly tested, might be
disruptive (see for example https://github.com/OSGeo/grass/issues/2137).

This is a call and invitation to read RFC 4: Release procedure [2] and RFC
8: Python Language Support [3], and comment/discuss on what's drafted there
so PSC can then vote and adopt consensuated procedures.

Looking forward to hear from you,
Vero

[1] https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20220211
[2] https://trac.osgeo.org/grass/wiki/RFC/4_ReleaseProcedure
[3] https://trac.osgeo.org/grass/wiki/RFC/8_LanguageStandardsSupportPython
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-PSC] difficult to get GRASS source code package

[Veronica Andreo]

El lun, 14 feb 2022 a las 20:29, Vaclav Petras ()
escribió:

>
> On Mon, 14 Feb 2022 at 14:22, Veronica Andreo 
> wrote:
>
>>
>> Currently, there's a link to releases  in the first entry of
>> https://grass.osgeo.org/download/ that points to
>> https://github.com/OSGeo/grass/releases. I agree that esp for 8.0.0 the
>> link to the tarball means a lot of browsing down.
>>
>
> Or instead of the releases page to that tags page I linked above. The
> links (both .tar.gz and .zip) are more readily available there. The target
> audience is technical anyway, so perhaps this is a preferred view at this
> point in the workflow.
>
> https://github.com/OSGeo/grass/tags
>

Here's the PR: https://github.com/OSGeo/grass-website/pull/284
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-PSC] difficult to get GRASS source code package

[Veronica Andreo]

Hi all,

El lun, 14 feb 2022 a las 18:47, Markus Neteler ()
escribió:

> On Mon, Feb 14, 2022 at 5:08 PM Michael Barton 
> wrote:
> >
> > This sounds a bit weird, but with some recent changes to the GRASS
> website, it has become more difficult to find and download a current stable
> release.
> >
> > I went to find a tar/zip package of GRASS 8.0.0 source code to build and
> could not find one from the web site. The links all lead only to the GitHub
> repository.
>
> I agree that it is missing from
> https://grass.osgeo.org/download/



> In my view (I expressed that also in the past) we should link a zip
> file/tarball directly on that page. Just pointing to GH isn't enough
> and we even have the tarballs on the server:
>
> https://grass.osgeo.org/grass80/source/


Currently, there's a link to releases  in the first entry of
https://grass.osgeo.org/download/ that points to
https://github.com/OSGeo/grass/releases. I agree that esp for 8.0.0 the
link to the tarball means a lot of browsing down.
How would you like to include the tarball directly in the website? Would
you mind creating an issue in the website repo?

[image: image.png]

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

Re: [GRASS-dev] [release planning] GRASS GIS 8.0.1

[Veronica Andreo]

There's also an email to grass-user reporting that extensions cannot be
installed in Windows with GRASS 8 standalone installer. In the user report,
it seems there was an issue with tags too as he reports that after
installing the standalone the version he gets is 8.0.0dev. See the email
here: https://lists.osgeo.org/pipermail/grass-user/2022-February/082861.html
(Anna already asked him to file an issue).

If this is the case, it may become a blocker, IMO.


El mar, 8 feb 2022 a las 13:08, Markus Neteler ()
escribió:

> Hi devs,
>
> Under certain circumstances (i.e., offline/sandbox compilation) the
> recent 8.0.0 release causes troubles (see
> https://github.com/OSGeo/grass/issues/2137).
> This has been addressed and fixed since then.
>
> Two blockers are still open (the second we already bumped from 8.0.0
> to 8.0.1, not sure if they are blockers at all):
>
> https://github.com/OSGeo/grass/issues?q=is%3Aopen+is%3Aissue+label%3Ablocker+milestone%3A8.0.1
>
> Now, since backports to the future 8.0.2 are piling up (esp. the
> ctypes related fix: https://github.com/OSGeo/grass/pull/2079), I would
> suggest that we release 8.0.1 asap.
>
> Hence I may prepare 8.0.1RC1 in the next day(s).
> Any objections?
>
> Best,
> 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] [release planning] GRASS GIS 7.8.7

[Veronica Andreo]

El mar, 18 ene 2022 a las 19:57, Markus Neteler ()
escribió:

> Hi devs,
>
> On Wed, Dec 22, 2021 at 8:32 PM Markus Neteler  wrote:
> >
> > Some important fixes (incl. GUI related) have accumulated:
> > https://github.com/OSGeo/grass/milestone/7?closed=1
> >
> > The still open ones we may bump to 7.8.8, if no objections:
> > https://github.com/OSGeo/grass/milestone/7
> > %3Aopen+is%3Aissue+label%3Ablocker+milestone%3A8.0.0
> ...
>
> Given that also a lot of wxPython/Python 3.10 fixes have been merged,
> I suggest that I create the 7.8.7RC1 by tomorrow.
>
> Any objections?
>

no objections :)

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

Re: [GRASS-dev] [release planning] GRASS GIS 8.0.0

[Veronica Andreo]

Hola Martin :)

El dom, 2 ene 2022 a las 16:41, Martin Landa ()
escribió:

> Hi,
>
> ne 2. 1. 2022 v 15:12 odesílatel Markus Neteler 
> napsal:
> > > Or do we keep `x86_64` in the URL to be "more clear" about 64bit?
> >
> > Maybe not as it looks IMHO too technical.
>
> +1
>
> I will remove `x64_64` from URLs (related to G8 only) if there are no
> objections. Martin
>

Is this complete? Which is the link for windows installer then? I'd like to
include it here: https://github.com/OSGeo/grass-website/pull/274 that is
pending for a while

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

Re: [GRASS-dev] [release planning] GRASS GIS 8.0.0

[Veronica Andreo]

El dom, 9 ene 2022 a las 16:36, Markus Neteler ()
escribió:

> Hi,
>
> On Thu, Dec 30, 2021 at 5:02 PM Markus Neteler  wrote:
> >
> > Dear all,
> >
> > hooray, GRASS GIS 8.0.0RC1 has been published:
> > https://github.com/OSGeo/grass/releases/tag/8.0.0RC1
> >
> > Please test it!
>
> I'd love to see 8.0.0 being published
>
> We have no more blockers:
>
> https://github.com/OSGeo/grass/issues?q=is%3Aopen+is%3Aissue+label%3Ablocker+milestone%3A8.0.0
>
> This is the 8.0.0 milestone:
> https://github.com/OSGeo/grass/milestone/4
>
> We may bump the remaining 13 issues/PRs to milestone 8.0.1.
>
> Here the changes after RC1 on releasebranch_8_0:
> https://github.com/OSGeo/grass/compare/8.0.0RC1...releasebranch_8_0
>
> Can we now publish "final" or do we still need a RC2?
>

With no blockers, I'd be in favor of publishing final already :)
Is there any "policy" regarding the number of RC's before final?

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

Re: [GRASS-dev] Invitation: End of year toast :)

[Veronica Andreo]

Here is the link (kindly provided by Vaclav :))

https://ncsu.zoom.us/j/96062234428?pwd=YnRxdVQ1OHFxcFVFV0hDSlpmOVp4Zz09

See you soon!
Vero

El lun, 27 dic 2021 a las 13:46, Veronica Andreo ()
escribió:

> Dear all,
>
> We'd like to invite you all to a virtual end of year toast on *Wednesday,
> December 29th at 20:00 UTC* (See some local times:
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021=12=29=20=0=0=485=48=207=197
> )
>
> We'll share the link on this thread a couple of hours before the event.
> Mark your calendars!
>
> Looking forward to seeing you!
> Vero
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Invitation: End of year toast :)

[Veronica Andreo]

Dear all,

We'd like to invite you all to a virtual end of year toast on *Wednesday,
December 29th at 20:00 UTC* (See some local times:
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021=12=29=20=0=0=485=48=207=197
)

We'll share the link on this thread a couple of hours before the event.
Mark your calendars!

Looking forward to seeing you!
Vero
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8.0.0

[Veronica Andreo]

Hi all,

El sáb, 18 dic 2021 a las 10:48, Markus Neteler ()
escribió:

> Hi,
>
> On Fri, Dec 10, 2021 at 6:34 PM Veronica Andreo 
> wrote:
> >
> > Huge +1!!!
> >
> > But... we have 3 blocker PRs:
> https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.0.0+label%3Ablocker
> > - #2011 seems ready to merge I think
>
> ... meanwhile merged.
>
> > - #1927 rename gui tabs seems also ready (discussion about changing
> module -> tool everywhere in the code base should happen in a separate
> issue/PR)
>
> ... meanwhile merged.
>
> > - #1892 utils/mkhtml.py: fix get and set addon manual page source and
> history URL link <<-- more work required according to Tomas, also it is
> related to PR #615 in the addons repo
>
> ... still open. Vaclav suggests therein that this be not considered as a
> blocker.
>

As there was no response there, I'd suggest to move on with RC1

>
> > So, I believe the last one seems the only one remaining, no?
>
> Or, nothing blocking remaining. @All - please remember that we talk
> about RC1, not final.
>

+1 for RC1 before Xmas!

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

Re: [GRASS-dev] [release planning] GRASS GIS 8.0.0

[Veronica Andreo]

Huge +1!!!

But... we have 3 blocker PRs:
https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.0.0+label%3Ablocker
- #2011 seems ready to merge I think
- #1927 rename gui tabs seems also ready (discussion about changing module
-> tool everywhere in the code base should happen in a separate issue/PR)
- #1892 utils/mkhtml.py: fix get and set addon manual page source and
history URL link <<-- more work required according to Tomas, also it is
related to PR #615 in the addons repo

So, I believe the last one seems the only one remaining, no?

Sorry for spoiling it... I really want to see an RC of GRASS 8 asap too

Best,
Vero


El vie, 10 dic 2021 a las 17:26, Markus Neteler ()
escribió:

> Hi devs,
>
> All major issues have been tackled and 8.0.0 is due by December 10,
> 2021 (hey, that's today!):
> https://github.com/OSGeo/grass/milestone/4
>
> We have no more blockers:
>
> https://github.com/OSGeo/grass/issues?q=is%3Aopen+is%3Aissue+label%3Ablocker+milestone%3A8.0.0
>
> Hence I would suggest that I create 8.0.0RC1 over the weekend.
>
> Any objections?
>
> Best,
> Markus
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - free data with free software
> https://grass.osgeo.org
> https://courses.neteler.org/blog
> ___
> 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] help with completing GRASS 8 new features wiki

[Veronica Andreo]

El jue, 9 dic 2021 a las 23:46, Markus Neteler ()
escribió:

> On Mon, Nov 29, 2021 at 2:39 AM Vaclav Petras 
> wrote:
> > On Sun, Nov 28, 2021 at 1:06 PM Markus Neteler 
> wrote:
> >> On Wed, Nov 24, 2021 at 2:10 PM Veronica Andreo 
> wrote:
> >>
> >> For populating this page I usually use "git log":
> ...
> > You could also use GitHub CLI to get merged PRs with milestone 8.0.0:
>
> Ok, I have made a major "milestone" cleanup (some hours of stupid
> work, so PLEASE all assign the milestone to their PRs!):
>
> https://github.com/OSGeo/grass/pulls?q=is%3Apr+no%3Amilestone+is%3Aclosed
> gives 0 at time, meaning that each PR has a milestone now assigned.
>
> I went through 944 unlabeled PRs... :-D
>

Oh, wow! That's a lot! Thanks Markus!!


> > gh pr list --search "milestone:8.0.0" --state merged --limit 100
> >
> > This gives 93 PRs.
>
> Now
> - 19 open
> - 827 closed
>
> > Unfortunately, we also have PRs with no milestone which is 919 items:
> >
> > gh pr list --search "no:milestone" --state merged --limit 100
> >
> Now: "No pull requests match your search in OSGeo/grass" :-)
>
> In my cleanup session, I have created the missing 7.x milestones in
> GitHub and assigned the respective PRs to them. See here for the
> closed 7.x milestones:
>
>
> https://github.com/OSGeo/grass/milestones?direction=desc=due_date=closed
>
> (If anyone comes across a wrong assignment, please just fix it right
> away by reassigning.)
>
> Method: Due to the sheer amount of unlabeled PRs I used the
> semi-heuristic approach of quick-reading the 944 PR titles and
> (ideally) spotting those which I knew they don't belong to 8.x. In
> addition, I checked the PR merge date and cross-checked that with the
> list of release dates to figure out to which milestone they belong to,
> then assigned them accordingly.
>
> Overall, it looks much better now.
>

Impressive, thanks again!

>
> CHANGELOG creation:
>
> Auto-generated changelog on command line (btw, how to sort the output via
> API?):
>
> gh api repos/OSGeo/grass/releases/generate-notes -f tag_name="8.0.0"
> -f target_commitish=releasebranch_8_0 -q .body
>

What type of sorting do we need? Does it provide the PR number or the hash?
If the number or date, maybe that could help. I have not tested or digged
into it myself so I'm only guessing here


> Alternative (in future use 8.0.0 tag which doesn't exist yet) in the
> browser:
> https://github.com/OSGeo/grass/compare/7.8.6...releasebranch_8_0
>

Doesn't look as nice, but it's an alternative indeed :)

Thanks again!
Vero

PS: PLEASE always assign a milestone to (new) PRs!
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [OSGeo-Discuss] FOSDEM 2022 (Online) – geospatial devroom Call for Participation - Deadline: 26.12.2021

[Veronica Andreo]

FYI :)

-- Forwarded message -
De: Astrid Emde (OSGeo) via Discuss 
Date: jue, 9 dic 2021 a las 8:44
Subject: [OSGeo-Discuss] FOSDEM 2022 (Online) – geospatial devroom Call for
Participation - Deadline: 26.12.2021
To: Discuss , Announce 


News item
https://www.osgeo.org/foundation-news/osgeo-at-fosdem-2022-online-call-for-participation-for-the-geospatial-devroom/
2021-12-09


Submission Deadline: 26.12.2021

FOSDEM is the largest free and open source developers meeting in Europe,
with 8000+ participants. It normally takes place in Brussels (Belgium).

FOSDEM 2021 will be Online. As in the last year we will have a
Geospatial devroom. The Geospatial devroom will be on Sunday 6 February
2022. In 2022 it will be our opportunity to bring our global community
to FOSDEM.

The geospatial devroom is the place to talk about the state of the art
of open, geo-related data, free and open source geospatial software and
its ecosystem. This includes standards and tools, e.g. spatial
databases, online mapping tools, geospatial services, used for
collecting, storing, delivering, analysing, and visualizing geodata.

We hope you will submit a talk or come around at FOSDEM 2022.

Call for Participation
-
Submission Deadline: 26.12.2021

We are looking for you to be part of the geospatial devroom. The
geospatial devroom aims to host talks about geospatial topics, GIS, and
geodata projects, standards and open data.

Please submit your talk till 26 December 2021.

About The FOSDEM

FOSDEM is a free event for software developers to meet, share ideas and
collaborate.

-FOSDEM is free to attend. There is no registration.
-FOSDEM website https://fosdem.org/2022/
-FOSDEM code of conduct https://fosdem.org/2022/practical/conduct/

New rules / What changes since last year

For obvious reasons, this year the event will not take place in a
physical location but online.

  -   The reference time will be Brussels local lime (CET).
  -   Talks will be pre-recorded in advance, and streamed during the
event
  -   Q/A session will be take live
  -   A facility will be provided for people watching to chat between
themselves
  -   A facility will be provided for people watching to submit questions
  -   Food and drinks is now allowed during the talks, but you are
responsible for cleaning your own space

Key dates

   -  Submission deadline: 26 December 2021
   -  Announcement of selected talks: 31 December 2021
   -  Conference dates 5 & 6 February 2022 online
   -  Geospatial devroom date: Sunday 6 February 2022 online

Desirable topics

The Geospatial devroom aims to host talks about all geospatial topics,
GIS,  geodata projects and open data. The talks can cover the following
subjects:

- New geo FOSS projects
- Update of existing geo FOSS projects
- User cases using geo FOSS
- Open Geodata or VGI data project
- News about Standards

Practical

General details

- The default duration for talks is about 45 minutes including
discussion.
- If you plan to register your proposal in several tracks to increase
your chances, don’t ! Register your talk once, in the most accurate
track.
- If the Geospatial devroom is not your first choice, just let us
know, and give us a chance to save you a slot.
- Presentations has to be pre-recorded and streamed before the event.

For accepted talks

- Once your talk was accepted, we will assign you a deputy to help
you to produce the pre-recorded content.
- The deputy will review the content and ensure it has the required
quality. The deputy is also responsible to ensure the content is into
the system and ready to broadcast.
- During the stream of your talk, you must be available online for
the Q/A session.

Submit a talk

Visit the FOSDEM 2022 Pentabarf website (see account creation bellow)
https://penta.fosdem.org/submission

Create an “event” and click on “Show all” in the top right corner to
display the full form.

Your submission must include the following information

Your contact Email

- The title and subtitle of your talk (please be descriptive, as
titles will be listed with ~500 from other projects) select “Geospatial
devroom” as the track.
- A short abstract of one paragraph
- A longer description if you wish to do so
- Links to related websites / blogs etc.

Account creation

If you already have a Pentabarf account, please don’t recreate a new
one.

If you forgot your password, reset it. If not, follow the instructions
to create an account.


Contact Us

- Twitter: @osgeo
- Contact Email:

[GRASS-dev] help with completing GRASS 8 new features wiki

[Veronica Andreo]

Dear all,

As we now have grass 8 branch and we approach the date for RC1 release, I
kindly ask your help to fill in the new features page:
https://trac.osgeo.org/grass/wiki/Grass8/NewFeatures80

We happily welcome text snippets and screenshots to highlight the new and
exciting changes that will come with GRASS 8 as well as bug fixing,
improvements, new modules, library changes, etc. These can then be recycled
to create more posts for social media ;-)

Thanks much in advance!
Vero
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] PSC meeting minutes - November 12, 2021

[Veronica Andreo]

Dear all,

Have a look the PSC meeting minutes of our recent meeting on November 12,
2021:
https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_2022

Topics covered:
- Decide a fixed day and hour for PSC meetings
- GRASS GIS 8 release schedule
- GRASS plugin in QGIS
- Budget - discuss student grants
- Presence in social media
- rgrass8
- Website

Thanks everyone!

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

Re: [GRASS-dev] [GRASS-user] gui not working in 7.9 after debian uprade to bullseye

[Veronica Andreo]

Hi Frank,

Did you `make distclean`, configure and recompile your grass79 after the
system upgrade?
Also, maybe update your local copy as there have been changes.

So, if you only did a simple git clone to get the source code and compile,
then:
make distclean
git fetch --all --prune && git checkout main && git pull && sh
conf_grass_dev.sh && make

## Note we now also have a releasebranch_8_0 :)
## conf_grass_dev.sh is my configuration script

my 0.2 cents

Vero

El jue, 18 nov 2021 a las 9:56, Frank David ()
escribió:

> Hello,
>
> I have upgraded my distro from debian buster to bullseye. I had two grass
> release installed installed : 1- grass 7.8.5 from repository, still works
> fine. 2- a grass 7.9 compiled. When I run this one I get this message :
>
> Lancement de l'interface graphique  en tâche de fond, merci de
> patienter ...
> GRASS 7.9.dev (France_L93):~ > free(): double free detected in tcache 2
> Impossible de déterminer la version de GRASS
> free(): double free detected in tcache 2
> Traceback (most recent call last):
>   File "/usr/local/grass79/scripts/g.extension", line 2177, in 
> version = grass_version['version'].split('.')
> KeyError: 'version'
> free(): double free detected in tcache 2
> Traceback (most recent call last):
>   File "/usr/local/grass79/gui/wxpython/wxgui.py", line 106, in OnInit
> mainframe = GMFrame(parent=None, id=wx.ID_ANY,
>   File "/usr/local/grass79/gui/wxpython/lmgr/frame.py", line 143, in
> __init__
> self.notebook = self._createNoteBook()
>   File "/usr/local/grass79/gui/wxpython/lmgr/frame.py", line 337, in
> _createNoteBook
> self.goutput = GConsoleWindow(
>   File "/usr/local/grass79/gui/wxpython/gui_core/goutput.py", line 118, in
> __init__
> self.cmdPrompt = GPromptSTC(parent=self, menuModel=self._menuModel)
>   File "/usr/local/grass79/gui/wxpython/gui_core/prompt.py", line 138, in
> __init__
> GPrompt.__init__(self, parent=parent, menuModel=menuModel)
>   File "/usr/local/grass79/gui/wxpython/gui_core/prompt.py", line 56, in
> __init__
> self.mapList = self._getListOfMaps()
>   File "/usr/local/grass79/gui/wxpython/gui_core/prompt.py", line 100, in
> _getListOfMaps
> result['raster'] = grass.list_strings('raster')
>   File "/usr/local/grass79/etc/python/grass/script/core.py", line 1347, in
> list_strings
> for line in read_command("g.list",
>   File "/usr/local/grass79/etc/python/grass/script/core.py", line 565, in
> read_command
> return handle_errors(returncode, stdout, args, kwargs)
>   File "/usr/local/grass79/etc/python/grass/script/core.py", line 392, in
> handle_errors
> raise CalledModuleError(module=module, code=code,
> grass.exceptions.CalledModuleError: Module run g.list g.list --q -m
> type=raster ended with error
> Process ended with non-zero return code -6. See errors in the (error)
> output.
> OnInit returned false, exiting...
> Error in atexit._run_exitfuncs:
> wx._core.wxAssertionError: C++ assertion "GetEventHandler() == this"
> failed at ../src/common/wincmn.cpp(477) in ~wxWindowBase(): any pushed
> event handlers must have been removed
>
> Do you have an idea to solve this problem ?
>
> Thank you
>
> Frank
> ___
> grass-user mailing list
> grass-u...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] addon r.area.createweight not available?

[Veronica Andreo]

Hi Charlotte,

I have now added all new addons to the News page:
https://trac.osgeo.org/grass/wiki/Release/7.8.6-News#NewAddonssinceGRASS7.8.5.
I overlooked that before, sorry about that.

Please note that the page it's just a wiki, so everyone can contribute
there, and everyone is encouraged to do so when they add new modules, new
features to existing modules or fix bugs.

Best wishes,
Vero


El mar, 19 oct 2021 a las 9:20, FLASSE Charlotte via grass-dev (<
grass-dev@lists.osgeo.org>) escribió:

> Dear all,
>
> I was expecting the add-on r.area.createweight to be included with the
> 7.8.6 release of GRASS, but it does not appear either in the 'new addons'
> list on the summary of changes
>  page, nor is it
> possible to add with g.extension.
>
> Was wondering what the issue might be ?
>
> Thanks,
>
> Charlotte
> ___
> 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

[GRASS-dev] GRASS GIS 7.8.6 released

[Veronica Andreo]

*GRASS GIS 7.8.6 released*

This is an update release of the GRASS GIS 7.8 series.

Download source code tarball at

   - https://grass.osgeo.org/grass78/source/grass-7.8.6.tar.gz
   - https://grass.osgeo.org/grass78/source/grass-7.8.6.md5sum

For further release details (bug fixes and enhancements), see

   - https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures78
   - https://trac.osgeo.org/grass/wiki/Release/7.8.6-News

The GRASS GIS 7.8.6 release provides more than 140 fixes and improvements

with respect to the release 7.8.5. Most importantly, this release comes
with a critical bugfix: the addon extension manager has been updated to
match the new addon repository structure which solves issues found when
installing addons in UNIX-like systems.

Visit the release page 
to download the source code of GRASS GIS 7.8.6.

Thanks to all contributors!
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Release of 7.8.6 ?

[Veronica Andreo]

Great news!!! Thanks a lot Martin! I'll check the links and prepare the
announcement and social media posts tomorrow (holiday today + traveling)

@Michael Barton  will you prepare Mac binaries?

Cheers,
Vero


El lun., 11 oct. 2021 08:35, Moritz Lennert 
escribió:

> Great news ! Thanks a lot for all your work, Martin !
>
> Moritz
>
> Le 11 octobre 2021 13:14:45 GMT+02:00, Martin Landa <
> landa.mar...@gmail.com> a écrit :
> >Dear all,
> >
> >čt 7. 10. 2021 v 23:21 odesílatel Veronica Andreo 
> napsal:
> >>> > Let's release 7.8.6 as it is (with an already big delay). If there
> are
> >>> > no objections I will prepare a 7.8.6 release in upcoming days. Martin
> >>
> >>
> >> Big +1!!
> >
> >7.8.6 is out [1]!
> >
> >* trac page updated [2] - feel free to improve
> >* PR for website prepared [3] - please contribute/review (we need a
> >new fancy screenshot for announcement)
> >* WinGRASS binaries 64 ready for testing (standalone installer [4] and
> >osgeo4w v2 [5])
> >* WinGRASS addons build activated [6]
> >
> >What is missing:
> >
> >* wingrass 32bits (will do it today)
> >* ubuntugis unstable (will do in next days)
> >* do marketing [7]
> >
> >Martin
> >
> >[1] https://github.com/OSGeo/grass/releases/tag/7.8.6
> >[2] https://trac.osgeo.org/grass/wiki/Release/7.8.6-News
> >[3] https://github.com/OSGeo/grass-website/pull/271
> >[4]
> https://grass.osgeo.org/grass78/binary/mswindows/native/x86_64/WinGRASS-7.8.6-1-Setup-x86_64.exe
> >[5] http://download.osgeo.org/osgeo4w/v2/osgeo4w-setup.exe
> >[6] https://wingrass.fsv.cvut.cz/grass78/x86_64/addons/grass-7.8.6/logs/
> >[7]
> https://github.com/OSGeo/grass/blob/main/doc/howto_release.md#marketing---tell-others-about-release
> >
> >--
> >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 mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Release of 7.8.6 ?

[Veronica Andreo]

Hi all :)

El jue., 7 oct. 2021 17:08, Nicklas Larsson via grass-dev <
grass-dev@lists.osgeo.org> escribió:

>
> > On Thursday, 7 October 2021, 21:57:03 CEST, Martin Landa <
> landa.mar...@gmail.com> wrote:
> >
> > Let's release 7.8.6 as it is (with an already big delay). If there are
> > no objections I will prepare a 7.8.6 release in upcoming days. Martin


Big +1!!

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

Re: [GRASS-dev] Community sprint at FOSS4G 2021

[Veronica Andreo]

Hey Moritz,

We are in the code sprint room with Vashek and Anna. Join!

Vero


El sáb, 2 oct 2021 a las 13:34, Moritz Lennert (<
mlenn...@club.worldonline.be>) escribió:

> Hi all,
>
> I wanted to at least pop by and say hi, but I don't see anyone on the
> map in the code sprint room. There are four different jitsi meeting
> rooms in that map, but only one is currently used.
>
> If we decide to use another Jiitsi link for GRASS GIS discussions, we
> are asked to include that into the wiki (and ideally also post it in the
> Code sprint channel on the foss4g venueless site.
>
> So, is anyone currently somewhere ? :-)
>
> Moritz
>
> On 2/10/21 10:32, Stefan Blumentrath wrote:
> > Hi,
> >
> > It`s autumn holiday around Oslo/Norway, so I will be a bit on and off
> > today (unfortunately more off than on), but try to join at least in the
> > European evening…
> >
> > Main aim for the community sprint for me would be to get a GRASS 8.0
> > packaged in OSGeo4W. Without PDAL support that is very close, but I
> > really think not having PDAL support on MS Windows would be sad.
> >
> > So, if anybody with C++ build experience (and maybe build experience on
> > MS Win) would be available for a chat about possible paths to achieve
> > that, I would be very glad. Please get in touch.
> >
> > If I find the time I will likely work on some of my stale PRs …
> >
> > That said, I briefly joined
> > https://play.workadventu.re/@/osgeo/foss4g/codesprint
> > 
> >
> > But no one seems to be there at the moment…
> >
> > Is there a Jitsi (or similar) room to meet? A chat maybe?
> >
> > Cheers
> >
> > Stefan
> >
> > *From:*grass-dev  *On Behalf Of
> *Wolf
> > Bergenheim
> > *Sent:* fredag 1. oktober 2021 16:32
> > *To:* Ondřej Pešek 
> > *Cc:* grass-dev@lists.osgeo.org
> > *Subject:* Re: [GRASS-dev] Community sprint at FOSS4G 2021
> >
> > European morning works for me. Will be in and out, though. Mainly I'm
> > looking for opportunities to contribute after 10 years away :P
> >
> > --Wolf
> >
> > *-- *
> >
> > * ^.___*
> >
> > *( ,__/
> > / / Wolf Bergenheim*
> >
> > On Fri, 1 Oct 2021 at 09:31, Ondřej Pešek  > > wrote:
> >
> > Ciao,
> >
> > st 29. 9. 2021 v 23:04 odesílatel Vaclav Petras
> > mailto:wenzesl...@gmail.com>> napsal:
> >
> > We are having a community sprint on Saturday, October 2nd, 2021.
> >
> > Is anybody interested in working together during the European
> > morning instead of waiting for the conference day to start?
> >
> > I wanted to make a quick visit in the European morning, but just to
> > do something with the addons (as the grass8 branch is going to be
> > created for the sprint, right?). Maybe in the end I'll do also some
> > source GRASS work, but I am still not sure if I'll have enough time
> > for that.
> >
> > ___
> > grass-dev mailing list
> > grass-dev@lists.osgeo.org 
> > https://lists.osgeo.org/mailman/listinfo/grass-dev
> > <
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.osgeo.org%2Fmailman%2Flistinfo%2Fgrass-dev=04%7C01%7CStefan.Blumentrath%40nina.no%7C6a48db276d984bc346b008d984e83527%7C6cef373021314901831055b3abf02c73%7C0%7C0%7C63768690921156%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000=i3kjIPbpthAzR%2BH6qtNqFYh4aAeuX4RT98o06JzGREg%3D=0
> >
> >
> >
> > ___
> > 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
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: [GRASS-web] New GIS mirror in Rabat, Morocco

[Veronica Andreo]

Internal links work now. Still, to have to do an extra click to get to the
grass site mirror seems odd. I agree that maybe an extra step is needed or
just a redirect from https://mirror.marwan.ma/grass/ to the actual site at
https://mirror.marwan.ma/grass/html

The only thing I found is what's already in the website:
https://grass.osgeo.org/contribute/ but I guess they have followed that
procedure already

Vero

El sáb, 18 sept 2021 a las 14:12, Moritz Lennert (<
mlenn...@club.worldonline.be>) escribió:

> FYI
>
> I think this needs some configuration because to get to the web site you
> need to go to https://mirror.marwan.ma/grass/html, but then none of the
> internal links work.
>
> Does someone have more experience with mirroring than me and can give
> some hints here ?
>
> Moritz
>
>  Forwarded Message 
> Subject: [GRASS-web] New GIS mirror in Rabat, Morocco
> Date: Fri, 17 Sep 2021 11:11:37 +0100
> From: Sami Ait Ali Oulahcen 
> To: grass-...@lists.osgeo.org
>
> Hi,
>
> We're mirroring GIS at https://mirror.marwan.ma/grass/
> We’re offering http, https, and rsync. The mirror is ipv4/ipv6 capable,
> and running behind a 5Gbps link.
> Institution: MARWAN
> Website: marwan.ma
> Technical contact: n...@marwan.ma
>
> Regards,
> Sami
> ___
> grass-web mailing list
> grass-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-web
> ___
> 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] GRASS releases: Let's meet to discuss/coordinate them!

[Veronica Andreo]

Dear all,

Thanks a lot for your participation yesterday! Also, a special thanks to
MarkusN for joining from hospital! It was really nice to see you, Markus!

Since we set FOSS4G as deadline, let's also complete these News pages in
trac:
- https://trac.osgeo.org/grass/wiki/Release/7.8.6-News
- https://trac.osgeo.org/grass/wiki/Grass8/NewFeatures80

The 7.8.6 page is pretty much done, but *the 8.0 page needs a lot of love*
:)
So, let's all add text snippets and screenshots about the new cool features
that will be delivered with GRASS 8

Thanks again!
Cheers,
Vero



El mar, 14 sept 2021 a las 20:01, Vaclav Petras ()
escribió:

> Starting in 1 hour. Here is the link to the call.
>
> https://ncsu.zoom.us/j/96809444905?pwd=VlY5ajZneDhWaUlVZUtFKzFvdWpEdz09
>
> On Fri, Sep 10, 2021 at 9:37 AM Veronica Andreo 
> wrote:
>
>> Dear all,
>>
>> Next Tuesday, September 14th at 21:00 CEST [1] we'll (videocall) meet to
>> discuss/coordinate upcoming GRASS GIS releases. You are all welcome to join
>> and contribute :)
>>
>> The link for the meeting will be shared in this thread soon before the
>> meeting.
>>
>> Looking forward to seeing you
>>
>> Have a great weekend!
>> Vero
>>
>> [1]
>> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021=9=14=19=0=0=485=207=48=25=197
>> ___
>> 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

[GRASS-dev] GRASS releases: Let's meet to discuss/coordinate them!

[Veronica Andreo]

Dear all,

Next Tuesday, September 14th at 21:00 CEST [1] we'll (videocall) meet to
discuss/coordinate upcoming GRASS GIS releases. You are all welcome to join
and contribute :)

The link for the meeting will be shared in this thread soon before the
meeting.

Looking forward to seeing you

Have a great weekend!
Vero

[1]
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021=9=14=19=0=0=485=207=48=25=197
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] nc_spm_08_grass8?

[Veronica Andreo]

Hi Anna, all

Good point! Thanks for raising this!

Seems we are all trying to better understand band references and how they
integrate with existing functionality :)  In
https://github.com/OSGeo/grass/pull/1844/ we discuss temporal framework and
band references.

Indeed, we have a problem if all examples using Landsat will stop working
in grass 8, so if this is the case, then we might need a new version of the
sample data which by the way might also include the MODIS LST mapset (~10
Mb) to do some time series stuff.

In my opinion, band reference should be something optional, no? On the
other hand, I think I understood from Maris that with r.support we could
add band references and that the restrictions were relaxed but these
changes are not yet documented. There's this thread:
https://lists.osgeo.org/pipermail/grass-dev/2021-September/095377.html

Band references need some further discussion IMHO

my 2 cents
Vero

El mié, 8 sept 2021 a las 20:56, Anna Petrášová ()
escribió:

> Hi devs,
>
> given the changes with bands (which I still don't fully understand) do we
> need to have a new sample dataset, in which the landsat scenes have bands?
> Context: I was playing with basic classification examples (g.gui.iclass,
> i.gensigset) and apparently it doesn't work and it's giving me error:
>
> Raster map  lacks band reference
>
> So my questions are:
>
> 1. Is that expected behavior? Seems little strict to me.
> 2. If yes, then what do I do when working with other data than Landsat,
> Sentinel, etc - g.bands doesn't currently support user-defined references.
> 3. Also, if yes, do we need a sample dataset for GRASS8 then? Otherwise
> any examples with landsat fail.
>
> Sorry if I misunderstood anything.
>
> Thanks,
> Anna
> ___
> 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] GSoC Final Report: Improved Integration of GRASS GIS and Jupyter Notebooks

[Veronica Andreo]

Dear Caitlin,

Thanks for such a nice report and for your contribution to GRASS by making
it easier to integrate with Jupyter. This is a great improvement!

Once again, huge thanks to your mentors Vaclav, Helena and Stefan for their
dedication and for their commitment to the project!! Great team!

We look forward to seeing your contributions after GSoC! Welcome onboard!

All the best,
Vero

ps: apologies for the delay in getting your email through, luckily we
managed now

El dom, 29 ago 2021 a las 16:56, Caitlin Haedrich (<
caitlin.haedr...@gmail.com>) escribió:

> Hello all,
>
> Here is my final report on my GSoC project, Improved Integration of GRASS
> GIS and Jupyter Notebooks. Thank you to all who provided comments, feedback
> and tested my work in Binder. Also, a *huge* thank you to my mentors
> Vaclav Petras, Helena Mitasova and Stefan Blumentrath.
>
> You can find a more detailed version of this report on the wiki page:
> https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS
>
> You can also test out grass.jupyter, the subpackage I wrote this summer,
> from your browser in Binder here:
> https://mybinder.org/v2/gh/OSGeo/grass/c173461?urlpath=lab%2Ftree%2Fdoc%2Fnotebooks%2Fgrass_jupyter.ipynb
>
> Best,
> Caitlin
>
> *Improved Integration of GRASS GIS and Jupyter Notebooks*
>
> *Abstract:*
> This project introduces a new subpackage for GRASS GIS, grass.jupyter that
> improves the integration of GRASS GIS with Jupyter Notebooks. The
> grass.jupyter subpackage introduces a new startup function, init(), and two
> display classes, GrassRenderer and InteractiveMap, specifically for making
> the usage of GRASS in Jupyter more simple and intuitive. GrassRenderer
> renders GRASS maps as PNG images and InteractiveMap displays rasters and
> vectors interactively with folium [1], a leaflet library for Python.
>
> *The state of integration BEFORE GSoC:*
> The previous integration of GRASS GIS and Jupyter Notebooks required a
> cumbersome environment variable setup after launching GRASS from within the
> notebook. There is an external python library grass_session that can be
> installed to shorten this launch substantially but, as an external library,
> it is not included in a typical GRASS install. Additionally, maps were
> rendered as PNG images using a relatively unintuitive sequence: calling
> d.erase, then modules from the display family and finally rendering the
> image with IPython.display.Image(). There was also no simple way to zoom or
> toggle between layers.
>
> *The state of integration AFTER GSoC:*
> With the help of my mentors, I introduced a new package grass.jupyter that
> contains a new init() function to shorten the launch and two
> display-related classes, GrassRenderer and InteractiveMap. GrassRenderer
> wraps the previous approach, rendering PNG images but with a more intuitive
> syntax. InteractiveMap, the other display-related class in `grass.jupyter`,
> allows users to view GRASS vectors and rasters in folium, a leaflet library
> for Python. After creating an instance of InteractiveMap, users can add
> vectors and rasters with add_vector() and add_raster(). Users can also add
> a layer control element with add_layer_control().
>
> *Conclusion:*
> In this project, I was successful in accomplishing the three goals stated
> at the beginning (thanks to my mentors!):
>
>1. creating new initiation functions for the launch of GRASS GIS in
>Jupyter Notebooks (init())
>2. creating functions for more intuitive map display (GrassRenderer)
>3. introducing an interactive map display function (InteractiveMap)
>
> I am grateful for the support I've received this summer and for the
> opportunity to contribute to GRASS GIS. I'm looking forward to continuing
> to improve `grass.jupyter`.
>
> *Future Work:*
>
>- Height and width defaults in `GrassRenderer` should be derived from
>computational region
>- init() should fail and report an appropriate error if a mapset that
>doesn't exist is provided
>- Add folium Tooltip method to InteractiveMap, allowing users to
>access vector attribute data by clicking on feature
>- Add simpleCRS option to add_raster method in InteractiveMap
>- Improve color options in InteractiveMap
>- Add option to display rasters as vectors (pixels -> polygon) in
>InteractiveMap
>- Clip vectors to computational region in InteractiveMap (currently
>the whole vector dataset is displayed)
>- Add more interactive functions such as a timeline slider for
>temporal datasets
>- InteractiveMap doesn't allow users to fully access folium. In the
>future, a new interface that allows users direct access to folium should be
>added. For example, it could look like:
>gj.Raster("elevation").add_to(folium_map)
>
> *Permanent Links:*
> *OSGeo Wiki Page:*
> https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS
> *OSGeo-GRASS github project page:*
> https://github.com/OSGeo/grass/projects/7
> *Github repo*:
> 

[GRASS-dev] News from Markus Neteler

[Veronica Andreo]

Dear all,

I'm writing on behalf of Markus. He wants all of you to know the reason for
his absence.

Some of you know already, but Markus had a stroke around a month ago and
went through brain surgery around 10 days ago to drain the hematoma because
he started having issues speaking and he dropped things from his hands.
This is the reason he has been offline all this time.

After the surgery, he was completely offline until today when he started
typing a few  text messages with quite some difficulty. He is in an
intermediate care unit with monitors and sensors. He said he has a good
appetite and with help he has started walking a little bit around the
alleys in the hospital. So, he is recovering, but the process is slow and
it will take time. He still does not remember certain things.

Let's send the best vibes and thoughts for a good recovery and let's all
keep pushing GRASS forward ;-)

Best wishes and take care all, please.
Vero
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Renaming master branch to main branch

[Veronica Andreo]

Well, since addon repo structure changed and master is no longer used as
base branch, but grass7, and eventually it will be grass8, the name change
does not seem very relevant or urgent there, no?

Not strong opinion though

Vero

El mié, 25 ago 2021 a las 21:21, Nikos Alexandris ()
escribió:

> Thank you Vaclav.
>
> Will the same name-update happen for the addons?
>
> Nikos
> ___
> 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] GSoC 2021: Final report: First steps towards a new GRASS GIS Single-Window GUI

[Veronica Andreo]

Dear Linda,

Thanks for such a detailed final report and for all your contributions to
make GRASS GUI easier and straightforward for users, especially first time
users! And thanks much for this cool new experimental single window GUI,
I'm eager to test :)

Once again, huge thanks to your mentors Anna, Vaclav, Stefan and Martin for
their dedication and for their commitment to the project!! Great team!

I'm sure we'll keep seeing your contributions after GSoC!

All the best,
Vero


El dom, 22 ago 2021 a las 20:15, Linda Kladivová ()
escribió:

> Hello everyone,
>
>
> I am sending my Final GSoC report. The more detailed version with
> permanent links on GitHub PRs and with several screenshots can be found at
> the project wiki:
> https://trac.osgeo.org/grass/wiki/GSoC/2021/SingleWindowLayout#FinalReport
> .
>
> *Abstract:*
> The project was focused mainly on the extensive Graphical User Interface
> refactoring necessary to prepare GRASS for Single-Window GUI. In addition
> to a good programming base, the simple working Single-Window GUI prototype
> was built in a parallel environment. This Single-Window frame largely
> copies the design (mockup) which the author had proposed for the GSoC
> application (see ​
> [1]).
> All main functionality will be put into operation after the successful
> merge of PR [2] and PR [3]. However,
> to completely replace the current Multi-Window GUI solution, many other
> improvements are still expected.
>
>
> *The state of the art BEFORE the start of GSoC:*
> Although the GRASS GUI has been enriched with many new features since last
> year, the basic Multi-Window GUI concept used in all historical GRASS
> versions has been preserved. As the name suggests Multi-Window GUI consists
> of several windows (frames) - the control window and additional separate
> map display windows. The control window includes a notebook containing 5
> tabs in a standard 2D map view - Data, Display, Modules, Console, and
> Python.
>
>
> *The state of the art AFTER GSoC:*
> A large part of the project was focused on GUI refactoring. The core work
> had to be done all at once in the PR ​
> [2] and since it overturns the
> core logic of map display widgets, it was decided to merge it after GSoC
> when the GRASS 8 will be released. To sum it up, we are probably not
> entirely done with the refactoring, but the main part was managed.
>
> In addition, a Single-Window GUI prototype has been coded in a parallel
> environment. I with help of my mentors handled to get to the stage where
> most of the functions are working. There is just missing completion of PR
> [3] and possible check/fix of workspaces functioning. It is important to
> emphasize here that I'm talking about basic functionality. To provide a
> really user-friendly environment, many other things will have to be changed
> or reprogrammed. All those steps are summed up in the "Next steps"
> paragraph.
>
>
> *Conclusion:*
> To follow the project idea I wrote for the GSoC application, I succeeded
> (with help of my mentors) to provide the first steps for a new era of
> Single-Window GUI. Those steps have a form of refactoring as well as a new
> parallel simple Single-Window GUI prototype. I believe it's one big step
> forward and I am looking forward to further development of which I would
> like to be a part.
>
>
> *Next Steps:*
> All these following points assume that the main functionality is working.
> In other words, we must have a merged main refactoring PR [2] and a merged
> PR [3]  aiming at the
> implementation of the AuiNotebook closing event. Then several improvements
> are possible (and probably necessary):
>
>- Enable undocking the Map Display notebook tab to a separate window.
>It will allow each user to use the Single-Window GUI as the Multi-Window
>GUI.
>- Fix switching to the Console pane in an automatic notebook if any
>information is written there.
>- Check/test if workspaces are functioning properly.
>- Focus on a newly added Map Display tab in the Display pane (now it
>may not be clear at first glance that it has been added).
>- Modify the appearance for the dark mode. Some parts are ugly and
>illegible (names of AuiNotebook tabs, names of panes, ugly gradients etc.).
>- Add the option for starting GRASS as the Single-Window GUI => we
>want GRASS geeks to try it out. :-)
>
> Other improvements mainly concern the organization of widgets and possible
> ideas for the future:
>
>- It is necessary to change the rendering of the 3D View panel. Now
>the 3D View pane is added as another panel under the Display tab - very
>problematic in terms of space.
>- A part of the Console pane in the startup Single-Window layout is
>not visible. We should completely reorganize the Console tab, 

Re: [GRASS-dev] [SoC] GSoC 2021 - Final Report [Parallelization of raster modules for GRASS GIS]

[Veronica Andreo]

Dear Aaron,

Thanks for your report and all your work to make GRASS raster modules run
faster, we like that :) Huge thanks as well to Vaclav, Huidae and Maris for
their commitment to the project and mentoring! You all did a great team
work!

One question: are these changes planned to be merged before the creation of
grass 8 branch or will they remain for 8+? Maybe add a milestone to
clarify?
One minor observation: all links currently point to the same PR

We hope to keep seeing you around, Aaron!

All the best,
Vero

El mar, 24 ago 2021 a las 3:18, Aaron Saw Min Sern ()
escribió:

> Hello everyone,
>
> Here is my final report for GSoC 2021 project, *Parallelization of Raster
> Modules for GRASS GIS*.
>
> *Abstract*
> The goal of this project is to introduce parallelization to existing
> raster modules in GRASS GIS using OpenMP. This will allow users to take
> advantage of more cores in their hardware to speed up the computation time
> especially for large raster files with large computation cost. The key
> challenge of this project is to separate the parallelizable components from
> the sequential part of the modules without introducing too much overhead in
> terms of memory, disk or computation resources
> *. *
>
> *Milestones*
>
> In total, I have introduced OpenMP support to 8 raster modules in GRASS
> GIS. The pull requests to each module are as follows:
>
>- r.univar - https://github.com/OSGeo/grass/pull/1634
>- r.neighbors - https://github.com/OSGeo/grass/pull/
>1724
>
>- r.mfilter - https://github.com/OSGeo/grass/pull/
>1708
>
>- r.resamp.filter - https://github.com/OSGeo/grass/pull/
>1759
>
>- r.resamp.interp - https://github.com/OSGeo/grass/pull/
>1771
>
>- r.slope.aspect - https://github.com/OSGeo/grass/pull/
>1767
>
>- r.series - https://github.com/OSGeo/grass/pull/
>1776
>
>- r.patch - https://github.com/OSGeo/grass/pull/
>1782
>
>
> Firstly, I have greatly underestimated the complexity of the work. Up to
> 20 modules were initially proposed at first but after the second week.
> However, it became clear that we had to cut down on the number of target
> modules and focus more on designing the algorithms. The modules we targeted
> behave differently as compared to some modules that had received OpenMP
> support in the past such as *r.sun*. In particular, the modules need to
> keep the same of behavior of having low memory footprint even after the
> parallelization, unlike *r.sun* which loads the entire raster map
> in-memory.
>
>
> During the first half of the GSoC, with the mentors’ discussion, we have
> come out with three different approaches to introducing parallel support to
> *r.neighbors*. After benchmarking their performance and taking account of
> their memory/disk usage, we decided to settle with the last approach which
> requires us to add an extra parameter *memory* to allow users to adjust
> their memory consumption. With this approach, we have to allow the modules
> to process the raster map by chunks. Once we settled about the design, we
> started applying the same approach to other similar modules with low memory
> footprints.
>
> For more information regarding the implementation, see
> https://grasswiki.osgeo.org/wiki/Raster_Parallelization_with_OpenMP.
>
> Furthermore, test scripts were included in the modules to ensure the
> consistency of the results. Benchmark scripts were added to allow users to
> easily benchmark the performance of the parallelization to monitor the
> speedup in their own local machine. User documentations were also modified
> to include sections detailing how to make use of the newly added features.
>
> *Future Work*
>
> In the future, more raster modules can be parallelized using similar
> approach. Then, we can consider tackling more complex modules such as
> *r.watershed* and *r.mapcalc*. Also, we could consider exploring 3D
> raster modules as well.
>
>
> Furthermore, when we implement parallelization for *r.univar*, we notice
> that modules that produce statistics involving arithmetic can often have
> floating point discrepancies when dealing with large summation. Because of
> this, computation using different number of threads will now produce
> different results due to having different order of arithmetic. One idea
> would be to introduce *Kahan Summation algorithm* to reduce the
> 

Re: [GRASS-dev] Fwd: [OSGeo AGM 2021] [Action required] GRASS GIS upload link please upload your video till August 30

[Veronica Andreo]

Dear Helena,

Yes, we completed the slide during the GRASS b'day meeting, and I
volunteered to record the video, remember? We have time till August 30th.

I'll make the first attempt tomorrow including maybe images from GSoC
projects that Linda, Caitlin and Aaron shared with me for the Twitter
threads. Wish me luck ;)

Vero

El sáb, 21 ago 2021 a las 5:35, Helena Mitasova ()
escribió:

> I am not sure whether this was discussed already or anybody from PSC knows
> about this but we need to prepare
> a short 1 minute video about GRASS updates for FOSS4G AGM - see more
> details below and here
> https://wiki.osgeo.org/wiki/Annual_General_Meeting_2021
>
> I checked the slides and GRASS project is updated (thanks Vasek?) so that
> is done, now we need the video.
> I think that adding 2 narrated slides with some nice
> images/photos/animations would be great and we will
> need a volunteer to record.
>
> I shared google slides with you - it has the AGM slide and 2 additional as
> template - feel free to add material keeping
> in mind that it should be 1 minute.
>
> Thanks a lot, Helena
>
> Begin forwarded message:
>
> *From: *"Astrid Emde (OSGeo Secretary)" 
> *Subject: **[OSGeo AGM 2021] [Action required] GRASS GIS upload link
> please upload your video till August 30*
> *Date: *August 16, 2021 at 11:56:17 AM EDT
> *To: *Markus Neteler , hmit...@ncsu.edu
> *Reply-To: *secret...@osgeo.org
>
> Hello Markus, hello Helena,
>
> we invite you and your team to present the GRASS GIS project at the OSGeo
> AGM 2021.
>
> This year we will publish the OSGeo AGM video in advance of FOSS4G [1].
>
> You find all important information about the AGM at [5].
>
>
> Video upload link
> ---
> Please use the following upload link to upload your video (Deadline
> 2021-08-30)
>
> https://vortraege.fossgis.de/u/d/b87f9e4fef7b434a839a/
>
> Timeline
> ---
> - 2021-08-30: upload your video and update the AGM slides [2]
> - 2021-09-10: AGM 2021 complete video will be published
> - 2021-10-01: 11h Argentinian Time Zone (14:00 UTC) Join the OSGeo AGM
> 2021 meeting at FOSS4G [3] [4]
>
> If you have questions or problems with the upload of your video please let
> us know secretary (at) osgeo (dot) org.
>
> Stay safe,
>
> Astrid Emde
> OSGeo Secretary
>
> [1] https://www.youtube.com/channel/UCDvJEf8hXbyeVqaYaS8sLvw
> [2]
> https://docs.google.com/presentation/d/1brbBb7-sKRI6U4dZ7LKnBT_-NnWzyS2TaZqVXzy8RDo/edit#slide=id.p4
> [3] https://callforpapers.2021.foss4g.org/foss4g2021/talk/WDEW3P/
> [4]
> https://www.timeanddate.com/worldclock/meetingdetails.html?year=2021=10=1=14=0=0=51=26=49=155=217=312=250=71=248=240
> [5] https://wiki.osgeo.org/wiki/Annual_General_Meeting_2021
>
> --
>
> -
> Astrid Emde
> OSGeo Board Member and OSGeo Secretary
> Open Source Geospatial Foundation
> https://www.osgeo.org/member/astrid-emde/
> astrid_e...@osgeo.org
>
>
> Helena Mitasova
> Professor, Department of Marine, Earth and Atmospheric Sciences
> Faculty Fellow,
> Center for Geospatial Analytics
> North Carolina State University
> Raleigh, NC 27695-8208
> hmit...@ncsu.edu
>
>
>
> ___
> 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] [release planning] GRASS GIS 8: create new release branch

[Veronica Andreo]

Hi all,

El vie, 6 ago 2021 a las 4:29, Vaclav Petras ()
escribió:

> Are we ready to create the 8.0 release branch?
>

Seems we are!!

Once we create it, we will need to backport (cherry-pick) updates from the
> master branch when needed.
>
> Please see the following for the individual issues we still have and post
> here if you see some priorities.
>
> On Wed, Jul 14, 2021 at 5:24 PM Vaclav Petras 
> wrote:
>
>>
>>
>>> Windows build & test is just bad (no bug or PR so far?),
>>
>>
>> Can someone give an update on that, please?
>>
>
>
>> #1683 is not merged yet, but missing sh in the test environment is not a
>> blocker in this case.
>>
>
> https://github.com/OSGeo/grass/pull/1683
>
> Tests are running!
>
>
>>  CentOS is too
>>
>>> old (#1709) & needs auto tools update to fix it (or at least env
>>> variable in build script as I just have done to enable testing in
>>> #1501),
>>
>>
>> ...or CentOS 8, CentOS Stream, or remove the CentOS test.
>>
>> https://github.com/OSGeo/grass/issues/1709#issuecomment-880215427
>>
>
> It would be better if Autotools are updated, but CentOS build works now.
> Are there any pressing issues?
>
>
>> I would also strongly advocate merging ctypes upgrade before 8.0
>>>
>>
>> Seems to be close to being finished too.
>>
>
> ctypes update is closer everyday, but not finished yet. Maybe not needed
> for 8.0?
>
> https://github.com/OSGeo/grass/pull/1651
>

Milestone was changed to 8.2 and Nicklas suggest to move forward with
release branch 8

>
> On Wed, Jul 28, 2021 at 4:28 AM Maris Nartiss  wrote:
>
>> 2021-07-27 18:26 GMT+03:00, Vaclav Petras :
>> >
>> > From what has the milestone 8.0 and is not mentioned below and is
>> major, I
>> > see only #1454 and #1501 which are related to band references. Maybe we
>> > should again consider reverting the band references in order to get 8.0
>> out
>> > or how do you see the status of #1454 and #1501, Martin and Maris?
>> >
>> > https://github.com/OSGeo/grass/milestone/4
>> > https://github.com/OSGeo/grass/pull/1454
>> > https://github.com/OSGeo/grass/pull/1501
>>
>> For #1454 the main remaining (and unsolvable) issue is semantics of a
>> mapset layout and its management functions. I just commited a more
>> clean workaround and thus it should be ready for a merge. A proper
>> solution will have to wait for GRASS 9 when we could reorganize mapset
>> structure and thus also clean-up naming, handling functions etc.
>>
>
> #1501 (Integrate band references into portable signature files) is close
> to being merged.
>

this one was merged just after you posted this

#1454 (TGIS DB v3 backward compatible with v2) has perhaps lower priority
> since there is both upgrade and downgrade.
>
> As for issues linked to the milestone, please review what is there. See
> what needs to stay there and what can be moved. For example, all issues
> which are features and are not changing existing API can be moved to 8.2
> milestone.
>
> https://github.com/OSGeo/grass/milestone/4
>

 If no further objections I'd suggest to move forward with grass8 release
branch creation

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

[GRASS-dev] GRASS GIS 7.8.6RC2 released

[Veronica Andreo]

 Dear all,

GRASS GIS 7.8.6RC2 

Repository:  OSGeo/grass  · Tag: 7.8.6RC2
 · Commit: 48c13c1

· Released by: veroandreo  (with Markus
Neteler's assistance)

This is the second release candidate of GRASS GIS 7.8.6.

Download source code tarball at

   - https://grass.osgeo.org/grass78/source/grass-7.8.6RC2.tar.gz
   - https://grass.osgeo.org/grass78/source/grass-7.8.6RC2.md5sum

For further release details (bug fixes and enhancements), see

   - https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures78
   - https://trac.osgeo.org/grass/wiki/Release/7.8.6-News

The GRASS GIS 7.8.6RC2 release provides more than 110 fixes and improvements

with respect to the release 7.8.5.

This release has 2 assets:
   - Source code (zip)
   - Source code (tar.gz)

Visit the release page
 to download
them.

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

[GRASS-dev] PSC meeting minutes on GRASS b'day (July 29, 2021)

[Veronica Andreo]

Dear all,

Please have a look at the PSC minutes of our recent meeting for GRASS GIS
birthday on July 29, 2021:
https://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20210729

Topics covered were:
- PSC meetings date
- GRASS GIS 8 release schedule
- New splash screen
- GRASS GIS 7.8.6 release schedule
- Sponsoring
- Presence in social media
- Website
- AGM at FOSS4G 2021
- Binder button in PR and commits to increase testing by the community
- GRASS green color

Meeting plus: Helena and Jeff showed their GRASS 4 printed manuals 8-)

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

[GRASS-dev] Nabble Forum shut down

[Veronica Andreo]

FYI

best,
Vero

-- Forwarded message -
De: Jorge Sanz via Discuss 
Date: jue, 5 ago 2021 a las 8:35
Subject: [OSGeo-Discuss] Fwd: Your Nabble Forum
To: System Administration Committee Discussion/OSGeo ,


Hi all,

Unfortunately, Nabble , a popular
interface to OSGeo mailing lists, is shutting down. Nabble has been very
useful to users that are not keen to use email to interact with their
community but rather a web interface. It also conveniently offered a way to
search through many mailing lists under a single entry point.

This is not really surprising, as the service has been struggling for a
couple of years. The OSGeo tickets 2574
 and 2616
 are just the most recent
examples.

Please find below the link to the official announcement, and forward this
message to anyone interested.

Happy to answer any questions.
Jorge

-- Forwarded message -
From: 
Date: Thu, 5 Aug 2021 at 05:57
Subject: Your Nabble Forum
To: 


We are downsizing Nabble to one server.  If you want to preserve your forum:

http://osgeo-org.1560.x6.nabble.com/

Then you should follow the instructions here:

http://support.nabble.com/Downsizing-Nabble-tp7609715.html


-- 
Jorge Sanz
http://jorgesanz.net
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 7.8.6

[Veronica Andreo]

Hello everybody,

El vie, 23 jul 2021 a las 8:41, Markus Neteler ()
escribió:

> Hi,
>
> Vaclav Petras  schrieb am So., 4. Juli 2021, 20:29:
>
>> On Sun, Jul 4, 2021 at 11:18 AM Markus Neteler  wrote:
>>
>>> On Mon, Jun 28, 2021 at 1:59 PM Vaclav Petras 
>>> wrote:
>>> >
>>> > The grass7 branch of the grass-addons repo is now in the state we want
>>> and is usable.
>>>
>>
>> The default branch is now grass7 which has the relevant code under src
>> (and not under the grass7 directory).
>>
>
> Let me suggest to publish a notice in the news section of the web site
> that the installation of add-ons is currently failing and will be fixed
> with 7.8.6, (and later) i.e. an updated g.extension will be published.
>

I just did here: https://github.com/OSGeo/grass-website/pull/259

please review

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

Re: [GRASS-dev] GRASS birthday meeting today!

[Veronica Andreo]

UPDATE!

Vaclav kindly provided a zoom link for today:
https://ncsu.zoom.us/j/96895562516?pwd=NTEzQVJvYXFIYkdETGVBZE5yUGFidz09
We meet there in one hour and a half from now :D

Just in case, here's the world clock link once again:
https://www.timeanddate.com/worldclock/converter.html?iso=20210729T17=1440=204=195=51=207=197=25=671

Looking forward to seeing you soon!

Vero

El jue, 29 jul 2021 a las 14:00, Veronica Andreo ()
escribió:

> Dear GRASS community,
>
> Our beloved software turns 38! We have planned a birthday call for today
> at 17:00 UTC [0]. You are all invited and welcome for a toast!
>
> We'll post the meeting link here one hour before the event.
>
> Cheers,
> Vero
>
> [0]
> https://www.timeanddate.com/worldclock/converter.html?iso=20210729T17=1440=204=195=51=207=671
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS birthday meeting today!

[Veronica Andreo]

Dear GRASS community,

Our beloved software turns 38! We have planned a birthday call for today at
17:00 UTC [0]. You are all invited and welcome for a toast!

We'll post the meeting link here one hour before the event.

Cheers,
Vero

[0]
https://www.timeanddate.com/worldclock/converter.html?iso=20210729T17=1440=204=195=51=207=671
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New splash screen image for GRASS GIS 8?

[Veronica Andreo]

Hello everyone,

El jue., 8 jul. 2021 00:29, Vaclav Petras  escribió:

> Dear all,
>
> It seems to me that the time has come for a new splash screen image.
>

Yes!! Fully agreed :)

Please see a dedicated issue on GitHub where we can upload the suggestions.
>
> https://github.com/OSGeo/grass/issues/1716
>

Thanks for bringing this up Vaclav! It was in my to-do for the weekend

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

[GRASS-dev] Fwd: [Projects] Join the FOSS4G 2021 Community Sprint on Saturday October 2nd, 2021 - please register

[Veronica Andreo]

FYI

Invitation to register and participate in the online community sprint after
FOSS4G 2021, on October 2nd

Our designer is doing a great job with the workadventu.re environment ;)
We are looking forward to seeing you there!

Vero

-- Forwarded message -
De: Astrid Emde (OSGeo) 
Date: vie, 2 jul 2021 a las 16:58
Subject: [Projects] Join the FOSS4G 2021 Community Sprint on Saturday
October 2nd,  2021 - please register
To: Announce , Discuss ,
OSGeo Projects 

See News Item
https://www.osgeo.org/foundation-news/foss4g-2021-community-sprint/

The FOSS4G 2021 Community Sprint [1] will be right after the global
FOSS4G 2021 conference [2] and has the aim to bring people together to
discuss and improve OSGeo projects. It will take place online on
Saturday October 2nd, 2021, using WorkAdventu.re [3] plus a bounce of
Jitsi channels for each project.

The Community Sprint offers an excellent opportunity to meet other OSGeo
members and get involved in OSGeo projects! It is a golden opportunity
for developers and non-developers to meet with the core team of those
projects, get a deeper insight into the software and participate in
development, testing or documentation. We follow this tradition since
2009.

Since we need to create the Workadventu.re environment, we ask all
projects to register on the wiki page by July 15th. Projects that have
registered on time will have their own Workadventu.re environment, those
that register later will only have a Jitsi channel reported on the
community sprint wiki page.

The OSGeo Code Sprint is open to all who wish to participate in one or
more projects. WorkAdventu.re environment is open only to people
registered to FOSS4G 2021 whereas the Jitsi channels are open to
everyone.

There is always plenty to do – it’s not all about programming;
translation, documentation, feedback, discussions, testing – all this is
also important for projects, so everyone is cordially invited to attend
the community sprint!

The Organizing Team is looking forward to your coming!

Please register soon [1]

See you at FOSS4G 2021!

The FOSS4G 2021 Community Sprint Team

[1] https://wiki.osgeo.org/wiki/FOSS4G_2021/Community_sprint
[2] https://2021.foss4g.org/
[3] https://workadventu.re/



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

Re: [GRASS-dev] Fwd: [OSGeo-Discuss] [FOSS4G] OSGeo Projects swag

[Veronica Andreo]

hihihi

I like Maris suggestion, sounds funny :)

I also thought/recalled of a beautifully handcrafted grass logo that looked
like a sticker made by Vaclav not so long ago. See:
https://twitter.com/vaclavpetras/status/1359972415233789952/photo/1. We
could offer it as a virtual sticker if Vashek agrees and kindly donates it,
of course!

A link to try GRASS online could also be something nice to promote and our
twitter handle (which reached 3k followers today!)

Vero

El mié, 7 jul 2021 a las 9:02, Maris Nartiss ()
escribió:

> 2021-07-06 11:50 GMT+03:00, Luca Delucchi :
> > Hi devs,
> >
> > Does anyone have any ideas?
> >
>
> Tired of your lawn looking like a mess? Check out best gardening tips
> at https://grass.osgeo.org
>
> GRASS – taking care of lawns since 1982.
>
>
> Designing an advertisement around logo I leave to more skill full artists.
> Māris.
> ___
> 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] [release planning] GRASS GIS 8: create new release branch

[Veronica Andreo]

Hi Maris,

El mié, 9 jun 2021 a las 9:23, Maris Nartiss ()
escribió:

> Hello Veronica,
> thanks for pushing this forward.
>
> Looking from a "it is ready when it is ready" perspective – what we
> are missing from functionality to call 8.0 ready? (I mean only things
> that are expected to be ready in less than a month)
>

I think, others please correct me if I'm wrong, restructuring the add-ons
repo + adapting g.extension are the main things missing/to be finished.


> From my side:
> Band references and integration with signature files are ready to be
> merged (please review!), missing functionality can wait for 8.2.
> https://github.com/OSGeo/grass/pull/1272
> https://github.com/OSGeo/grass/pull/1501
>
> I'll try to work on r.in.pdal this Friday (I need to do some LiDAR
> work myself). It is almost merge ready (as long as we add extra
> functionality in 8.2)
> https://github.com/OSGeo/grass/pull/1200
>
> Then from my side I'd call 8.0 ready.
>

Great!!

So, can we have a birthday release then? :-D

Vero

2021-06-08 17:09 GMT+03:00, Veronica Andreo :
> > Hello devs,
> >
> > As you all know, grass birthday is approaching... July 29th is just
> around
> > the corner. I'd love to celebrate GRASS' bday with a new release, with a
> > big release ;)
> > Do you think that is doable? How much is missing for GRASS 8 release?
> >
> > The next important date is FOSS4G 2021 on September 27th - October 2nd,
> > where we have proposed GRASS 8 talks and workshops. If we can't make it
> for
> > GRASS GIS' birthday, do you think it's feasible to release before FOSS4G,
> > say August for example?
> >
> > I think it's really important to agree on a date so we can all manage our
> > reduced time and focus our efforts towards that aim.
> > What do you say?
> >
> > Best,
> > Vero
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8: create new release branch

[Veronica Andreo]

Ciao Luca,

El vie, 11 jun 2021 a las 12:40, Luca Delucchi ()
escribió:

> On Tue, 8 Jun 2021 at 16:10, Veronica Andreo  wrote:
> > Hello devs,
>
> Hi,
>
> > As you all know, grass birthday is approaching... July 29th is just
> around the corner. I'd love to celebrate GRASS' bday with a new release,
> with a big release ;)
> > Do you think that is doable? How much is missing for GRASS 8 release?
>
> I would like to improve t.remove as reported
> https://trac.osgeo.org/grass/ticket/3362#comment:1
> I try to work on it next week
>

This is great news! It'd be great to have t.remove flags behaviour
changed/fixed in grass 8.
Shall we move the ticket in trac to an issue in github so we give it more
visibility? If yes, I can do that.

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

Re: [GRASS-dev] [release planning] GRASS GIS 7.8.6

[Veronica Andreo]

What about this one https://github.com/OSGeo/grass/issues/1594? Shall we
bump it to 7.8.7 and move forward? I vote, yes :)

El jue, 10 jun 2021 a las 18:38, Markus Neteler ()
escribió:

> Hi devs,
>
> GRASS GIS 7.8.6RC1 has been released 22 days ago,
> https://github.com/OSGeo/grass/releases/tag/7.8.6RC1
>
> and no major issues happened. One fix (plus translations update) has
> been applied since then:
>
>
> https://github.com/OSGeo/grass/commit/83c45339c98e7b587aa218a5731226ac8f6cb355
>
> Do we need another RC for this or release anyway?
>
> Markus
>
>
> --
> Markus Neteler, PhD
> https://www.mundialis.de - free data with free software
> https://grass.osgeo.org
> https://courses.neteler.org/blog
> ___
> 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] [release planning] GRASS GIS 8: create new release branch

[Veronica Andreo]

Hello devs,

As you all know, grass birthday is approaching... July 29th is just around
the corner. I'd love to celebrate GRASS' bday with a new release, with a
big release ;)
Do you think that is doable? How much is missing for GRASS 8 release?

The next important date is FOSS4G 2021 on September 27th - October 2nd,
where we have proposed GRASS 8 talks and workshops. If we can't make it for
GRASS GIS' birthday, do you think it's feasible to release before FOSS4G,
say August for example?

I think it's really important to agree on a date so we can all manage our
reduced time and focus our efforts towards that aim.
What do you say?

Best,
Vero

El lun, 7 jun 2021 a las 3:34, Vaclav Petras ()
escribió:

> The word "branch" in "previewbranch_8_0" seems superfluous to me as it
> does in releasebranch_7_8 plus it is two words together without a
> separator. Would v8 be a good time to change that practice?
>
> Advantages of just release_8_0:
>
> A1) No 'branch == releasebranch_7_8' or 'switch to the releasebranch_7_8
> branch' statements.
>
> A2) Master branch is also only a branch and does not have the word branch
> in it.
>
> A3) Both QGIS and GDAL use only "release", not "branch", in the name of
> their release branches.
>
> Disadvantages of just release_8_0:
>
> D1) In contexts where you use Git to get a specific branch or tag, you
> don't see from the command that it is indeed a branch (in `git --branch
> release_8_0`, release_8_0 could, in theory, be a tag). However, you are
> likely to correctly guess it is a branch, not a tag, since tags for release
> are most often mostly the numbers only, i.e., in format v8.0 or, as in our
> case, 8.0.
>
> D2) Scripts constructing the branch name from the version name will break,
> however it seems like a better practice to me in this case to parameterize
> the whole branch name and there needs to be likely other changes for v8 in
> these scripts anyway.
>
> Vaclav
>
> On Sun, Jun 6, 2021 at 2:41 AM Markus Neteler  wrote:
>
>> Hi all,
>>
>> The new 8.0.0alpha preview branch is ready:
>>
>> https://github.com/OSGeo/grass/tree/previewbranch_8_0
>>
>> Best,
>> 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
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release planning] GRASS GIS 8: create new release branch

[Veronica Andreo]

+1 from my side too

Time to move forward!

El sáb., 29 may. 2021 08:37, Moritz Lennert 
escribió:

>
>
> Le 29 mai 2021 08:58:59 GMT+00:00, Markus Neteler  a
> écrit :
>
> >If there are no objections I'd merge PR 1597 in the next days.
>
> +1
>
> I think at this stage it should just happen, especially if it's a
> throw-away branch.
>
> Moritz
> ___
> 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] GRASS on IRC

[Veronica Andreo]

Ciao Lu,

I was about to ask the same.

I do not use IRC so I cannot really tell what would be the best. QGIS is
having the same discussion right now. matrix seems like a good option if we
can use our osgeo credentials. In twitter, I have seen many open source
projects are moving to https://libera.chat/

my 2 cents
Vero



El vie, 28 may 2021 a las 13:20, Luca Delucchi ()
escribió:

> Hi all,
>
> there are problem with Freenode [0] where we have #grass channel.
>
> What do you think to move to matrix.osgeo.org? It works with OSGeo
> account!
>
>
> [0] https://diziet.dreamwidth.org/8514.html
>
> --
> ciao
> Luca
>
> www.lucadelu.org
> ___
> 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] [release planning] Enable Zenodo before 7.8.6 and 8.0.0

[Veronica Andreo]

+1 from my side too

El lun., 24 may. 2021 03:23, Moritz Lennert 
escribió:

> Clear +1 from me.
>
> Moritz
>
> Le 24 mai 2021 03:08:06 GMT+01:00, Vaclav Petras  a
> écrit :
>>
>> Hi all,
>>
>> Let's enable the Zenodo link before 7.8.6 and 8.0(.0?) releases to get
>> DOIs and Zenodo records.
>>
>> Solving the whole DOI linking and Zenodo archiving for the old versions
>> may be complex [1], but enabling the link between GitHub and Zenodo is
>> trivial (one click) and every newly created GitHub release (we do those)
>> will be automatically registered and receive DOI.
>>
>> Zenodo uses a system of DOI versions and a main DOI (Concept DOI).
>> Whether it is an ideal system, that's a question, but it is currently the
>> expected one since it is the same for everything on Zenodo. It is used
>> automatically when using the GitHub-Zenodo integration.
>>
>> It seems I have the permissions to enable it for GRASS GIS. The one who
>> enables that becomes a maintainer of it. I'm fine with that, but I won't be
>> uploading any older versions. The maintainer can be changed later by
>> contacting Zenodo support [2].
>>
>> Although there are things to figure out in terms of next steps, I don't
>> see much risk in enabling it. There are no choices available in the setup
>> or in terms of alternatives. DOI and some kind of registration are expected
>> more and more.
>>
>> Thoughts?
>>
>> Vaclav
>>
>> [1] https://grasswiki.osgeo.org/wiki/GitHub-Zenodo_linkage
>> [2] https://github.com/zenodo/zenodo/issues/826
>>
> ___
> 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] [release planning] GRASS GIS 8: create new release branch

[Veronica Andreo]

Hi all,

El jue, 20 may 2021 a las 17:21, Maris Nartiss ()
escribió:

> Hello Makrus et al.
>
> 2021-05-15 16:40 GMT+03:00, Markus Neteler :
> > On Sat, May 15, 2021 at 4:05 AM Vaclav Petras 
> wrote:
> >> On Fri, May 14, 2021 at 11:10 AM Markus Neteler 
> >> wrote:
> >>> Let me suggest to create a new release branch in the next two weeks
> >>> ...
> >>>
> >>> Now, the question is, also to avoid excessive cherry-picking of fixes
> >>> and changes from master (to be called 8.1 then), which of the open PR
> >>> may be merged soon?
>


> >> I actually expected that you would be a "beta" release, not an RC,
> marked
> >> by tagging a commit on master branch with the code as is.
> >> This would avoid any backporting,
> >
> > Yes, that's an alternative idea.
> >
> >> but perhaps, it is not creating enough focus for 8.0 and having a 8.0
> >> branch gives more freedom in what goes into the master branch.
> >
> > Indeed, a full blown new release branch for G800 would open the master
> > branch for new (radical) changes.
> >
> > @All: your opinion?
>
> I would like to get PR #1501 (depends on #1272) into master before
> branching as it is already quite large and disruptive.
> It is almost ready (today I wrote first of three management
> functions). I want to finish lib part before merging – management
> module can be then created as a separate PR at some point later.
>

I'd really like to see these changes merged before the creation of grass 8
branch.

Maybe we can agree on a deadline that suits both the need to have an 8
branch for the upcoming conferences where a GRASS 8 demo is already
accepted (*FOSSGIS is in ~2 weeks*) and the time needed to complete ongoing
development at least up to a working version that can be merged.

@Maris Nartiss  what do you think?

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

Re: [GRASS-dev] Management of signature files

[Veronica Andreo]

Hi Maris,

El mar, 27 abr 2021 a las 8:44, Maris Nartiss ()
escribió:

> Hello list,
> I have been working on moving automatic classification signature files
> (ones used by i.maxlik and i.smap) out of imagery groups. Existing
> approach was not flexible enough as there was no official way of how
> to reuse signatures from one imagery group in another group (train on
> one, classify many).
> At the moment I have managed to implement all internal bits of fully
> reusable signatures – at the time of creation, band references are
> written to the signature file; before signature use, band references
> are used to reorder signatures to match band order in the new group
> (or bail out if bands do not match).
> https://github.com/OSGeo/grass/pull/1501
>
> There are only two bits left before this work is complete:
> 1) remove current special signature file handling in GUI;
> 2) signature management.
>

There are 3 add-ons that Luca wrote at OSGeo code sprint in Bonn 2018:
i.signature.copy, i.signature.list, i.signature.remove.
Would they be of help for any of the options proposed?

In any case, thanks for your impressive work!

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

[GRASS-dev] Fwd: [GRASS-web] GRASS i.segment

[Veronica Andreo]

This arrived at the grass-web list, for those of you maybe interested and
not subscribed ;)

-- Forwarded message -
De: Sinter Guy 
Date: lun, 19 abr 2021 a las 13:59
Subject: [GRASS-web] GRASS i.segment
To: grass-...@lists.osgeo.org 
Cc: Beeri Ofer , Pelta Ran <
ran.pe...@manna-irrigation.com>

Hi Grass GIS team



My name is Guy and I’m from Manna Irrigation we provide farmers with
irrigation recommendation and fields images,

We are working on an algorithm to identify  point of interest within field
and for that our remote sensing team have used  your i.segment as part of
their algorithm,

We would like to ask if you are planning to develop the i.segment package
as a standalone python package without the need for Grass GIS installation ?

If so can you share the details ? we are also willing to pay for such
development,



Thanks Much ,

*Guy Sinter*

*Director, Software Engineering*

+972 52 6433180 (Cell)

www.manna-irrigation.com

[image: manna]


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

Re: [GRASS-dev] [release planning] GRASS GIS 7.8.6

[Veronica Andreo]

Hi,

Is there anything we can do here before 7.8.6 release:
https://lists.osgeo.org/pipermail/grass-dev/2021-April/095084.html

best,
Vero

El mié, 7 abr 2021 a las 15:05, Markus Neteler ()
escribió:

> Markus Neteler  schrieb am So., 21. März 2021, 09:21:
>
>> Hi devs,
>>
>> Since the last stable release 7.8.5 almost 70 commits have been
>> accumulated:
>> https://github.com/OSGeo/grass/compare/7.8.5...releasebranch_7_8
>>
>> I suggest the following time schedule:
>>
>> - Soft freeze of release branch: 26 March 2021
>> - RC1: 6 Apr 2021
>> - RC2: 16 Apr 2021, if needed
>> - Final release: 27 Apr 2021
>>
>> What's still to be done for 7.8.6?
>
>
> Is g.extension failing for all add-ons or only for a few? A new blocker or
> not?
>
> See the 7.8.6 milestone, it is
>> showing the remaining open issues:
>> https://github.com/OSGeo/grass/milestone/6
>> --> 78% complete
>>
>> Please check what really applies to the upcoming 7.8.6 release.
>
>
> 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] [GRASS-PSC] Min. req. of programming language standard support, GRASS GIS 8

[Veronica Andreo]

Hi everybody,

Ok, so we can now vote the C/C++ RFC, and then open a new thread + RFC
regarding support for python versions.

I'll send the voting motion later today or tomorrow.

Cheers,
Vero

El lun, 22 mar 2021 a las 11:18, Nicklas Larsson ()
escribió:

> Forgot to add: Python support changes with GRASS minor versions adds a bit
> of complication with add-ons, which are bound to major version. I don't
> know what would be the better solution for this.
>
> N.
>
>
>
>
>
>
>
> On Monday, 22 March 2021, 10:24:06 CET, Nicklas Larsson via grass-psc <
> grass-...@lists.osgeo.org> wrote:
>
>
>
>
>
> Hi,
>
> Although I didn't see the need to remove Python from RFC 7 (as it was
> originally formulated), there is also some logic to treat Python as a whole
> in a separate RFC. I don't have strong opinion on either way, therefore I
> lifted out Python from the draft, which now only deals with C and C++.
> Hopefully it may now be ready for vote :).
>
> Regarding Python: I believe version support should be linked to Python
> end-of-life circle and GRASS minor version.
>
> Best,
> Nicklas
>
>
>
>
> On Sunday, 21 March 2021, 09:04:24 CET, Markus Neteler 
> wrote:
>
>
>
>
>
> Hi,
>
> On Tue, Mar 16, 2021 at 8:30 PM Veronica Andreo 
> wrote:
> >
> > Hi everyone
> >
> > Thanks for all the feedback.
> >
> > In practical terms then, shall we:
> > - remove all python references from the Language Standards draft RFC [0]
> and vote only for C/C++, while creating a separate RFC for the minimum
> python version?
> > - add a formula that sets on which pace the minimum supported python
> version will change to the Language Standards draft RFC [0] and vote for
> everything altogether?
>
> For Python support, it is worth looking at the GDAL RFC 77 which
> includes useful tables and links:
> - https://gdal.org/development/rfc/rfc77_drop_python2_support.html
>
> esp.:
> -
> https://endoflife.date/python#:~:text=The%20support%20for%20Python%202.7,dropping%20support%20for%20Python%202.7
>
> Useful is also
> - https://repology.org/project/python/versions
>
> With respect to the pace of periodic review and updating of the
> language standards support I believe that we need that at the pace of
> sub-major releases (e.g., 7.8 -> 7.9). Just look back at the major
> releases (https://grass.osgeo.org/about/history/releases/) we observe
> quite some time span:
>
> - (2021) GRASS GIS 8.0.0
> - 2015 GRASS GIS 7.0.0
> - 2005 GRASS GIS 6.0.0
> - 2002 GRASS GIS 5.0.0
> - 1991 GRASS 4.0
> - 1988 GRASS 3.0
> - 1987 GRASS 2.0
> - 1984 GRASS 1.0
>
> Hence sub-major releases might be the way to go.
>
> Markus
>
>
> > [0] https://trac.osgeo.org/grass/wiki/RFC/7_LanguageStandardsSupport
>
>
> ___
> grass-psc mailing list
> grass-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Add-ons not building since January

[Veronica Andreo]

El mié, 17 mar 2021 a las 15:11, Martin Landa ()
escribió:

> Hi all,
>
> út 16. 3. 2021 v 13:27 odesílatel Markus Neteler 
> napsal:
> > Well, the problem is that the ZIP files carry a current timestamp but
> > the content (!) is from Jan 2021...
> > So, only old stuff included...
> >
> > @Martin Landa can you pls take a look?
>
> It should be fixed now. Martin
>

Thanks a lot, Martin!
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-PSC] Min. req. of programming language standard support, GRASS GIS 8

[Veronica Andreo]

Hi everyone

Thanks for all the feedback.

In practical terms then, shall we:
- remove all python references from the Language Standards draft RFC [0]
and vote only for C/C++, while creating a separate RFC for the minimum
python version?
- add a formula that sets on which pace the minimum supported python
version will change to the Language Standards draft RFC [0] and vote for
everything altogether?

Vero

[0] https://trac.osgeo.org/grass/wiki/RFC/7_LanguageStandardsSupport

El mar, 2 mar 2021 a las 22:54, Markus Neteler ()
escribió:

> Hi all,
>
> On Tue, Mar 2, 2021 at 8:15 AM Nicklas Larsson via grass-dev
>  wrote:
> >
> > Good, Anna, you brought up this question on regular update of Python
> version support. I deliberately left that part out of the draft for
> setting/updating language standards, as I would argue it deserves a RFC on
> its own.
>
> I agree to both:
>
> - we need to find a formula with our release rhythm and the oldest
> still supported Python version,
> - and yes, please let's separate this out into a different discussion
> (RFC if needed).
>
> I.e., one C/C++ RFC and one Python RFC.
>
> > A RFC should't be updatable, but may be overridden, partly or
> completely, with a new RFC. Adopting adherence to a new C or C++ standard
> will most likely be a quite rare business and should be dealt with a new
> RFC.
>
> I agree to that, as it would become a moving target otherwise.
>
> > The discussed approach, following the Python versions life-cycle, could
> possibly look a little different, however the forms and modes for this
> should be established likewise with a RFC.
> >
> > If we agree now, to set Python 3.6 as a minimum, we have roughly six
> months to work out such a procedure. I’m glad to assist to this in, say
> around, October, in time for the 3.6 retirement.
>
> Let me suggest to separate Python out into another discussion.
> The pace of C/++ standards and that of Python versions are quite
> different and not easy to handle in a single RFC.
>
> Just my 0.02 cents,
>
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Add-ons not building since January

[Veronica Andreo]

Hi all,

Thanks for the feedback

El mar, 16 mar 2021 a las 14:57, Moritz Lennert (<
mlenn...@club.worldonline.be>) escribió:

> On 16/03/21 14:45, Anna Petrášová wrote:
> >
> > On Tue, Mar 16, 2021 at 8:55 AM Moritz Lennert
> > mailto:mlenn...@club.worldonline.be>>
> wrote:
> >
> > On 16/03/21 06:57, Luca Delucchi wrote:
> >  > On Tue, 16 Mar 2021 at 01:10, Veronica Andreo
> > mailto:veroand...@gmail.com>> wrote:
> >  >>
> >  >> Hi devs,
> >  >
> >  > Hi Vero,
> >  >
> >  >> I'm teaching a GRASS course and one of the students using
> > windows told me that he didn't have i.landsat.qa <
> http://i.landsat.qa>.
> >  >>
> >  >> Checking the log, the last building date seems to be January
> > 26th [0]. i.landsat.qa <http://i.landsat.qa> was added a couple of
> > weeks later, hence not there.
> >  >>
> >  >> Is there a way to re trigger the building of add-ons for
> > windows? Or an alternative solution for windows users to install
> > add-ons?
> >  >
> >  > I'm not a windows user, so I could say something wrong, since it
> is a
> >  > python script could be enough to copy the python file into addons
> >  > folder and make it executable (on Unix it works)
>

Yes, I just don't even know where grass add-ons are in windows.


> > I think in MS Windows, this implies creating a .bat file which then
> > call the .py script. Look at how the current version of the scripts
> in
> > i.landsat (or any other Python addons) are organized.
> >
> > You can create the zip file yourself and make it available to the
> > students and they can point to the file directly with url=.
>

No idea how to build these bat files myself... Can I do that from linux? Or
you mean, just zip the makefile + html + py? Sorry for my ignorance here.

> Spo yes, it is definitely possible, but it is always a bummer when you
> > have to use such an approach to install an extension when g.extension
> > should "just work". Just makes GRASS GIS less credible.
>

Fully agree. I feel really frustrated when teaching GRASS to Windows users
(all of the time since most new users come with windows machines), while
not being one... I'd love to convince them of the great things that they
can do with GRASS, but then this (among others) kind of issues arise...


> Yes, there seems to be a specific issue with the grass78 addons. This
> said: is there any special reason to differentiate between grass78 and
> grass79 addons for Python scripts ?
>
> Vero, you could try if the student can install by pointing url to
>
> https://wingrass.fsv.cvut.cz/grass79/x86_64/addons/grass-7.9.dev/i.landsat.zip
> .
>

I told the student to try this since it seemed the most straightforward of
all potential solutions, let's see what he reports back.

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

[GRASS-dev] Add-ons not building since January

[Veronica Andreo]

Hi devs,

I'm teaching a GRASS course and one of the students using windows told me
that he didn't have i.landsat.qa.

Checking the log, the last building date seems to be January 26th [0].
i.landsat.qa was added a couple of weeks later, hence not there.

Is there a way to re trigger the building of add-ons for windows? Or an
alternative solution for windows users to install add-ons?

Thanks much!
Vero


[0]  https://wingrass.fsv.cvut.cz/grass78/x86_64/addons/latest/logs/
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS-PSC] Min. req. of programming language standard support, GRASS GIS 8

[Veronica Andreo]

Dear Nicklas,

Thanks much for such a clearly written RFC! I only made very minor cosmetic
changes.

Are there any other comments, objections or suggestions? Or further aspects
to be discussed?
If no, maybe we can vote on it soon-ish, no?

Have a nice weekend :)
Vero

El mar, 16 feb 2021 a las 15:36, Nicklas Larsson via grass-psc (<
grass-...@lists.osgeo.org>) escribió:

> I added the RFC draft to GRASS Wiki [1].
>
> Well, it's only a draft, so any thoughts, modifications, additions are
> most welcome!
>
> Nicklas
>
>
> [1] https://trac.osgeo.org/grass/wiki/RFC/7_LanguageStandardsSupport
>
>
>
> On Thursday, 11 February 2021, 14:34:44 CET, Moritz Lennert <
> mlenn...@club.worldonline.be> wrote:
>
>
>
>
> Am 11. Februar 2021 13:29:10 MEZ schrieb Nicklas Larsson <
> n_lars...@yahoo.com>:
> > Moritz,
> >
> >I'd be honoured!
> >I will put it on GRASS Wiki [1] if you don't have another suggestion and
> notify here when done.
>
>
> Great, thanks a lot !
>
>
> Moritz
>
> >
> >[1] https://trac.osgeo.org/grass/wiki/RFC
> >
> >
> >
> >On Thursday, 11 February 2021, 12:54:30 CET, Moritz Lennert <
> mlenn...@club.worldonline.be> wrote:
> >
> > On 10/02/21 13:16, Nicklas Larsson wrote:
> >> It would be most favourable for all contributors and the project if the
> >> community could come to an agreement on this topic. I see no reason to
> >> postpone a decision on this much longer.
> >>
> >> The final word on this need to be that of the PSC's. Whether through
> >> simple vote or a RFC. However, a sounding of the opinion of the
> >> dev-community on this matter is of equal importance and can be of help
> >> for the PSC.
> >
> >Thanks a lot, Nicklas, for this very comprehensive summary !
> >
> >A suggestion made at the first meeting of the new PSC was to use this
> >discussion as a use case for a more extensive usage of RFC's to put
> >important decisions into more permanent documents than mailing list
> >archives and to provoke a formal decision as you suggest. Would you be
> >willing to write a first draft of such an RFC ?
> >
> >Moritz
> >
> ___
> grass-psc mailing list
> grass-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-psc
>
___
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?

[Veronica Andreo]

Hello everybody,

I wonder if this discussion should also be moved to a RFC [1]. What do you
think?
If yes, is there anyone willing to draft it detailing background,
advantages,
disadvantages and alternatives?

It might be interesting to know how many OSGeo projects use it and how it
works for them. It was mentioned here that QGIS PSC is considering to close
it,
but what about others?

my 2 cents

Cheers,
Vero

[1] https://trac.osgeo.org/grass/wiki/RFC

El mié, 10 feb 2021 a las 15:28, Stefan Blumentrath (<
stefan.blumentr...@nina.no>) escribió:

> Hi,
>
>
>
> Personally, I tried being active on StackExchange. However, even though I
> do like to support colleagues using GRASS and the project in general, the
> GIS SE system somehow put me off. I just did not like the attitude there
> and would myself not even think about asking questions there...
>
>
>
> That said, GitHub discussions can be different. But I still would very
> much prefer the mentioned option to “modernize” the ML system.
>
>
>
> I also think that if people could register at OSGeo (and MLs) with other
> accounts (Github, Google, …) that could lower entrance barriers. But that
> is a different, and probably more complicated (?) issue…
>
>
>
> Cheers
>
> Stefan
>
>
>
> *From:* grass-dev  *On Behalf Of *Vaclav
> Petras
> *Sent:* onsdag 10. februar 2021 04:10
> *To:* Markus Neteler 
> *Cc:* GRASS developers list 
> *Subject:* Re: [GRASS-dev] Should we use GitHub Discussions?
>
>
>
>
>
>
>
> On Tue, Feb 9, 2021 at 3:59 PM Markus Neteler  wrote:
>
> On Tue, Feb 9, 2021 at 9:50 PM Vaclav Petras  wrote:
> > On Tue, Feb 9, 2021 at 4:01 AM Markus Neteler  wrote:
> >>
> > If we had a presence on StackExchange like QGIS has, we wouldn't be
> having a discussion about GitHub Discussions in the first place.
>
> Try this:
>
> https://gis.stackexchange.com/questions/tagged/grass
> 
> --> 2,027 questions
>
>
>
> I wish this would indicate a healthy community and I wish we would have
> one there. However, with a small sample from questions with recent
> activity, I see only a couple of users answering (2 or so; BTW thanks! you
> know who you are) and from the 2027 questions tagged grass, there are "475
> questions with no upvoted or accepted answers" [1]. This does not sound
> like what is in the original Nyall's email against QGIS using GitHub
> Discussions which says "there's LOTS of informed users answering all the
> QGIS questions on gis.stackexchange." [2]. Perhaps even more telling is
> that no one except myself [3] mentioned GIS StackExchange in this
> discussion up until now.
>
>
>
> [1] https://gis.stackexchange.com/questions/tagged/grass?tab=Unanswered
> 
>
> [2] https://lists.osgeo.org/pipermail/qgis-psc/2021-February/009244.html
> 
>
> [3] https://lists.osgeo.org/pipermail/grass-dev/2021-January/094867.html
> 
>
>
>
> ___
> 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] Min. req. of programming language standard support, GRASS GIS 8

[Veronica Andreo]

I was just about to pop up in this discussion with the RFC suggestion :)

Thanks a lot Nicklas and Moritz!

El jue, 11 feb 2021 a las 14:34, Moritz Lennert (<
mlenn...@club.worldonline.be>) escribió:

>
>
> Am 11. Februar 2021 13:29:10 MEZ schrieb Nicklas Larsson <
> n_lars...@yahoo.com>:
> > Moritz,
> >
> >I'd be honoured!
> >I will put it on GRASS Wiki [1] if you don't have another suggestion and
> notify here when done.
>
>
> Great, thanks a lot !
>
> Moritz
>
> >
> >[1] https://trac.osgeo.org/grass/wiki/RFC
> >
> >
> >
> > On Thursday, 11 February 2021, 12:54:30 CET, Moritz Lennert <
> mlenn...@club.worldonline.be> wrote:
> >
> > On 10/02/21 13:16, Nicklas Larsson wrote:
> >> It would be most favourable for all contributors and the project if the
> >> community could come to an agreement on this topic. I see no reason to
> >> postpone a decision on this much longer.
> >>
> >> The final word on this need to be that of the PSC's. Whether through
> >> simple vote or a RFC. However, a sounding of the opinion of the
> >> dev-community on this matter is of equal importance and can be of help
> >> for the PSC.
> >
> >Thanks a lot, Nicklas, for this very comprehensive summary !
> >
> >A suggestion made at the first meeting of the new PSC was to use this
> >discussion as a use case for a more extensive usage of RFC's to put
> >important decisions into more permanent documents than mailing list
> >archives and to provoke a formal decision as you suggest. Would you be
> >willing to write a first draft of such an RFC ?
> >
> >Moritz
> >
> ___
> 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