News for hackers. Stuff that matters.
Re:A Sad Day for Rust by zozbot234 on Friday January 17, 2020 @02:25PM (#22078197)
Expecting a reasonably-quick response to security concerns is certainly appropriate.
Re:A Sad Day for Rust by jdbernard on Friday January 17, 2020 @03:27PM (#22078852)
In a free project where the author isn't paid? What if he's on vacation? What's the SLA there? Is it reasonable to expect him to cut short the vacation?

If you want to be able to place expectations on the author, pay them and get a contract.

Re:A Sad Day for Rust by atoav on Saturday January 18, 2020 @05:31AM (#22083632)
Then it is about communicating exactly this. Security and trust hinge on properly communicating what is going on.
Re:A Sad Day for Rust by dunnock on Friday January 17, 2020 @03:48PM (#22079106)
That's like expecting your boss to double your salary because he is paying you salary. Opensource expectation should be in general if you are not happy feel free to fork and fix yourself. Then submit PR if you want to push your fix upstream.

But still so many PRs getting rejected, because they do not pass code review and usually it does not cause reporters of those failed PRs to open whole big flame discussion. That + overreaction on reddit was a last drop after which Nikolay decided to close the thing.

Re:A Sad Day for Rust by protomyth on Friday January 17, 2020 @03:30PM (#22078882)
What is reasonably-quick time wise?