LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  June 2016

CODE4LIB June 2016

Subject:

Re: Formalizing Code4Lib? [diy]

From:

Eric Lease Morgan <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 8 Jun 2016 12:40:23 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (47 lines)

On Jun 8, 2016, at 1:55 AM, Kyle Banerjee <[log in to unmask]> wrote:

> My recollection is that in the bad 'ol days, c4l was much more about sharing ideas to solve practical problems… Nowadays, the conference (which has become like other library conferences) has become an end in itself…


In the spirit of open source software and open access publishing, I suggest we earnestly try to practice DIY — do it yourself -- before other types of formalization be put into place.

I was struck by Kyle’s statement, “the conference has become an end in itself”, and the more I think about it, the more I think this has become true. The problem to solve is not identifying a fiduciary for the annual conference. The problems to solve surround communication and sharing. A (large) annual conference is not the answer to these problems, but rather it is one possible answer.

Unless somebody steps up to the plate, then I suggest we forego the annual meeting and try a more DIY approach for a limited period of time, say two or three years. More specifically, I suggest more time & earnest effort be spent on local or regional meetings. Hosting a local/regional meeting is not difficult and relatively inexpensive. Here’s how:

  1) Identify one or two regional leaders - These are people who will initialize and coordinate events. They find & recruit other people to participate. Sure, they require “spare cycles", but they do not have to keep this responsibility past a single event.

  2) Create/maintain a Web presence - This is a Web page and/or a mailing list. These tools will be communication conduits. Keep the Web page up-to-date on the status of the event. Refer to it in almost every email message. Use it to record what will happen as well as what did happen. The mailing list can start out as someone’s address book, but it can grow to an mail alias on a Linux machine or even a Google Group. The Web page can live in the Code4Lib wiki.

  3) Communicate - Kind of like voting in Chicago, “Talk early. Talk often.” This is essential, and can hardly be done too much. People delete email. People don’t plan ahead. People think they are not available, then at the last minute they are. The reverse happens too. Send communications about your event often, very often. Use email to build a local/regional community. Share with them your intention as early as Step #1. Keep people informed. 

  4) Identify a venue — Find a place to have the event. Colleges, universities, and municipal libraries are good choices. Ideally they should be associated with the output of Step #1. The meeting space has to accommodate fifty people (more or less), but bigger is not necessarily better. The space can be an auditorium, a meeting room, many meeting rooms, or any combination. The space requires excellent network connectivity. A meeting space sans strong wi-fi is detrimental.

  5) Identify a time - The meeting itself needs to be at least one afternoon long. A day is good. More than two full days becomes a bit difficult. Starting at times like noon allows people to have traveling time, or for folks who arrived the night before time to get oriented. Starting at nine and ending at 5 makes for a nice full day. Ending the meeting around noon makes it easy for people to travel back home. Host the event on a weekday and maybe ending on a Saturday. This is professional work, and it may be fun & interesting, but it should not require vacation leave.† 

  6) Outline an agenda - The agenda embodies "la raison d’être”. The agenda is a tool for facilitating the communication and sharing. Put it on the Web page. Allow others to fill it in. Outline show & tell sessions of various lengths. Recruit people who you know are doing interesting things. Be prepared to show one or two things from the local institution. Do show & tell on things other than computers in libraries. Give tours of local cool stuff, like an archive, special collection, museum, maker space, or even churches. These tours are less about the showing of the stuff as they are about enabling communication of the attendees. Do you really think people are not going to talk work while gazing at a painting? Identify concrete (library) problems to solve, and these form the basis of hack sessions. Do the “unconference” thing. Take hints from THATCamps. Do roundtable discussions and have reporting back sessions. Bring in people outside computing but inside the hosting community, and learning by everybody will take place.

  7) Identify how to eat - Going to one more more restaurants/bars for lunch or in the evening is a very good thing. When it comes to lunch, people can go out on their own, or the hosting institution may want to sponsor. Cookies and snacks during the day are good things, but not necessary. Shy away from caterers. They are expensive. Take the same money, go to the grocery store, and buy things to eat. Make reservations in restaurants for larger groups.

  8) Do the event - On the day of the event, make sure you have name tags, lists of attendees, and logistical instructions such as connecting to the wi-fi. Have volunteers who want to help greet attendees, organize eating events, or lead tours. That is easy. Libraries are full of “service-oriented people”. Use the agenda as an outline, not a rule book. Smile. Breath. Have fun. Play host to a party. Understand the problem you are trying to solve — communication & sharing. Let it flow. Don’t constantly ask yourself, “What if…” because if you do, then I’m going to ask you, “What are you going to do if a cow comes into the library?” and I’m going to expect an answer. 

  9) Record the event - Have people take notes on the sessions, and then hope they write up their notes for later publishing. Video streaming is expensive and over the top. Gather up people’s presentation materials and republish them.

 10) End the event - Graciously say good-bye, clean up, and rest. Put the coordination on your vita and as a part of your annual review.

 11) Evaluate - Follow-up with the people who attended. Ask them what they thought worked well and didn’t work well. Record this feedback on the Web page. This is all a part of the communication process.

 12) Repeat - Go to Step #1 because this is a never-ending process. 

Now let’s talk about attendee costs. A national meeting almost always requires airfare, so we are talking at least a couple hundred dollars. Then there is the stay in the “cool” hotel which is at least another hundred dollars per night. Taxi fare. Meals. Registration. Etc. Seriously, how much are you going to spend? Think about spending that same amount of money more directly for the local/regional meeting. If you really wanted to, coordinate with your colleagues and sponsor a caterer. Carpool with your colleagues to the event. Coordinate with your colleagues and sponsor a tour. Coordinate with your colleagues and sponsor video streaming. In the end, I’m positive everybody will spend less money.

What do you get? In the end you get a whole lot of professional networking with a relatively small group of people. And since they are regional, you will continue relationships with them. Want to network with people outside your region? No problem. Look on the Code4Lib wiki, see what's playing next, and attend the meeting.

Instead of centralization — like older mainframe types of computing — I suggest we embrace the ideas of de-centralization a la the Internet and TCP/IP. This way, there is no central thing to break, and everything will just find another path to get to where it is going. Instead of one large system — let’s call it the integrated library system — let’s employ the Unix Way and have lots of tools that do one thing and one thing well. When smaller, lesser expensive scholarly journal publishers get tired and find the burden to cumbersome, what do they do? They associate themselves with a sort of fiduciary who takes on financial responsibilities as well as provides a bit of safety. And then what happens to those publications? Hmmm… Can anybody say, “Serials pricing crisis?”

Let’s forgo identifying a fiduciary for a while. What will they facilitate? The funding of a large meeting space in a “fancy” hotel? Is that really necessary when the same communication & sharing can be done on a smaller, lesser expensive, and more intimate scale? DIY. 

† Here’s a really tricky idea. Do what the TEI people do. Identify a time and place where many similar people are having a meeting, and then sponsor a Code4Lib-specific event on either end of the first meeting. NASIG? DLF? ACRL? Call it a symbiotic relationship.

—
Eric Lease Morgan

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

October 2024
September 2024
August 2024
July 2024
June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager