Perspectives on Open Source for Museums’ Digital Projects

Duane Degler
Design for Context
@ddegler
duane@designforcontext.com
David Newbury
Software Developer
@workergnome
david.newbury@gmail.com
Robert Sanderson
J. Paul Getty Trust
@azaroth42
rsanderson@getty.edu
Perspectives on Open Source
for Museums’ Digital Projects
AAM • Wednesday, May 10, 2017

@ddegler @workergnome @azaroth42 #AAM2017 AAM St. Louis, MO – May 10, 2017
Photo of additiona
presenter here (in
grayscale)
INFORMATION
ARCHITECT, DESIGNER
Understand models that
make information tick to
help people do things.
Duane Degler
STRATEGIST,
DEVELOPER
Building tools that help
make impossible things
merely difficult.
David Newbury
LINKED DATA
STRATEGIST
Maintaining strong
communities in support
of open standards.
Rob Sanderson
2

u What is Open Source, and Who Funds It?
u Using Open Source
u Creating Open Source
u Maintaining Open Source
SHARING PERSPECTIVES
3

WHAT IS OPEN SOURCE, AND WHO FUNDS IT?
4

● An individual who “scratches their itch”
● Corporate development
● Often growing out of a bespoke project
● Reputation and mind-share
● Community project
5
“There are three main ways that OSS
is created…”
What is Open Source? Who Funds It?

● In an individual’s spare time
● Corporate consultancy – services around the “product”
● Cloud-based services and hosting
● An OSS project becomes fundamental infrastructure
6
“There are four main ways that OSS is
sustained…”
What is Open Source? Who Funds It?

USING OPEN SOURCE SOFTWARE
7

● Software is a Tower of Babel – there is always a need for
translation and integration.
● You do it, or a contractor does it. Either way, you own
the effort.
● You have greater flexibility – but with it comes responsibility.
8
“Your institution is committing to
become an integrator.”
Using Open Source Software

● Open Source works well for developers
… But that means you need developers
● Are you willing to be your own support team?
9
“Open Source is not ‘Free’ –
It’s just a different cost model.”

● How do you manage the impact that changes have on users?
● You – not a product vendor – manage updates.
● Within one product (e.g. WordPress, Drupal), individual
modules upgrade at different rates.
● The process needs to be managed, and communication
with the development community is important.
10
“Keep up with evolving code bases?”

@ddegler @workergnome @azaroth42 #AAM2017 AAM St. Louis, MO – May 10, 2017 11
Your
thoughts?

CREATING OPEN SOURCE APPLICATIONS
12

● OSS makes the world a better place…
… but in a different way than museums do.
13
“Intrinsic motivation?”
Creating Open Source Applications

● What are standards? Norms? “Best” practices? e.g.
● Code syntax – HTML, CSS, JSON…
• Implementation will rarely be “standard”
● Data models and formats
● Accessibility
● Device dependence / independence
14
“How to interpret ‘standards-based’?”

● Projects have specific needs
● Your goal will not rarely be: create a generalizable application
● Is “custom open source” a thing? Or a myth?
16
“There’s no such thing as a generic
design.”

● Step 1: Build your project.
● X = time and $ required
● Step 2: Generalize for a range of uses/environments.
● 3X
● Step 3: Document and build community
● 3X
17
“What would a process look like?”

Your
thoughts?

MAINTAINING OPEN SOURCE PRODUCTS
19

● Benevolent dictator for life (continuing the hobby/passion model)
● “Corporate” support (large companies & consultancies)
● (are CH institutions “corporations”?)
● Fundamental infrastructure (supported by, or establishing, foundations)
● Community-driven
20
Maintaining Open Source Products
“There are four main ways that OS is
maintained…”

● Portfolio and community management
● Retaining knowledgeable staff
● Retaining budget / management commitment
● Preparing (not planning) for (inevitable) disruptions
21
“Sustaining commitment…”

● That ol’ “I can do it better and faster” lament…
● Reinventing 80% is easy
● The specialized 20% is hard
22
Maintaining Open Source Products
“Keep… or Reinvent?”

Your
thoughts?

What can we learn from
this discussion?

Know how you’re going to fund it.
• Allow your developers time
• Join a consortium
• Create an institutional program
• Look to grants for seed money
25
Know what kind of software you’re making.
• One-off Software
• Custom Software
• Published Software
• Open-Source software
OUR RECOMMENDATIONS

Perspectives on Open Source for Museums’ Digital Projects

Recomendados

Recomendados

Más contenido relacionado

Similar a Perspectives on Open Source for Museums’ Digital Projects

Similar a Perspectives on Open Source for Museums’ Digital Projects (20)

Más de Design for Context

Más de Design for Context (20)

Último

Último (20)

Perspectives on Open Source for Museums’ Digital Projects