Niall Douglas wrote
We heard back. Google's explanation is simply that they like to give a year off to particularly successful and long running GSoC orgs in order to make space for new orgs, and they hope we apply again next year.
To say I found this explanation jaw dropping would be putting it mildly, but there you go.
We've asked if they would have any issue with us running the Summer of Code in 2016 out of Boost monies. If they don't, we'll send a petition to your good selves at the Steering Committee, and go from there.
I would expect potentially half our students won't be interested this year as they are really seeking Google Summer of Code for their resumes, however for those who really genuinely want to work in the Boost libraries I expect they may be as keen as ever.
So I guess watch this space!
Niall
That's a sad news and Boost being a successful GSoC org is a really poor excuse for that decision.. However, I think I'll keep working on fixing and improving Boost.Compute anyway, in my free time. I'm waiting for more information regarding "running the Summer of Code in 2016 out of Boost monies". Thanks to everybody who worked on Boost GSoC application etc. -- View this message in context: http://boost.2283326.n4.nabble.com/gsoc16-Boost-rejected-as-GSoC-2016-org-tp... Sent from the Boost - Dev mailing list archive at Nabble.com.