Rules v3: getting to 15y #67
Loading…
x
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?
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)
Vulnerable/EoL software may be upgraded by force. This is mainly aimed at VMs.
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).
Required contact info on file: email, phone, (? at least minimal presence on slack), billing info
explicit right to measure power usage (provide to snmp possibly)
measure-stats on consuming activity (doors, actual consumibles, whatever)
Rules v3to Rules v3: 10y specialRules v3: 10y specialto Rules v3: getting to 15yhttps://pad.k-space.ee/p/rules
Membership is often volunteer and not much to lose by abandon-leaving (common pattern), concrete fines may be a way. 'x counts of very-messy and did not clean up other things (off a specified common public list) to offset it', 'repeated messes'. One side is to motivate with small sums, other side is 'so be it your way' to plain pay people (professionals or other members reclaiming €) for hours (often days and weeks) of cleanup.
See also: #146 (rules/policies surrounding the competences)
resource- (electricity-)intensive mining / training forbidden unless accounted for in a special billing package
right to refuse service for any reason
Paying loans on discounted terms, discounts are billed for, at least as part of membership price on rejoin (ex. 20-50% of current price goes towards recouping).
Lengthy debtors are winning on inflation, and cashflow anyway, make 'special deals' to trade debts for value (which are unavailable to good-standing members), or get magic discounts to keep the multi-year sum under a thousand.
Estimating lost income to discounts so far to be 3-7k€.