<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Rights and Obligations of Hackerspace Members</title>
	<atom:link href="http://blog.hackerspaces.org/2009/08/19/rights-and-obligations-of-hackerspace-members/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hackerspaces.org/2009/08/19/rights-and-obligations-of-hackerspace-members/</link>
	<description>Redefining hackerspace culture, one post at a time.</description>
	<lastBuildDate>Thu, 22 Nov 2012 04:47:53 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: Jonathan D. Abolins</title>
		<link>http://blog.hackerspaces.org/2009/08/19/rights-and-obligations-of-hackerspace-members/comment-page-1/#comment-274</link>
		<dc:creator>Jonathan D. Abolins</dc:creator>
		<pubDate>Sun, 23 Aug 2009 18:44:35 +0000</pubDate>
		<guid isPermaLink="false">http://hackerspaces.org/blog/?p=877#comment-274</guid>
		<description>Nick, thank you for your post on hackerspaces and how to keep the movement going.

Although I don&#039;t have much opportunity to get involved with hackerspaces these days, I am glad to see the establishment of places such as the Hacktory in Philadelphia and HacDC. In some ways, they also parallel the MAKErs movement, another great development to encourage hacking/tinkering. 

I agree about the importance of the casual attendees and visitors being important. Besides their direct contributions to the hackerspace, they also serve as ambassadors of the hackserspace concept. Getting the hackspaces somewhat visible to the general public helps to dispel the weird associations people have with the term &quot;hacker&quot;. 

This ambassador triat points to one of the responsibilities for people associated with hackserspaces: educate others about what hacking is and what it isn&#039;t. Sometimes, this may mean dealing with a newcomer who see hacking as the means of ripping off freebies or harassing others.  (I am thinking of the occasional newbies whose questions centre on how do I break in... motifs and hardly on how do things work and how can do some really cool stuff with them. Hacking as merely a tool, not as an approach to tech, systmes, and such.)

That may bring an obligation to try encourage such probelmatic newbies to see other aspects of hacking, to mentor where possible. In some cases, it may mean distancing from somebody really going on a disastrous course. 

