My name is Fawaz Lawal and I am a fourth-year engineering student at Obafemi Awolowo University (OAU) in Ife, Nigeria. I am deeply passionate about open-source development and GIS ecosystems.
I am working toward participating in the upcoming GSoC 2027 cycle with OSGeo, specifically focusing on pgRouting and I am currently using this period to build my technical foundations. My current roadmap includes configuring my local PostgreSQL/pgAdmin sandbox, diving into PostGIS network topologies, and studying pgRouting’s core C++ architecture (graph algorithms and data validation structures).
My goal right now is to get familiar with the codebase and start contributing to small patches, documentation fixes, or unit tests early on.
I am incredibly excited to join this community, listen, and learn from you all. Please let me know if there are any specific low-hanging issues or areas you recommend a newcomer look into!
@cvvergara is in the middle of updating that for upcoming FOSS4G in Japan so it would be good to review what is there and let us know anything that seems out of place or is unclear as a user trying to follow along
I should also add, that PostGIS topology and pgrouting topology have nothing to do with each other. So trying to learn postgis_topology extension to understand pgrouting topology will not be very helpful. The pgrouting topology is a much simpler model.
Thank you very much for that clear direction, Regina. You just saved me from moving the wrong way.
I will keep watching the pgrouting-dev Discourse. I will also dive right into reviewing the pgrouting Workshop source files and will note down anything that looks out of place or unclear to share with you and @cvvergara
I started going through the workshop documentation and noticed a small typo in Section 1.1 (Basic). The opening sentence starts directly with ‘will demonstrate…’ and seems to be missing its subject. I think adding ‘This section will’ or ‘This level will’ would make it much clearer for a user following along.
Ah great catch. @cvvergara is it okay if @Fawaz-Lawal starts a pull request for things he finds or you prefer he wait until you’ve made some restructurings.
Thank you for the warm welcome. I’ll get right on fixing those typos and grammatical mistakes in the documentation and open a Pull Request shortly for your review.
It’s my pleasure. Thank you so much for the opportunity. I’ll keep looking out for fixed I can suggest. I’m also open to taking up new tasks to get more familiar with the codebase.
They are very outdated as you can see from the versions we reference. It would be good to have an update of that, which maybe you can do as you try to setup your env and run into issues.
Sorry I’ve been away for too long. My laptop got damaged shortly after our last conversation so I wasn’t able to carry on with the work. I’ve got a new one so I’m back now. I’ll get started with setting up the dev env and go through the dev docs as I do so. Any problems run into along the way will be duly noted.
Please, I have a question regarding running test suite on develop branch build as stated in the contributor requirements. I have successfully built and installed both the latest tagged release and the develop branch into Postgresql and verified that they installed successfully. I am now attempting to run the test suite for the develop branch build and I kept running into issues: No tests were found!!! error
Could you clarify the recommended command or CMake configuration flags needed to execute the test suite, please?
There’s definitely something I’m doing wrong. Looking forward to a favourable response.
Ps: I have been making few changes to the developer wiki on the GitHub page. Just trying to squeeze time out of my busy schedule to fix things here and there.
ctest won’t find anything and that’s not your setup, there’s no enable_testing() or add_test() anywhere in the CMake files
They’re pgTAP files under pgtap/ and the doc examples under docqueries/, both run by their own scripts
Between the two @robe mentioned, go with pg_prove_tests.sh. The run.sh one is a personal scratch script, its header says to copy it to your repo root and edit it first, so it won’t work the way you wanna use it
Two thinbs worth knowing before you run it. pg_prove and the pgtap extension ain’t build dependencies, so building fine doesn’t mean you have them, check that first, and the script doesn’t create the test database itself, setup_db.sh only creates the extension and loads the fixtures, so you have to create it beforehand and drop it after
running it twice on the same database fails because the fixtures aren’t
One last thing, if pg_prove says Bad plan … ran 0 it usually means the extension loaded in the database is still the old one, not what you just installed
recreating the extension in the test db after installing sorts that out
Thank you for the response and explanation. I will make the installations, create the test database manually, rerun the test and note whatever response I get.
Thanks for the guidance. Following your steps, I was able to run the test using pg_prove_tests.sh cleanly on the develop build and all 532 TAP test files passes 100%
Appreciate the help from both you and @robe helping me set up with the testing environment.
