As a student who is interested in Gsoc 2025, I have finished tasks in Intent of application. Now I want to fix some bugs in pgrouting repository which can help me get more familiar with pgrouting, but it seems a bit difficult to start. Could you give me some advices?
Which bugs?
Did you take a look at the list - GitHub · Where software is built
to see what interests you and what you want to try tackling?
After that maybe you give us a specific one and how you tried and what questions you have about it, would be easier to help you.
Thanks for your instructions! @cvvergara @robe
I have took a look at some issues in pgrouting repository before I post this topic, but I still feel a bit confused about how to choose a proper issue for me:
- Can I only select issues marked as bug?
- Since I just started getting familiar with pgrouting, I’m not sure which type of issue I should choose to solve.
- In addition, I think my understanding of pgrouting projects is still relatively shallow. Is there anything I can do to become more familiar with pgrouting?
Hi wifi
Based on your comment: “I think my understanding of pgrouting projects is still relatively shallow.”
Have you solved all the workshop exercises?
You will get an understanding on how to use pgRouting.
Please, if you find something wrong there open a PR.
Have you tested all the queries of all the functions on the documentation?
For example from pgr_dijkstra
Sometimes we don’t even open an issue and we get a PR solving it. Like this one and just like that is how people start to get involved.
In any case I prefer PR’s on workshop if you find an issue.
I know you have come to a couple of developer meetings.
By going to those meetings you will get familiar with the code of pgRouting.
If you are aiming to contribute with GSoC, you must know:
We are not teachers/professors, we are developers.
Maybe you are a student at school, but this is not school.
Maybe like me, you are an economist, and this is not school.
I am going to quote myself see comment on a documentation issue on Jul 25, 2013:
“Never used Sphinix before… but I never used postgis nor pgrouting nor mapserver before march this year and I have already a working map of mexico with the 32 states that includes all the 2010 census data, So I am fast learner, I have the time and I would like very much to participate.”
And 40 days after that conversation, I had my first PR on Sep 5, 2013
You, if selected on GSoC, you will get a bonding period where there will be an explanation on how the code is organized.
Most of the Opens Source developers do not get bonding periods.
We just start to get involved.
As early starter I hope to see you in all our meetings.
Regards
Vicky
Dear Vicky,
Thank you so much for your detailed and thoughtful response! I deeply appreciate the time and care you’ve taken to share your insights and experiences with me. Your words are both inspiring and motivating, and they have given me a clearer understanding of how to approach contributing to pgRouting.
The story of your first PR and how quickly you got involved in the community is truly inspiring. It’s a testament to what determination and a willingness to learn can achieve.
I’ve already completed the workshop exercises and tested the queries for functions like pgr_dijkstra
in the documentation, which has helped me build a solid foundation for using pgRouting. However, I’m still not very familiar with the process of further development, such as modifying or writing pgRouting’s C and C++ source code. This is the next area I aim to explore, and I’ll continue to learn by experimenting and participating in upcoming developer meetings.
Your suggestions and encouragement have strengthened my confidence to take this next step. I am committed to growing as a contributor and will try to engage with the pgRouting community by opening PRs, providing feedback, and participating in discussions.
Thank you once again for your guidance and support. I look forward to seeing you in the next meeting and learning more from this incredible community!
Best regards,
Wifi