Government Funds Secret Sustainable Computing
SEWilco writes "OSDN's NewsForge reports that Carnegie Mellon University has started a Sustainable Computing Consortium to improve the quality and security of software.
The only news release is that NASA gave CMU $23 million to help create dependable software.
SCC members get an internal-use license for SCC software. So taxpayers are paying millions to create proprietary software, and companies get access for a few thousand dollars.
(There is some blurring between CMU's SCC and CMU's High Dependability Computing Consortium, although HDCC's web site has been idle for a year.)"
Non-classified government funded software should be Free for public use, I guess is the point here. Are there any ongoing lobbying efforts to this effect?
I don't understand the title of this article. What's "secret" about this?
Propriatary, yes, and perhaps it's wrong for the gov. to turn our tax money into a Microsoft product (but of course, the government gives billions in tax rebates, subsidised loans, etc. to EVERY american business), but there is definitly nothing secret about this.
Stop the FUD!
>>So taxpayers are paying millions to create proprietary software, and companies get access for a few thousand dollars.
I hope this is not trollish, but there has been a lot of this going around for quite some time; indeed, it's how the world works in the domestic USA. Pharmaceutical (sp?) funding gets Gov. grants for the coarse, laborious, and often empty research, and then hands over any promising results for free to Merck and others for development into actual drugs. Universities do lots of basic research that then, when promising, can be used by manufacturers, and if classified will even be denied to you and I.
Now you can argue that these results help fuel the economy, but you can also argue that the marketplace should be charging for the information developed at the expense of the funders.
Hey, it's only our money. What's on TV?
If the software is written using public funds (i.e. my tax dollars are paying for this), then the resulting software should be publically available. Either under a GPL type license or under a BSD sytle license (with a BSD license, then even companies could incorporate the publically funded technology into their products to sell, sorta giving them something back for their tax dollars). Either way, if we paid [taxes] for it, then it should be available to us.
Maybe we could get a bill passed that states all software not written for national security that is paid for by taxes should be open to the tax payers. Just a thought.
To rehash what appears to be a popular theme around these parts... I just don't see how one can excuse the use of public money for projects that only select private parties can benifit from. Granted, this project is likely to benifit NASA in that it could help them provide better mission-critical systems for the space station, future spacecraft, and so on... but I still feel that taxpayers should not be made to pay to help develop a product that targets them as consumers, a project with a licensing scheme that would make it anything but available to the general taxpaying public.
These are, perhaps, the kinds of things that we need better government accounting regulations to keep track of.
stuff from the FSF is still around in a few decades, and their stuff has been completely rewritten 100 times?
Maybe then they'll realize what sustainable means...
nahh....
This is left as an exercise for the reader.
So NASA needs some Sustainable Computing and they spent $23million of their budget to get it. Where is the problem here?
Is this trying to imply that all NASA software should be free?
Hmmm, didn't Microsoft go on record that they supported taxpayer funded research being freely available provided it would not be encumbered by the GPL?
Or would that just have been a divide and conquer approach to make sure the free software camps keep fighting each other rather than joining forces?
I personally shudder at the thought that taxpayer money should go to subsidizing software hoarding (and that's any taxpayer money, not just US).
Oh well. This won't impact open software one way of the other until patents get thrown into the mix. Closed source has never hurt open source.
Bert Driehuis -- All I asked was a friggin' rotatin' chair. Throw me a bone here, people.
That is currently reviewing Carnegie Mellon's restricted research policy. I'll bring this up. Just so that you all know, this research must be with one of CMU's "semi-autonomous units," and no students are participating in the research, otherwise it could not have cleared our Provost. At any rate, this is interesting information to have.
Ceci n'est pas un post