stanto
11 November 2016 03:02
1
A chat room is useful for quickfire sanity checking before going full blown into a discussion on discourse. When this resurgence started, it began on telegram.
300+ posts a day got somewhat unruly. Telegram is also an utter pain at exporting chat logs (it doesn’t).
I’ve managed to record the conversation, and digested main points that aren’t already ‘acted upon’ or identified, on github:
[TOC]
#Notes from Telegram Conversation
The following will be documented as copied from people's personal opinions and inputs, others will be documented as collected observations if they are more like decisions.
The conversation on Telegram started with the intention of using the examples of Hackspaces to help one another to lead by good examples to document, adopt and share.
The UK Hackspace Foundation can now be better supported by people whom have experience running a Hackspace for a number of years and it can now be time to collect this knowledge together to help each other and new Hackspaces.
Intention is to have files supporting these areas to be stored inside a git repository, that way it can be tracked, version controlled and kept up to date with pull requests guiding on 'how to build a Hackspace', supporting a Hackspace and maintaining a Hackspace.
Observations that there needed to be a way for people to allow their voices to be acknowledged and heard, without hindering the progress of project owners.
#Acknowledged, Repeated Barriers to 'Get Stuff Done'
* Difficult requirements analysis of a task because of lack of experience
* Deciding on a lead action while acknowledging suggested actions and opinions
* Encouraging continued development of the task or finding/handing over the task to enthusiastic people to completion
##A Suggested way to handle tasks:
show original
So far I have three/four total logs to go through, the first one was the largest.
1 Like
stanto
13 November 2016 01:26
3
stanto:
Updated, 3 more to go.
Done. Up to date as of 12.50 this morning.
1 Like