Comment by layer8
17 hours ago
That’s just incorrect. “Open source” can mean the licensing as well as the development model [0]. It certainly has been associated with the development model since The Cathedral and the Bazaar [1].
[0] https://en.wikipedia.org/wiki/Open-source_software_developme...
[1] https://en.wikipedia.org/wiki/The_Cathedral_and_the_Bazaar
> “Open source” can mean
Keyword being "can"
The Wikipedia page you linked to refers to "Open-source software development (OSSD)" which implies that it's a different concept than "open source" by itself
You and Bigstrat2003 are arguing a technicality, and you're technically correct, but in context I think that's somewhat beside the point. Skrebbel and Layer8 are focused on the cultural associations of "open source" development, and this mismatch is causing everyone to talk past each other.
The original post in this thread was:
> This is because Carmack doesn't really do OSS, he just does code dumps and tacks on a license ("a gift"). That's of course great and awesome and super nice, but he's not been painstakingly and thanklessly maintaining some key linux component for the last 20 years or something like that. It's an entirely different thing; he made a thing, sold it, and then when he couldn't sell more of it, gave it away. That's nice! But it's not what most people who are deep into open source mean by the term.
Skrebbel probably shouldn't have said that Carmack "doesn't really do OSS", but what they clearly meant was, Carmack doesn't participate in the sort of community development as the Linux kernel or Apache or whatever.
More succinctly, Carmack only contributes his code to OSS, but not his time, and shouldn't impose his values on the wider community that contribute both.
> technically correct, but in context I think that's somewhat beside the point
Talking past people to argue on semantics and pedantry is a HN pastime. It may even be it's primary function.
8 replies →
I’m saying that “open source” can mean both things. The parent was arguing that it only means the licensing. I’m not arguing that it always means the development model.
> The Wikipedia page you linked to refers to "Open-source software development (OSSD)" which implies that it's a different concept than "open source" by itself
By that logic, “open source licensing” would also imply a different concept than “open source” by itself.
Note that the Wikipedia page for “open-source software” [2] states: “Open-source software is a prominent example of open collaboration, meaning any capable user is able to participate online in development, making the number of possible contributors indefinite”. That would really only be the case in the context of open-source development.
[2] https://en.wikipedia.org/wiki/Open-source_software
> By that logic, “open source licensing” would also imply a different concept than “open source” by itself.
It does
1 reply →
Isn't Carmack just employing the 'Cathedral' type of 'Open Source'?
The “cathedral” model refers to closed-source development: https://en.wikipedia.org/wiki/Open-source_software_developme...
"The cathedral" was originally GNU and GCC. (raymond's site is super slow.)
Appending ‘development’ seems like a significant departure from ‘vanilla’ “Open Source” to me, and wouldn’t all development be ‘closed-source’ at least between commits, if not between pull requests?
6 replies →
> In closed-source software development, the programmers are often spending a lot of time dealing with and creating bug reports, as well as handling feature requests. This time is spent on creating and prioritizing further development plans. This leads to part of the development team spending a lot of time on these issues, and not on the actual development.
So, in closed source you work on bug reports and feature requests. In open source you work on development. But it's the closed source people working on building a cathedral.
I understand what they're driving at, but this is still the stupidest description of the analogy that I've ever seen.
The "development model" of open source is that one person code dumps, another takes, changes it then dumps it, another picks up the copy with the changes, changes it again, and so on. Sometimes it finds it's way back.
A bazaar is a chaotic market with a million vendors, not anything remotely cooperative. The Cathedral and the Bazaar is meant to convey the idea that OSS code develops without central organization, through endless forking and cloning.
The bazaar model definitely isn't the cooperation and vibes model that the HN crowd thinks it is...
Have you read the essay? http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral...
In it, the bazaar is a metaphor for how Linux was being developed.
Yes. Here's a relevant excerpt:
> No quiet, reverent cathedral-building here — rather, the Linux community seemed to resemble a great babbling bazaar of differing agendas and approaches (aptly symbolized by the Linux archive sites, which would take submissions from anyone) out of which a coherent and stable system could seemingly emerge only by a succession of miracles. The fact that this bazaar style seemed to work, and work well, came as a distinct shock. As I learned my way around, I worked hard not just at individual projects, but also at trying to understand why the Linux world not only didn’t fly apart in confusion but seemed to go from strength to strength at a speed barely imaginable to cathedral-builders.
1 reply →
"Open source" means the source code is open to the public for reading and copying. Licenses have complicated the idealistic definition to restrict copying, but that is only within the context of taking credit (ie implicit relicensure). The only winning move is not to play the game at all.