News for hackers. Stuff that matters.
Re:The People's Code by voltagex_ on Friday November 04, 2016 @12:38AM (#12870422)
I have no intention of getting into an argument with you but wow, you must be having a bad day. I wonder if you would have gotten a different response to your report if you'd taken a different tone with the people trying to understand the issue itself.
Re:The People's Code by mistermann on Friday November 04, 2016 @02:07AM (#12870678)
> if you'd taken a different tone

I've been thinking about this a lot lately....I think "why didn't you just use a different tone" is very similar to how people that grew up in environments where everything went right when they say to people struggling "why don't you just do x,y,z". The problem is, they don't know how.

Re:The People's Code by 15thandwhatever on Friday November 04, 2016 @07:06AM (#12871655)
I agree, but with a little twist: the problem is not that the latter party doesn't know how and the former party has the answers, maybe it's that the former party doesn't know how either.

In this particular instance, the actual problem is notification. OP said he fixed the bug in his original code, and one of his downstreams should fix the bug too.

Fair enough.

But then things took a turn towards "you should do the work", "civic duty", and what not. To which OP replied he's not going to fix it in a code base he's not compensated for.

The actual problem in this scenario here isn't OP's willingness to donate his time, it's that the right person at the downstream needs to be notified (and in turn acknowledge the problem). And in the world of open source, this is a common issue which is impacted by multiple notification avenues, developer continuity, and general infosec policy.

But instead of any one of us creating an issue saying "Hey dudes, this was fixed in the upstream -- here's a copy-and-paste pointing to the fixed and respective vulnerable code", it's a pile-on with holier-than-thou mantras regarding why OP should do the free work of reading the source code, testing a fix, and creating a patch.