Rules v3 #67

New Issue

rasmus · 2024-08-13T07:16:10Z

rasmus commented

2024-08-13 07:16:10 +00:00

Better define non-onprem members (think VPS). What should they be able to access, what are their ways of communication (Rasmus: e-mail + backup phone nr?), while keeping costs low. Most k-space.ee/rules apply to on-location, could we reduce it for non-onprem (especially, if there is no member-to-member comms)?
Make it dead clear touching core infra (routers, switches (but leave room for a-la retro switch), proxmox) is zero tolerance (+ other member's hosting ofc). No means no means no. Redirect any efforts to hosting your own stack.
As Lauri is no longer in lead, maybe de-emphasize first-preson / signed off by Lauri in rules. (Rasmus: 'Treat like your own' may also mean treat like shit.)
Items not labeled with k6.ee AND linked to an inventory item may be assumed the property of K-SPACE. + K-SPACE not a dump, both explicitly.
Üle vaadata infosüsteemid, leida mille kasutamine on kohustuslik.
Paber jm majapidamistarbed on kohalkasutuseks.
K-SPACE is not a company, generally does not oblige/require anyone to do anything. Entropy generation PM headaches. There is no HR, there is nobody overseeing all doings/work.
Workshop rules: #61
How to handle broken stuff, how ordering works (writing to todo = it dead). 'Something', 'like', 'stuff', 'better' doesn't work. See #77 (comment)
Use of K-SPACE's own infrastructure is only for K-SPACE, used for providing services. No subdomains (my-awesome-box.k-space.ee) for members (management cost (ft. lingering legacy) + possible brand damage), personal services are not welcome on infra kube cluster (oh, cool app, what if we host it?). Of course, this excludes services, such as VMs (which are available(!) to host personal/company services, private or public). (this would be against k-space/kube#25 as well, see also https://k-space-ee.slack.com/archives/C86KD62TB/p1726565854840639)
No cloning keys. Procedures for giving and returning keys (signatures + showing the estimated cash sum for replacements are involved). Where the (append-only, or editable only by board) audit log is for cloning and giving. Else we end up with #92 or among other things, replacing the server room key (25€/key + lock + services).

- Better define non-onprem members (think VPS). What should they be able to access, what are their ways of communication (Rasmus: e-mail + backup phone nr?), while keeping costs low. Most k-space.ee/rules apply to on-location, could we reduce it for non-onprem (especially, if there is no member-to-member comms)? - Make it dead clear touching core infra (routers, switches (but leave room for a-la retro switch), proxmox) is zero tolerance (+ other member's hosting ofc). No means no means no. Redirect any efforts to hosting your own stack. - As Lauri is no longer in lead, maybe de-emphasize first-preson / signed off by Lauri in rules. (Rasmus: 'Treat like your own' may also mean treat like shit.) - Items not labeled with k6.ee AND linked to an inventory item may be assumed the property of K-SPACE. + K-SPACE not a dump, both explicitly. - Üle vaadata infosüsteemid, leida mille kasutamine on kohustuslik. - Paber jm majapidamistarbed on kohalkasutuseks. - K-SPACE is not a company, generally does not oblige/require anyone to do anything. Entropy generation PM headaches. There is no HR, there is nobody overseeing all doings/work. - Workshop rules: https://git.k-space.ee/k-space/todo/issues/61 - How to handle broken stuff, how ordering works (writing to todo = it dead). 'Something', 'like', 'stuff', 'better' doesn't work. See https://git.k-space.ee/k-space/todo/issues/77#issuecomment-35412 - Use of K-SPACE's own infrastructure is only for K-SPACE, used for providing services. No subdomains (my-awesome-box.k-space.ee) for members (management cost (ft. lingering legacy) + possible brand damage), personal services are not welcome on infra kube cluster (oh, cool app, what if we host it?). Of course, this excludes services, such as VMs (which are available(!) to host personal/company services, private or public). (this would be against https://git.k-space.ee/k-space/kube/issues/25 as well, see also https://k-space-ee.slack.com/archives/C86KD62TB/p1726565854840639) - No cloning keys. Procedures for giving and returning keys (signatures + showing the estimated cash sum for replacements are involved). Where the (append-only, or editable only by board) audit log is for cloning and giving. Else we end up with https://git.k-space.ee/k-space/todo/issues/92 or among other things, replacing the server room key (25€/key + lock + services).

rasmus added this to the (deleted) project 2024-08-16 19:47:19 +00:00

rasmus modified the project from (deleted) to k-space.ee/todo

2024-08-16 19:58:50 +00:00

rasmus referenced this issue from k-space/kube

2024-08-26 21:02:58 +00:00

Discourese init commit Draft #30

Sign in to join this conversation.