3 ms·
The OSI doesn't get to own the definition of open source regardless if they were involved in the initial usage of it. It is clear we mean different things as w
by colechristensen 8y ago
The OSI doesn't get to own the definition of open source regardless if they were involved in the initial usage of it. It is clear we mean different things as we use term and arguing about what it should mean is pointless.
Patents and "open source" (whatever your definition) share some goals. Specifically, to get design details published in a way accessible to the public. Both patents and OSI Open Source restrict freedoms, but in different ways.
- kragen 8y agoThe OSI has had to deal with charlatans attempting to co-opt the term "open source" since its inception, using dishonest arguments like the one you are deploying here; this is no different from trying to sell water with chalk dust as "milk" or gold-plated tungsten as "gold". It is possible that what you are doing falls within the ambit of US federal fraud statutes, depending on whether you are in a position to receive money for it. However, the Hacker News readershp is savvy enough to understand the difference; here, you have failed and you will continue to fail. Aside from the issue of passing off whatever sad scam you're wanting to pass off as "open source" in order to take advantage of the goodwill earned by genuine open source, it is entirely and transparently false to claim that "OSI Open Source restrict[s] freedoms." Copyright, patent, and trade secret laws restrict freedoms; open source just gives some of them back.
- colechristensen 8y agoYour reply is ridiculous and not what I would expect to find on HN.
- antidesitter 8y agokragen’s comment went over the line, but he’s correct in saying that “open source” has a well-established meaning: https://en.wikipedia.org/wiki/Open-source_software https://en.wikipedia.org/wiki/Open-source_software
- gpm 8y agoAssuming your interpretation of the law is right (and I do not think it is even close to being so), this comment comes very close to accusing the person you are replying to of committing a crime. Hopefully you didn't mean it that way, and the phrasing was an accident, but I honestly can't tell.
- samatman 8y ago> Copyright, patent, and trade secret laws restrict freedoms; open source just gives some of them back. I can't say this is 100% true. OSI licenses divide into two camps, usually called "permissive" and "copyleft". Even permissive licenses usually restrict the freedom to publish the source without the author's name, which is, while trivial, a restriction nonetheless. But copyleft licenses restrict the ability to modify the source without publishing your modifications. This is indeed a significant restriction of freedom, and why the BSD/MIT/etc camp are called "permissive", because copyleft is less permissive. I prefer the permissive licenses for this very reason, although I'm not opposed to using or contributing to GPL-licensed code. Now, you may say that the freedom hereby restricted is justly restricted, as we justly restrict the freedom to, say, put chalk in milk. I find it more consistent to reject the restrictions of copyright entirely rather than exploit them to force sharing; after all, the only way to use the clause in GPL requiring source sharing is to pursue satisfaction through the court system. One thing on which I'm sure we can agree: both of these camps are producing open source software, and 'source available' is an entirely separate state of affairs which cannot be included.
- kragen 8y agoCopyright laws are what restrict the freedom to publish the source without the author's name or to copy or modify the source. Open-source licenses give some of those freedoms back, but, in some cases, not all of them.
- landryraccoon 8y ago> It is clear we mean different things as we use term and arguing about what it should mean is pointless. I strongly disagree with this. Open source is a commonly used term; if there is disagreement in it's meaning then that issue has to be resolved first, otherwise what are you even discussing? If you wish to take your attitude IMO you either have to first demonstrate that your definition of "Open Source" is either the one that should be used, or avoid using the term entirely and talk on neutral terms. You are attempting to claim that it's possible to have a neutral position on "open source" when your own position is in fact highly opinionated. Commenters are absolutely right to question whether your definition is appropriate or not.
- colechristensen 8y agoSource is obvious, what does the adjective open mean? >Allowing access, passage, or a view through an empty space; not closed or blocked. >exposed to the air or to view; not covered. "an open fire burned in the grate" >having no enclosing or confining barrier : accessible on all or nearly all sides >not restricted to a particular group or category of participants "open source" taken literally only means that the source code is available to view. The adjective open doesn't seem to lend itself to anything more than that. Getting back to the original point I was trying to make instead of unproductive defining, an original purpose of patents was to OPEN design specifications for inventions to the public instead of everything being kept as closely protected corporate secrets.
- landryraccoon 8y ago> Source is obvious, what does the adjective open mean? > "open source" taken literally only means that the source code is available to view Why is the literal meaning relevant? Language doesn't work that way. Do shitstorms have to refer to literal fecal weather patterns? Hackernews is frequented by professional software engineers and "Open Source" is a commonly used term in that industry. Using the dictionary definition of the words composing that terms is irrelevant. What is relevant is how the term is commonly employed in industry. Your approach only makes sense if we are talking about some sort of newly coined phrase. Open Source software has existed in industry for decades and has an understood meaning. Generally speaking, a professional software engineer will refer to something as Open Source if the source code can be both read and reused in some context. If you believe that in the tech industry it is commonly used by professionals in a different way I'd like to hear your evidence.