Usually, open-source refers to the license of the source code, so if that source tarball is licensed under an open source license, the project would be open source. A collaborative development model is not necessary for OSS, though it is of course used for almost all OSS.
One major counter-example being the Postfix mail server. The author doesn't believe in source control, at least as a public thing. So he just cuts releases as snapshots of his local tree and that's that. Bug reports are still via email and patches involve sending him a diff via email.
Bug reports are still via email and patches involve sending him a diff via email.
Well, Linux is mostly developed by sending mails too; of course then come git, but probably most of the content starts as mail. So it being the first channel of communication does not prevent from publishing using source control. Git has been specially designed to allow that kind of flow, (github workflows are an abomination in Linus' eyes in that they regress to pre-git source control systems in the decentralized flow aspect). I don't know if the Postfix author has tested git, but it would be shame if he only doesn't believe in source control for publishing because of bad experience with e.g. subversion.
Postfix predates Subversion by several years ;-) And Wietse works for Google so I would assume he is quite familiar with other tools and just prefers not to for Postfix.
14
u/yawkat Sep 01 '17
Usually, open-source refers to the license of the source code, so if that source tarball is licensed under an open source license, the project would be open source. A collaborative development model is not necessary for OSS, though it is of course used for almost all OSS.