> This is a weak argument to not participate in GSoC
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.
I guess I wasn't very clear in my comment. I don't use OpenBSD, I don't subscribe to their mailing list and I am not a contributor. Hence, it will be nonsensical of me to go and criticize their decisions there.
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.
Well, the way they spoke out about their lack of participation kinda hurts the perception of GSoC, thus I'd say it's a good moment to talk about it.
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.