THE OPEN-SOURCE LANDSCAPE

CHAPTER SUMMARY Open-source software is published so that anyone may read it and usually use it, under the conditions of a license. Curated lists work as maps of the ecosystem, but inclusion is not a guarantee of quality or safety. Reference implementations and starter templates are excellent for learning and for seeding projects, but you must read and own what you copy. Community benchmarks allow fair comparison, but they can lead to over-tuning, leakage, and mismatch with real tasks, so combine them with private evaluations. Free software still needs security review for maintenance, defaults, supply-chain risk, and licensing, and should be tried in a sandbox first. KEY TERMS REVIEW Open-source software: software whose source code is published for anyone to read and usually use. Source code: the human-readable instructions that make software work. License: a legal document stating how software may be used. Curated list: a chosen and organized collection of links to good resources. Reference implementation: a complete working example of one good way to build something. Starter template: a ready-made project skeleton to copy and modify. Benchmark: a standard set of tasks and scoring for comparing systems. Over-tuning: improving a system for a test rather than for real work. Leakage: test answers appearing in what a model learned from.