NASA’s new dark energy space telescope can also detect killer asteroids
technologyreview.com·3h ago
Data Science
Simon Willison's Blog·Jun 5·5 min read
Quoting Andreas Kling
TL;DR
A gap existed in the assumption that substantial code contributions indicated good faith. Ladybird, a web browser, is now being developed with a focus on accountability, requiring contributors to be responsible for their changes.
✦ Why It Matters
Engineers should prioritize accountability in code contributions to enhance project integrity and user trust.
Key Takeaways
- Reassess contribution guidelines to prioritize accountability.
- Limit code changes to trusted contributors.
- Encourage direct involvement in decision-making processes.
- Focus on the implications of code changes for end users.
Full Summary
Andreas Kling, in a recent update on the development of Ladybird, a web browser, declared a significant policy change: the project will no longer accept public pull requests. Previously, substantial patches were seen as indicators of good faith and effort, but this assumption has become unreliable.
Kling argues that the focus should shift from how code is contributed to who is responsible for it once integrated into the browser. As Ladybird evolves to serve real users, it is crucial that those making changes are also accountable for their implications.
This change aims to enhance the quality and reliability of the browser by ensuring that contributors are directly involved in decision-making and responsible for the outcomes of their code.