GSoC 2026 first coding period

Comments

• Mohit242-bit@discourse.osgeo.org ⁨3⁩ ⁨weeks⁩ ago

  Hii @cvvergara ,

  Following our last meeting where you suggested working on both algorithms in parallel, I wanted to confirm how I should structure the weekly plan on my GitHub wiki page.

  My proposal had pgr_makeBiconnectedPlanar in Weeks 1–6 and pgr_makeMaximalPlanar in Weeks 7–12 sequentially. Since we’re now doing both in parallel, should I restructure the wiki plan to show combined milestones per week? For example:

  • Week 1: Core implementation files for both algorithms (SQL, C, C++ driver, HPP)

  • Week 2: Edge cases and testing for both

  • Week 3: …so on

  I have made PRs for both and for makebiconnected done with basic implementation, Just wanted to know regarding github wiki page updates so I am aligned with the goals.

  Thank you!

  original

  • cvvergara@discourse.osgeo.org ⁨3⁩ ⁨weeks⁩ ago

    First topic of the meeting will be then, review admin procedures, filling the wiki is part of it

    original

    • cvvergara@discourse.osgeo.org ⁨3⁩ ⁨weeks⁩ ago

      Hi all,

      Dont forget we have a meeting in about an hour.
      Regards
      Vicky

      original
• sakirr05@discourse.osgeo.org ⁨4⁩ ⁨weeks⁩ ago

  Hi Vicky,

  I couldn’t properly catch up with the work earlier this week because I had exams and also needed to prepare for two exams scheduled for tomorrow.

  I have now pushed the remaining skeleton structure changes that were discussed in the meeting. Some tests/CI checks are still failing at the moment, but I’m already working on fixing them and plan to resolve everything by tomorrow night.

  Also, if there is any meeting planned for tomorrow (friday), I would really appreciate if it could be postponed because of the exams.
  Sorry for the delay

  original

  • cvvergara@discourse.osgeo.org ⁨3⁩ ⁨weeks⁩ ago

    @sakirr05
    ok, meeting is usual monday at usual place and usual time.

    original
• cvvergara@discourse.osgeo.org ⁨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

  original