[geos-devel] git .mailmap

[Sandro Santilli]

I've added a .mailmap file to the repository so that `git shortlog`
correctly groups commits by people who for any reason changed their
git attribution (name,email) over time.

Committers please review .mailmap file in the root of the repository
if you want to be recognized in some other way from what I've guessed.

HINT: use `git shortlog -ens` for a quick view of what we have so far

--strk; 

  ()   Free GIS & Flash consultant/developer
  /\   https://strk.kbt.io/services.html
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] git .mailmap

[Komяpa]

Hi,

Can it also fix the issue that github statistics shows you only starting
working on postgis in 2016?

On Thu, May 16, 2019 at 2:29 AM Sandro Santilli  wrote:

> I've added a .mailmap file to the repository so that `git shortlog`
> correctly groups commits by people who for any reason changed their
> git attribution (name,email) over time.
>
> Committers please review .mailmap file in the root of the repository
> if you want to be recognized in some other way from what I've guessed.
>
> HINT: use `git shortlog -ens` for a quick view of what we have so far
>
> --strk;
>
>   ()   Free GIS & Flash consultant/developer
>   /\   https://strk.kbt.io/services.html
> ___
> geos-devel mailing list
> geos-devel@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel



-- 
Darafei Praliaskouski
Support me: http://patreon.com/komzpa
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] git stats (was: git .mailmap)

[Sandro Santilli]

On Thu, May 16, 2019 at 09:07:39AM -0500, Darafei "Komяpa" Praliaskouski wrote:

> Can it also fix the issue that github statistics shows you only starting
> working on postgis in 2016?

I've no idea. GitHub bugs can only be fixed by GitHub owners, who
decided that they have exclusive rights on fixing bugs and seeing
how the code works, and on deploying it.

But on the bright side, `git` (without the "hub") is free software,
so you can use this:

git log --oneline --date-order --reverse --date=short \
--pretty=format:'%cd -- %aN <%aE>' | \
perl -ne 'm/(.*) -- (.*)/; print "$1 -- $2\n" unless ( $seen{$2}++ > 0 
)'

Which yelds first commit per author:

2001-06-22 -- No Body 
2001-06-22 -- David Blasby 
2001-06-26 -- Paul Ramsey 
2001-09-17 -- Jeff Lounsbury 
2002-03-22 -- Chris Hodgson 
2003-10-20 -- Sandro Santilli 
2004-04-29 -- Ralph Mason 
2004-08-16 -- Mark Cave-Ayland 
2004-09-16 -- Mark Leslie 
2005-02-07 -- Markus Schaber 
2005-09-27 -- Devrim GÜNDÜZ 
2006-12-05 -- Kevin Neufeld 
2007-06-06 -- Norman Barker 
2007-07-03 -- Stephen Frost 
2008-01-18 -- Ben Jubb 
2008-06-24 -- Regina Obe 
2009-02-10 -- Olivier Courtin 
2010-01-21 -- Nicklas Avén 
2010-09-26 -- Jorge Arévalo 
2010-10-08 -- Pierre Racine 
2010-12-02 -- Mateusz Loskot 
2011-05-16 -- Bborie Park 
2011-09-30 -- David Zwarg 
2014-03-03 -- Baris Ergun 
2014-07-03 -- Stephen Woodbridge 
2015-11-18 -- Daniel Baston 
2017-02-26 -- Björn Harrtell 
2017-12-15 -- Darafei Praliaskouski 
2018-02-27 -- Raúl Marín Rodríguez 
2019-04-11 -- Martin Davis 

--strk;
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] git stats (was: git .mailmap)

[Sandro Santilli]

On Thu, May 16, 2019 at 05:41:47PM +0200, Sandro Santilli wrote:
> On Thu, May 16, 2019 at 09:07:39AM -0500, Darafei "Komяpa" Praliaskouski 
> wrote:
> 
> > Can it also fix the issue that github statistics shows you only starting
> > working on postgis in 2016?
> 
> I've no idea. GitHub bugs can only be fixed by GitHub owners, who
> decided that they have exclusive rights on fixing bugs and seeing
> how the code works, and on deploying it.
> 
> But on the bright side, `git` (without the "hub") is free software,
> so you can use this:
> 
>   git log --oneline --date-order --reverse --date=short \
>   --pretty=format:'%cd -- %aN <%aE>' | \
>   perl -ne 'm/(.*) -- (.*)/; print "$1 -- $2\n" unless ( $seen{$2}++ > 0 
> )'
> 
> Which yelds first commit per author:

