Write initial approach email

[syberphunk]

Related: https://forum.hackspace.org.uk/t/how-are-we-going-to-do-the-initial-outreach-to-all-the-new-spaces/35/2

[amunizp]

I think Any email sent out would be great if it has links to definitions to terms like 'bikeshedding'. Related link goes to survey but there was a draft email somewhere.

[castaway]

@amunizp worth starting the @glossary@ doc now then? I don't think we have yet..

[amunizp]

Dunno, or commit ourselves to avoid the terms? if glossary doc, would it go under resources? yeah it would.

[castaway]

@amunizp Kay had volunteered to review things for clarity (its her job).. we should still have a doc imo

[notquitehere]

We can avoid such terms in our external communications however it's not realistic to expect people not to use such terms in less formal communications. For this reason we're making a glossary (which will be on the website).

tamarisk

p: 07949 151 100 e: tamarisk@tamarisk.it t: @notquitehere

On 19 Nov 2016, at 23:04, Jess notifications@github.com wrote:

@amunizp Kay had volunteered to review things for clarity (its her job).. we should still have a doc imo

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[amunizp]

Started: https://github.com/UKHackspaceFoundation/resources/blob/master/glossary.md

[idnorton]

There is an issue for writing a glossary which has been added to as terms crop up.

See UKHackspaceFoundation/UKHackspaces.github.io#11

On 19 Nov 2016 23:09, "amp" notifications@github.com wrote:

Started: https://github.com/UKHackspaceFoundation/resources/blob/master/glossary.md

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/UKHackspaceFoundation/foundation/issues/20#issuecomment-261746013, or mute the thread https://github.com/notifications/unsubscribe-auth/ABLju3BzL1RRH6flDA26q-LzHtpL2oWoks5q_4G2gaJpZM4Krp0N .

[idnorton]

I'm pretty sure that @BuildTheRobots has already done this, can you update please Fligg?

[BuildTheRobots]

Not started a glossary, or at least nothing that couldn't be replicated in minutes - I hope that's actually what I'm being asked :)

As to not using certain terms with our external communication, this strikes me as a slippery slope and I wonder where we draw the line? I seem to spend an inordinate amount of time trying to explain what the concept of a hackspace is, maybe we should be careful not to use this term either? ;)

On 24 Nov 2016 15:10, "Ian Norton" notifications@github.com wrote:

I'm pretty sure that @BuildTheRobots https://github.com/BuildTheRobots has already done this, can you update please Fligg?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/UKHackspaceFoundation/foundation/issues/20#issuecomment-262797052, or mute the thread https://github.com/notifications/unsubscribe-auth/AFD8h24N7ek-3WcWC6RXHNM4463w29jPks5rBajjgaJpZM4Krp0N .

[idnorton]

@BuildTheRobots No, glossary was a tangent to the original issue of initial approach email 😀

[Axford]

have drafted an initial comms email and supporting survey on Google Drive

[idnorton]

This has been sent so I think we can call it done unless we want to add lessons learned?

[castaway]

@idnorton Would suggest a new task for "follow up on initial approach email" ?