I hope you’re doing well. I wanted to sincerely thank you for the opportunity to participate in GSoC 2025 with OSGeo. It was a rewarding experience preparing the proposal and working with pgRouting, and I’ve learned a great deal through the process.
While I was not selected in the final list, I’m very committed to continuing open source work — and possibly contributing to pgRouting outside of GSoC as well.
To help me improve and understand how close I was to being accepted, would it be possible to know where my proposal ranked in the final evaluation? I understand you may be busy post-announcement, but any insight — even a brief note — would be greatly appreciated.
Thank you again for your time, mentorship, and the platform you’ve built.
Students:
You must have received a couple of invitations to the projects github organization. Please accept.
Once accepted you will be able to add your wiki page on pgRouting wiki.
Here you will need to fill up with the link of the wiki page you created above.
For the OSGeo wiki you need to log in with your OSGeo ID to be able to modify the page.
As I mentioned previously we will use these days to set up a schedule which will be a little bit complicated:
Meetings, bonding or otherwise, are planned to be on Monday. That way it allows to plan the work for the week.
Developing Open Source in general is done asynchronously because of time differences and the way we communicate, is by
a PR comment or
an issue comment or
a discourse topic
In pgRouting: mentors and students are considered a team, regardless of the “main mentor” or the “assigned mentors” that google stated. Having said that:
Any mentor can help any student.
In administrative tasks
In coding tasks
Any student can help any student. As the coding process is similar with one another:
Explanations of work done.
Because of the big time difference between mentors and students, we will work as follows:
Before or just after the Monday meeting, there should be a PR to your branch in the GSoC-pgRouting repository
We will create the branch during the bonding period
Any work you do, commit it and push it.
It is the only way we have to see what you are doing
The commit will show on the PR you opened
Use code rabbit when you have doubts, and we are not around. It will give you some hints.
@coderabbitai review
If you can resolve “fast” please do.
Note: Not everything the rabbit says needs resolution
Create a summary of your PR before the weekly report:
@coderabbitai summary
You can create an issue about pending work:
@coderabbitai create an issue with all the unresolved conversations
Merge your PR before you write your weekly report
Mentors do not do the merge
Your detailed weekly report is to be done on your wiki page
Sorry, starting next week, I’ll have another weekly meeting at the same time (Tuesday at 11 AM JTS) in my new job, so it will be difficult for me to join the GSoC weekly meetings.
I’ll do my best to stay updated on the progress asynchronously, but I apologize for the inconvenience.
Since you won’t be available at the usual time starting next week, should we consider rescheduling our weekly GSoC meeting to a new time that works for everyone?
Since you won’t be available at the usual time starting next week, should we consider rescheduling our weekly GSoC meeting to a new time that works for everyone?
Thanks for considering it!
If possible, one hour later would work best for me, as that aligns with my lunch break:
I’m sorry to inform you that I’ll be on the train for my tennis match from 10 AM to 12 AM this week, so it’s a bit inconvenient for me to attend the meeting during that time.
Starting next week, I’m available from 11 AM China time.
By the way, I wonder if it’s possible to adjust this week’s meeting to the same time slot as Saloni and Bipasha, if that works for everyone.
