LYRASIS has published three open source software case studies on FOSS4LIB.org as part of its continuation of support and services for libraries and other cultural heritage organizations interested in learning about, evaluating, adopting, and using open source software systems.
In the DLTJ Thursday Threads this week: an analysis of how external services included on library web pages can impact patron privacy, pointers to a series of helpful posts from OCLC on communication between software users and software developers, and lastly an update on the continuing discussion of the Kuali Foundation Board’s announcement forming a commercial entity.
Before we get started on this week’s threads, I want to point out a free online symposium that LYRASIS is performing next week on sustainable cultural heritage open source software. Details are on the FOSS4Lib site, you can register on the LYRASIS events site, and then join the open discussion on the discuss.foss4lib.org site before, during and after the symposium.
Welcome to the latest edition of Thursday Threads. This week’s post has a continuation of the commentary about the Kuali Board’s decisions from last month. Next, news of a fundraising campaign by the Ada Initiative in support of women in technology fields. Lastly, an article that looks at the relative bulk bandwidth costs around the world.
This weeks threads are a mixture of the future, the present and the past. Starting things off is A History of the Future in 100 Objects, a revealing look at what technology and society has in store for us. Parts of this resource are available freely on the website with the rest available as a $5 e-book. Next, in the present, is the decision by the Kuali Foundation to shift to a for-profit model and what it means for open source in the academic domain. And finally, a look at the past with the mindset list for the class of 2018 from Beloit College.
Did you feel a great disturbance in the open source force last week? At noon on Friday in a conference call with members of the Kuali community, the Kuali Foundation Board of Directors announced a change of direction:
We are pleased to share with you that the Kuali Foundation is creating a Professional Open Source commercial entity to help achieve these goals. We expect that this company will engage with the community to prioritize investments in Kuali products, will hire full-time personnel, will mesh a “software startup” with our current culture, and will, over time, become self-sustaining. It enables an additional path for investment to accelerate existing and create new Kuali products.
There is an final report as submitted to the Mellon Foundation. This version of the report has minor corrections in the text and now includes information about the group of libraries that have committed to the build phase of the project. Those libraries are:on the OLE Project site that links to the
- Indiana University (lead)
- Florida Consortium (University of Florida, Florida International University, Florida State University, New College of Florida, Rollins College, University of Central Florida, University of Miami, University of South Florida, and the Florida Center for Library Automation)
- Lehigh University
- Triangle Research Libraries Network (Duke University and North Carolina State University participating)
Carl Grant, president of Ex Libris North America, posted a pair of messages on his corporate blog that it is worth calling attention to regarding the OLE Project final report, if you haven’t already run into them: OLE; The unanswered questions and Library Software Solutions – We need a higher level of discourse... Equally important is the comment on the first by Brad Wheeler, Vice President for Information Technology and Chief Information Officer at Indiana University. The whole thread should take about five minutes to read; five minutes well spent if you are interested in the intersection of community source software development with proprietary, closed-source software development. It is even more important if you are looking for a case study of governance issues surrounding community source software development. Go ahead…I’ll wait.