Re:Openrsync imported into the tree
by StavrosK on Monday February 11, 2019 @09:25PM
(#19140475)
> Just because some forks of a project aren’t free, doesn’t mean that the project itself isn’t free
We aren't talking about non-free, we're talking about less-free.
> Just because some forks of a project aren’t free, doesn’t mean that the project itself isn’t free
No. The fact that there can be forks of the project that aren't open is what means that the project itself is less free than a project where all forks must be open.
> Especially if the project, like much of the e.g. MIT-licensed code in the world, is “done”
I don't consider this relevant to the argument at hand.
> then exactly what is the point of choosing the latter over the former?
Are you asking me what the point is of making something you don't want people to do hard for them vs making it easy?
We aren't talking about non-free, we're talking about less-free.
> Just because some forks of a project aren’t free, doesn’t mean that the project itself isn’t free
No. The fact that there can be forks of the project that aren't open is what means that the project itself is less free than a project where all forks must be open.
> Especially if the project, like much of the e.g. MIT-licensed code in the world, is “done”
I don't consider this relevant to the argument at hand.
> then exactly what is the point of choosing the latter over the former?
Are you asking me what the point is of making something you don't want people to do hard for them vs making it easy?