{"id":1265,"date":"2016-06-08T19:21:10","date_gmt":"2016-06-09T02:21:10","guid":{"rendered":"https:\/\/galencharlton.com\/blog\/?p=1265"},"modified":"2016-06-08T19:21:10","modified_gmt":"2016-06-09T02:21:10","slug":"code4lib-and-the-open-source-way","status":"publish","type":"post","link":"https:\/\/galencharlton.com\/blog\/2016\/06\/code4lib-and-the-open-source-way\/","title":{"rendered":"Code4Lib and the “open source way”"},"content":{"rendered":"

The question of what Code4Lib wants to be when it grows up seems to be perennial, and the latest iteration of the discussion<\/a>\u00a0is upon us. Quoting Christina Salazar<\/a>:<\/p>\n

…\u00a0I really do think it’s time to\u00a0reopen the question of formalizing Code4Lib IF ONLY FOR THE PURPOSES OF\u00a0BEING THE FIDUCIARY AGENT for the annual conference.<\/p><\/blockquote>\n

I agree \u2014 we need to discuss this. The annual main conference has grown<\/a> from a hundred or so\u00a0in 2006 to 440 in 2016. Given the notorious rush of folks racing to register to attend each fall, it is not unreasonable to think that a conference in the right location that offered 750 seats \u2014 or even 1,000 \u2014 would still sell out. There are also over a dozen regional Code4Lib groups that have held events over the years.<\/p>\n

With more attendees comes greater responsibilities \u2014 and greater financial commitments. Furthermore, over the years the bar has (appropriately) been raised on what is counted as the minimum responsibilities of the conference organizers. It is no longer enough to arrange to keep the bandwidth high, the latency low, and the beer flowing. A conference\u00a0host that does not consider accessibility and representation is not living up to what Code4Lib qua group of thoughtful GLAM tech people should be; a host that does not take attendee safety and the code of conduct seriously is being dangerously irresponsible.<\/p>\n

Running a conference or meetup that’s larger than what can fit in your employer’s conference room takes money \u2014 and the costs scale faster than linearly. \u00a0For recent Code4Lib conferences, the budgets have been in the low- to-middle- six figures.<\/p>\n

That’s a lot of a money \u2014 and a lot of antacids consumed until the hotel and\/or convention center\u00a0minimums are met.\u00a0The Code4Lib community has been incredibly\u00a0lucky that a number of people have voluntarily<\/em> chosen to take this stress on \u2014 and that a number of institutions have chosen to act as fiscal hosts and incur the risk of large payouts if a conference were to collapse.<\/p>\n

To disclose: I am a member of the committee that worked on the erstwhile bid to host the 2017 conference in Chattanooga. I think we made the right decision to suspend our work; circumstances are such that\u00a0many attendees would be faced with the prospect of traveling to a state whose legislature is actively trying<\/a> to make it more dangerous to be there.<\/p>\n

However, the question of building or finding a long-term fiscal host for the annual Code4Lib conference must be considered separately from the fate of the 2017 Chattanooga bid. Indeed, it should have been discussed\u00a0before<\/em> conference hosts found themselves transferring five-figure sums to the next year’s host.<\/p>\n

Of course, one option is to scale back and cease attempting to organize a big international conference unless some big-enough institution happens to have the itch to backstop one. There is a lot of life in the regional meetings, and, of course, many, many people who will never get funding to attend a national conference but who could attend a regional one.<\/p>\n

But I find stepping back like that unsatisfying. Collectively, the Code4Lib community has built an annual tradition of excellent conferences. Furthermore, those conference\u00a0have gotten better (and bigger) over the years without losing one of the essences of Code4Lib: that any person who cares to share something\u00a0neat about GLAM\u00a0technology can have the respectful attention of their peers. In fact, the Code4Lib community has gotten better \u2014\u00a0by doing a lot of hard work<\/strong> \u2014 about truly meaning “any person.”<\/p>\n

Is Code4Lib a “do-ocracy”? Loaded question, that. But this go around, there seems to be a number of people who are interested in\u00a0doing<\/em> something to keep the conference going in the long run. I feel we should not let vague concerns about “too much formality” or (gasp! horrors!) “too much library<\/em> organization” stop the folks who are interested from making a serious go of it.<\/p>\n

We may find out that forming a new non-profit is too much uncompensated effort. We may find out that we can’t find a suitable umbrella organization to join. Or we may find out that we can keep the conference going on a sounder fiscal basis by doing the leg-work \u2014 and thereby free up some people’s time to hack on cool stuff without having to pop a bunch of Maalox every winter.<\/p>\n

But there’s one in argument against “formalizing” in particular that I object to. Quoting<\/a> Eric Lease Morgan:<\/p>\n

In the spirit of open source software and open access publishing, I suggest we
\nearnestly try to practice DIY \u2014 do it yourself — before other types of
\nformalization be put into place.<\/p><\/blockquote>\n

In the spirit of open source? OK,\u00a0clearly<\/em> that means that we should immediately form a non-profit foundation<\/a> that can sustain nearly USD 16 million in annual expenses. Too ambitious? \u00a0Let’s settle<\/a> for just about a million in annual expenses.<\/p>\n

I’m not, of course, seriously suggesting\u00a0that Code4Lib aim to form a foundation that’s remotely in the same league\u00a0as the Apache Software Foundation or the Mozilla Foundation. Nor do I think Code4Lib needs to become another LITA \u2014 we’ve already got one of those (though I am proud, and privileged, to count myself a member of both). \u00a0For that matter, I do think it is possible for a project or group effort to prematurely spend\u00a0too much time adopting the trappings of formal organizational structure and thus forget to actually\u00a0do\u00a0<\/em>something.<\/p>\n

But the sort\u00a0of “DIY” (and have fun unpacking that!)\u00a0mode\u00a0that Morgan is suggesting is not the only viable method of “open source” organization. Sometimes open source projects get bigger. When that happens, the organizational structure\u00a0always<\/em> changes; it’s better if that change is done openly.<\/p>\n

The Code4Lib community doesn’t have to grow larger; it doesn’t have to keep running a big annual conference.\u00a0But if we\u00a0do\u00a0<\/em>choose to do that \u2014 let’s do it right.<\/p>\n

Share this:<\/h3>