And in fairness, the corollary: An open-source project which inconsistently applies standards can potentially be worse than an open-source project which applies no standards at all.
Näytä tämä ketju
Hot take: Bad code written for free is still bad code. If you expect open-source projects to fall over themselves with gratitude and overlook any kind of bare minimum bar of quality just because you deign to "contribute", it isn't the project that's toxic, it's you.
-
-
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
-
-
Addendums on the other side of the fence: * If the code is bad because the contributor simply doesn't know better, the project should ideally help the contributor to improve their work. * Releasing insecure software as a maintainer is irresponsible, free or not.
-
For the former, the Rust community's mentorship model is an interesting one to look into. It helps to *decrease* project workload in the long run, by on-boarding new good contributors. For the latter, this obviously only applies for *known* security issues they refuse to fix.
- Näytä vastaukset
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.