(I am thinking of how some of the sports lockspicking club in the Netherlands and Germany handle those people who want to breaking into places rather than learning how locks work. Those clubs face liabilities with their countries&#039; criminal laws. One of the good things I&#039;ve seen is how to the clubs managed to prevent overt criminal use of their resources and, at the same time, not lose the hacker spirit.)</description>
		<content:encoded><![CDATA[<p>Nick, thank you for your post on hackerspaces and how to keep the movement going.</p>
<p>Although I don&#8217;t have much opportunity to get involved with hackerspaces these days, I am glad to see the establishment of places such as the Hacktory in Philadelphia and HacDC. In some ways, they also parallel the MAKErs movement, another great development to encourage hacking/tinkering. </p>
<p>I agree about the importance of the casual attendees and visitors being important. Besides their direct contributions to the hackerspace, they also serve as ambassadors of the hackserspace concept. Getting the hackspaces somewhat visible to the general public helps to dispel the weird associations people have with the term &#8220;hacker&#8221;. </p>
<p>This ambassador triat points to one of the responsibilities for people associated with hackserspaces: educate others about what hacking is and what it isn&#8217;t. Sometimes, this may mean dealing with a newcomer who see hacking as the means of ripping off freebies or harassing others.  (I am thinking of the occasional newbies whose questions centre on how do I break in&#8230; motifs and hardly on how do things work and how can do some really cool stuff with them. Hacking as merely a tool, not as an approach to tech, systmes, and such.)</p>
<p>That may bring an obligation to try encourage such probelmatic newbies to see other aspects of hacking, to mentor where possible. In some cases, it may mean distancing from somebody really going on a disastrous course. </p>
<p>(I am thinking of how some of the sports lockspicking club in the Netherlands and Germany handle those people who want to breaking into places rather than learning how locks work. Those clubs face liabilities with their countries&#8217; criminal laws. One of the good things I&#8217;ve seen is how to the clubs managed to prevent overt criminal use of their resources and, at the same time, not lose the hacker spirit.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Farr</title>
		<link>http://blog.hackerspaces.org/2009/08/19/rights-and-obligations-of-hackerspace-members/comment-page-1/#comment-271</link>
		<dc:creator>Nick Farr</dc:creator>
		<pubDate>Thu, 20 Aug 2009 16:42:29 +0000</pubDate>
		<guid isPermaLink="false">http://hackerspaces.org/blog/?p=877#comment-271</guid>
		<description>I absolutely agree.  It&#039;s worth noting that the spaces that informed the Design Patterns were inspired by the L0pht and similar spaces.  No criticism of these spaces was intended, quite the opposite--I had a great time hanging out at NHC while I was in San Francisco and I wish it were still around.  If anything, we have to acknowledge their contributions as being vital to this latest wave of Hackerspaces.

NHC was truly an epic space, I wish there was more documentation available about it.  I was sad to see it fail, to be there helping members move the last of their equipment out of it.  In the end, it closed because it failed to bring in new members and excite the community in the way that Noisebridge does.  There are other structural issues that might be worth getting into, were it not for the spirit of pluralism and democracy that informs our current spaces.

It would be a tragedy to see this next wave of hackerspaces see the same fate, to close because of a lack of interest or enthusiasm.  This wave of spaces must focus on sustainability, and we must examine the ongoing theory to ensure that these spaces continue to exist.  So much effort goes into building these spaces and so much good comes out of them that I believe we must focus on ways of keeping them alive and vital.  Being aware of this responsibility to the community outside the membership is, I believe, the biggest contributing factor to ensuring their continued success.</description>
		<content:encoded><![CDATA[<p>I absolutely agree.  It&#8217;s worth noting that the spaces that informed the Design Patterns were inspired by the L0pht and similar spaces.  No criticism of these spaces was intended, quite the opposite&#8211;I had a great time hanging out at NHC while I was in San Francisco and I wish it were still around.  If anything, we have to acknowledge their contributions as being vital to this latest wave of Hackerspaces.</p>
<p>NHC was truly an epic space, I wish there was more documentation available about it.  I was sad to see it fail, to be there helping members move the last of their equipment out of it.  In the end, it closed because it failed to bring in new members and excite the community in the way that Noisebridge does.  There are other structural issues that might be worth getting into, were it not for the spirit of pluralism and democracy that informs our current spaces.</p>
<p>It would be a tragedy to see this next wave of hackerspaces see the same fate, to close because of a lack of interest or enthusiasm.  This wave of spaces must focus on sustainability, and we must examine the ongoing theory to ensure that these spaces continue to exist.  So much effort goes into building these spaces and so much good comes out of them that I believe we must focus on ways of keeping them alive and vital.  Being aware of this responsibility to the community outside the membership is, I believe, the biggest contributing factor to ensuring their continued success.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steen</title>
		<link>http://blog.hackerspaces.org/2009/08/19/rights-and-obligations-of-hackerspace-members/comment-page-1/#comment-270</link>
		<dc:creator>steen</dc:creator>
		<pubDate>Thu, 20 Aug 2009 03:08:39 +0000</pubDate>
		<guid isPermaLink="false">http://hackerspaces.org/blog/?p=877#comment-270</guid>
		<description>Thanks, Nick. A well-written piece, and evocative of both the successes and challenges that come with what we do. I personally think that the functions served by entities like l0pht and NHC are slightly different than those served by Noisebridge and Cbase. I believe your observations here are spot-on, but I also think that it&#039;s important to note that we should avoid falling into the trap of being overly critical of groups like l0pht, because, frankly, they were trying to do something completely different than we are.

That said, thanks for speaking so kindly about Noisebridge ;&gt;</description>
		<content:encoded><![CDATA[<p>Thanks, Nick. A well-written piece, and evocative of both the successes and challenges that come with what we do. I personally think that the functions served by entities like l0pht and NHC are slightly different than those served by Noisebridge and Cbase. I believe your observations here are spot-on, but I also think that it&#8217;s important to note that we should avoid falling into the trap of being overly critical of groups like l0pht, because, frankly, they were trying to do something completely different than we are.</p>
<p>That said, thanks for speaking so kindly about Noisebridge ;&gt;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
