chapter 2: qdd note about proprietary software

Author: drupol

src/thesis/2-reproducibility.typ

@@ -562,6 +562,25 @@ bolstering both confidence and safety in software systems. This widespread
 participation and verification process inherent in open-source development
 contributes significantly to the reliability and security of the software.
 
+#info-box(kind: "note", ref: "info-box-proprietary-software")[
+  Proprietary software does not expose its source code to the public, which may
+  seem counter-intuitive to the principles of reproducibility. Proprietary
+  software typically cannot be distributed, inspected, or modified by others.
+  They are, thus, reliant on a single supplier and prone to proprietary
+  obsolescence #cite(<9403875>, form: "normal", supplement: [p. 3]).
+
+  Ensuring the reproducibility of such software is challenging, as users lack
+  access to the build process and the software's lifespan is often limited due
+  to its proprietary nature. Pre-built binaries will work only as long as there
+  are no breaking changes in dependencies like the GNU C library, making their
+  reproducibility capabilities time-limited.
+
+  Being aware of the broader implications of using proprietary software is
+  crucial but does not necessarily compromise reproducibility at short term.
+  However, relying on them for long-term reproducibility is risky due to the
+  lack of transparency and control over the software's evolution.
+]
+
 === Terminology
 
 Establishing formal definitions and terminology is crucial for aligning