[GRASS-user] Download release sources?

[Veronica Andreo]

Hi all,

I have created a PR addressing this:
https://github.com/OSGeo/grass-website/pull/220

To be honest, I very much liked the code style of the link to the repo as
it was (still is), but when adding also a link to releases, then it does
not match anymore... Other ideas are welcome :)

Vero

El vie., 14 ago. 2020 a las 13:43, Hernán De Angelis (<dhdeangelis at comhem.se>)
escribió:

> Hello Stefan,
>
> Yes, I see. This is a good link of course. I also see now that the issue
> has already been disccused in the github repo for the page.
>
> My humble opinion is that a new user (or an old but absent minded one like
> me) could easily miss this release page in Github. May be this could be
> easily solved with minimal extra clutter in the new page by just adding a
> line with link to the releases page in Github following the link to the
> main repository.
>
> See the example below.
>
> Best
>
> Hernán
>
>
>
>
> On 2020-08-14 11:19, Stefan Blumentrath wrote:
>
> Hello Hernán,
>
>
>
> Best place to look for the source code of the different releases is
> probably here:
>
> https://github.com/OSGeo/grass/releases
>
>
>
> @website-devs: I see that Download source code shows up as an option on
> the landing page (https://grass.osgeo.org/download/), but not in the menu.
>
> Maybe worth adding a subpage for download of source code?
>
>
>
> Cheers
>
> Stefan
>
>
>
> *From:* grass-user <grass-user-bounces at lists.osgeo.org>
> <grass-user-bounces at lists.osgeo.org> *On Behalf Of *Hernán De Angelis
> *Sent:* fredag 14. august 2020 08:33
> *To:* grass-user <grass-user at lists.osgeo.org> <grass-user at lists.osgeo.org>
> *Subject:* Re: [GRASS-user] Download release sources?
>
>
>
> Thanks for your answer, Vero.
>
> The links in the page you refer to point to the binaries and my question
> was rather where the source code for different releases is going to be
> found. The answer seems to be trac (which one reaches when clicking in
> announcements: https://grass.osgeo.org/grassNN/source/grass-*) or github
> for the latest.
>
> Perhaps it could be nice to have a link to the source directly in the link
> list for every release. This is not critical of course.
>
> Bets
>
> Hernán
>
>
>
> On 2020-08-13 21:38, Veronica Andreo wrote:
>
> Hello Hernan,
>
>
>
> You can go to any of those marked links below and they will lead to other
> links/pages for the different operating systems with options to download.
> Please let us know if you find that we could make it more explicit.
>
>
>
> [image: image.png]
>
> best,
>
> Vero
>
>
>
> El jue., 13 ago. 2020 a las 21:02, Hernán De Angelis (<
> dhdeangelis at comhem.se>) escribió:
>
> Since the migration to the new web it is not obvious to me where will
> one go to get the source code for different releases. Those were
> previously found at https://grass.osgeo.org/download/software/sources/.
> Perhaps it is the trac page that will be used from now on for downloads?
> Or just the latest code from github? Perhaps I missed something. Thanks
> for clarification.
>
> /H.
>
>
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
>
> _______________________________________________
> grass-user mailing list
> grass-user at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20200817/15d2e523/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dcnlpkgbpacffkkl.png
Type: image/png
Size: 31893 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20200817/15d2e523/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 408775 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/grass-user/attachments/20200817/15d2e523/attachment-0003.png>