FYI I forward this email from postgis-devel list.<div><br></div><div>As Anton mentioned in a previous email: this is an idea and there is no decision made, so we welcome your opinion and comments.</div><div>Please share them with us if you have some!</div>
<div><br></div><div>Daniel</div><div><br></div><div><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Paul Ramsey</b> <span dir="ltr"><<a href="mailto:pramsey@cleverelephant.ca">pramsey@cleverelephant.ca</a>></span><br>
Date: 2010/9/10<br>Subject: [postgis-devel] Bringing PgRouting into PostGIS<br>To: PostGIS Development Discussion <<a href="mailto:postgis-devel@postgis.refractions.net">postgis-devel@postgis.refractions.net</a>><br>
<br><br>PSC,<br>
<br>
Discussing with the PgRouting team here in Barcelona the prospect of<br>
moving them into PostGIS as an integrated feature. The process would<br>
take some time and probably not land until 2.1.<br>
<br>
The benefits in terms of offering a more integrated and complete<br>
product seem very compelling to me (and are similar to the benefits we<br>
are going to get as raster moves into the main tree), and since they<br>
are willing and eager to join us, this is a great opportunity.<br>
<br>
The stages would be<br>
<br>
(a) move their code and tickets into our OSGeo infrastructure, with<br>
their code living in /spike/pgrouting to start with and their tickets<br>
under a "routing", basically following the model we used with raster<br>
(b) they will prepare a migration plan for how to bring their code<br>
into the main tree. This will involve changes on their part<br>
(standardizing function names, directory structures, etc) and perhaps<br>
changes on our part (adopting a CMake build)<br>
(c) prepare the ground for the migration by making any changes<br>
required in our tree (CMake, for example)<br>
(d) final cut-over into the main tree<br>
<br>
Any questions on this?<br>
<br>
Paul<br>
_______________________________________________<br>
postgis-devel mailing list<br>
<a href="mailto:postgis-devel@postgis.refractions.net">postgis-devel@postgis.refractions.net</a><br>
<a href="http://postgis.refractions.net/mailman/listinfo/postgis-devel" target="_blank">http://postgis.refractions.net/mailman/listinfo/postgis-devel</a><br>
</div><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse"><div><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse"><br>
</span></div><div><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse"><br></span></div><div><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse"><br>
</span></div><div><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse"><br></span></div>-- <br>Georepublic UG & Georepublic Japan<br>eMail: <a href="mailto:daniel.kastl@georepublic.de" style="color:rgb(66, 99, 171)" target="_blank">daniel.kastl@georepublic.de</a><br>
Web: <a href="http://georepublic.de" style="color:rgb(66, 99, 171)" target="_blank">http://georepublic.de</a><br><br></span>
<br></div>