Editing The 2019 BarnCamp Inquiry

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
 
In order the better understand the issues surrounding the failure of BarnCamp 2019, we want to kick off a relatively informal process of opinion and perspective gathering, with a strong emphasis on what we can do in the future to make our event not just happen, but also totally kick ass.   
 
In order the better understand the issues surrounding the failure of BarnCamp 2019, we want to kick off a relatively informal process of opinion and perspective gathering, with a strong emphasis on what we can do in the future to make our event not just happen, but also totally kick ass.   
  
The deadline for submissions was Friday 13th September.   
+
The deadline for submissions will be Friday 13th September.   
  
 
We've compiled a list of questions below:  
 
We've compiled a list of questions below:  
Line 11: Line 11:
 
* Anything else to share?
 
* Anything else to share?
  
'''''All entries will end up on this page, copied from the other media, unless request them to be kept private'''''. References to particular people who performed tasks has been avoided. All personal references will be removed.
+
Answer them by:
 +
 
 +
* Filling in this page, format as per the example below.
 +
* Emailing you answers. Email details provided by personal invitation.
 +
* Filling in an entry on https://pad.riseup.net/p/2019BarncampInquiry.
 +
 
 +
'''''All entries will end up on this page, copied from the other media, unless request them to be kept private.''''' Please do not add references to particular people who performed tasks. Simply mention that person did, or failed to do that task. All personal references will be removed.
  
 
== Stephanie "Example" Jones ==
 
== Stephanie "Example" Jones ==
Line 72: Line 78:
 
== [[User:MaRk|MarkR]] ==
 
== [[User:MaRk|MarkR]] ==
  
This offer is only once a year  https://is.gd/CflR1n
+
=== What went wrong? ===
 +
 
 +
# most of the people who expressed an interest in helping, either on the HL mailing list or in the survey we did at the end of BC2017, did not help even when sent a personal email suggesting how their skills would be useful
 +
# I tried to provide what I though would be enough structure to enable people to form themselves into task-related [[2019 Tasks|working groups]]. The plan was that each group would work independently and send a spoke into the weekly jitsi meeting. Based on the initial expressions of interest, there should have been 4-6 people in each of 6 groups, but it turned out that there were only 1-3, and some weren't represented at the weekly meetings so we had to ask for 2nd- or 3rd-hand rumours about what was happening.
 +
# this lead to an impression in the meetings that things would be OK when they weren't
 +
# two people took on critical roles and didn't let the rest of us know that they were struggling until it was too late
 +
# I assumed that our email account was configured well, but it was less than perfect, which caused several important emails not to be delivered
 +
# I assumed that all members of the group would be good at using jitsi and irc, but a few struggled
 +
 
 +
=== What could we do to prevent those things going wrong again? ===
 +
 
 +
# more people need to help in advance of the event
 +
# we can't assume that anyone is capable of taking responsibility for their own participation, so we need people to either demonstrate that they can, or be prepared to be offended by being given very simple instructions
 +
# even when given very simple instructions, people may not be able to carry them out, so we all need to check in regularly, either within a working group or to a hub group, for example
 +
# anyone who misses a check-in should be assumed to be a casualty and replaced immediately, at the same time as support is offered to both the absent person and their replacement
 +
# people need to learn / get trained in how to use whichever comms tools we use, and share their contact details with all other participants (email address, PGP public key, IRC handle, phone number...)
 +
# I'd recommend that if we use a hub & spoke model again, any spoke needs to be proficient and have a working setup for all of the below tools. Non-spokes should have at least 3 out of 4:
 +
## Email with working PGP setup
 +
##Jitsi meet
 +
## IRC chat
 +
## Signal (phone and desktop)
 +
# the people who run the mail server, mediawiki and other infrastructure need to give them an inspection and confirm they're in a fit state before we start relying on them
 +
# if anyone wants to add more infrastructure (e.g. a decision-making tool or a project management tool) they need to get it up and working before we all spend lots of time discussing how/whether to use it
  
 
=== How did you feel about the process of trying to organise Barncamp 2019? ===
 
=== How did you feel about the process of trying to organise Barncamp 2019? ===
 
Fun at times and a good feeling of working together, but also very frustrating because it was hard to find the optimum level of slack.
 
Fun at times and a good feeling of working together, but also very frustrating because it was hard to find the optimum level of slack.
  
QGWK1O0BVB9T70EWXF  www.google.com    Where are you located ? I want to come to you one of these days
+
=== Would you be willing to try to help organise next year in 2020? ===
 +
I would not want to be part of the bootstrapping / structural organisation process, but I would join a working group or similar.
  
 
=== Anything else to share? ===
 
=== Anything else to share? ===
 
I'm unsure whether starting earlier would have helped. I imagine that with less of a sense of time-pressure, things might have been even more slipshod than they were.
 
I'm unsure whether starting earlier would have helped. I imagine that with less of a sense of time-pressure, things might have been even more slipshod than they were.
  
== Michael ==
+
<br />
As long as there is still comments on this topic I’ll chip in.  I always thought Barncamp was great fun and that brings some people- but for me there are lots of techie camps so Barncamp when it reaches out to more than techies is more valuable.  Being able to invite other people and having something useful for them – lots of new people workshops, basic security workshops, political workshops that aren’t directly about techie stuff, how do we support movements more broadly (I’m thinking of some of the work in the past like Tech Tools for Activists, or linking with mobilizations, etc) were what made Barncamp different.  The original hacktionlab event and several after that had this emphasis.  How the movement uses tech has changed now (for better or for worse) so I’m not certain how we are linked-in now in the same way.  Getting the non-techie activist world involved takes a lot more early-planning and inviting, not last minute invite to go to the Wye Valley.  I wonder if some low difficulty to organize small events- a hacktionlab in a local city that has at least one introductory workshop (security for activists for example) advertised in the local scene and a discussion more broad about the role of tech in our movements would be an easier way to build up some momentum, maybe another one to happen a couple of months later in another city.  Help link the activist techie community to the broader activist community and give a bit more feedback on what the role is for hacktionlab now.  Barncamp might come out as a priority, or it might not, but a Saturday with a discussion hour and one or two workshops is a lower bar to get things going and bring a few people together.
 
 
 
  Just a thought,
 
 
 
Regards, michael
 
 
 
And ps, good work on effort to organize this summer and also quite thoughtful to have an inquiry. Sorry I haven’t commented earlier even though I meant to
 

Please note that all contributions to HacktionLab: A UK-wide network tech-activists providing meet-ups, events, workshops, national skillshare gatherings and hacklabs may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see HacktionLab: A UK-wide network tech-activists providing meet-ups, events, workshops, national skillshare gatherings and hacklabs:Copyrights for details). Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)