That being said, the Free Software movement was obviosly seminal in all of the open data talk, and for that matter open patent talk; it's not the same thing, but a strong and heavily influential idea in one context inspires analogues in other contexts. I think your overall point is wrong, although I think your supporting point is completely correct.
My argument is that that analogy doesn't follow from free software principles.
If it did, then it would follow that if you publish the paper, you're obligated to release your source.
And we don't see that coming out of the free software movement. We do see that coming out of the open data/open science movement.
If you publish your software, you are required to release everything needed to develop it further, yes.
However, if you publish your paper, you are not required, under the free software principles.
If I am wrong, show me where the FSF/GNU say that.
I believe your argument is that there's a clear parallel to publishing a paper and publishing the software.
However, there's also a clear parallel to, say, publishing an internet service based on free software, and publishing the software. This lead to the AGPL.
The GPL does not have that requirement, which means it isn't a free software principle. It could have - I think I've heard Eben Moglen say it was discussed early on. But if so, then having a telnet server, or ftp server, or anything reacting to the network, would require the ability to download the source.
> free software people have been working out these "reproducibility" issues in practice for decades before the biologists even got on the bus.
While biologists were working out other "reproducibility" issues long before there were buses.
Consider #1: I think of an improvement to gcc. I get a copy of the gcc source, modify it, and prove to my satisfaction that it works.
I stop at that point, intellectually satiated, tell a few friends, and don't release any software (source or binary).
The principles of free software say that I am not forced to release any changes. I am not even obligated to send improvements upstream.
Am I wrong about this?
Consider #2: The same as above, but I know that Yoyodyne could save $1 million per year with my improvements. I don't tell them. The free software principles say that I have no obligation to tell them.
Am I wrong about this?
Consider #3: The same as above, but I go to Yoyodyne and say that I'll sell my gcc modification to them - under the GPL - for $250,000. They of course can then redistribute those changes, including back to mainline.
Is that contrary to any free software principle? I don't think so, according to my years of reading the history of the FSF and the free software movement.
But, suppose you are correct, and Stallman's essay only applies to "the service of duplicating and mailing tapes pre-Internet". If so, there's a simple workaround:
Consider #4: I have the idea, implement it, and distribute it to a single organization - a tape duplicating service - and it's that organization which sells the software to Yoyodyne, for $300,000, of which $250,000 comes back to me. (My brother just happens to run the tape service.)
Is that against the principles of free software, and if so, how?
I don't think Stallman's "selling free software" essay was meant to be so easy to work around.
Just because free software is generally distributed at no price or "reasonable cost of physically performing this conveying of source" (quoting GPLv3), doesn't make it the same as saying that there's an free software principle which obligates that.
While the open data movement in science does have the principle that the data should be free, or should only cover the "reasonable cost of physically performing this conveying of" data.
How am I off base?