Difference between revisions of "Membership Agreement"
Line 21: | Line 21: | ||
* ''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. --[[User:Jonlesser|Jonlesser]] 07:25, 9 July 2009 (UTC)'' | * ''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. --[[User:Jonlesser|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? [[User:Mehuman|Mehuman]] 18:24, 9 July 2009 (UTC)'' | ||
== Fine Print == | == Fine Print == |
Revision as of 18:24, 9 July 2009
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
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)
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
- This section should include a brief outline of the rights and privileges of membership. Access, voting, etc.
Dues
- This section should say how much dues are, when they are due, and briefly, how we can accept payment.
Release of Liability
- This text is direct from this document on hackerspaces.org. It needs some tweaking. --Jonlesser 07:25, 9 July 2009 (UTC)
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.
Licensing Policy
- This section will contain our licensing policy. One available model is the HacDC Licensing Policy. We should consider alternative ideas as well.'
Signatures
Signature of new member Signatures of one or more members