a webinar for lyrasis
Jennie Rose Halperin
Mozilla Community Building Team
David Berry Libre Culture: Meditations on Free Software
I. Why choose open source software?
II. What is the state of open source software in libraries?
III. What is open source governance and how do you make decisions?
IV. Designing your governance structure
V. Some common problems
VI. Case study: Kuali
VII. Conclusion
via Wikipedia
via Wikipedia
Auto-Graphics, Inc.
Biblionix
Book Systems, Inc.
COMPanion
Cyber Tools for Libraries
EOS
Ex Libris
Follett Software Company
Innovative Interfaces
Library World
Mandarin Library Automation
Polaris Library Systems
SirsiDynix
The Library Corporation
BiblioteQ
Evergreen
Koha
OpenBiblio
phpMyLibrary
Aquabrowser
Axiell Arena
Bibliocommons
Carmen (LANius)
CS Library
DIMDATA ILS
Ebsco Discovery Service
Encore
Libramatic
The Library Corporation (TLC)
Polaris Library Systems
Primo (ExLibris)
Prism 3 (Capita)
Retrievo (KEEP SOLUTIONS)
Serials Solutions Summon
VTLS Inc.
WorldCat Local (OCLC)
via Wikipedia
Mozilla Libraries and Open Source Focus Group, January 2014
(see Bibliography for articles on the topic)
Hugh Rundle, "Who are you Empowering?" In the Library with the Lead Pipe
Peter Murray, "Governance in Open Source Software Projects"
Tim O'Reilly, The Architecture of Participation
Peter Murray, "Governance in Open Source Software Projects"
The goal of open is:
participation. rocket fuel for smart collaboration.
agility. speed. flexibility. getting shit done.
momentum. communities want to push boulders that are already rolling.
testing and rapid prototyping. iterating and refining as we go.
leverage. getting greater bang from limited resources. punching above our weight.
The goal of open is NOT:
public performance. creating the fake appearance of consultation.
endless opinion-sharing. never-ending “feedback.” bike-shedding.
magic “crowd-sourcing.” crowds aren’t smart — communities of peers are.
Matt Thompson, "How to Work Open"
Scott Berkun, The Year Without Pants: Wordpress.com and the Future of Work
via Wikipedia
via Wikipedia
via Karl Fogel Producing Open Source Software
via Geek Feminism
via Karl Fogel, "Producing Open Source Software"
see: Mozilla Modules
via Wikipedia
via Wikipedia
Gwyn Firth Murray, "Attribution Requirements in Free and Open Source Software Licensing"
(thank you for the slogan, David Eaves!)
For example, anything involving personal data, security, etc.
SOON. We want to work open — but we’re not ready yet. We’re not ready for widespread attention. Or can’t meaningfully absorb offers from people to help. So let’s wait until we are.
This is a totally reasonable gear to operate in — but can also become a trap or semi-permanent holding pattern. Without forcing functions or test cases, it’s a recipe for going slow.
Matt Thompson, "How to Work Open"
Our standard default setting. Working in public spaces like etherpads and community lists, instead of closed email threads. Sharing signposts, drafts, prototypes and roadmaps on our blogs, etc. The primary goal is surfacing what’s needed to enable smart co-building. If we don’t, not only will our communities have no idea how to get involved — our immediate peers and colleagues won’t be able to help as effectively, either.
Like: “Holy crap we’re releasing Firefox 4!” Or: “We’re ready for the cover of Rolling Stone!” Taking it up a notch to a higher order of magnitude. Participation at scale. From co-builders to more mainstream participants or consumers.
Brad Wheeler, "Open Source 2010: Reflections on 2007"
Brad Wheeler, "Open Source 2010: Reflections on 2007"
Phil Hill, "Kuali: A Primer for Community Source Administrative Systems in Higher Ed"
Brad Wheeler in Chronicle of Higher Education April 2014
Want to be added to my bibliography on Zotero? Send me an email to see my sources!