cvvergara
@cvvergara@discourse.osgeo.org
- Comment on GSoC 2026 first coding period 3 weeks ago:
Hi all,
Dont forget we have a meeting in about an hour.
Regards
Vicky - Comment on GSoC 2026 first coding period 3 weeks ago:
First topic of the meeting will be then, review admin procedures, filling the wiki is part of it
- Comment on GSoC 2026 first coding period 3 weeks ago:
@sakirr05
ok, meeting is usual monday at usual place and usual time. - Comment on GSoC 2026 first coding period 4 weeks ago:
From tuesday meeting:
Week plan (for function
pgr_foo):Create the code skeleton to be used (in appropriate subdirectories).
- sql: _foo.sql, foo.sql
- src: foo.c, foo_process.cpp foo_driver.cpp
- include: foo_process.h foo_driver.hpp
If possible:
- doc: pgr_foo.rst
- docqueries: foo.pg (can be empty) foo.result
My wish is that the skeleton compiles before the start of next week so we can start modifying it.
From the PRs I see 2 PR missing, one for each contributor that is doing 2 functions
I had time today to review the progress and prepare for the meeting where we add the code to the build and make it compile but the PRs still have only the sql files. (except mine)
That is, on your PRs they have the work you did while during the meeting and the demo copy/paste of the remaining files I also did during the meeting is missing.
This is like running a marathon: Average Speed: (2.6) to (3.5) mts/s
You don’t run a marathon by sitting down, then run 100mts in 10 seconds, then sit down, then run another 100mts in 10 seconds, to get that average speed.
You run the marathon by running all the time, maybe the speed is faster at the beginning than at the end because you are tired, but you keep a pace.Remember we am not behind you, the only way for us to see your work is because you pushed it.
You wouldn’t be the first ones or the last ones that get a fail on the program on the second week.
Regards
Vicky - Submitted 4 weeks ago to pgrouting-dev@discourse.osgeo.org | 6 comments