Also I can't tell if you are directing the last part of your comment towards me or towards Google, but I certainly respect their decision to not participate. They participated previously and decided that the payout in terms of new contributors wasn't worth it (and I agree with them there) - at the same time there is a second angle to look at GSoC from and that is what I pointed out in the last part of my comment.
Option A: Discuss shortcomings of a project that its members don't intend to change on Hacker News like a lot of other things. Maybe learn something.
Option B: Send email about those to the project's official mailing list. Spend some amount of time in a flame war that teaches nobody anything.
Although you want B, I think most should just stick with A. Better time/reward ratio.
Also, is there a list of software development taboos we shouldn't discuss here or it's just my impression that it's a bit too easy to get you angry by a simple comment?
Hey, at least have the courage and in integrity to tell them directly how to run their project. On the mailing list. Not here.
Open source drive-by project management is one of the most fascinating (and sad) phenomenon to me. How can people who have no association with some other group of individuals have the audacity to tell them how to spend their time and how to run their project. It's bewildering.