Let me continue by talking about "constraints." When I worked in industry, the sales people I worked with sometimes talked about the sales process as a "funnel." The wide part of the funnel is where prospects are collected. The narrow end of the funnel is where those few prospects who actually became paying customers exit the sales process.

Part of my work at Creighton involves playing with open-source software, which is hardly a chore when a) I can get it to work and b) it solves a problem.

Editorial Introduction - Code4Lib: Long May You Run by Tom Keays
http://journal.code4lib.org/articles/1695

The Code4Lib Journal mirrors the diversity and depth of interests and expertise of its readership. Our successes, indeed, are yours.

How Hard Can it Be? : Developing in Open Source by Joann Ransom with Chris Cormack and Rosalie Blake
http://journal.code4lib.org/articles/1638

Editorial Introduction - Issue 6
Christine Schwartz
http://journal.code4lib.org/articles/1376

The intelligent use of technology in libraries continues to be one of our most crucial challenges. For those of us who became librarians because we loved to explore the book stacks, we are now finding new ways to explore both old and new content in digital form. With issue 6 of the Code4Lib Journal we hope you will find new ways to explore, experiment, and bring to your library users what they want and need.

We're excited to announce the publication of the fifth issue of the Code4Lib Journal. Check out our 1 year anniversary issue! And with the upcoming Code4Lib conference, don't forget to scroll down to the bottom for Noel Peden's special report on what it takes to get good conference video.

http://journal.code4lib.org/

The Code4Lib Journal (http://journal.code4lib.org) is looking to expand
its volunteer staff. We are looking for one or two new Editorial
Committee members, and one new Web/Tech Administrator. As we add more
staff, we are also interested in expanding the diversity of our staff,
especially in regard to types and locations of organization worked for.

The Editorial Committee collectively manages the entire business of the
Journal, including editorial as well as publishing/business functions.
Duties expected of Editorial Committee members include taking

The first issue of the Code4Lib Journal has been released: http://journal.code4lib.org

Call for Submissions

The Code4Lib Journal (C4LJ) will provide a forum to foster community and
share information among those interested in the intersection of
libraries, technology, and the future.

Submissions are currently being accepted for the first issue of this
promising new journal. Please submit articles, abstracts, or proposals
for articles to c4lj-articles@googlegroups.com (a private list read only by C4LJ editors) by Friday, August 31, 2007. Publication of the first issue is planned for late December 2007.

Possible topics for articles include, but are not limited to:

* Practical applications of library technology. Both actual and

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!

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.