Outline for LITA Guide on OPen Source Software
I. Introduction (Eric Lease Morgan)
This needs to be a general intro to open source - a bit of background as
to the origins of the movement and its philosophy, as well as some mention
of the practical issues of collaboration, documentation, etc. Mention some
real OSS stalwarts: apache, perl, linux.
Then Eric can wax eloquent on why open source is good for libraries.
II. Case studies
(I'm calling them this for lack of any other term -- we won't use that
language in the guide itself because it sounds boring.)
So far (and volunteers still being accepted):
Koha project (Rachel Hamilton-Williams)
SiteSearch (Peter Binkley)
Tree of Life project (Jeremy Frumkin) (or something else?)
cygwin (Dan Chudnov)
Prospero (Eric Schnell)
XMLMARC (Kevin Clarke) (Kevin, could you do a general round-up of
LTSP - Linux Terminal Server Project (if Cindy Murdock wants to re-write
her tutorial to this format)
Each section should include the following, although not slavishly:
1. Who you are (you being your institution or operating unit). Some
context: we're a small college in New England with a staff of x.
2. What was the situation that brought you to think about using/creating
open source? Here's where you tell your story (and for some it may be
short, for others it could be longer) and give your thinking and your
decision process. I.e. "we wanted to do x and we looked at a, b and c
software but it was (too expensive | not really what we needed)..." and so
on. This will help the audience relate because they will have had similar
3. What you did with open source. You should mention things like staffing,
how long it took, etc., but here is also where you get into some details of
what you actually did. Code snippets, screen shots, all of that are
helpful. (examples are important) You probably can't give enough that
someone could exactly copy what you did, but try to be step-by-step (if
appropriate) so that others could follow in your footsteps. Make the
outcome look good!
4. Project evaluation. Now that you've done it, was it worth it? would you
do it again? Did it change your thinking, or the way your institution
works? Is the software you used "ready for prime time?" How much effort did
5. Technical sheet.
I want each section to have a standard "tech sheet" for the software
described. I can't spell this out completely right now, but we can come up
with it. It will have things like:
name of software:
where to obtain it:
where the documentation is:
what it's written in:
level of difficulty to use ?:
program or output sample (if appropriate):
In addition to the above, I am going to need an OSS-savvy editor to look
over each piece for accuracy, completeness and appropriateness. I can
handle format, clarity for the novice, and general editorial. If Eric L-M
is willing, that would be an ideal role for the "introducer" of the piece.
Next I will create a mailing list for us and future postings will not go to
the general list (unless you all want to watch sausage being made ;-). We
may return to the list to find reviewers for the various sections.
Karen Coyle karen.coyle@...
University of California Digital Library
From: Kevin S. Clarke <ksclarke@st...> - 2002-02-28 22:31:31
On Thu, 2002-02-28 at 13:44, Karen Coyle wrote:
> XMLMARC (Kevin Clarke) (Kevin, could you do a general round-up of
> MARC-related products?)
Yes, I'd be glad to...
Kevin S. Clarke (ksclarke@...)
Digital Information Systems Developer
Lane Medical Library, Stanford University
"Pick a job you love, and you will never
have to work a day in your life."