Well, it seems I was unintentionally cunny, as I just wrote …
There were no word about GSOC ! 
Some GSOC student completed their work … coming back as a contributor.
We hope so you - I mean GSOC assignees - may like Haiku during your coding period, and find a way to support Haiku and/or the services/applications added/improved by you to continue implementing things after your “official” challenging/learning period ends.
Of course we accept that also if our beloved project and associates is just a one time curve for you, guys.
For us every year and every season, moreover every month have surprises.
For example waddlesplash you mentioned earlier, as who would help you out with AMD hardware to help coding/testing SVM stuff, he is - in July - just sheds the patches of several areas, even more than doubled the patches of last month.
As I’ve seen, it happens sometimes, as
someone create a patch or two,
he reviews it/them and based on that he starts to refactor/clean(remove or fix)/complete/add new debug options/reduce log entries of that part of Haiku kernel/driver/service or even Haiku application.
It will be interesting monthly report of July 2024.
And of course,
we are awaiting your GSOC final reports, – from all of you, guys.
This year it was five very interesting and moving selections - some might personally differentiated how important for each Haiku users - by their usage - but all of them was expected long time here to be improved or implemented.
We are appreciated you selected our beloved, friendly project to your GSOC learning curve … this year, and generally every year…