Bristol · 3 sessions · 32 members listed
SkillSwap Bristol
Bristol was the second city to run SkillSwap sessions of its own, and the only one besides Brighton that actually held any. The group described itself simply as a SkillSwap group based in Bristol, listed 32 members, and used one venue throughout: Waterside 1.
It was curated by Laura Griffiths and Oliver Humpage. Three sessions were held in 2006, all in the first half of the year, and all longer and more workshop-shaped than the two-talk evenings that Brighton later settled on.
The Bristol Evenings
| Session | Date | Venue |
|---|---|---|
| Web Standards Workflows | 15 May 2006 | Waterside 1 |
| Intellectual Property Rights (IPR) | 10 April 2006 | Waterside 1 |
| Plone skinning workshop | 27 February 2006 | Waterside 1 |
The subjects were squarely of their moment: a Plone skinning workshop, a session on intellectual property rights, and one on web standards workflows. Two of the three were about process rather than code, which is a fair reflection of what a working web team in 2006 needed help with.
Why Bristol Stopped and Brighton Did Not
Nothing in the record explains it directly, so this is inference rather than fact: Bristol ran three sessions in five months and then none. Brighton, over the same period, had a longer habit already established and a group that had been meeting since 2003.
The pattern is worth noticing if you are starting something. Two curators and a venue are enough to hold a first handful of evenings. Getting to a fourth and a fifth appears to need an audience that has already decided the evening is a fixture. The Brighton archive shows what that looks like once it works.
There is a second difference worth weighing, and it is about format rather than people. The Bristol sessions were workshops: single subjects, three hours, one person leading. Brighton settled on two speakers and a couple of hours. A workshop is better teaching and worse infrastructure, because it needs a prepared leader every time and it does not turn attendees into future leaders. Nobody sits through three hours of Plone skinning and concludes they could run next month.
Two curators is also fewer than it sounds. It is enough to share the work, which is why three sessions happened. It is not enough for either person to drop out for a month, which is what a fourth and fifth session usually require somebody to absorb. The Brighton group had been meeting since 2003 by this point and had an audience that expected an evening, which is a different kind of support from having a co-organiser.
What Was Actually Taught in Bristol
Three evenings, and none of them about writing code. The Plone skinning workshop is the closest, and even that is about applying a visual design to somebody else’s content management system rather than about programming — a job that in 2006 fell to whoever in a small agency was least afraid of the templating language.
Intellectual property rights is the outlier and the most telling inclusion. It is not a technical subject at all. It is the kind of thing a small studio needs and cannot easily buy: who owns the work, what a client is entitled to, what happens to a design when a contract ends. A peer who has been through it once is genuinely more useful on that than a general course, because the useful content is the specific mistakes.
Web standards workflows completes the picture. Not what the standards were — that was already written down in abundance — but how to organise a job around them: what to hand a client, what to check, in what order. Process rather than syntax. Two of Bristol’s three sessions were about how to do the job rather than about the tools, which is a fair reflection of where a working studio actually needed help.
Why This Page Exists
Bristol is the smallest chapter in this archive and the one most likely to be dropped from a tidier version of it: three evenings, one venue, one year, no recordings, no handouts. It has a page because other sites still link to it as the Bristol branch of SkillSwap, and an address that has been cited deserves to keep resolving to what it described.
It also earns its place on the merits. A record made only of the thing that worked teaches almost nothing, because success has too many causes to separate. Bristol and Brighton started in the same period with the same name and the same tools, and one of them held three times as many evenings in a year as the other managed in total before stopping. Reading them side by side is the only way to see which differences mattered.
Waterside 1
One venue for all three sessions, which is the pattern every group in this record follows. Waterside 1 is a conference and meeting space in the harbourside part of the city, the sort of room a small organisation can book for an evening without a negotiation.
That is the whole specification, and it is worth noting how low the bar is. Not a lecture theatre, not a venue with a technical crew, not somewhere with a reputation. A room with chairs, a way to project, and a booking process a volunteer can complete on their own. The Brighton run used an arts centre and the earliest sessions used a broadcaster’s building, and functionally none of that mattered more than being able to book the same room again next month.
The one requirement that does matter is the second booking. A venue you can have once produces an event; a venue you can have repeatedly produces a series. Bristol had that and still stopped, which is a reminder that the room is necessary and not sufficient.
What Is Known and What Is Inferred
Worth separating, because this page draws conclusions from a small record and the line between the two should be visible.
Known, from the pages themselves: the group described itself as a SkillSwap group based in Bristol, listed thirty-two members, named two curators, used one venue, and held three sessions between February and May 2006 on Plone skinning, intellectual property rights, and web standards workflows. The dates, subjects and venue are recorded on each session page.
Not known: who led each individual session, how many people attended any of them, what was actually taught, and why no fourth session was held. The speakers section on those pages was left empty, no handouts were published, nothing was recorded, and no closing note exists.
Inferred, and marked as such wherever it appears above: that the workshop format was harder to sustain than the two-talk evening, and that two curators without an established audience is a thinner base than a group that had been meeting for three years. Both are consistent with the record and neither is stated in it.
The Three Sessions in Order
February 2006, the Plone skinning workshop. Plone was a content management system built on Python, and skinning it meant applying a client’s visual design to a system whose templating was unfamiliar to most web designers. It is the most technical of the three and the most obviously a workshop rather than a talk: this is material you learn by doing it alongside somebody.
April 2006, intellectual property rights. The odd one out and the most valuable inclusion, because it is not a technical subject at all. Who owns the work, what a client is buying, what happens to a design when a contract ends. Small studios need this and rarely buy it, and a peer who has been through a dispute once is more use on it than a general course, because the useful content is the specific mistakes.
May 2006, web standards workflows. Not what the standards were, which was already documented at length, but how to organise a job around them: what to hand over, what to check, in what order. Process rather than syntax.
Two of the three, then, are about how to run the work rather than about the tools — which is a fair picture of where a working studio in 2006 actually needed help, and a useful corrective to the assumption that a technical community wants technical talks.
Thirty-Two Members
The number is worth pausing on because of what it is not. Thirty-two people had registered with the group; the sessions were attended by however many turned up, which is not recorded anywhere.
That gap between a list and a room is the most useful thing this record has to say about running anything. The group in London listed fifteen members and held nothing at all. Bristol listed thirty-two and held three. Brighton listed forty-four and ran for years. The numbers correlate loosely with outcomes and explain nothing, because a member list measures interest and interest is not the constraint.
What appears to be the constraint is a named person deciding a specific date is their responsibility. Both groups that held sessions had curators; the one that did not, did not. Thirty-two names on a list produced three evenings because two of those names took the date on.
The Wider Record
Bristol sits between two other chapters and reads differently against each. Set beside London, which listed members and held nothing, three evenings in a single year is a success. Set beside Brighton, which ran for another seven years after Bristol stopped, it is the shorter of two attempts that started from the same place.
Both comparisons are worth making, and the second is the one usually left out of accounts like this.