NASA Goes SourceForge
refactorator writes "We have a lift-off! The NASA Ames Research Center has open sourced Java PathFinder , a JVM that is an explicit state software model checker, all written in Java. For the first time, the complete master development site of a live NASA software engineering project is hosted on SourceForge. Read the official press release for details. The team around John Penix, Willem Visser, and Peter Mehlitz fought long and hard to get the development hosted outside of NASA, to enable true collaborative software development. Now show the government that it works - join the fray. May Java PathFinder boldly go where no NASA program has gone before." (Both Slashdot and SourceForge are part of VA Software.)
The bigger question for me is if the open source software is used and fails then where does the accountability lie? consider the stress that would be required for anything NASA does, and consider the results of even slight errors. now imagine the sort of bugs that crop up in other open source projects... this could be bad.
This app spiders through all routes of an app through the bytecode. Not only will this become a very stable and usable debugging application, but the applications that borrow from this application are endless with possibilities. For NASA to OS an app, this was probably the best choice!
Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
This can change things a lot. If the goverment sees open source work, imagine how many more projects(non security of course. Hell will freeze before those will be OS) will be opened up? Also, what about these OS authers? Do you think job offers might ever come to people? Is there a possibility that these Open Source Projects can change the way the Goverment operates?
What happenes if this project fails? Then what? OS will seem to be a failure then, and that would not be a good thing, at all.
All I can say is, this is one hell of a chance for OS.
Yay, I have a sig.
I worked under a programmer as part of a government contract and he said "everything we code is public domain, b/c we work for the govt." There are/were a few different classes of private contractors ones that worked on site and those that didn't. We worked on site and were often introduced as "government" to off-site contractors. But still I would think that the govt. could retain rights(ownership) to the code (and this would seem to support that). It'd be nice if the government open sourced all code it developed that wasn't necessarily "secret."
Recently, several large corporations, which (apart from other things) develop commercial software, released a number of projects on sourceforge.net. Among them were: Microsoft (3 projects), Google (4 projects), IBM (30 projects), Adobe (1 project). The reasons they gave for such move are often somewhat "foggy". My personal opinion is that it finally became "cool" to have a project on sourceforge.net, which is great of course.
- The freedom to run the program, for any purpose
- The freedom to study how the program works, and adapt it to your needs. Access to the source code is a precondition for this.
- The freedom to redistribute copies so you can help your neighbor.
- The freedom to improve the program, and release your improvements to the public, so that the whole community benefits. Access to the source code is a precondition for this.
From what I can tell, this is definitely a true Free Software license. However, you have to register with an agency of the United States government in order to muck with the code. Some may have a problem with this, be forewarned.Years ago (1980s) NASA used to have a repository called COSMIC that contained lots of code. It was mostly FORTRAN code for mathematical modeling or simulation of things like aerodyamics or heat transfer or stresses. A lot of it came from the Apollo program and some from Shuttle. When I did simulations for DOD systems we'd look there for code to reuse before we did our own as we felt if NASA was using it then it was verified and pretty tight in execution time.