> hold the hackerspace responsible for endangering a minor<br><br>The courts are not populated with zombies, they can think about whether intent to cause harm or ignorance of risk were involved on the part of the space. I have to sign waivers everytime I take my kids to do *anything* physical. Sports leagues, climbing gyms, summer camps; they all require me as a parent to give my explicit permission. "Do you know what you're getting into?" But even though I sign, if they get a raging alcoholic bus driver who takes the kids off a cliff, I'm going to get very litigious. <br>
<br>The courts exist to punish the guilty and malicious. If you are putting anyone, child or adult, at physical risk by something you, the organizer, do or fail to do, then you are guilty. If person A leaves bare mains leads exposed and unmarked and person B gets electrocuted to death, then yes, person A was negligent and is going down. Solutions include: don't be stupid and leave dangerous projects unsecured, don't let people use dangerous tools and equipment inside the space (or outside the space if the hackerspace is taking responsibility) without training, don't let people bring anything that is designed or intended to kill humans into the space at all. I'm not saying any of these are rules hackerspaces should follow, just that they're guidelines for minimizing risk.<br>
<br>This is general liability stuff, not child specific rules. I work in a "normal" white collar office, but if a box falls off a self and breaks my face, work has to pay because they didn't provide a safe work environment. If you work in the USA, you've got a poster that says about the same hung somewhere in your workplace too. <br>
<br>> That we're sacrificing not only the future of Hacking in general, but<br>
THE FUTURE for *insurance reasons* strikes me as a horrendous FAIL.<br><br>Well that's a bit dramatic, but all this does speak to why people wouldn't want to put official labels on something that's been happening for a long time up until now. Once you invite anyone to do anything, you kind of take responsibility for what happens to them in the interim. This also, has always been true. Solutions include: be excellent to one another and party on.<br>
<br>> That this conversation ended this way signals to me that Hackerspaces<br>
have peaked<br><br>Well if they're higher than they've ever been, then by definition they've peaked ;) We don't know what we'll see over the next rise till we're standing on top of it. Perhaps the next ridge over will be more interesting. <br>
<br><br>- Adam<br>
<br><div class="gmail_quote">On Tue, Jan 26, 2010 at 3:17 PM, Sean Bonner <span dir="ltr"><<a href="mailto:sean@seanbonner.com" target="_blank">sean@seanbonner.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>On Tue, Jan 26, 2010 at 10:49 AM, Serendipity Seraph <<a href="mailto:sseraph@me.com" target="_blank">sseraph@me.com</a>> wrote:<br>
> But what exactly is a minor?<br>
<br>
</div>In the united states this is a legal definition - anyone under 18<br>
years old is a minor regardless of how skilled or competent they are.<br>
What that means is anyone under 18 is assumed not to be old enough to<br>
know right from wrong, safe from dangerous and therefor that<br>
responsibility lies on someone elses shoulders. What this means is a<br>
17 year old could be at a hackerspace and burn him/her self with a<br>
soldering iron and that persons parents (or in some cases even the<br>
city) could hold the hackerspace responsible for endangering a minor<br>
and sue and or arrest them. If the same thing happened to a person who<br>
was 18 the courts would assume the person was responsible for<br>
themselves and no one needed to be watching them because they are<br>
legally an adult.<br>
<br>
It's dumb, but it's the law.<br>
<br>
-s<br>
<div><div></div><div><br>
<br>
<br>
> I know some 7 year olds who can hack rings<br>
> around me in certain domains and are at least as little accident prone.<br>
> Then I know some dear grown up geeks that I wouldn't want to see moving<br>
> around much away from their domain of expertise without supervision. :)<br>
> At the very least a lot of teenage hackers should not be a big issue.<br>
> - samantha<br>
> On Jan 25, 2010, at 7:47 AM, Matt Joyce wrote:<br>
><br>
> Preface:<br>
> I think kids should be allowed in hackerspaces when conditions make that a<br>
> sane parenting move.<br>
><br>
> Characters:<br>
> Tommy Juvenile<br>
> Dave Derelict<br>
> Tim Hacker<br>
> Maxine Maker<br>
><br>
> Setting: A random hacker space in present day United States.<br>
><br>
> Act I:<br>
><br>
> Maxine and Tim enter<br>
><br>
> Tim: wow this is awesome, we're hacking up a storm.<br>
> Maxine: hell yes it is. I just attached a cat to another cats back and<br>
> through it off a roof... I've violated the fundamental laws of conservation<br>
> of energy. Next! Toast!<br>
><br>
> Act II:<br>
><br>
> Maxine and Tim are hosting an open hackathon<br>
> Dave Derelict enters with his son Tommy Juvenile<br>
> Tim: Hey Dave, brought the kid today eh?<br>
> Dave: Yeah, he loves this stuff<br>
> Tommy stares blankly<br>
> Dave unpacks and gets to work assembling a fine product from american vendor<br>
> adafruit. Go USA!<br>
> Maxine: Hey Tim come help me hoist up this antenna on the roof.<br>
> Tim: Okay, Dave you have the helm.<br>
> Dave: leave it to me!<br>
> Dave solders away<br>
> Tommy is wandering around<br>
> Tim and Maxine exit<br>
><br>
> Act III:<br>
><br>
> Tim and Maxine enter<br>
> Dave is finishing up his kit<br>
> Tommy is lying under a collapsed shelf<br>
> Tim: Jesus Christ!<br>
> Maxine: I'll call 911<br>
> Dave: This thing is so cool.<br>
> Tommy gives a death rattle.<br>
><br>
> Act IV:<br>
><br>
> Tim and Maxine are sitting under a box eating cat food.<br>
> Tim: We had waivers..<br>
> Maxine: We had insurance..<br>
> Together: Why the hell did we attach our names to this...<br>
><br>
> Big Dance Number.<br>
><br>
> Obviously a worse case scenario. But it closely mimics a real scenario that<br>
> almost played out at nycr. What you need to realize about US liability is<br>
> that it absolutely is 100% non functional. TORT reform has been wanted by<br>
> most people for 30 years. But beyond that, courts always rule in the<br>
> interests of what is best for the welfare of a child. One major injury to a<br>
> child under any circumstances would be the end of your hackerspace.<br>
> Insurance would likely cover it, but you'd be unable to pay increased fees<br>
> and find a new provider. And that's best case.<br>
><br>
> Additionally some folks just don't want to deal with kids sometimes. Which<br>
> I get as well, but that's neither here nor there.<br>
><br>
> Simply put though, a kid could easily hurt themselves in our space. And we<br>
> would cease to exist for increasing values of hurt.<br>
><br>
> -Matt<br>
><br>
> You can argue with that logic as much as you want, but we did our homework<br>
> at nycr and contacted local legal minds. Our rule against kids was base<br>
> mostly on this single issue. I was among an almost non existent group of<br>
> dissenters, but I clearly recognize the sanity in choosing to disallow<br>
> children in US spaces.<br>
><br>
> On Jan 25, 2010 9:25 AM, "jur1st" <<a href="mailto:jur1st@cowtowncomputercongress.org" target="_blank">jur1st@cowtowncomputercongress.org</a>><br>
> wrote:<br>
><br>
> Our memberships apply to households and if a kid isn't of legal age to enter<br>
> into a contract their parents must sign on their behalf.<br>
><br>
> Parents (that would be involved in hackerspaces) aren't stupid and even with<br>
> our new CNC machine, we don't have anything down there more dangerous than<br>
> what you might find in a high school shop class or down at the vo-tec.<br>
><br>
> For what it's worth, our insurance provider didn't specifically ask about<br>
> minors using the facility.<br>
><br>
><br>
> - jur1st<br>
><br>
> On Jan 25, 2010, at 7:55 AM, Eric Gerlach wrote: > On Mon, Jan 25, 2010 at<br>
> 01:16:53PM +0100, webm...<br>
><br>
> _______________________________________________ Discuss mailing list<br>
> <a href="mailto:Discuss@lists.hackerspaces.org" target="_blank">Discuss@lists.hackerspaces.org</a> ...<br>
><br>
> _______________________________________________<br>
> Discuss mailing list<br>
> <a href="mailto:Discuss@lists.hackerspaces.org" target="_blank">Discuss@lists.hackerspaces.org</a><br>
> <a href="http://lists.hackerspaces.org/mailman/listinfo/discuss" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/discuss</a><br>
><br>
><br>
> _______________________________________________<br>
> Discuss mailing list<br>
> <a href="mailto:Discuss@lists.hackerspaces.org" target="_blank">Discuss@lists.hackerspaces.org</a><br>
> <a href="http://lists.hackerspaces.org/mailman/listinfo/discuss" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/discuss</a><br>
><br>
><br>
<br>
<br>
<br>
</div></div><font color="#888888">--<br>
Sean Bonner<br>
<a href="http://www.seanbonner.com" target="_blank">http://www.seanbonner.com</a> - homebase<br>
<a href="http://www.metblogs.com" target="_blank">http://www.metblogs.com</a> - get local<br>
Unless agreed upon, assume everything in this e-mail might be blogged.<br>
Sent from Marina Del Rey, CA, United States<br>
</font><div><div></div><div>_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.hackerspaces.org" target="_blank">Discuss@lists.hackerspaces.org</a><br>
<a href="http://lists.hackerspaces.org/mailman/listinfo/discuss" target="_blank">http://lists.hackerspaces.org/mailman/listinfo/discuss</a><br>
</div></div></blockquote></div><br>