DataBasementProcedures

1. Introduction
   1. The DataBasement collective is a consensus-run group that operates a computer hosting service on a T1 internet connection. Members provide their own computer hardware, software, and administration for use in a shared power, networking, and shelving environment. The collective owns two computers which together act as a webserver for this twiki and a serial console management system with 25 RS-232 ports for remote management of members' machines.
2. Terms
   1. Assets: Total current value of all equipment, money and other possessions of the collective. Computers are typically owned by individual members, and not the collective. Technological physical assets are depreciated on a 3-year straight line schedule, items such as shelving and racks are held on the books at their purchase price unless they become damaged or are sold.
   2. Member: A person or entity (currently all members are persons) that is part of the collective. Members share equally in all costs and decision making.
   3. Fees: All service costs incurred by the collective.
   4. Colo: The collective location, where the network connection, routers, computers, and other assets are located. Currently in Clifton, NJ.
3. Membership
   1. Joining members may be accepted into the collective at any meeting. Upon joining, new members assume as a liability their equal share of the assets - 1/(number of members before new member joined).
   2. Members accept responsibility for an equal share of all fees, new asset purchases and sales, and depreciation that occur between their joining and leaving dates.
   3. Members shall be afforded reasonable access to the colo for installation, administration, and removal of equipment. A key-box is mounted outside the colo site to let members reach their equipment in the event that the host is not available.
   4. Leaving members will give 1 month notice. The departure must be minuted at a meeting to be effective. Upon leaving, members are reimbursed their equal share of the (depreciated) assets.
   5. Joining and leaving dates need not coincide with meeting dates, but they must be clearly minuted if they differ.
4. Meetings
   1. All decisions are made by consensus at duly called meetings. A secular variant of the Quaker business process is used; see the web site for a detailed description.
   2. Meetings are open to all and are held approximately monthly, currently on the first Thursday of each month when possible. Meetings are announced on the email list at least one week prior, and decisions of the collective are recorded as minutes that are kept on the web site.
   3. Meetings are held at the colo unless otherwise indicated. Members may attend by teleconference, by pre-arrangement.
   4. Special meetings may be called by at least 4 members, with at least a one week notice by email.
5. Financials
   1. Transactions are maintained by in Quicken by the collective's elected treasurer.
   2. Members of What Exit normally pay their fees directly to the host, and send an email to the host and the treasurer to log the transaction. The host then sends a confirming receipt email to the treasurer, who enters the transaction into Quicken.
   3. Upon leaving, the departing member will be paid their share of the collective's assets (1/(number of members before leaving member leaves), as well as being refunded any fees they may have paid in advance. Departing members are requested to settle any outstanding debts to the collective, lest their ultimate Departure be hastened by our cousins from North Jersey.
6. Communication
   1. The collective maintains a web site at www.databasement.org which contains this document and other relevant information: current members with their contact information and roles, meeting schedules and minutes, colo physical address, listing of assets, network addresses, and so on.
   2. Announcements and discussion are held by email on a list maintained by the collective. This list is open to any friends or prospective members as well. See the web site for the current list name and subscription procedure.
   3. Emergency colo incidents shall be communicated to members by an alternate email list, with text suitable for delivery to cell phones, in the event that colo connectivity or computer services are disrupted.

-- PhilSalkie - 15 Mar 2005

Updated bandwidth specs..

-- GlennSieb - 26 Jan 2009
to top