Sorry, I was running the command on the wrong repository.
For GEOS this is the correct output:

  2002-06-07 -- No Body 
  2002-06-07 -- Paul Ramsey 
  2002-06-11 -- Yury Bychkov 
  2002-09-03 -- Fernando Villa 
  2002-10-23 -- Norman Vine 
  2003-02-11 -- Martin Davis 
  2003-04-04 -- David Blasby 
  2003-09-26 -- Sandro Santilli 
  2004-07-25 -- Sean Gillies 
  2004-12-03 -- Frank Warmerdam 
  2006-04-04 -- Howard Butler 
  2006-04-06 -- Mateusz Łoskot 
  2006-07-11 -- Charlie Savage 
  2007-12-21 -- Ben Jubb 
  2009-01-05 -- Stephen Wong 
  2013-07-31 -- Regina Obe 
  2017-04-06 -- Daniel Baston 
  2017-04-12 -- Kurt Schwehr 
  2017-06-22 -- Manuel Grizonnet 
  2017-07-18 -- Tamas Szekeres 
  2017-09-01 -- nila 
  2018-01-06 -- Evgeniy A. Dushistov 
  2018-01-10 -- cvvergara 
  2018-03-28 -- Even Rouault 
  2018-06-08 -- Raul Marin 
  2018-06-21 -- J Smith 
  2018-09-16 -- Sergey Fedoseev 
  2018-10-02 -- John K. Harvey 
  2018-10-07 -- Greg Troxel 
  2018-10-19 -- Simon Wells 
  2018-10-26 -- Darafei Praliaskouski 
  2018-12-09 -- doskabouter 
  2018-12-19 -- doskabouter 
  2019-03-27 -- Kirill Kouzoubov 

--strk;
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] [GEOS] #968: Let Delaunay triangulation look at Z values to resolve 2D ties performing 2.5D triangulation

[GEOS]

#968: Let Delaunay triangulation look at Z values to resolve 2D ties performing
2.5D triangulation
-+--
 Reporter:  komzpa   |  Owner:  geos-devel@…
 Type:  enhancement  | Status:  new
 Priority:  major|  Milestone:
Component:  Default  |Version:  master
 Severity:  Feature Request  |   Keywords:
-+--
 When performing delaunay triangulation of 2.5D grid, you get randomly
 oriented triangles.

 In this case the tie can be broken by re-running the check with inSphere
 predicate instead of inCircle.

 This also can help resolving numerical precision issues, where inSphere
 resolves in more clear way than inCircle.

-- 
Ticket URL: 
GEOS 
GEOS (Geometry Engine - Open Source) is a C++ port of the Java Topology Suite 
(JTS).
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

[geos-devel] RFC 9: Restore C++ API as public API

[Mateusz Loskot]

Dear All,

I'd like propose to effectively revert the RFC 6:

https://trac.osgeo.org/geos/wiki/RFC9

I'll appreciate if the PSC members considered to review my proposal
and arranged the voting.

Although I've made my best to prepare the write short,
clear and unambiguous proposal, I'll welcome your feedback.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] RFC 9: Restore C++ API as public API

[Kurt Schwehr]

+1 from a non-PSC person

On Thu, May 16, 2019 at 2:28 PM Mateusz Loskot  wrote:

> Dear All,
>
> I'd like propose to effectively revert the RFC 6:
>
> https://trac.osgeo.org/geos/wiki/RFC9
>
> I'll appreciate if the PSC members considered to review my proposal
> and arranged the voting.
>
> Although I've made my best to prepare the write short,
> clear and unambiguous proposal, I'll welcome your feedback.
>
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
> ___
> geos-devel mailing list
> geos-devel@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel



-- 
--
http://schwehr.org
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] RFC 9: Restore C++ API as public API

[Regina Obe]

-1

Not much has changed since we made this decision to make it non-public. In fact 
ironically I feel like more people are using GEOS than before.
I was hoping removing the C++ public would scare more people away so we could 
do some major rework :).

I'd like us to be able to guarantee some bit of ABI stability before we go 
taking this restriction off.

NO ONE READS READMES, they rely on at least some light punches :)




> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Mateusz Loskot
> Sent: Thursday, May 16, 2019 5:28 PM
> To: geos-devel@lists.osgeo.org
> Subject: [geos-devel] RFC 9: Restore C++ API as public API
> 
> Dear All,
> 
> I'd like propose to effectively revert the RFC 6:
> 
> https://trac.osgeo.org/geos/wiki/RFC9
> 
> I'll appreciate if the PSC members considered to review my proposal and
> arranged the voting.
> 
> Although I've made my best to prepare the write short, clear and
> unambiguous proposal, I'll welcome your feedback.
> 
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
> ___
> geos-devel mailing list
> geos-devel@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geos-devel

___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel

Re: [geos-devel] RFC 9: Restore C++ API as public API

[Sebastiaan Couwenberg]

On 5/16/19 11:28 PM, Mateusz Loskot wrote:
> I'd like propose to effectively revert the RFC 6:
> 
> https://trac.osgeo.org/geos/wiki/RFC9

Please don't. We'll get more projects like OSSIM that break with new
GEOS releases, this causes significant delays before the new release can
be included in distributions where lots of projects depend on GEOS
(which all need to build with the new release).

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
___
geos-devel mailing list
geos-devel@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/geos-devel