6 ms·
I 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://
by eesmith 8y ago
I 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...
- eesmith 8y agoJust to check - you think that Bruce Perens, author of the Debian Social Contract, didn't think there was an existing, albeit ill-defined, implicit and non-universal, social contract for free software projects before he wrote that document? My comments here concern the advocacy from when open source was new, so pointing to Perens' comment from a few days ago doesn't provide insight to what he thought 20 years previous. I'm sure if you ask Raymond about forks now, his answer would be different than it was in 1998. My observation is that his analysis then was flawed because it made a specific prediction about preventing forking. Things can be influential even if flawed, so confirming that there is a flaw doesn't mean it wasn't influential.