[hackerspaces] Another registry?

[Will Bradley]

Glad to hear it Jerry, and I totally agree. I wonder what the laws are for
such terms; i.e. Coke and Kleenex are almost genericized names as to be
unenforceable; how do we ensure nobody hijacks Hackerspace, and how can
Dale prove that Makerspace is safe and free? I'd rather not trademark
either.
On Feb 8, 2012 11:12 PM, "Jerry Isdale" <isdale at gmail.com> wrote:

> I got a personal email from Dale Dougherty today that he isn't interested
> in a ™ or other wise restricting Makerspace --- the licensing of Maker
> Faire not withstanding.  I would still like a public recognition - from
> MAKE and DARPA - that that the term is already public domain, and generic.
>
> On 2/8/12 3:21 PM, Arclight wrote:
>    Do you suppose this could be 3D Printed?
> lol… Sure.  Handcarved or turned on a lathe too.
>
> Willow Brugh ..
> > If the main issue with bringing in minors is that of insurance, what
> would
> go into making our own insurance co-op?
>
> That would be a great idea. I don't know that we could provide the $mil
> required in case of payouts…
>
> Youth Education is the central component of the MAKErspace in the
> makerspace.com world. That it steps on the generic makerspace will be an
> unfortunate point of contention and irritation.
>
> Personally, I support the Make/Darpa/OtherLab effort.  I hope they open
> source their curriculum, etc.
>
> Our makerspace does outreach to kids, and we have kids as young as 2mo
> regularly at meetings.  Liability is a big worry for me.  We currently
> occupy space on Dept of Education land and they require both liability
> insurance and non-profit status. ugh.
>
> Jerry Isdale
> http://MauiMakers.com
> http://www.mauimakers.com/blog/thursday-public-meeting/
>
>
> _______________________________________________
> Discuss mailing list
> Discuss at lists.hackerspaces.org
> http://lists.hackerspaces.org/mailman/listinfo/discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hackerspaces.org/pipermail/discuss/attachments/20120208/3852b6e3/attachment.html>