Have some sort of agreement on installed infrastructure in the space to prevent this kind of schism rendering the space inhospitable

[m]

Related to #955

Having a member agreement or policy with regards to the murky provenance of "donated"/"loaned" infrastructure within the space.

I don't think we should force members to explicitly label everything they're bringing into the space as either "transferring ownership to devhack" (lots of taxable & legal liabilities with this one) vs "indefinite loan to devhack" (clarifies the relationship and the reclamation process)

I do think we should have a nuanced approach such as "an installed lightbulb worth less than $20 is forfeit to the space either after N amount of time or after you're banned or whatever else" "an installed lightswitch worth less than $20 is more inconvenient for everyone to remove, it's forfeit"

and some things are worth more! And are still hard to uninstall. like a switch or a router or a PDU that we've ended up relying on. or shelving, lol. There should be a process in which devhack has an option of either reimbursement or procurement of an equivalent object, with reasonable agreement from the opposing party.

If something is rare, hard to aqcuire, one of a kind. sure, it's not on us to keep something someone can't reacquire with the same amount of money.

this all is not explicitly even acknowledging the labor that's gone into shopping for a thing, figuring out what kind of thing we need, recieving the thing, transporting it, setting it up, maintining/administering it, etc etc. We can't really give back that time.

[m]

also not acknowledging the labor of documenting the model & cost of any equipment you bring into the space. but the burden is kinda on you if you want to remove it in a way that doesn't fuck us over heavily

[nc@…]

i think it's reasonable for an item essential to the operations of /dev/hack (even if replaceable) to be owned by /dev/hack

[nc@…]

i could imagine a classification ("core-capable") that means an item is owned by /dev/hack and can be used for the core services, and infra team works to eliminate non-core-capable items from core services, with a policy of introducing no new ones

[m]

All of this lends itself to spending money devhack doesn't rlly have right now and also moves infra from being "anarchist-first" to making decisions about the infrastructure from a place of private property ownership, which I'm not very partial to.

I would rather defer the decision of making authoritative decisions about the usefulness of infrastructure until there's a threat of it dissapearing.

[m]

from friends:

also I think it is maybe time to write an onboarding contract

if possible I would really like "the tech is not the point" to make an appearance in it

We should also mention that dues are not rent.

Since they've claimed we're landlords

this can be covered by a larger delineation of "the space has been to some degree entrusted to the members, but it is not owned by the members"

[m]

this should probably have something along the lines of "if you don't document that something's yours in an easily accessible place, we assume it's ours. documenting that it's yours could look like: -label on it, -wiki page about it that says it's yours, you're loaning it, -inputted into our future inventory tracking system #871

[m]

There should be a process in which devhack has an option of either reimbursement or procurement of an equivalent object, with reasonable agreement from the opposing party.

okay so something to keep in mind when doing this is the fact that something aqcuired off of ebay might be very cheap relative to the MSRP price. what to do here? can't really pay the ebay price because re-aqcuiring might not be possible, we don't want to pay the MSRP because it's like $4k. hmm

[m]

Milestone renamed

[m]

also specifying that equipment you leave at the space / set up at the space may be locked away and we need to be given a heads up for if you want access to reclaim it.