I spotted this interesting article by Ryan Funduk, on the culture of exclusion generated by piss-up parties at tech conferences — primarily at conferences in America, but the issue is certainly prevalent in other places.
I attended OSCON last year, and whilst OSCON is clearly not as bad as the type of events that have been highlighted in this writeup, there were still plenty of events that were promoted by the conference and their sponsors, but clearly served only as an opportunity to booze up some delegates. In fact, there was at least one such party advertised in the conference schedule each night — peaking on the Wednesday where there were three such conference parties advertised on the conference schedule, cleverly paced for two hours so that delegates could move on to each of the parties as the previous one wound up.
I personally feel as though these sorts of events have no place being actively promoted by the conference schedule. There are several good reasons for this that are all detailed in the parent article, but they all boil down to the fact that not everyone drinks. Parties where the key attraction is drinking only attracts those who drink. By advertising such events as part of the programme, they create cliques within the conference community that aren’t defined by the community that the conference serves to support.
Worse still is when such events are not run with alternatives available, because this strongly promotes the subtext that drinking is the only way to socialise at the conference. So a delegate who doesn’t drink will not fit in to any part of the conference, because there is no well-established way for non-drinkers to find each other.
As an active participant in tech conferences in Australia, it’s important to reflect on criticisms of such conferences in other countries, as well as here, to make sure that we’re providing a culture that actively encourages any delegate who chooses to attend — regardless of age, gender or lifestyle choice.
In the case of conferences run in Australia, I don’t believe that the issues of Alcohol-driven events are near as much of a problem as they are in America.
At Linux.conf.au, since the demise of the Google Party (an event very much brought over by American employees of Google), I don’t think I’ve seen a single event associated with the conference where drinking was the sole purpose of the event. One exception of this is the Professional Delegates Networking Session, however, I have always seeked to run a non-alcohol driven alternative against it. As a non-drinker for most of the LCAs I’ve been to, I don’t think I’ve lost out by not participating in the drinking.
At PyCon Australia, we’ve been careful to not offer up any events with an open tab — companies who want to sponsor alcohol have to do so in a way that ensures that the amounts provided are limited, and any foray into dangerous territory comes at the expense of the delegates. There is no conference event planned without a defined activity, and in every case, the presence of a bar at the event is clearly a distant second in terms of priorities for the organisers.
One of the great successes over the past few years in Australia has been ensuring that toxic cultures within the tech community aren’t tolerated. I think it’s imporant that we look at everything we do with a critical eye. I’m sure that our record on avoiding the fostering of an alcohol culture at our events isn’t spotless, and it’s one that we should look over with as critical an eye as we use to look over issues of gender or sexuality.
It’s definitely my intention to do this as I continue to put together PyCon — constantly looking at what we can do as Australian-based conference organisers do to ensure that the culture of alcohol doesn’t take over from the culture of the technology that we’re gathering for?
Update: I’ve written a further post on this topic. Do try it.