4 ms·

I don't know exactly how big the OpenBSD volunteer team is but I think it must be substantially larger than most open source projects because of their user base

by pkd 10y ago

I don't know exactly how big the OpenBSD volunteer team is but I think it must be substantially larger than most open source projects because of their user base. This is a weak argument to not participate in GSoC. There are multiple projects with a much smaller volunteer base than OpenBSD who participate in GSoC. At the same time I do recognize that the effort involved for mentoring someone is huge and the actual payout is not much for the mentor (it was $500 the time I participated). I think it is viable to see GSoC as a platform through which you can reward your existing student contributors as well - ask them apply through GSoC and they can get paid for their contributions. This eliminates the effort involved in onboarding new contributors and also provides a nice reward for the existing contributors.

4ad 10y ago
> 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.
- pkd 10y ago
  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.
- d33 10y ago
  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?
- nickpsecurity 10y ago
  "Hey, at least have the courage and in integrity to tell them directly how to run their project. On the mailing list. Not here." 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.

by pkd 10y ago

4ad 10y ago

> 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.

pkd 10y ago
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.
d33 10y ago
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?
nickpsecurity 10y ago
"Hey, at least have the courage and in integrity to tell them directly how to run their project. On the mailing list. Not here." 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.