4 ms·
Thanks for the clarification but that's pretty much what I just said. Not sure about this though: > "Open Source" is a development methodology. Development m
by c-smile 8y ago
Thanks for the clarification but that's pretty much what I just said.
Not sure about this though:
> "Open Source" is a development methodology.
Development methodology is one of these as far I understand:
https://www.synopsys.com/blogs/software-security/top-4-software-development-methodologies/ https://www.synopsys.com/blogs/software-security/top-4-softw...
In any case my question/suspicion still stands: far not all types of software projects are fit or benefit from being OpenSource.
- mindcrime 8y agoIn my experience, when most people talk about "software development methodologies" they mean something like "the kinds of things captured by labels like Scrum, XP, Crystal, RUP, AUP, waterfall, etc." In that sense, I wouldn't say that "open source" has traditionally been thought of as a "development methodology", but by the same token, I can see how it would be fair to refer to it that way. Maybe it would be better to say "open source is a development philosophy" or "open source is a development approach" or something, but I actually think it fits as a "development methodology" with the caveat that it's not just a development methodology. For a lot of people, (myself included) it's more of an ideology or even a way of life. Anyway, there are companies that actively talk about running projects as "internal open source" and in that sense, I would argue that referring to "open source" as a "development methodology" is reasonable.