mgorny-nyan (he) :autism:🙀🚂🐧<p>"""<br><a href="https://social.treehouse.systems/tags/OpenRC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenRC</span></a> […] has been in a state of bureaucratic decay for a decade now, having all been hoarded by a random corporate contractor about as responsive to the outside universe as OpenOffice (while taking up as much space; they're the entire reason for the farcical metadata/AUTHORS file in the main package repo).<br>"""<br><a href="https://lwn.net/Articles/964589/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">lwn.net/Articles/964589/</span><span class="invisible"></span></a></p><p>This reminds me of the story. The modern <a href="https://social.treehouse.systems/tags/Gentoo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Gentoo</span></a> copyright policy (AKA <a href="https://social.treehouse.systems/tags/GLEP76" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GLEP76</span></a>) has been a long time in the making. More specifically, as you can guess from the author list, it has been a long time in fruitless debate, followed by a short period of creative activity. In its original form, it has been unanimously approved both by the Council and the Trustees in September 2018.</p><p><a href="https://bugs.gentoo.org/653118" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">bugs.gentoo.org/653118</span><span class="invisible"></span></a></p><p>Not a month later, once we've actually started requiring signoffs per the new policy, one of the Council members requested a "transitional period", to give their company's legal team more time to approve it. Like, they've actively influenced the policy, they've actually voted for approving it, but they didn't mean for it to actually apply at the time — and they've never bothered telling anyone about the problem earlier. Fortunately, they've managed to get a quick approval and started using it.</p><p><a href="https://bugs.gentoo.org/667602" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">bugs.gentoo.org/667602</span><span class="invisible"></span></a></p><p>As a side effect of using it, attribution lines to said company started popping up in random ebuilds that their employees touched (malicious compliance or just corporate bullshit?). This heralded a maintenance nightmare. Two months later, metadata/AUTHORS was proposed as a compromise to stop that.</p><p><a href="https://bugs.gentoo.org/672962" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">bugs.gentoo.org/672962</span><span class="invisible"></span></a></p><p>All these years later, I'm thinking that we had a simpler solution to all these, and many later problems, at our disposal back then…</p>