2 ms·
I wrote "If that exists" because as you see in my first sentence, I agree with you - I don't think it exists at all. Instead, I'm pointing out that if there's
by eesmith 8y ago
I wrote "If that exists" because as you see in my first sentence, I agree with you - I don't think it exists at all.
Instead, I'm pointing out that if there's a social contract one way, which places expectations about what upstream must do for downstream, then it also must be read in a reciprocal way.
I called out to esr to emphasize that we're talking about "open source" and not "free software". Raymond is one of the group who decided to use that term in 1998, and one of its most ardent early proponents.
His writings include "Homesteading the Noosphere", where he talks about the gift economy of open source. Quoting http://www.catb.org/esr/writings/homesteading/homesteading/ http://www.catb.org/esr/writings/homesteading/homesteading/ :
> There are reasons general to every gift culture why peer repute (prestige) is worth playing for: ...
> Thirdly, if your gift economy is in contact with or intertwined with an exchange economy or a command hierarchy, your reputation may spill over and earn you higher status there.
This is an argument that open source gains reputation which gains "higher status" in an exchange economy. (Meaning 'control of things (not necessarily material things) to use or trade', including money.; quoting http://www.catb.org/esr/writings/homesteading/homesteading/ar01s06.html http://www.catb.org/esr/writings/homesteading/homesteading/a... )
Other examples of people suggesting that such a 'promise' exists are not hard to find. For example, "How contributing to open source can help you land your first job; Six compelling reasons why, warm fuzzy feelings aside, contributing to open source is good for your career." https://about.gitlab.com/2018/04/06/contribute-to-open-source-land-jobs/ https://about.gitlab.com/2018/04/06/contribute-to-open-sourc...
Stallman and the FSF's view of free software and the mechanisms for funding such are different than those expressed by the major open source proponents, so I don't consider it useful to point to the original GNU projects for a discussion of the implicit social contract described by open source proponents.
FWIW, my projects followed the free software path for nearly 10 years, until I could no longer support my (growing) family on the "incidental side effect commercialisation" of that movement.
- simonh 8y ago> Instead, I'm pointing out that if there's a social contract one way, which places expectations about what upstream must do for downstream, then it also must be read in a reciprocal way. I don't agree at all. That you reputation 'may spill over', or that contributing to open source 'can help you' is hardly the language of obligation. If you do want to impose obligations on downstream, it's grossly unfair and duplicitous to make them implied and unspoken. What sort of chance does that give downstream to understand what they're getting into? Put it in the license, up front.
- eesmith 8y agoI didn't use the term "obligation", I said "expectation". I was unsure what 'obligation' meant so I looked at https://en.wikipedia.org/wiki/Obligation https://en.wikipedia.org/wiki/Obligation . "An obligation is a course of action that someone is required to take, whether legal or moral." I did not say they were required, I said there were expectations of what is required. Raymond's paper makes explicit mention of some open source obligations, like his description of taboos like "There is strong social pressure against forking projects. It does not happen except under plea of dire necessity, with much public self-justification, and requires a renaming." (That this is no longer true highlights a weakness of his argument.) However, in reference to the text I quoted, neither I nor Raymond was saying that there is an obligation. Raymond's argument is that participating in the gift economy of open source development is more likely to lead to a higher status in an exchange economy than not participating. It is expectation of this increased propensity which was the implied social contract. Yes, you are absolutely right that "it's grossly unfair and duplicitous to make them implied and unspoken". However, some open source proponents - eg, in Raymond's paper - say that they exist, and as such they are making an assertation that there is a social contract when - as both you and I agree - there isn't. That's my point. Thus, arguments like AWS's "This was part of the promise the maintainer made when they gained developers’ trust to adopt the software. When the core open source software is completely open for anyone to use and contribute to, the maintainer (and anyone else) can and should be able to build proprietary software to generate revenue." are simply wrong because they depend on a social contract that doesn't exist. Where did the maintainer explicitly make the promise? Where did the maintainer demand that developers trust the maintainer? My point is that if AWS's implied social contract is meaningful, that social contract must be read both ways in the context of the cultural expectation. I'll note in passing that AWS's view rejects AGPL as being open source, as AGPL does not allow the construction of proprietary software for cases when "proprietary" means something other than "for internal use only".
- simonh 8y agoMaybe our positions aren't as far apart as I thought, but I do think you're stretching some of Raymond's quotes. Also not every open source pioneer sees things the same way. Bruce Perens is on record saying in his opinion forking is a fundemantal part of open source and healthy for the ecosystem, and has no sympathy for companies unable to make money off the back of it - https://www.theregister.co.uk/2019/03/12/aws_elasticsearch_distro/ https://www.theregister.co.uk/2019/03/12/aws_elasticsearch_d...