archives

  • warning: mktime() expects parameter 5 to be long, string given in /data/www/code4lib.org/drupal-4.7.7/modules/archive.module on line 223.
  • warning: mktime() expects parameter 5 to be long, string given in /data/www/code4lib.org/drupal-4.7.7/modules/archive.module on line 80.

code4lib journal: mission, format, guidelines

Purpose

Library technologists (developers, programmers, sysadmins, and systems librarians) need better ways to share information both among themselves and with the library community as a whole, including public and technical services staff, library management, and other non-IT specialists. The code4lib journal facilitates technical communication by publishing articles on tools, specs, and challenges in the world of library technology. The journal focuses on showcasing practical hacks, working code, best practices, and implementation issues, and also includes higher-level discussions of large projects or challenges pertaining to information technology in libraries. It is what Roy Tennant calls a "truly technical rag" for libraries.

#code4lib logging

Since the code4lib conference the #code4lib irc channel has gained a lot of new voices with new ideas. In fact dsalo and ksclarke have already said all I can think of saying on the topic of the changing culture of the #code4lib channel. Some people have suggested that some of the ideas, such as a journal, doing outreach/consulting work, etc will require the irc channel to become a bit more 'professional'.

My theory is that having a public log might help encourage this sort of atmosphere. The logging would allow you to go 'off the record' if you really want to say something and don't want it viewable in the logs. In addition to making you think before you type, logging would have some other benefits:

  1. it would allow people with lives to scan the logs looking for stuff and get other work done
  2. it would encourage international participation by people who aren't online with the (Eastern|Central|Mountain|Pacific) Standard Tribe
  3. and most importantly it would allow for interesting consuming applications

At any rate I think that code4lib changing is a good thing. Afterall, an organism that has ceased changing is umm, dead. Unless there are any objections I'm going to create a poll and see what the general feeling on this is.

Create an archive for #code4lib?

* Public Centralized Archive (wide open)\n* Private Centralized Archive (code4lib.org registered only)\n* No Centralized Archive (no logging & I mean it!)\n* \n* \n

#dspace

If you are a dspace user/admin/fan there is a new irc channel on freenode #dspace for discussing all things dspace.

Results of the journal name vote

Here are the results of the code4lib journal name vote:

  1. /lib/dev: A Journal for Library Programmers (14 votes)
  2. Indexed: The Library Coder’s Quarterly (11 votes)
  3. Code4Lib Journal (8 votes)
  4. TIE: /dev/lib/journal and Access Points (7 votes each)

All other names received 5 or fewer votes. 28 people voted, four of whom voted for 5 or more names.

Thanks to everyone who participated!

Test

This is a test

Kevin S. Clarke

test

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

2007 Code4Lib Conference Schedule

Presentations and videos are on individual presentation pages and the Lightning Talks page. In addition to Google Video, video is being hosted in high def format at the Internet Archive.

Audio is also available. A podcast of the presentation audio is available on Odeo.

2007 Code4Lib Conference Lightning Talks

A lightning talk is a fast paced 5 minute talk on the topic of your choosing. If you'd like to do a lightning talk please add your name, topic to this page. You can do more than one if you want, but if the lots fill up (there are 30 of them) you might have to choose which one you want to do.

Mark Jason Dominus has a nice page about lightning talks, which includes this summary of why you might want to do one:

Maybe you've never given a talk before, and you'd like to start small. For a Lightning Talk, you don't need to make slides, and if you do decide to make slides, you only need to make three.