I have had multiple persons tell me recently that they truly hesitated and made really sure they didn't submit slop before they filed their first security reports to #curl.

Meaning: public shaming seems to at least partially work. Banning, taunting and ridiculing the fools works as a reminder for people to maybe think again and make sure.

== less wasted time for us.

#curl
in reply to daniel:// stenberg://

While I agree that "public shaming" of the worst is for now a needed tool, it should not be the only, or even the main one, used.

We who live the open source way of life need to also get better on showing the benefits for everyone when contributing quality, at any level.

Including ones own journey learning and using all the amazing stuff we collaborate in creating.

If we can do that, I think it will be easier for more to quicker understand that open source is so much more for them.

in reply to daniel:// stenberg://

right or wrong, a response is at least useful. The person can decided whether it's worth their time doubling down constructively, and if they really are honest they likely will because they care (it's kinda like human greylisting) . Importantly, the burden and onus is not on you.

I've submitted many bugs in closed source software (mostly Microsoft) and hear literally nothing back.

This entry was edited (1 month ago)
⇧