Free Culture
in an
Expensive World
OpenSourceBridge 2016
Shauna Gordon-McKeon - @shauna_gm
Thanks for having me!
about money & sustainability in FOSS
not an economist or business person but I've been on enough mailing lists... to see many arguments break
out about money (esp corp money) in FOSS
money in foss is important but fraught, but money always is
At its heart, our question is “How do we get free culture projects the resources they need?”
Humans have been fighting over resources for tens of thousand of years with words and with weapons
We can't resolve this question today, or this year, or this decade, or maybe ever.
These are deep waters, folks. We may never get to the bottom of them.
But it's important that we keep trying, because without enough resources our communities and our projects will continue to struggle.
My original proposal centered this talk around a project of mine.
Same name - it's an interview project, goal is collecting experiences, resources, insights
It's volunteer - can't tell if it's ironic or merely fitting but I haven't had time to do much
There is some material there, and I invite you to contribute to it. But I can't base this talk on it.
So instead, I'm going to take you on a whirlwind tour, covering:
current methods, why their insufficient, roadblocks, next steps
I’m going to start with the phrase that inspired this talk.
It’s a pretty common catch phrase that’s used to describe free software and to emphasize its political underpinnings.
If you know it, shout it out.
"Free as in speech, not as in beer"
I don't like this catchphrase
Not because I dislike being political. I love being political!
I dislike it because it's so not that easy to separate politics from money
Ask campaign finance reformers in the US
The freedom to run the program as you wish, for any purpose (freedom 0).
The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1).
The freedom to redistribute copies so you can help your neighbor (freedom 2).
The freedom to distribute copies of your modified versions to others (freedom 3).
The first two freedoms in this definition revolve around personal liberty.
They take for granted that a user has a piece of software and guarantees them the right to understand and to change it.
But the second two freedoms revolve around property rights.
The freedom to run the program as you wish, for any purpose (freedom 0).
The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1).
The freedom to redistribute copies so you can help your neighbor (freedom 2).
The freedom to distribute copies of your modified versions to others (freedom 3).
They make claims about how software should be distributed.
Whether or not you agree with the claim, it *is* a claim about property.
It does mean "free as in beer", more or less.
So why do people keep using the catchphrase?
Money == difficult topic, can tear relationships & communities apart. Tempting to ignore it.
But that gives us communities made of people who can afford to ignore it.
"Going back to their houses, I first heard the phrase “We don’t discuss money.”
My mom discussed money, my dad, far away in northern California hardly discussed anything
else. How could you not discuss money? It was like a family that announce they didn’t allow
the mention of food. Or hope."
- Quinn Norton, Count
Post from Quinn Norton that stuck with me.
She talks about growing up poor in a gentrifying neighborhood, and making friends with wealthier neighbors.
{read}
Ignoring money is a privilege. Ignoring money is a political decision.
We talk about the four software freedoms, but there’s another, more famous set of four freedoms – FDR’s:
Freedom from want, in our capitalist society, usually means having money.
To care about money - to care about giving people the resources they need - is in its own way to care about freedom.
But of course, not all free culture activists do ignore money.
In some ways, the decision to rebrand “free software” as “open source” and to actively court the interest and investment of for-profit companies can be viewed as a collective acknowledgment of the importance of money.
"Open source enables a development method for software that harnesses the power of distributed peer
review and transparency of process. The promise of open source is higher quality, better reliability,
greater flexibility, lower cost , and an end to predatory vendor lock-in."
Open Source Initiative, steward for OS definition, highlights market competitiveness of FOSS
This rebranding has been very successful
Anyone who says "there's no money in open source" is wrong.
There are many projects and individuals that use for-profit models to build and maintain OSS.
Let's talk about some of them!
Models
support, training and integration
Best known example: red hat - 8000 employees, over a billion in revenue
Provides flagship product: RHEL, which has subscription based support, integration, training
Other projects: Revolution R (Microsoft); HortonWorks (Apache Hadoop)
Red Hat employs ppl to work on Linux - not the only one!
Models
support, training and integration
vendor-neutral corporate foundation
"Who Writes Linux" 2015 states over 80% of contribs are employeed by companies, 11.8% unpaid.
That's thousands of people employed by companies to work on Linux.
Additionally, the Linux Foundation itself employs Linux developers, including Linus Torvalds. Over 500 companies donate money.
It bills itself as vendor neutral but "platinum" members donating half a mil or more get a seat on the board of directors, and together for a majority.
Until 2016 individuals could be members and run for two board seats, but in Jan 2016 the bylaws were quietly changed to get rid of individual memberships.
Models
support, training and integration
vendor-neutral corporate foundation
affiliate advertising
hosting
Another model is Mozilla Firefox. Arguably this should be filed under not-for-profit.
Worth pointing out their model. Used to be google made up 98% of MF revenue, now country-by-country.
More common method is hosting. Matt Mullenweg founded Wordpress, which is GPL and overseen by non-profit WP foundation.
Also founded Automattic, successful Wordpress hosting platform.
Two other pay for host: Discourse, a community discussion platform, and Ghost, a blogging platform.
Models
support, training and integration
vendor-neutral corporate foundation
affiliate advertising
hosting
freemium
open core
dual licensing
That's the famous ones! What else?
Controversial "Freemium" model. Why is it controversial? I'll tell you about that in a bit. Also used by PyCharm & a # of others.
Offers free open source version and proprietary, fully featured version for pay.
Related is "open core" model where the core is open but there are proprietary add ons or plugins.
Similar yet distinct is "dual licensing".
Attractive to customers who want to use the project in their own proprietary product & can't use GPL. Example: MySQL
Models
support, training and integration
vendor-neutral corporate foundation
affiliate advertising
hosting
freemium
open core
dual licensing
sponsored by proprietary company
customization through agencies
freelance development
bounties
Google: Go, Angular, Android, Chromium (note: Chrome/Chromium is "freemium")
Not just tech companies: Django framework developed @ Lawrence Journal-World.
Web dev agencies like Caktus Group (Django) and Boston's Bocoup (Javascript - makes Grunt, contributes to jQuery, Node, others.
Freelance: Kronda Adair talk tomorrow "Building a Life with Wordpress" - Wordpress, Django, Drupal, Bootstrap, more
Topic specific: CiviCRM used by non-profits and educational platform open EdX.
Bounties!
With so many great examples, tempting to say "open source has won".
But if it has, why is there still so much proprietary software?
Why are important projects still struggling to get resources they need to be competitive, or to be developed at all?
"Although the Open Source Initiative suggests "the promise of open source is better quality, higher reliability, more flexibility," this promise is not always realized. Although we do not often advertise the fact, any user of an early-stage free software project can explain that free software is not always as convenient, in purely practical terms, as its proprietary competitors. Free software is sometimes low quality. It is sometimes unreliable. It is sometimes inflexible."
- Benjamin Mako Hill, When Free Software Isn't Better
Benjamin Mako Hill wrote a post back in 2010 where he points out the flaws in the OSI’s definition:
It’s vitally important not to equate the success of free and open source software with success in the market.
We can’t ignore money, but we also shouldn’t be tied to a single model of sustainability or a single standard for success.
A conversation that’s focused on profit is a conversation that’s way too narrow.
So what alternatives are there?
(More) Models
volunteer
First off – the most common open source model: volunteering.
I can't emphasize this enough: volunteering is not some sort of null option – all projects require resources.
Volunteer projects are funded through donation of labor.
This is not necessarily a bad thing, but it is absolutely a funding model.
(More) Models
volunteer
software-focused non-profit
Mozilla (kinda). More famously: Wikipedia. $70 mil a year in donations, 280 staff (yes, I did get that info from their wikipedia page)
Most OSS non-profits not as well funded.
I think Django is pretty sadly underfunded given the # of projects and companies that use it, so I've included it here.
Also: Python Software Foundation, Apache Software Foundation,
Sahana, which develops open source disaster management software
OpenMRS, which is an open source medical records system led by two non-profits.
Can't name them all.
(More) Models
volunteer
software-focused non-profit
other non-profit
government
academia
Other-focused: Sunlight, COS, ONA. These are just three I've actively worked with or volunteered for - there are hundreds more.
More models: government-developed FOSS. Britta Gustafson talk on 18f, develops all OSS. They are also experimenting with microprocurements.
Academia: NumFocus foundation is non profit but their projects are often staffed by academics, for example Project Jupyter.
MIT: Scratch & AppInventor for beginning developers. Sustainable Engineering Lab @ Columbia.
George Mason University’s Center for History and New Media develops Zotero.
Oregon’s own OSU has the Open Source Lab. Again, I can't name them all.
(More) Models
volunteer
software-focused non-profit
other non-profit
government
academia
crowdfunding
grants
fellowships, internships & retreats
One-off - Kickstarter, Indiegogo; ongoing - Patreon; experimental: Snowdrift
Grants: Knight Foundation, Shuttleworth Foundation, Open Society Foundation -- regular give OSS grants. Open Technology Fund (Privacy-focused)
Fellowships etc many of which are targeted at newcomers, underrepresented people:
GSoC, Outreachy, Rails Girls Summer of Code, Summer of Code in Space, Knight Mozilla Fellowships, Code for America, Code for Progress & More. Stripe "Open Source Retreat" for experienced devs.
(More) Models
volunteer
software-focused non-profit
other non-profit
government
academia
crowdfunding
grants
fellowships, internships & retreats
“Shauna,” you might be ready to protest. “You’ve just named a ton of projects that are funded in a variety of ways. Surely one of these options will work for me and/or my project!”
Maybe one will! I encourage you. They all have their pros and cons. I'd go into detail about those but presumably you want to hear other talks today.
(But maybe a pros & cons of FOSS models BoF?)
Anyway, these models are not enough, because we've still got problems.
What's the problem?
Let's take a moment to define them, because without clearly defining our problems we won't know what success looks like.
This is my definition of the problem. Yours may be different - whatever it is, I encourage you to articulate it, including what success looks like to you.
Problem 1
Key technologies are still proprietary
Widely used by non-developers
Widely used by developers
Likely to influence future technology
Intersect with other areas of concern
Measure success by: how competitive open source projects are in these key areas.
“Key technologies” is an ill-defined and ever-changing term. The FSF has a high priority projects list that's a good start.
What are some things that might make a technology key?
Intersections: privacy, harassment, government transparency, open science and medicine, and more.
Problem 2
Many projects are not 'well rounded'
Design
UX research
Documentation
Translation
Outreach
Teaching & mentorship, including technical mentorship
Community management
Project management
Marketing & publicity
Measure success by: how many non-coders are in our communities and how prominent they are.
Why are so many of our projects not competitive? In part, not 'well rounded'. Over-emphasize code contributions, and in particular new feature development over easing technical debt.
Under-valued: in companies, these jobs pay less. In FOSS projects, these tasks get less acknowledgement and reputation and enthusiastic "thank yous". No wonder so many projects have trouble attracting vital contributions.
Problem 3
Lack of diversity
Recommended: The Ethics of Unpaid Labor and the OSS Community by Ashe Dryden
Measure success by: if our communities become as diverse as the general population.
Not representative of general population. In part because most forms of oppression have a hefty financial impact.
Many of you have probably read Ashe's post, where she discusses how the dependence on unpaid labor in FOSS discriminates against people from marginizalized communities who are less able to donate their time.
This lack of diversity is unfair to those excluded and hypocritical for a community that prides itself on being free and open.
Some of the most successful and impactful projects come from lived experience. We talk about developers scratching their own itch – what about developers tracking their
own periods or protecting themselves from harassment or abuse? What kind of amazing open source projects haven't
even be conceived of because the people who can think of them aren't part of our community?
Problem 4
Burnout
Measure success by: if our community members are generally happy and not stressed.
A way of measuring success here is surveying open source community members and seeing if they report decreased stress, increased happiness, a desire to continue working on their projects and within open source as a whole, and a sense that they and their communities are equal to the challenges ahead of them.
Problem 4
Burnout
Measure success by: if our community members are generally happy and not stressed.
Four ways we're currently struggling, and four ways to measure success.
We need to be more competitive, more well rounded, more diverse, and emotionally healthier.
How do we move towards that?
There are a few things holding us back. I want to talk about three of them – three fears that I think are derailing our conversations.
Fear of Money
Ashe's essay in response to a post by David Heinemeier Hansson, aka DHH, aka creator of Ruby on Rails
"External, expected rewards diminish the intrinsic motivation of the fundraising open-source contributor. It risks transporting a community of peers into a transactional terminal. And that buyer-seller frame detracts from the magic that is peer-collaborators."
- David Heinemeier Hansson, The perils of mixing open source and money
That bit about the magic of peer collaboration resonates with me. But there’s another line in this quote that sticks with me, and not in a good way: “expected rewards diminish intrinsic motivation”.
"External, expected rewards diminish the intrinsic motivation of the fundraising open-source contributor. It risks transporting a community of peers into a transactional terminal. And that buyer-seller frame detracts from the magic that is peer-collaborators."
- David Heinemeier Hansson, The perils of mixing open source and money
Social psych jargon. Translated it means: "If you inherently like or want to do something..."
dhh cites Dan Ariely and Alfie Kohn, but no consensus
meta-analysis from 2014 - 4 decades, 180+studies, 200,000+ people
they say rewards increase motivation
"External, expected rewards diminish the intrinsic motivation of the fundraising open-source contributor. It risks transporting a community of peers into a transactional terminal. And that buyer-seller frame detracts from the magic that is peer-collaborators."
- David Heinemeier Hansson, The perils of mixing open source and money
are Ariely and Kohn wrong? not necessarily. social psychology is a troubled field. & I say this as a former social psychologist.
take social psych results as suggestions, not facts. but - they're great suggestions to provoke research and new approaches.
There's other research we could discuss but I cut it for time -- social psychology of open source collaboration BoF anyone?
in conclusion: I'm not saying shut down talk about social psychology. but don't let social psych shut down talk about money.
Fear of Corporations
I’ve already highlighted a number of open source projects supported by for-profit companies.
These efforts are not without their critics, and these critics are not without their reasons.
Fear that goals of companies and community will not align. That when there's conflict, companies will pursue their bottom lines.
And perhaps they will. But “for profit companies” are not a monolith, any more than “open source software” is.
Different ways that companies can interact with projects and if we can identify the beneficial ways than we can support them while discouraging others.
Are for-profit companies good or bad for open source?
What kinds of negative influences have they had? What kind of positive ones?
How do licensing decisions, governance structures or business models change their influence?
Does the company size, how the company was founded, or where the company was incorporated play a role?
What company behavior is unacceptable, and what's just annoying?
So scratch out the question “are companies good for open source?” It’s way too broad. Instead, I want to know...
Are for-profit companies good or bad for open source?
What kinds of negative influences have they had? What kind of positive ones?
How do licensing decisions, governance structures or business models change their influence?
Does the company size, how the company was founded, or where the company was incorporated play a role?
What company behavior is unacceptable, and what's just annoying?
Here's a quick case study: 2004 "open source" SugarCRM released. Quickly popular, lots of downloads, tens of mil in VC investment.
By 2011 company went "freemium", releasing paid proprietary versions. By 2014, they announced they were no longer supporting open source version.
So do we conclude companies are bad for open source? Company SuiteCRM forked the OS version and adopted a pay for hosting model. They seem to do a good job from this distant vantage point.
Perhaps instead the lesson to learn is that “freemium” open source business models leave projects more vulnerable than “hosting” open source business models.
Are for-profit companies good or bad for open source?
What kinds of negative influences have they had? What kind of positive ones?
How do licensing decisions, governance structures or business models change their influence?
Does the company size, how the company was founded, or where the company was incorporated play a role?
What company behavior is unacceptable, and what's just annoying?
There are a lot of stories to be told and lessons to be learned here, and I’m looking forward to that.
Bradley Kuhn’s talk on Thursday about “The Politics of Cooption in Open Source and Free Software”.
Another person: Karl Fogel of Open Tech Strategies. He posted a draft “Company Code of Conduct” for
people to use when dealing with new companies that want to contribute to an existing open source project.
Specific use case but great he’s identifying concrete behaviors that indicate real commitment.
Fear of Communism
In 2005, Bill Gates famously called FOSS activists "new modern-day sort of communists"
By textbook definition, this is ludicrous, but in American culture "communism" is a smear used to discourage forms of collective action.
Since many FOSS people lean libertarian, this makes it extra difficult to talk about.
But let's leap right in and talk about the role of state intervention.
In “The Entrepreneurial State”, Mariana Mazzucato challenges idea that business responsible for tech development.
Despite protests that gov't should "step back and let business innovate" the state has stepped forward to develop our most important technologies.
Figure 13. Origins of popular Apple products. Copied from The Entrepreneurial State –
Debunking Public vs. Private Sector Myths (p. 116), by M. Mazzucato, 2013, Anthem Press.
Take, for example, Apple’s success.
Just some of the relevant technologies. The US has also provided tax credits and other benefits to get businesses to adapt these technologies for commercial use.
Socialized risk, privatized profits.
Figure 13. Origins of popular Apple products. Copied from The Entrepreneurial State –
Debunking Public vs. Private Sector Myths (p. 116), by M. Mazzucato, 2013, Anthem Press.
Other technologies - internet and email (DARPA); Tor (onion routing invented at naval research lab, currently funded by various depts)
So US gov't already does a lot of funding. Can we more explicitly direct our tax dollars towards open source software?
Gov't offered up Federal Source Code Policy for public comment.
Federal gov't work is technically public domain but practically most of it is not accessible.
Draft policy also requires that 20% or more of third party software developed for gov't be open.
Official policy not enacted or even released yet, but pushing gov't to work more openyl is one vital thing we can do.
Another option is to seek direct public funding for OSS. The NSF, for instance, has funded a variety of grants for open source research.
Of course, governmental intervention isn’t the only way for people to act collectively.
Kelsey Gilmore-Innis gave a fantastic talk in January called "What Tech Workers Can Learn From Harry Bridges". There's so much there
that I don't have time to cover, so please, please check it out.
Tech workers as a group are in a rare position of power, one that we won’t have forever. If we act together, we could achieve a lot for ourselves, for other works, & for open source.
Just take a moment to dream with me here - what if employees demanded that they be able to release their code as open source, or a fee be paid by their employer to support the open source project of their choice?
Many other ways to act collectively besides government and unions.
I had a whole section about the tragedy of commons here, and how scholarship on how people manage
various kinds of resources can inspire how we manage our software commons. BoF anyone?
Summing up: every society has both protections for private interests and ways to encourage collective benefit.
Every individual has both competitive and collaborative instincts.
Advocating for altruism is not the first step on the road to a totalitarian state. It’s an embracing of the best parts of ourselves.
Tragedy of the Commons (cont)
Ostrom & Hess see information as a common-pool resource, rather than an "open access" resource (Lessig, Benkler).
Distinction? Exclusion.
Exclusion feels anathema in open source - but what ideas can we come up with?
Fair source license
Stronger membership organizations with greater benefits
Exclusion not on code use but on use of community time & labor
Next Steps
Getting to the end of the talk, so let's focus on specific steps.
To start off, we need to talk more openly and empathetically about money, in individual conversations and in our public discussions at conferences, in workplaces and online.
Why is it so important to talk about money? Because everyone views money differently. It's an age-old and familiar abstraction - but a super leaky one.
Assuming that a dollar to me equals a dollar to you can cause very real problems. Take an example with sliding scale.
Hadassah Damien of Ride Free: Fearless Money has a great post
explaining why and how to explain your sliding scale. They reference this explanation from Little Red Bird Botanicals.
Silence about money reinforces inequality. It's well documented that men get paid more than women and whites more than nearly every other racial and ethnic group.
Transparency won't fix everything, but it's a good step.
As long as talking about money is stigmatized, people will tend to discuss money only with close friends, who will tend to be in their demographic group, who will tend to be paid the same as them.
Remember, it's important to be empathetic. Many have good reason not to talk about money. This isn't about pushing people out of their comfort zone,
it's about changing what's comfortable for everyone.
What can you do?
Join my interview project: Free Culture in an Expensive World
Propose money-related talks, open spaces and BoFs at conferences
Write about money in free culture on your social media
Share the commentary of others
Find a person or two you feel comfortable with and start a conversation
Another thing I’d really love to see is investment in community infrastructure.
Infrastructure is the basic system which supports a community and allows it to function. Development
and improvement of infrastructure aids the entire community.
There are a few different kinds of technological infrastructure out there - for instance, package managers - and it needs our support. But we also need to support community infrastructure.
Community Infrastructure
Financial
Educational
Design, documentation, marketing, and more?
What if there was an organization that projects could turn to for financial advice for help applying to grants, running crowdfunding campaigns, getting non-profit status, or deciding between business models?
An open knowledge base, contributed to by many and maintained by a core team with expertise?
Many small projects get stuck in a position where they need money to buy time - but first, they need time to find money. This is one way to break that cycle.
Community Infrastructure
Financial
Educational
Design, documentation, marketing, and more?
There are other kinds of infrastructure I’d like to see supported too. Projects like Outreachy and OpenHatch bring new and diverse contributors into a wide variety of free and open source projects, but they can’t do it without support.
We talked before about areas that FOSS is historically weak in - design, documetnation, marketing, etc - which could be improved
by an org which works on specifying best practices for open source projects and providing consultation and advice.
Submit patches upstream
Advocate for classic social safety nets, for basic income, for living wages, or other ways to fight poverty and precarity
Solidarity with other workers & other people, especially in tech spaces - check out Silicon Valley Rising
Buy tech devices that don't harm human or natural resources
The open source community is far from the only one struggling with money, and the pressures we face are not entirely of our own making. I think it's important that we keep hacking on solutions from our end, but sometimes it's worth submitting a patch upstream – to the source of the problem.
In Summary
Ignoring money isn't an option. But neither is embracing the market without reservations.
There are many models for sustaining a project, but we're still struggling.
We're not competitive enough, not well-rounded enough, not diverse enough, not healthy enough.
We've got a lot of hangups: fear of money, fear of corporations, fear of being branded socialist or just too idealistic.
But we can move forward by talking about money, by supporting community infrastructure and by addressing financial issues in our societies at large.
How do we get the resources we need?
Together
I hope this wasn’t too much of a whirlwind for you all. I cut out a lot of relevant stuff but I wanted to leave as much as I could in, because I think it’s worth stressing the complexity and the enormity of this issue. We’re not going to get very far on our own - this is something we need to address together.
Luckily for us, we're not alone. Open source is all about working openly and collaboratively. Let’s apply our process and our values to this vital issue.
I said at the beginning of this talk that at its heart, our question is, “How do we get the resources we need?” There are a hundred different answers, none of them complete, but I'll tell you my favorite: we get them together.