https://hyper-expanse.net/Recent content on hyper-expanseHugoen-USSun, 12 Jul 2026 17:35:33 -0500https://hyper-expanse.net/guides/developer-certificate-of-origin/Sun, 12 Jul 2026 17:35:33 -0500https://hyper-expanse.net/guides/developer-certificate-of-origin/<h1 id="developer-certificate-of-origin">Developer Certificate of Origin</h1> <p>All contributors MUST certify they are able and willing to provide their contributions under the terms of a project&rsquo;s license by signing off on a <a href="https://developercertificate.org/"><em>Developer Certificate of Origin</em></a> (Version 1.1).</p> <p>For a contributor to certify their ability, and willingness, to meet the requirements of the <em>Developer Certificate of Origin</em> (DCO), the following line must be included as the last line of a commit message for every commit contributed:</p>https://hyper-expanse.net/hutson/Sun, 12 Jul 2026 17:35:33 -0500https://hyper-expanse.net/hutson/https://hyper-expanse.net/guides/labels/Sun, 12 Jul 2026 17:35:33 -0500https://hyper-expanse.net/guides/labels/<h1 id="labels">Labels</h1> <p>Many source control platforms, including GitHub and GitLab, have limited issue tracking capabilities, usually leaving you with nothing more than the ability to assign an issue to a milestone, assign the issue to one or more individuals, and lastly, to attach one or more labels.</p> <p>As a result, labels carry significant importance to communicate information about an issue, such as the component of a project the issue is associated with, the importance, or priority of the issue, what kind of experience may be required to resolve the issue, etc.</p>