Re: [GRASS-dev] FYI: Season of the Docs

2019-05-12 Thread Luca Delucchi 
On Thu, 9 May 2019 at 15:18, Moritz Lennert
 wrote:
>
>
> Generally all GSoC or similar events are handled centrally via OSGeo
> with individual projects providing ideas.
>
> This year, OSGeo has been accepted as organisation:
> https://wiki.osgeo.org/wiki/Season_Of_Docs_2019
>
> For GSoC, see:
> See https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019
>
>
> Markus did transmit the info to the list:
>
> https://lists.osgeo.org/pipermail/grass-dev/2019-April/091819.html
>

If we want to partecipate we should write some ideas as Geonetwork o
QGIS [0], if someone would like to leads this action I can help..

>
> Moritz
>

[0] https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019


-- 
ciao
Luca

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

Re: [GRASS-dev] [GRASS GIS] #3424: v.random add minimum distance between points

2019-05-12 Thread GRASS GIS 
#3424: v.random add minimum distance between points
--+---
  Reporter:  lucadelu |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:  7.2.4
 Component:  Default  |Version:  unspecified
Resolution:  wontfix  |   Keywords:  v.random distance
   CPU:  Unspecified  |   Platform:  Unspecified
--+---
Changes (by lucadelu):

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


-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] svn/trac -> git/github migration plan

2019-05-12 Thread Markus Neteler 
On Fri, May 10, 2019 at 5:06 PM Martin Landa  wrote:
>
> Hi,
>
> út 7. 5. 2019 v 10:26 odesílatel Martin Landa  napsal:
> > commits can be referenced to github issues. Issue migration needs to
> > be also done on private repository. This would require to set up empty
> > private repo, migrate tickets and than transfer ticket using GitHub
> > API to public repo. This complicates procedure a bit. I would still
> > prefer to do source code and issues migration together even it will
> > take some time.
>
> back to this topic, I added to trac an alternative scenario based on
> two steps (source code and issues migration separated) [1]. Opinions
> welcome. We are very close to day D.

Excellent.

IMHO the separate migration of source code and issues is the way to go.
Like that we can already work with the then completed migration next
weekend in Berlin and define workflows.

Issue migration can follow then.

Best,
Markus

> Ma
>
> [1] https://trac.osgeo.org/grass/wiki/GitMigration#Scenario2twosteps
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] [GRASS GIS] #3844: Make Region importable from pygrass.gis

2019-05-12 Thread GRASS GIS 
#3844: Make Region importable from pygrass.gis
-+-
 Reporter:  pmav99   |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  normal   |  Milestone:  7.8.0
Component:  PyGRASS  |Version:  svn-trunk
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 Currently, in order to import the {{{Region}}} class you need to import it
 from {{{pygrass.gis.region}}}. The following patch allows to import it
 from the {{{pygrass.gis}}} package. This way, all gis objects can be
 imported/used from the same module. E.g.

 {{{
 import grass.pygrass.gis as ggis

 ggis.Region
 ggis.Location
 ggis.Mapset
 }}}

 The patch:
 {{{
 diff --git lib/python/pygrass/gis/__init__.py
 lib/python/pygrass/gis/__init__.py
 index 82e176bd..2e65e990 100644
 --- lib/python/pygrass/gis/__init__.py
 +++ lib/python/pygrass/gis/__init__.py
 @@ -9,11 +9,11 @@ import shutil
  import ctypes as ct
  import fnmatch

 -
  import grass.lib.gis as libgis
  from grass.pygrass.errors import GrassError
  from grass.script.utils import encode, decode
  from grass.pygrass.utils import getenv
 +from grass.pygrass.gis.region import Region

  test_vector_name = "Gis_test_vector"
  test_raster_name = "Gis_test_raster"
 }}}

-- 
Ticket URL: 
GRASS GIS 

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