<div dir="ltr">Yves, we are friendly with the folks from Chaos Computer Club in general, who gave us a spot at Camp in '11 to present on Space Federation. We're trying to work with Francois Taddei at the Center for Interdisciplinary Research at U. Descartes to get a space rolling in Paris sometime this year. Beyond that are just individual contacts with some of the spaces in EU.<div>
<br></div><div style>As to the wider discussion, if we can separate the problem into:</div><div style>* where to host / who to admin the hackerspaces.* domains and</div><div style>* what to do with the content on the sites and how to manage community participation to maintain/improve that content</div>
<div style><br></div><div style>Are there docs anywhere on what all is running on the servers? Specs and whatnot? Pardon me if I've missed this information from prior in the thread.</div><div style><br></div><div style>
Is there a way we could set up a trust model for access control to the content, so the community can take a larger role in posting content and keeping things up to date? I know the wiki is relatively open but I don't know about the rest of the *.hackerspaces.* components or how they are managed.</div>
<div style><br></div><div style>We've been using OpenAtrium for managing / communications on the Space Federation community (<a href="https://atrium.schoolfactory.org/spacefed">https://atrium.schoolfactory.org/spacefed</a>) which has a wiki, project management and discussion threads and allows for email-only participation. </div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Apr 14, 2013 at 7:51 PM, Yves Quemener <span dir="ltr"><<a href="mailto:quemener.yves@free.fr" target="_blank">quemener.yves@free.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks for the summary and my apologies to Sean, as I apparently answered<br>
to a debate he was not taking part in. I did not miss the genesis of the<br>
conversation but did indeed get lost in its forkings, sorry.<br>
<br>
But am I missing another thing if I say that simply owning the<br>
hackerspaces.* domains just involved managing DNS records and is not really<br>
a big problem or a big task, as long as the servers are maintained by the<br>
current team?<br>
<br>
I don't really understand why the people currently controlling the servers<br>
should not also own the domain names. Alternatively, Matt Joyce proposed to<br>
take them, why wouldn't that be a proper solution?<br>
<br>
Making a whole organization only for deciding to which IP<br>
*.<a href="http://hackerspaces.org" target="_blank">hackerspaces.org</a> points to seems way overkill.<br>
<div class="HOEnZb"><div class="h5"><br>
On 15/04/13 02:22, hellekin wrote:<br>
> On 04/14/2013 06:57 PM, Sean Bonner wrote:<br>
><br>
>> Glad that all got resolved. Good work everyone!<br>
><br>
> *** Sarcasm apart, let's clear misunderstanding about the evolution of<br>
> the discussion, for the sake of people who left the "Abuse of Power"<br>
> thread early on. After the initial burst that sparked it, Paul<br>
> announced that he wants to leave the keys of hackerspaces.* domains to<br>
> someone else, preferably not to the same people who control the<br>
> server. That's the issue number one to solve.<br>
><br>
> The discussion derived to the lack of activity of late in the<br>
> hackerspaces community (stall of bonding activities such as Call-Ins,<br>
> Challenges, etc.).<br>
><br>
> Matt Joyce (NYC Resistor) proposed to setup a foundation to handle the<br>
> domains, provide a more transparent management of the community's<br>
> assets, and to move away from the benevolent dictator model.<br>
><br>
> Walter van Holst (RevSpace) reframed the issue from a lawyer's point<br>
> of view, saying that a foundation might not be the best choice, and we<br>
> should ask: 'what is the problem you're trying to solve?'<br>
><br>
> Mark Janssen proposed to gamify the decision process.<br>
><br>
> James Carlson introduced a working model for an umbrella organization<br>
> that manages resources across hackerspaces (makerspaces, etc.) which<br>
> sounds very interesting.<br>
><br>
> Rubin Abdi suggested we're here to fuck with your robots, to which<br>
> Monochrom agreed gleefully.<br>
><br>
> And you Sean, reminded that the topic of turning <a href="http://hackerspaces.org" target="_blank">hackerspaces.org</a> into<br>
> something more formal have come up a lot in this mailing list before<br>
> and failed.<br>
><br>
> Yves Quenemer and others reminded that <a href="http://hackerspaces.org" target="_blank">hackerspaces.org</a> have two<br>
> objectives that are properly fulfilled: providing this (and other)<br>
> mailing lists, and a working site of hackerspaces around the world.<br>
><br>
> So indeed, there are two topics:<br>
><br>
> 0 - who's going to take charge of the hackerspaces.* domains<br>
> 1 - what do you want to do to restore/expand regular community activity<br>
> - and robots hardcore forking<br>
><br>
> Cheers,<br>
><br>
> ==<br>
> hk<br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> Discuss mailing list<br>
> <a href="mailto:Discuss@lists.hackerspaces.org">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>
</div></div><br>_______________________________________________<br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.hackerspaces.org">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></blockquote></div><br></div>