Beyond Open Source - Speaker Deck

Slide 1

Slide 1 text

Beyond Open Source Jason Casden Bret Davidson Code4Lib 2015 Slides: cazzerson.github.io/Code4Lib-2015-slides

Slide 2

Slide 2 text

10+ years of Code4Lib Transparency, sharing, vendor indepedence, code as scholarly output... Yay!

Slide 3

Slide 3 text

We made stuff! We shared stuff!

Slide 4

Slide 4 text

This talk starts where we usually end.

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

"[W]ho would be the best person on your team to talk with about the technical requirements and skills needed for us to install SUMA and get it up and running. For example, do we need a computer programmer with such and such skills. I’m sure you have good documentation available, however, we would like to talk with someone. We are also curious as to how much time it would take to get SUMA working for us. I am not sure we have the expertise in-house." - librarian at a RU/H research university (with permission)

Slide 7

Slide 7 text

On canceling a pilot project... "Ultimately, I didn’t want to get on our IT support’s bad side and because I’m not allowed to play with our development servers I can’t exactly go at the installation process alone." - librarian at a RU/VH research university you've totally heard of and might work at (with permission)

Slide 8

Slide 8 text

How has free software supported growing user communities?

Slide 9

Slide 9 text

1950s-1960s: The Great Unbundling

Slide 10

Slide 10 text

"In the early days of computing, the need to generate massive adoption was strong and the compatibility threat was weak—open- source software reigned supreme." Martin Campbell-Kelly & Daniel D. Garcia-Swartz. (2009). "Pragmatism, not ideology: Historical perspectives on IBM's adoption of open-source software."

Slide 11

Slide 11 text

A-2 system Vassar Hub. "Amazing Grace: Hopper's Computer Innovations."

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

Free? software Big vendors, big machines, big users.

Slide 15

Slide 15 text

"Such practices allegedly included anticompetitive price discrimination such as giving away software services for "the purpose or with the effect of . . . enabling IBM to maintain or increase its market share . . . . " (Id. at 9.) The Government also alleged that IBM's bundling of software with "related computer hardware equipment" for a single price was anticompetitive. (Id. at 10.)" (1995). "United States' Memorandum on the 1969 Case." [United States vs. International Business Machines Corporation].

Slide 16

Slide 16 text

1970s: Stop the hobbyists! The cover of the Homebrew Computer Club's first newsletter.

Slide 17

Slide 17 text

Cover of Popular Electronics, January 1975.

Slide 18

Slide 18 text

"Black and white image of four lapel buttons."Performance Plus VAX II/785 digital" with a star in center; "Interact with BASIC" in script; " VAXstation 1090"; " I gave to the library DECUS" on a reel of tape. Two of these were used in the book, VAXstation 110 and Interact with BASIC."

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

"One thing you do do is prevent good software from being written. Who can afford to do professional work for nothing? What hobbyist can put 3-man years into programming, finding all bugs, documenting his product and distribute for free? The fact is, no one besides us has invested a lot of money in hobby software. We have written 6800 BASIC, and are writing 8080 APL and 6800 APL, but there is very little incentive to make this software available to hobbyists. Most directly, the thing you do is theft." Bill Gates. (1976). "Open Letter to Hobbyists."

Slide 21

Slide 21 text

1980s: My parents get a computer.

Slide 22

Slide 22 text

"Office Wars 3 – How Microsoft Got Its Office Monopoly"

Slide 23

Slide 23 text

(1988). Sierra Game Setup/Installation Program.

Slide 24

Slide 24 text

Shareware

Slide 25

Slide 25 text

GNU, BSD, MIT licenses

Slide 26

Slide 26 text

"Unix is not my ideal system, but it is not too bad. The essential features of Unix seem to be good ones, and I think I can fill in what Unix lacks without spoiling them. And a system compatible with Unix would be convenient for many other people to adopt." Richard Stallman. (1985). "The GNU Manifesto."

Slide 27

Slide 27 text

1990s-Now My grandparents get a computer.

Slide 28

Slide 28 text

Gateway 2000 1994 Desktops.

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

Feb 3, 1998: "Open Source" "The conferees believed the pragmatic, business-case grounds that had motivated Netscape to release their code illustrated a valuable way to engage with potential software users and developers, and convince them to create and improve source code by participating in an engaged community. The conferees also believed that it would be useful to have a single label that identified this approach and distinguished it from the philosophically- and politically-focused label "free software." Brainstorming for this new label eventually converged on the term "open source", originally suggested by Christine Peterson." History of the OSI

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

