Abstract
Open source software and the community source movement are raising questions for administrators about whether and when to adopt or devote resources to software development projects, provoking questions of sustainability, future directions, and total cost of ownership. This research bulletin frames the issues an institution should consider with respect to adding community source products to the portfolio of software, infrastructure, and services that constitute the IT environment.