Permacomputing considerations thread #119
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#119
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Inspired by http://viznut.fi/texts-en/permacomputing_update_2021.html.
How can Co-op Cloud be influenced by these ideas and what can we do?
E.g. https://principles.green but not from Microsoft.
"guidelines for permacomputing in this project"
theres so much greenwashing, it seems like it might be worth making a step forward here as an example, at the very least...
attached
attached
port abra to z80 and m68kmaking sure it runs on multitude of architectures like arm, arm64 and i386 is a good starting point imo.This is an ongoing discussion so maybe having a ticket is not so useful rn.