I think this is a good idea.  However, I wonder if the number of
contributions from those other than the sponsoring institution or original
developer might also be considered when evaluating open source software?
Contributions come in many forms -- code, design, testing, and documentation
to name a few.  The sustainability and evolution of software is probably
more important than its initial popularity.  Libraries have struggled to
work together on the maintenance of these tools, despite the fact that the
"distributed workload" argument is often cited as a reason to move toward
open source.

Even though I believe those who develop "cool" tools should be rewarded for
their vision and hard work, I would lean toward rewarding developers
involved in projects which remain active over time, and provide sustained
value to the community.   In this sense it would be the software that gets
the award, and by proxy, anyone who had a hand in developing it.

-Shaun Ellis
Web Applications Developer
Rutgers University Libraries



On Thu, Mar 5, 2009 at 7:52 PM, Eric Lease Morgan <[log in to unmask]> wrote:

> As a community, let's establish the Code4Lib Open Source Software Award.
>
> Lot's of good work gets produced by the Code4Lib community, and I believe
> it
> is time to acknowledge these efforts in some tangible manner. Our
> profession
> is full of awards for leadership, particular aspects of librarianship,
> scholarship, etc. Why not an award for the creation of software? After all,
> the use of computers and computer software is an essential part of our
> day-to-day work. Let's grant an award for something we value -- good,
> quality, open source software.
>
> While I think the idea of an award is a laudable one, I have more questions
> than answers about the process of implementing it. Is such a thing
> sustainable, and if so, then how? Who is eligible for the award? Only
> individuals? Teams? Corporate entities? How are awardees selected?
> Nomination? Vote? A combination of the two? What qualities should the
> software exemplify? Something that solves a problem for many people?
> Something with a high "cool factor"? Great documentation? Easy to install?
> Well-supported with a large user base? Developed within the past year?
>
> As a straw man for discussion, I suggest something like the following:
>
>  * Regarding selection, I suggest there be a
>    committee who solicits nominations and
>    selects the awardee(s). As the years go by
>    an individual from the committee drops off
>    and the/an awardee becomes a member.
>
>  * Regarding who is eligible, I suggest it be
>    individuals, teams, or corporate entities.
>    Awardees must be willing to serve on the
>    next year's nominating committee.
>
>  * Regarding what is eligible, I suggest the
>    software be open source, directly
>    library-related, and developed within the
>    past two years.
>
>  * Regarding the timing, I suggest this be an
>    annual award given at each Code4Lib
>    conference.
>
> These are just suggestions to get us started. What do you think? Consider
> sharing your thoughts as comments below, in channel, or on the Code4Lib
> mailing list.
>
> --
> Eric Lease Morgan
> University of Notre Dame
>