You are here


You know, when people get together and talk about stuff.

Rails Edge Reston

Pragmatic Studio does it again, putting on another top notch event: Rails Edge Reston. I was fortunate enough to attend and pick up a few more gems of Ruby wisdom. Some of the highlights:

Evergreen Keynote

The Evergreen team presented a "virtual keynote" that consisted of a PowerPoint presentation (see below), a conference call and someone on stage to run things.

Stone Soup

(my first code4lib post)

Ed Summers and William Groppe have jumped in head-strong to crafting a Ruby DSL to Solr. solrb is coming along nicely thanks to our collaborations.

Another early adopter asked a question on the solr-user e-mail list, and I replied with a lot of juicy tidbits to whet your appetite.

We're moving as fast as we can in order to use this infrastructure for the basis of Solr Flare, destined to be faceted browsing plugins for Rails allowing your Rails application to easily benefit from what Solr and solrb offer. Solr Flare will debut at the code4lib pre-conference event in whatever form it happens to be in by then.

2007 Conference Schedule Now Available

The 2007 Conference Schedule is now available. There may be some minor tweaks to be made still, but it is mostly set. It is an incredible line-up, plus there are a lot of cool unknowns hidden in the Lightning Talks and Breakout Sessions, for which ideas and sign-ups will be taken at the conference. See you there!

Code4Lib2006 Audio

The audio for the 2006 Code4Lib Conference is now available online. You can get it the following ways.

Please let me know if you have any problems. Unfortunately quite a few of the objects in Dspace had multiple mp3 files associated with it. It looks like some presentations were cut across cd's and it also seems that some use the same file. Atom 1.0 allows multiple enclosures, which is what I used so that it was associated with the same URI. Unfortunately most aggregators only support single enclosures (RSS only allows one depending on the interpretation) so you may only get the first part. Also the files are rather large. I'm hoping to go through and seperate the individual presentations and then post an updated feed. I still need to determine the copyrights of the audio however.

I created the Atom by hand and carried over the majority of the metadata. It's valid so you should be able to parse it for whatever you want.

Code4LibCon Site Proposals

