It saves ewaste. In 6 years, will macOS still be supported on these machines? Maybe. Will an open source distro be supported? If it’s still thriving, yeah.
Mastodon: @sean@dice.camp
It saves ewaste. In 6 years, will macOS still be supported on these machines? Maybe. Will an open source distro be supported? If it’s still thriving, yeah.
AGPL? Google has a ban on all AGPL software. Sounds like if you write AGPL software, corporations won’t steal it.
Code licensed under the GNU Affero General Public License (AGPL) MUST NOT be used at Google.
The license places restrictions on software used over a network which are extremely difficult for Google to comply with. Using AGPL software requires that anything it links to must also be licensed under the AGPL. Even if you think you aren’t linking to anything important, it still presents a huge risk to Google because of how integrated much of our code is. The risks heavily outweigh the benefits.
Any FLOSS license that makes a corporation shit its pants like this is good enough to start from IMO.
https://opensource.google/documentation/reference/using/agpl-policy
If it’s only internal then technically the internal users should have access to the source code. Only the people who receive the software get the rights and freedoms of the GPL, no one else.
Asahi Linux
https://asahilinux.org/