Hi Steve, Daniel,<br><br>Sorry, I have been occupied with things in college. But I think I will have time to take up small coding assignments starting January. Besides I would be willing to contribute in designing and discussion regarding the next release.<br>
<br>The points which Steve mentioned, should we discuss them in separate dedicated threads (start with priority tasks)?<br><br><div class="gmail_quote">On Mon, Dec 5, 2011 at 7:06 AM, Daniel Kastl <span dir="ltr"><<a href="mailto:daniel@georepublic.de">daniel@georepublic.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi Steve,<div><br></div><div>Good point and reminder!</div><div>Shall we collect all your items in the Wiki?</div>
<div><a href="https://github.com/pgRouting/pgrouting/wiki/2.0-Development-Plan" target="_blank">https://github.com/pgRouting/pgrouting/wiki/2.0-Development-Plan</a></div>
<div><br></div><div>Some work has been done already in this branch:</div><div><a href="https://github.com/pgRouting/pgrouting/commits/devel-2_0" target="_blank">https://github.com/pgRouting/pgrouting/commits/devel-2_0</a></div>
<div><br>
</div>
<div>Daniel</div><div><br></div><div><div><div class="h5"><br><br><div class="gmail_quote">On Mon, Dec 5, 2011 at 10:29 AM, Stephen Woodbridge <span dir="ltr"><<a href="mailto:woodbri@swoodbridge.com" target="_blank">woodbri@swoodbridge.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div>On 12/4/2011 8:10 PM, Stephen Woodbridge wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Devs,<br>
<br>
So I have been thinking about the next release and thought it would be a<br>
good idea to start getting input in what we think are potential target<br>
items that can and need to be in the next release.<br>
<br>
This should probably be put in a release ideas wiki page and we probably<br>
should open tickets for these also, but it is easier for me to think by<br>
just writing email. So here are some items to seed the list:<br>
<br>
o rename all pgrouting functions to use the namespace pgr_*<br>
o write some new wrapper functions<br>
- we need to discuss what the public API should be<br>
- we need to standardize the routing function calls so that it is<br>
trivial to change the function name but 99% of the arguments are the<br>
same or similar<br>
o potentially remove CGAL and GAUL dependencies<br>
o identify what new algorithms in git should get promoted to a core release<br>
o fix shooting star which is seriously broken in v 1.0.5 and maybe v1.0.3<br>
o automated tests in git for developers and release managers to use to<br>
validate functionality before we code gets committed or released<br>
o update all the documentation based on the changes that get committed<br>
to the release.<br>
</blockquote>
<br></div>
And one more:<br>
<br>
o all wrappers AND pgrouting need to work with data in any schema.<div><div><br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Since Anton has moved on to other projects, we do not have a C++<br>
developer on the project. I can do plpgsql, C and some very minor C++<br>
stuff. Daniel and I have contacted former GSoC students, but they are<br>
all pretty busy with careers. I have been working with Ashraf that<br>
worked on OpenGraphRouter code as a GSoC student and we have him working<br>
on pgRouting project at the moment, but if we could pick up another C++<br>
developer even part time to help with some of this that would be great.<br>
Obviously, Boost Graph and/or graph theory knowledge would be a big plus.<br>
<br>
Thoughts?<br>
<br>
-Steve<br>
______________________________<u></u>_________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><span style="font-family: arial,sans-serif; font-size: 13px; border-collapse: collapse;">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></span><br>
</font></span></div>
<br>_______________________________________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Regards,<br>-Jay Mahadeokar<br><br>