Secondary / backup account for @[email protected]
(header photo by Brian Maffitt)
In addition to not qualifying by most definitions of open source (as already mentioned), CC is not recommended for use in software: https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software
We recommend against using Creative Commons licenses for software. Instead, we strongly encourage you to use one of the very good software licenses which are already available.
[…]
Unlike software-specific licenses, CC licenses do not contain specific terms about the distribution of source code, which is often important to ensuring the free reuse and modifiability of software. Many software licenses also address patent rights, which are important to software but may not be applicable to other copyrightable works. Additionally, our licenses are currently not compatible with the major software licenses, so it would be difficult to integrate CC-licensed work with other free software. Existing software licenses were designed specifically for use with software and offer a similar set of rights to the Creative Commons licenses.
Edited link for kbin/mbin users: https://creativecommons.org/faq (scroll to Can I apply a Creative Commons license to software?)
Through long and weary travels,* I bring the gift of source preserved by the workers of the great archives: https://web.archive.org/web/20140831164530/http://bjorn.tipling.com/if-programming-languages-were-weapons
* (they weren’t that bad honestly, a kind soul that took the journey 9 years ago made mine much shorter)
Not that it really matters much, but here’s the original version of the image: https://www.gettyimages.com/detail/photo/google-android-phone-characters-group-royalty-free-image/458243847
Finding optimal CO values that are long-term stable across all workloads (namely: idle) is such an enormous PITA though X_X