Tux wallpaper

Slide 33

Slide 33 text

"The more recent switch to hybrid strategies reveals (a) an attempt to recreate, via open-source software, the single-platform scenario that IBM achieved with System/360 (and that IBM failed to recreate, in a proprietary context, via SAA), and (b) an attempt to boost revenues from middleware and services while allowing the old cash cows (e.g. proprietary operating-system software) to peacefully die an unavoidable death." Martin Campbell-Kelly & Daniel D. Garcia-Swartz. (2009). "Pragmatism, not ideology: Historical perspectives on IBM's adoption of open-source software."

Slide 34

Slide 34 text

"In the open source community there exists a tremendous need for exactly the skills librarians have always used in making information resources truly useful. In particular, systems testing, evaluation, and feedback to open source designers is welcome and even sought after; documentation for open source systems is always needing improvement; instructional materials for open source products are often lacking. These are all areas in which librarians excel." Dan Chudnov. (1999). "Open Source Library Systems: Getting Started."

Slide 35

Slide 35 text

"We hope the Code4Lib Journal can manifest the values that have been successful for the Code4Lib community, while providing increased access to the collective knowledge and experience held throughout our diverse professional networks and local organizations, increasing cross-pollination and collaboration among library technology innovators–and helping more people and organizations become innovators." Jonathan Rochkind. (2007). Code4Lib Journal. "Editorial Introduction — Issue 1."

Slide 36

Slide 36 text

Our software generally privileges some users over others.

Slide 37

Slide 37 text

Libtech should be able to thrive in diverse environments.

Slide 38

Slide 38 text

2011-2012 ALA Public Library Funding & Technology Access Study

Slide 39

Slide 39 text

"I believe that building and maintaining library software is vitally important work and it's too big a job to leave to a small group of people. We are creating the future of libraries here." Bess Sadler. (2013). "Creating a Commons."

Slide 40

Slide 40 text

We've done a good job of supporting collaborative development.

Slide 41

Slide 41 text

Our code is more robust, reliable, and open.

Slide 42

Slide 42 text

We have more flexibility and more choices.

Slide 43

Slide 43 text

Current approaches are for those who are almost there.

Slide 44

Slide 44 text

Many can't do servers or don't have staff.

Slide 45

Slide 45 text

Sometimes, small amounts of money are easier to find.

Slide 46

Slide 46 text

What technology might address these other factors?

Slide 47

Slide 47 text

Installers

Slide 48

Slide 48 text

wordpress.org

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

"Create a database for WordPress on your web server."

Slide 51

Slide 51 text

Hosted & Managed Services

Slide 52

Slide 52 text

duracloud.org dspacedirect.org

Slide 53

Slide 53 text

Virtualization

Slide 54

Slide 54 text

vagrantup.com

Slide 55

Slide 55 text

docker.com

Slide 56

Slide 56 text

For software development, when programmers check their code into git, a Dockerfile could be included in the source code, allowing for quick testing of code on remote servers or as a demonstration tool to let others quickly bring up their own versions of an application without having to worry about specific building instructions or dependency management. John Fink. (2014). Docker: a Software as a Service, Operating System-Level Virtualization Framework.

Slide 57

Slide 57 text

Software that can be managed more easily, using less IT resources, by a wider audience of users.

Slide 58

Slide 58 text

wider ≠ bigger

Slide 59

Slide 59 text

wider === different

Slide 60

Slide 60 text

One way to improve the usefulness of open- source software is to make it easier to install, maintain, and evaluate.

Slide 61

Slide 61 text

"Our software is like children. ... We expect that after a time the child will mature, will grow up, will be able to take care of itself, to solve problems, to cope, and perhaps to contribute something new. Initially selfish—for what other options are there?— the child becomes responsible. With luck or persistence or as the result of good upbringing, the child may become conscientious. Shall we hope similarly for our software?" Richard P. Gabriel & Ron Goldman. (2006). "Conscientious Software."

Slide 62

Slide 62 text

Teaching software how to create an environment in which it can thrive.

Slide 63

Slide 63 text

For Suma, the vast majority of our project support is during the installation process.

Slide 64

Slide 64 text

(Selected) List of Suma Install Issues mod_rewrite disabled cURL missing config errors symlink problems server hardening software db access installation method confusion