We need to know how to describe software in ways that are meaningful to engineers, developers, and managers, while including practical considerations such as the nature of the collected data and the units of measurement. That need leads us to ask this question: "What is the current state of the art in the process of making software visible?" The aim of this edition is to open this discussion up to the profession. To that end, we present five views on how to make the software process and product more visible.