Membership Agreement
When a new member joins, by whatever process, they will need to sign a membership agreement. We can begin drafting that document here.
Contents
Questions to be filled in by new member
Name
Address
Phone Number
Username (for use with Node member accounts)
Why?
- not "why should we let you?", but "why do you want to?" Abachman 19:31, 9 July 2009 (UTC)
Questions to be filled in by a Node member
Date affirmed
Dues:
[ ] Will pay 100%
[ ] Some other arrangement (describe below)
- It might not be a bad idea to ask for a photo ID when people are filling out this form, and if we have the means, make a copy of said ID for our files. If people are on the lam, but we still want them to be members, we can perhaps skip the ID. We absolutely cannot discriminate against anyone, including those who don't have photo IDs. So in that case, we'd need to skip the photo ID step. Presumably, by the time someone if filling out this form, they have been elected or gone through some amount of process, such that we trust them. HacDC requires photo ID only when giving out a key, I think. "Trust, but verify", as Ronnie would say. --Jonlesser 07:25, 9 July 2009 (UTC)
- Do we want to put in a minimum time a member can be to add some stability to our budget? I wasn't thinking anything long like a year, maybe 3-4 months? Mehuman 18:24, 9 July 2009 (UTC)
- I think asking people to commit to $150 or $200 is too steep. It's on us to provide a space people want to be part of. If people are dropping out after a month, we need to ask why and fix it. Jonlesser 23:59, 17 July 2009 (UTC)
- Asking the founding members to commit to three months membership is not unreasonable, given that we're starting from scratch. It'd be purely voluntary, but an expression of a desire to make this thing work. Abachman 01:27, 18 July 2009 (UTC)
Fine Print
- Perhaps for good measure we should have a place for people initial next to each section. --Jonlesser 07:25, 9 July 2009 (UTC)
Membership Rights and Privileges
All members of the Baltimore Node receive:
- Access to the space to work on projects either on your own or in collaboration with other members
- Use of all community tools and equipment within the space
- Free access to all workshops and events
- A designated area to store in progress work
- A voice and a vote in all decisions affecting the Baltimore Node
Key Access
The Load of Fun space uses high security keys that can only be duplicated by the landlord. Members may obtain a key to access the space at any time by providing a valid photo ID (driver's license, passport, etc.) and paying for the cost of key duplication.
Dues
Dues are $50 a month. Dues for each month must be paid by the 20th of the preceding month. For example, April dues should be paid by March 20th. Dues should be delivered to the treasurer in the form of cash or by check written out to "Baltimore Node". Dues can also be paid online with a credit card, however, there will be a $1.75 fee to cover the processing fee.
Release of Liability
In consideration for my being permitted to participate in the activities of Baltimore Node, I agree to the following waiver and release:
ASSUMPTION OF RISK: I acknowledge that inherent risks, dangers and hazards exist when using hand tools, power tools, working with or constructing electronic circuits, soldering, welding or otherwise working with metal, using chemicals or building materials and other related activities. Participation in these activities and the use of equipment associated with electronics, manufacturing, construction and scientific practices may result in injury, illness, death or damage to personal property. These risks and dangers may be caused by myself, other participants, by accident, acts of nature or other causes. Risks and dangers may arise from foreseeable or unforeseeable causes including, but not limited to electrocution, burns, impalement, injury from slips or falls, or loss of limb.
RELEASE OF LIABILITY: The member fully assumes all risks associated with participation in events and exempts and releases Baltimore Node, its members, officers, agents, and directors from liability arising out of any damage, loss or injury to the participant or the participant’s property while upon the premises or using any equipment of the organization or while participating in any of the activities contemplated by this agreement whether such loss, damage, or injury results from the negligence of the corporation, its members, agents, or from some other cause.
COVENANT NOT TO SUE: The participant agrees never to institute any suit or action at law otherwise against Baltimore Node, its members, officers, board members, agents, nor to initiate or any way assist the prosecution of any claim for damages or course of action which the member, member’s heirs, executors or administrators hereafter may have by reason of injury to the person of the member or to the participant’s property arising from the activities contemplated by this agreement.
THIRD PARTY INDEMNIFICATION: The member will indemnify, save and hold harmless Baltimore Node, its members, officers, board members, or agents from any and all losses, claims, actions, or proceedings of every kind and character which may be presented or initiated by any other persons or organizations and which arise directly or indirectly from the actions of the member while engaged in the activities contemplated by this agreement.
I hereby acknowledge that I have CAREFULLY read all of the provisions above, fully understand the terms and conditions expressed there, and do freely choose acceptance of the provisions of the foregoing paragraphs relating to assumption of risk, release of liability, covenant not to sue, and third party indemnification.
Intellectual Property
Baltimore Node makes no claim to any intellectual property created by Baltimore Node members or created using Baltimore Node resources or facilities. Members are strongly encouraged, but not required, to make freely available under an open source license approved by Open Source Initiative (OSI) or a Creative Commons (CC) license, any documentation, schematics, plans, and/or source code created using Baltimore Node resources or facilities. Any member working on a project that is NOT licensed under an OSI approved or CC license must inform collaborating members of the project's licensing terms BEFORE collaborating.
Disclaimer
Baltimore Node provides all services “as is”, as a service, and not as a lease of real property, and disclaim all warranties and conditions, whether express, implied or statutory, including, but not limited to, merchantability, fitness for a particular purpose or use. there is also no warranty of title, quiet enjoyment or possession. the entire risk of participating in or using the Baltimore Node service, remains with you.
Signatures
Signature of new member Signatures of one or more members
