<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Darafei,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>I think the issues you faced wouldn't matter if we were on github, gogs, or svn and we'll still have at the very least a Github mirror for the very reasons you mentioned.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The reason half your PR for parallelization did not go thru is because I intentionally deleted them. I did not want them in 2.3 and wanted to think about them for 2.4.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>So that has nothing to do with github/svn<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The travis issue with not being able to test was because our travis was broken. I think regardless which we choose, our laziness about fixing bots is not going to change.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The other patch about the points index optimizations that was then again me deliberating. There is some stuff there I have not committed and some I might revert because I wanted to do more tests on real data and some tests I did I did not see much of an improvement and in some cases slower.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>So as far as your commits it shouldn't matter whether github, git whatever. I’d still want to study and cut things out I don't think should be in there.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Regina<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='margin-left:.5in'><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> postgis-devel [mailto:postgis-devel-bounces@lists.osgeo.org] <b>On Behalf Of </b>Darafei "Kom?pa" Praliaskouski<br><b>Sent:</b> Wednesday, August 09, 2017 9:25 AM<br><b>To:</b> PostGIS Development Discussion <postgis-devel@lists.osgeo.org><br><b>Subject:</b> Re: [postgis-devel] PSC Vote: Github or Gitea (OSGeo Git) or stay on SVN<o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><p class=MsoNormal style='margin-left:.5in'>I'm not that frequent PostGIS contributor or a maintainer.<o:p></o:p></p><div><p class=MsoNormal style='margin-left:.5in'><br>Most time I'm interacting with its code is when something is not covered in docs (like O() of the functions to get idea of how long the query will be running, or details of estimator, etc.).<br>I just read it on Github repo, as search and code highlighting are good enough there.<br>Sometimes I see a logical error and fix it right away in the github web editor, making a PR and looking at tests passing or not.<br><br>I think process of moving from git to svn let half of our parallel aggregates patch fall through the cracks, and I'm not even sure if it's completely there, as it's not a "merged PR", but a diff applied by maintainer. I also had issues creating OSGeo account, so a couple of tickets were created on trac by my IRC reports by other good people.<br><br>Github as a main home for postgis would be much easier for me, as postgis is not the only piece of software I'm looking into.<o:p></o:p></p></div></div><p class=MsoNormal style='margin-left:.5in'><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-left:.5in'>ср, 9 авг. 2017 г. в 16:10, Regina Obe <<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>>:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal style='margin-left:.5in'><br>> On 8 August 2017 at 23:07, Paul Ramsey <<a href="mailto:pramsey@cleverelephant.ca" target="_blank">pramsey@cleverelephant.ca</a>> wrote:<br>>> The practical aspects of "going where the people are" leads me to<br>>> advocate for going all over to github. Code, tickets, etc.<br><br>> I second Paul's vote,<br><br>Paul has not voted. He has advocated. Advocation is NOT a vote.<br>It's a way of saying I'm encouraging other people to move in the direction I feel is right. :)<br><br>He has to say +1, -1, 0 for it to be considered a vote.<br><br>I suspect Sandro is conveniently not voting either.<br><br>> Although, I'm just an ad-hoc contributor, so I don't aim to interfere with PSC decision.<br><br>> Best regards,<br>--<br>> Mateusz Loskot<br><br>Mat,<br><br>If you had a choice between doing noting (e.g. keep svn, trac)<br><br>Or moving to<br><br>Gogs (<a href="http://git.osgeo.org" target="_blank">git.osgeo.org</a>, gogs ticket system)<br><br>Which would you choose?<br><br>I would choose the second, because even if <a href="http://git.osgeo.org" target="_blank">git.osgeo.org</a> isn't stable it's more trivial to go to github.<br>Nothing lost - we get to experiment, developers get to use git instead of svn while we do so.<br>We've already started the experiment.<br><br><br>Thanks,<br>Regina<br><br><br>_______________________________________________<br>postgis-devel mailing list<br><a href="mailto:postgis-devel@lists.osgeo.org" target="_blank">postgis-devel@lists.osgeo.org</a><br><a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><o:p></o:p></p></blockquote></div></div></body></html>