Maker Community Rack Agreement

Merri-bek Tech (MBT): Currently an unincorporated collective, described in detail https://www.merri-bek.tech/. Agreements with Merri-bek Tech are currently really agreements with Jade (Craig Ambrose), but will move to being with Merri-bek Tech once it incorporates

Maker Community Inc (MCI): The not-for-profit incorporated association that runs the Makerspace at 70 Saxon St, as described at https://makercommunity.org.au/

MBT wishes to run not-for-profit web hosting on computers located in the makerspace run by MCI. MBT's goals in doing so include:

• Reducing barriers for locals to use open source web software
• Building local involvement in web software, including skills development and DIY mentality
• Increasing local resilience through having software locally hosted
• Experimenting with reducing climate emissions by attempting to run the servers on renewables where possible

These goals align fairly well with MCI's goals. It's possible that there will be an overlap in interest between MCI members and MBT volunteers and users.

The reason for selecting the MCI makerspace for this web hosting installation is not because it is an ideal location (it contains dust and is often hot). Instead, it is a local hub for makers and tinkerers, and so it seems ideal for a first experimental server setup. MBT plans to have several sites across Merri-bek eventually, and it's possible that the MCI site will eventually become the experimental one that volunteers learn on, rather than the most efficient primary site.

MBT would like to use a small rack, about the size of a bar fridge, initially containing a network switch and 1-3 rack servers with room to expand to several more. This will consume power, and create heat. It will create very low levels of noise. It will be susceptible to dust. The rack will contain a network switch connected to MCI's internet connection or network in some way, and it will be using both upstream and downstream bandwidth. It will have static IPs on the MCI network, the MCI internet account will be given a static IP, and certain ports on the MCI internet gateway will be open and forwarded to the MBT rack for public hosting.

Location of any MBT equipment is to be determined in consultation with MCI so that it is mutually agreeable. Once decided, the location of the equipment will be added to this agreement.

There will be no cost to MCI for setup. Hardware will all be supplied by MBT and will remain the property of MBT. MBT will supply an asset inventory to MCI for hardware in the building. MCI will take all care with MBT hardware, and will even attempt to cover it with any insurance it already has, providing there is no additional cost in doing so. Beyond that, however, MCI takes no responsibility for the hardware and MBT assumes the risk of the loss or damage to the hardware.

The goal is for no additional ongoing costs to MCI, while recognising that MBT is a new not-for-profit and has no incoming funds other than donations. MBT will supply a device to measure power consumption for the servers, and will reimburse MCI for electricity on a monthly basis, based on a reasonable estimate of additional electricity cost based on the measured power usage. MBT will not cover a proportion of line fees or other electricity charges that would have been paid by MCI anyway.

MBT may need to increase the bandwidth of MCI's internet plan, and if so this clearly incurs additional cost. Such costs would be negotiated between the two parties, and an amount determined to be paid by MBT to MCI on a monthly basis. As MBT does not have good sources of ongoing funds, if MCI would like to discuss any in-kind compensation for these costs instead of money, such as providing web hosting that MCI currently pays for, that would be much appreciated by MBT.

MBT takes no responsibility for fire, electrocution or public liability risk for the presence of it's equipment, and expects it to be covered by MCI's insurance. However, it will also ensure that it's equipment meets any safety standards imposed by MCI (or it's insurer), including any testing and tagging, additional fire-safety equipment, etc. This will all be provided at MBT's cost. MBT will provide transparency to MCI of it's hardware plan's so that MCI can determine if any additional risks are posed.

The agreement start date will be noted here, which is the date from. After that an area will be made available for the planned equipment by MCI, with the assistance of MBT volunteers if desired. MBT will instead it's equipment only after that occurs.

If MBT agrees to provide hosting for MCI, that will only be available once such systems are setup by MBT. This is a volunteer run process and is expected to take quite some time, at least three months, maybe more. This should be taken into account when planning any in-kind contribution.

This agreement lasts for one year from the start date. After that it can be re-negotiated. The intent from parties is to continue if the arrangement is found to be mutually satisfactory.

The agreement can be terminated early by either party with 30 days written notice. If not, the agreement automatically terminates at the end of the duration if no extension is agreed.

On or before the end date of the agreement, MBT will:

• Remove all it's equipment from MCI property
• Undo any changes to MCI's internet connection with provide public access to internal systems (port forwarding,e tc)
• Leave the area provided for MBT equipment in a clean and tidy state
• Settle any outstanding costs with MCI, pro-rated if necessary

And MCI may wish to:

• Change their internet plan if it had been increased to support MBT

MBT would like to move towards running their equipment on renewable energy. This agreement does not cover that, and that would be negotiated separately. After measuring power consumption for some time, MBT hopes to propose to MCI the installation of a small solar and battery system solely to power the MBT equipment. No agreement is assumed, but we hope that all parties will consider that option favourably.