Corvallis, Oregon
Proposed by jaf.
Repeat of 2006. Possibility of holding in Portland if deemed a better venue.
Madison, WI
Proposed by Debra Shapiro
As we mentioned at ALA, the continuing ed dept. here at UW-Madison SLIS has a lot of experience hosting conferences, and the facilities ( here could easily accomodate a roughly 200 person conference. Now that I have looked at the code4lib web site, the only concern I have is if people would be willing to come to WI in FEBRUARY - but I do see that the 2007 conference is late February into March, so maybe we could make that sound appealing. We do have an annual, extremely popular film fest ( here that brings in people in March (usually late March).
Arlington, Texas
Proposed by Michael Doran
UT Arlington has a lot going for it as a conference venue. Prime location: For those not familiar with Arlington, Texas, we are located smack dab in middle of the Dallas/Fort Worth “Metroplex”...In the interest of full disclosure, let me say that the good transportation news is that it is easy to get to Arlington, but the bad news is that it is hard to get around Arlington if you don’t have a car. Although Arlington has a population of about 300,000, there is no public transportation here. (There is public transportation in Dallas and Fort Worth and train service between the two.) Related to the local Arlington lack-of-public-transportation problem is the fact that there are no accommodations directly on campus, and probably no acceptable accommodations within walking distance, so some type of shuttle service would have to be arranged.

Code4Lib Conference Hosting

If you wish to host a Code4Lib Conference in your community, please review this information before applying. The Code4Lib Conference occurs in or near February each year, to provide a complement to the Access Conference.

Requirements of a Hosting Site

  • A host (usually a committee) willing to make local arrangements and coordinate with the site. Many colleges and universities have conference planning assistance.
  • An auditorium or similar space suitable for the conference itself (capacities in recent years have been 400-450), and room for 8-12 pre-conference workshops "breakout" groups (30-50), which may be a combination of the main space and smaller rooms. Note that while a keynote may be held in an auditorium, it is preferable for the main conference day to have tables and chairs for seating.
  • Wireless network available to attendees free or sponsored by the conference
  • A commitment to work with the conference planning group to help keep attendee costs to a minimum. Past costs have been about $120-200 including meals for 3 days. This requires substantial sponsorship from outside institutions and the hosting institution.

Additional Desirable Qualities

  • Small college or university town (why? "amenities", my friend, amenities). Conferences are also often held in large cities.
  • Reasonably near a major airport (we are prepared to interpret this liberally if the other qualifications are strong)
  • Some distance away from the last conference site, all things being equal (to spread the travel pain)
  • Pre-conference day/events, preferably with optional separate registration

What the Hosting Site is Responsible For

  • Since there is no legal Code4Lib entity, the hosting site must provide a fiscal sponsor for signing any necessary contracts for space or hotel rental. From a legal point of view, the sponsor is putting on the conference with Code4Lib branding. This institution is responsible for gathering sponsorship and registration funds and then transferring them to next year's host. The hosting site may choose to contract with other entities as necessary to fulfill these responsibilities.
  • Managing the program planning process (scheduling and arranging the presentation application and voting process, etc.) Prior years have used a voting mechanism tied to the Code4Lib website (e.g., this); the same system may be used for subsequent conferences.
  • Arranging evening networking opportunities (e.g., interesting and/or good restaurants and bars and/or events)
  • Leading the effort to sign on conference sponsors (various members of the community are expected to volunteer to help sign up sponsors

What the Conference Planning Groups are Responsible For

These items are the responsibility of the Code4Lib Conference planning group (anyone on the conference planning list, which is open to anyone), but the conference host is often actively involved with these aspects as well:

  • Participating in garnering conference sponsors
  • Assisting with conference planning tasks

See also: How to Plan a Code4LibCon and the wiki for various pages used for previous conferences

Code4Lib Conference Hosting

If you wish to host a Code4Lib Conference in your community, please review this information before applying.

Desirable Qualities of a Hosting Site

  • Small college or university town (why? "amenities", my friend, amenities)
  • Reasonably near a major airport (we are prepared to interpret this liberally if the other qualifications are strong
  • Good evening venues (e.g., interesting and/or good restaurants and bars)
  • A host or hosts willing to manage local arrangements (many colleges and universities are skilled at facilitating conferences)
  • An auditorium or similar space suitable for 150-200 persons, plus three or more "breakout" rooms for 30-50.
  • Wireless network available to attendees free or sponsored by the conference
  • Some distance away from the last conference site, all things being equal (to spread the travel pain)

Applying to Host

Send your proposal to the Code4Lib Conference Planning List. Please try to be as complete as possible regarding the situation you offer the conference (keeping criteria such as those above in mind). Proposals received by August 15, approximately 18 months prior to the proposed conference, will have the first chance at consideration.

2007 Code4Lib Conference

The Conference Schedule links to pages for each talk as well as to a Lightning Talk page, which has links to presentation slides and video when they are available.

code4lib 2007 is...

  • building on the great success of code4lib 2006!
  • a loosely structured camp/conference for library technologists to commune, gather/create/share ideas and software, be inspired, and forge collaborations
  • an outgrowth of the Access HackFest, wrapped into a conference-ish format by the folks in #code4lib
  • being planned using an ancient asynchronous messaging protocol and this site
  • open to all interested people/organizations for both planning and participation
28 February - 2 March 2007
(27 February Lucene/Solr pre-conference)
Conference Schedule
Check out the incredible line-up in the Conference Schedule. Notice all of the opportunities to give a five-minute talk during one of the Lightning Talks sessions, sign-ups will happen at the conference.
  • The Georgia Center has a hotel attached, and rooms are blocked off for the conference that can be reserved at the time of registration. Update:The Georgia Center hotel is now fully booked, try other hotels nearby.
  • Accommodation Sharing Notices
Fly into:
Types of Activites and Programs
  • Keynotes - 45 minutes, talks from the farthernmost reaches of library software development where significant real work is getting done. To provide an opportunity to see where they are up close, to learn details of their implementation choices, to hear about the challenges they're facing and how those might scale/translate to the rest of us.
  • Prepared talks - 20 minutes, which must center on "tools" (some kick-ass new software library or integration platform), "specs" (how to get the most out of some protocols, or proposals for new ones), or "challenges" (Some Big Problem we should collectively address). We will evaluate proposals on criteria of geekiness, usefulness, newness, and diversity of topics.
  • Lightning talks - 5 minutes, those interested sign up on a wiki that opens at the start of the conference. *Hard* 5 minute limit... at 4 minutes the next person gets up and starts attaching their screen, and somebody keeps a hard count.
  • Breakouts - People interested in the same project/problem can hang out in a space together for 60-90 minute blocks. Somebody near to the project/problem can coordinate discussion, set up hackers, tackle a challenge session topic, etc. Larger groups will get separate space, smaller groups can just spread out in the larger conference room space.
Planning Group
The planning group includes dozens of members of the code4lib community. If you want to get involved please join the email discussion list.

Email your permission to be recorded

Code4Lib conference

The Code4Lib conference was born in a chatroom discussion in November 2005*. code4lib members quickly coalesced around the idea, and Jeremy Frumkin stepped forward to host it at Oregon State University. It was such a success that the code4lib community has continued hosting the conference annually.

Code4Lib conferences are subject to our community maintained CodeofConduct4Lib

Read more about the code4lib community and conference.


Subscribe to RSS - conferences