<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>How about a wiki? </div><div><div><br></div><div>Sorry to knock the forum idea, but I think it is a really poor way of structuring information, especially complex technical information that is probably subject to change.</div><div><br></div><div>I will happily set one up on <a href="http://www.swanseahackspace.org/">www.SwanseaHackspace.org</a> and host it temporarily for free (until it finds an independent home).</div><div><br></div><div>-- Paul</div><div><br></div><div><br></div><div><br><div><div>On 24 Apr 2013, at 18:26, Tim Moore <<a href="mailto:timmoore47@gmail.com">timmoore47@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Forums are a great long term repository for technical solutions provided there is a good 'search' facility. (mail lists are not IMHO ) <br><br>A good Forum is of equal benefit as a 'HackSpace' facility to make stuff for those who can easily get to Swansea.<br>
<br>I think that is a bit of a no-brainer, so if anyone is more skilled than I, to pop a Forum on <a href="http://www.swanseahackspace.org/">www.SwanseaHackspace.org</a>, I'd be pleased to fund the www site costs.<br><br>
(Is that title ok ?)<br><br>: )))<br><br>Tim_1<br><br><div class="gmail_quote">On 24 April 2013 16:45, <span dir="ltr"><<a href="mailto:hackspace-request@swansea.hackspace.org.uk" target="_blank">hackspace-request@swansea.hackspace.org.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">Send Hackspace mailing list submissions to<br>
<a href="mailto:hackspace@swansea.hackspace.org.uk">hackspace@swansea.hackspace.org.uk</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://stoneship.org.uk/mailman/listinfo/hackspace" target="_blank">http://stoneship.org.uk/mailman/listinfo/hackspace</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:hackspace-request@swansea.hackspace.org.uk">hackspace-request@swansea.hackspace.org.uk</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:hackspace-owner@swansea.hackspace.org.uk">hackspace-owner@swansea.hackspace.org.uk</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Hackspace digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Community building (Andrew Price)<br>
2. Re: Community building (Justin Mitchell)<br>
3. Re: Community building (Tom Lloyd)<br>
4. Re: Community building (Paul Harwood)<br>
5. Re: Community building (Tom Lloyd)<br>
6. Re: Community building (Justin Mitchell)<br>
7. Re: Community building (Andrew Price)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 24 Apr 2013 12:30:00 +0100<br>
From: Andrew Price <<a href="mailto:andy@andrewprice.me.uk">andy@andrewprice.me.uk</a>><br>
Subject: [Swansea Hackspace] Community building<br>
To: <a href="mailto:hackspace@swansea.hackspace.org.uk">hackspace@swansea.hackspace.org.uk</a><br>
Message-ID: <<a href="mailto:5177C238.50208@andrewprice.me.uk">5177C238.50208@andrewprice.me.uk</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
On 24/04/13 10:50, Paul Harwood wrote:<br>
> Starting a successful community is very hard.<br>
<br>
Absolutely. I'm already noticing that we're not a very diverse bunch so<br>
we really should put some early effort into making the environment as<br>
comfortable and welcoming as possible to anyone who might want to get<br>
involved.<br>
<br>
How do we feel about drawing up a general code-of-conduct kind of<br>
policy? It doesn't have to be long and detailed, just something that<br>
generally states that we're an inclusive community which doesn't<br>
tolerate discrimination, abuse or harassment.<br>
<br>
Andy<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 24 Apr 2013 12:39:33 +0100<br>
From: Justin Mitchell <<a href="mailto:justin@discordia.org.uk">justin@discordia.org.uk</a>><br>
Subject: Re: [Swansea Hackspace] Community building<br>
To: <a href="mailto:hackspace@swansea.hackspace.org.uk">hackspace@swansea.hackspace.org.uk</a><br>
Message-ID: <<a href="mailto:1366803573.9429.16.camel@quartz.geode.org.uk">1366803573.9429.16.camel@quartz.geode.org.uk</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
On Wed, 2013-04-24 at 12:21 +0100, Tim Moore wrote:<br>
> Does any member have the knowledge to pop up a Forum type www site<br>
> like this :-<br>
><br>
> <a href="http://www.raspberrypi.org/phpBB3/index.php?sid=965c39f37fada4d4899c7c6d13e24f55" target="_blank">http://www.raspberrypi.org/phpBB3/index.php?sid=965c39f37fada4d4899c7c6d13e24f55</a><br>
><br>
<br>
I can easily set up a copy of phpBB or similar,<br>
it's more do we really want to,<br>
<br>
as briefly discussed in the first meeting, web forums are a pull<br>
technology, you have to actively remember to go and check them for<br>
updates, where as mailing lists are push, updates come to you.<br>
<br>
I can setup any number of mailing lists easily, its all running on my<br>
own hosted server anyway.<br>
<br>
hardest part is naming it, community@... or discuss@... ?<br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 24 Apr 2013 13:12:17 +0100<br>
From: Tom Lloyd <<a href="mailto:napalmllama@gmail.com">napalmllama@gmail.com</a>><br>
Subject: Re: [Swansea Hackspace] Community building<br>
To: Andrew Price <<a href="mailto:andy@andrewprice.me.uk">andy@andrewprice.me.uk</a>><br>
Cc: <a href="mailto:hackspace@swansea.hackspace.org.uk">hackspace@swansea.hackspace.org.uk</a><br>
Message-ID:<br>
<<a href="mailto:CAF85AwU37xQreVSDgvW%2Ba734mO%2BByQWy1if%2BM7TJVXAvQriMyQ@mail.gmail.com">CAF85AwU37xQreVSDgvW+a734mO+ByQWy1if+M7TJVXAvQriMyQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
How about keeping hackspace@ for admin related stuff, and setting up either<br>
a new list or a forum for general discussion? I think a list would be<br>
better, at least until we have more people. We could call it general@ or<br>
talk@.<br>
A technical list might be a good idea too, for help with those matters.<br>
<br>
-- Tom<br>
On Apr 24, 2013 12:30 PM, "Andrew Price" <<a href="mailto:andy@andrewprice.me.uk">andy@andrewprice.me.uk</a>> wrote:<br>
<br>
> On 24/04/13 10:50, Paul Harwood wrote:<br>
><br>
>> Starting a successful community is very hard.<br>
>><br>
><br>
> Absolutely. I'm already noticing that we're not a very diverse bunch so we<br>
> really should put some early effort into making the environment as<br>
> comfortable and welcoming as possible to anyone who might want to get<br>
> involved.<br>
><br>
> How do we feel about drawing up a general code-of-conduct kind of policy?<br>
> It doesn't have to be long and detailed, just something that generally<br>
> states that we're an inclusive community which doesn't tolerate<br>
> discrimination, abuse or harassment.<br>
><br>
> Andy<br>
><br>
> ______________________________**_________________<br>
> Hackspace mailing list<br>
> <a href="mailto:Hackspace@swansea.hackspace">Hackspace@swansea.hackspace</a>.**<a href="http://org.uk/" target="_blank">org.uk</a> <<a href="mailto:Hackspace@swansea.hackspace.org.uk">Hackspace@swansea.hackspace.org.uk</a>><br>
> <a href="http://stoneship.org.uk/**mailman/listinfo/hackspace" target="_blank">http://stoneship.org.uk/**mailman/listinfo/hackspace</a><<a href="http://stoneship.org.uk/mailman/listinfo/hackspace" target="_blank">http://stoneship.org.uk/mailman/listinfo/hackspace</a>><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://swansea.hackspace.org.uk/pipermail/hackspace/attachments/20130424/b1c8f11a/attachment-0001.html" target="_blank">http://swansea.hackspace.org.uk/pipermail/hackspace/attachments/20130424/b1c8f11a/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 24 Apr 2013 13:56:53 +0100<br>
From: Paul Harwood <<a href="mailto:paul@harwood-leon.com">paul@harwood-leon.com</a>><br>
Subject: Re: [Swansea Hackspace] Community building<br>
To: Tom Lloyd <<a href="mailto:napalmllama@gmail.com">napalmllama@gmail.com</a>><br>
Cc: <a href="mailto:hackspace@swansea.hackspace.org.uk">hackspace@swansea.hackspace.org.uk</a><br>
Message-ID: <<a href="mailto:ABC01F4B-A216-4997-875F-539C75B6C568@harwood-leon.com">ABC01F4B-A216-4997-875F-539C75B6C568@harwood-leon.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
All I can say it that on the Bristol Hackspace list (which I have been following for a few months) there is no real distinction and the threads are all lumped into the main Hackspace list as far as I can tell (admin, chat, access issues). They seem to have a thriving list. I could be wrong there, but that is my impression.<br>
<br>
In the inclusive nature of these things - I would also argue that administrative issues are everyones business, as their implications may affect everyone.<br>
<br>
Issues of a private nature are best sent directly to individuals, such as the one I am about to send to Justin about a possible space (with plans that cannot go onto a public archive). Further details can be then filtered down to the list for everyone to see at the individuals discretion.<br>
<br>
@talk is not a bad idea, but it would create a bit of a dilemma for topics that cross the divide - such as chatting about venues for meetings.<br>
<br>
Perhaps a simpler solution would be to mark administrative items with "ADMIN - thread name" or things that are blatantly off topic can be market with "OT - Thread name". Then people can set up their email filters accordingly (i.e. if they only want to get admin messages). As a convention, not a rule though.<br>
<br>
As for a code-of-conduct - absolutely.<br>
<br>
Forums - nope, bad idea.<br>
<br>
:)<br>
<br>
Paul<br>
<br>
On 24 Apr 2013, at 13:12, Tom Lloyd <<a href="mailto:napalmllama@gmail.com">napalmllama@gmail.com</a>> wrote:<br>
<br>
> A technical list might be a good idea too, for help with those matters.<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://swansea.hackspace.org.uk/pipermail/hackspace/attachments/20130424/3236e366/attachment-0001.html" target="_blank">http://swansea.hackspace.org.uk/pipermail/hackspace/attachments/20130424/3236e366/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 24 Apr 2013 14:57:52 +0100<br>
From: Tom Lloyd <<a href="mailto:napalmllama@gmail.com">napalmllama@gmail.com</a>><br>
Subject: Re: [Swansea Hackspace] Community building<br>
To: Paul Harwood <<a href="mailto:paul@harwood-leon.com">paul@harwood-leon.com</a>><br>
Cc: "<a href="mailto:hackspace@swansea.hackspace.org.uk">hackspace@swansea.hackspace.org.uk</a>"<br>
<<a href="mailto:hackspace@swansea.hackspace.org.uk">hackspace@swansea.hackspace.org.uk</a>><br>
Message-ID:<br>
<<a href="mailto:CAF85AwVFoccsGFWMqcSwGvdrwirAbSteey%2B5udCTpus9fUA8sQ@mail.gmail.com">CAF85AwVFoccsGFWMqcSwGvdrwirAbSteey+5udCTpus9fUA8sQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
All lists would be open - I meant to have separate lists purely so admin<br>
and organisational business doesn't get lost amongst general chit chat.<br>
Subject line prefixes could do this job too, although I lean more toward<br>
separate lists, as the functionality is already there in Mailman and it<br>
keeps things nicely sorted. Justin's the one who actually has to do it, so<br>
up to him :)<br>
<br>
Re. guidelines, good idea - but let's avoid hard rules where possible.<br>
Where there are rules there are rules-nazis, and nobody likes them.<br>
<br>
-- Tom<br>
<br>
<br>
On 24 April 2013 13:56, Paul Harwood <<a href="mailto:paul@harwood-leon.com">paul@harwood-leon.com</a>> wrote:<br>
<br>
> All I can say it that on the Bristol Hackspace list (which I have been<br>
> following for a few months) there is no real distinction and the threads<br>
> are all lumped into the main Hackspace list as far as I can tell (admin,<br>
> chat, access issues). They seem to have a thriving list. I could be wrong<br>
> there, but that is my impression.<br>
><br>
> In the inclusive nature of these things - I would also argue that<br>
> administrative issues are everyones business, as their implications may<br>
> affect everyone.<br>
><br>
> Issues of a private nature are best sent directly to individuals, such as<br>
> the one I am about to send to Justin about a possible space (with plans<br>
> that cannot go onto a public archive). Further details can be then filtered<br>
> down to the list for everyone to see at the individuals discretion.<br>
><br>
> @talk is not a bad idea, but it would create a bit of a dilemma for topics<br>
> that cross the divide - such as chatting about venues for meetings.<br>
><br>
> Perhaps a simpler solution would be to mark administrative items with<br>
> "ADMIN - thread name" or things that are blatantly off topic can be market<br>
> with "OT - Thread name". Then people can set up their email filters<br>
> accordingly (i.e. if they only want to get admin messages). As a<br>
> convention, not a rule though.<br>
><br>
> As for a code-of-conduct - absolutely.<br>
><br>
> Forums - nope, bad idea.<br>
><br>
> :)<br>
><br>
> Paul<br>
><br>
> On 24 Apr 2013, at 13:12, Tom Lloyd <<a href="mailto:napalmllama@gmail.com">napalmllama@gmail.com</a>> wrote:<br>
><br>
> A technical list might be a good idea too, for help with those matters.<br>
><br>
><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://swansea.hackspace.org.uk/pipermail/hackspace/attachments/20130424/094bd78e/attachment-0001.html" target="_blank">http://swansea.hackspace.org.uk/pipermail/hackspace/attachments/20130424/094bd78e/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 24 Apr 2013 16:33:54 +0100<br>
From: Justin Mitchell <<a href="mailto:justin@discordia.org.uk">justin@discordia.org.uk</a>><br>
Subject: Re: [Swansea Hackspace] Community building<br>
To: <a href="mailto:hackspace@swansea.hackspace.org.uk">hackspace@swansea.hackspace.org.uk</a><br>
Message-ID: <<a href="mailto:1366817634.9429.23.camel@quartz.geode.org.uk">1366817634.9429.23.camel@quartz.geode.org.uk</a>><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
On Wed, 2013-04-24 at 14:57 +0100, Tom Lloyd wrote:<br>
> All lists would be open - I meant to have separate lists purely so<br>
> admin and organisational business doesn't get lost amongst general<br>
> chit chat. Subject line prefixes could do this job too, although I<br>
> lean more toward separate lists, as the functionality is already there<br>
> in Mailman and it keeps things nicely sorted. Justin's the one who<br>
> actually has to do it, so up to him :)<br>
<br>
Just reading through the docs, mailman has a concept of 'topics' within<br>
one mailing list. once defined you can tag your emails to belong to a<br>
specific topic, and users can select which ones they want / dont want to<br>
receive.<br>
<br>
<a href="http://www.gnu.org/software/mailman/mailman-member/node29.html" target="_blank">http://www.gnu.org/software/mailman/mailman-member/node29.html</a><br>
<br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Wed, 24 Apr 2013 16:45:21 +0100<br>
From: Andrew Price <<a href="mailto:andy@andrewprice.me.uk">andy@andrewprice.me.uk</a>><br>
Subject: Re: [Swansea Hackspace] Community building<br>
To: <a href="mailto:hackspace@swansea.hackspace.org.uk">hackspace@swansea.hackspace.org.uk</a><br>
Message-ID: <<a href="mailto:5177FE11.7030908@andrewprice.me.uk">5177FE11.7030908@andrewprice.me.uk</a>><br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
On 24/04/13 16:33, Justin Mitchell wrote:<br>
> On Wed, 2013-04-24 at 14:57 +0100, Tom Lloyd wrote:<br>
>> All lists would be open - I meant to have separate lists purely so<br>
>> admin and organisational business doesn't get lost amongst general<br>
>> chit chat. Subject line prefixes could do this job too, although I<br>
>> lean more toward separate lists, as the functionality is already there<br>
>> in Mailman and it keeps things nicely sorted. Justin's the one who<br>
>> actually has to do it, so up to him :)<br>
><br>
> Just reading through the docs, mailman has a concept of 'topics' within<br>
> one mailing list. once defined you can tag your emails to belong to a<br>
> specific topic, and users can select which ones they want / dont want to<br>
> receive.<br>
><br>
> <a href="http://www.gnu.org/software/mailman/mailman-member/node29.html" target="_blank">http://www.gnu.org/software/mailman/mailman-member/node29.html</a><br>
<br>
"but it is the responsibility of each poster to make sure that their<br>
post is put with the correct topic"<br>
<br>
Um, yeah, that's not going to work well. Separate lists would be fine.<br>
<br>
Andy<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Hackspace mailing list<br>
<a href="mailto:Hackspace@swansea.hackspace.org.uk">Hackspace@swansea.hackspace.org.uk</a><br>
<a href="http://stoneship.org.uk/mailman/listinfo/hackspace" target="_blank">http://stoneship.org.uk/mailman/listinfo/hackspace</a><br>
<br>
<br>
End of Hackspace Digest, Vol 4, Issue 20<br>
****************************************<br>
</blockquote></div><br>
_______________________________________________<br>Hackspace mailing list<br><a href="mailto:Hackspace@swansea.hackspace.org.uk">Hackspace@swansea.hackspace.org.uk</a><br>http://stoneship.org.uk/mailman/listinfo/hackspace<br></blockquote></div><br></div></div></body></html>