What qualities and characteristics make for a good piece of open source
software? And once that question is answered, then what pieces of
library-related open source software can be considered best?
I do not believe there is any single, most important characteristic of open
source software
Quality of code in general: How well-designed is the code
architecture, for maintenance and debugging? [This not only matters if
you plan to do in-house development with it, but matters for predicting
how likely the product is to stay 'alive' and continue to evolve with
the times, instead
On Mon, 28 Dec 2009, Eric Lease Morgan wrote:
For my own education and cogitation, I have begun to list questions to
help me address what I think is the best library-related open source
software. [1] Your comments would be greatly appreciated. I have listed
the questions here in (more or
I'm with Jonathan on the community health, one of the things I stress
when teaching my open source classes is that the developer and user
community is essential to the success and life of the product.
Nicole C. Engard
On Mon, Dec 28, 2009 at 12:51 PM, Jonathan Rochkind rochk...@jhu.edu wrote:
I really like this topic, and I like how you're thinking about it. I
tried to ask similar questions in an article I published in July:
http://inthelibrarywiththeleadpipe.org/2009/w-e-b-s-i-t-e-find-out-what-it-means-to-me/
I think Jonathan and Nicole nailed it with community health, though
this
While I think the author draws to strong of a line between Open Source
and Closed Source, there is a good book about evaluating Open source
software by Bernard Golden called Succeeding with open source [1].
Edward
[1] http://www.worldcat.org/oclc/55124574
Brett Bonfield wrote:
I really
Apologies for cross posting. A library systems position was recently
advertised within the New School Libraries in New York City, NY, USA.
The position is a hybrid web developer/ILS librarian.
For a full description of that position, please see
