+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.
>
>
#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|
-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
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
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
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
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
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
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
