[pgrouting-dev] GSoC Timeline

[Jinfu Leng]

Hello Steve, Daniel and Jay,

Thanks very much for your suggestions. It looks like there is a lot of
staff are waiting for me to discover.

I am working on my final, and it should be done on May 6th. After that I
will devote myself to this exciting project. Then I can start the weekly
report. In addition, during this summer, I will stay in US for half and a
month, and stay in China for half and a month.

Steve, thanks for you suggestions on the calender. My calender was already
updated now.
Daniel,as you asked, I just created a github account, and the user name is
"jinfu-leng".
Jay, your experience as a previous GSoC students would give me many help.

Thanks,
Jinfu

On Mon, Apr 23, 2012 at 9:33 PM, Jay Mahadeokar <jai.mahadeokar at gmail.com>wrote:

> Hi Jinfu and Razequl,
>
> Congrats again for getting the project accepted.
>
> Daniel and Steve have already given most of the instructions in detail. I
> would say most important steps are - learning to compile any existing
> pgRouting algorithm and debugging it. Make sure you are able to print out
> additional debug messages from your core function, since that will be most
> helpful in the future. Let me know if you have problems with that.
>
> Next I would suggest you plan out the design and exact prototype of your
> implementation. Last year I had this:
> https://github.com/pgRouting/pgrouting/wiki/TDSP-Details
>
> This can be modified a bit when you implement but most of the ideas should
> be conveyed with this.
>
> Best of luck!
>
> On Tue, Apr 24, 2012 at 7:48 AM, Daniel Kastl <daniel at georepublic.de>wrote:
>
>> Hi Jinfu, Razequl,
>>
>> First of all congratulations!
>> And thank you, Steve, for this post.
>>
>> Just let me add a little additional information:
>>
>> OSGeo as mentoring organization wants to help students to pass milestones
>> and deadlines.
>> For that we often have OSGeo internal deadlines a few days ahead of GSoC
>> deadlines. And OSGEo also requires weekly reports.
>> All this can help you not to run out of time at the end of the GSoC
>> program.
>>
>> What really helps is to being ahead of deadlines. Ask Jay! ;-)
>>
>>
>>>
>>> http://download.osgeo.org/**pgrouting/forum/pgrouting.**
>>> postlbs.org/wiki/**pgRoutingDocs.html<http://download.osgeo.org/pgrouting/forum/pgrouting.postlbs.org/wiki/pgRoutingDocs.html>
>>
>>
>> Steve pointed you to the previous (cached) website Wiki.
>> The newer (and slightly updated and revised one) should be here:
>> http://www.pgrouting.org/documentation.html
>>
>> If you don't have a GitHub account yet, create one and let me know your
>> account ID.
>> You can then use also pgRouting's GitHub Wiki pages for planning and
>> documenting your project. If you like you can use the issue tracker as well.
>>
>> Here is a link to last year's GSoC projects documented in the Wiki:
>>
>> https://github.com/pgRouting/pgrouting/wiki/Multi-modal-Public-Transit-Routing
>>
>> https://github.com/pgRouting/pgrouting/wiki/Time-dependent---Dynamic-Shortest-Path
>>
>> There is no required structure, so you can organize it as you like.
>>
>> Daniel
>>
>>
>>
>> --
>> Georepublic UG & Georepublic Japan
>> eMail: daniel.kastl at georepublic.de
>> Web: http://georepublic.de
>>
>> _______________________________________________
>> pgrouting-dev mailing list
>> pgrouting-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>>
>>
>
>
> --
> Regards,
> -Jay Mahadeokar
>
>
> _______________________________________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20120424/429d89ff/attachment.html