Slashdot Log In
Navy Commissions Open Source R&D
Posted by
Zonk
on Fri Mar 25, 2005 10:27 PM
from the penguins-with-pips dept.
from the penguins-with-pips dept.
Lin_Matt writes "OSSI has announced a three year Cooperative Research and Development Agreement (CRADA) with the U.S. Navy to explore and expand the usage of Open Source Software. Barry Duplantis of Red Hat will be serving as the Program Manager for this CRADA which will cover the Navy's use of OSS within the Naval Oceanographic Office's Web services, scientific computing and enterprise architecture systems."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
OSS to the rescue (Score:5, Funny)
Re:OSS to the rescue (Score:3, Funny)
BSD is diving.
An interesting anecdote (Score:5, Interesting)
Re:An interesting anecdote (Score:2, Funny)
Re:An interesting anecdote (Score:2)
Re:An interesting anecdote (Score:2, Insightful)
Yeah, I can just see the smiles on the soldiers faces when they go to fire their smart weapon, and the bullet needs authenticating because they replaced the firing pin earlier that day...
Re:An interesting anecdote (Score:3, Interesting)
The Windows based systems are presumably the same sort of computers the soldiers use at home, no wonder they are more familiar and easier. Stick Linux on those computers and order people to use it.
Re:An interesting anecdote (Score:2)
Maybe it wasn't the Unix (Score:2)
It may be that the applications written for the UNIX boxes were the problem. Windows doesn't have a monopoly on poorly written applications. If a application uses a lot of the memory and dives into a memory hogging infinite loop, it isn't pretty, whether it is a Windows box or UNIX box.
It could possibly be the hardware itself. The military often has their computers in places that aren't the most hardware-fri
ethics (Score:4, Insightful)
Re:ethics (Score:2)
Besides, t
Re:ethics (Score:2)
No, because
(1) assassination guilds are illegal, and so ignore copyright law
(2) The purpose of the military is to defend or sieze land, not kill people. (Military strategy holds that wounding is generally preferrable to killing--makes the casualty more of a drain for the other side.)
(3) Amending the GPL couldn't do that much; either you'd have to make an incompatbile fork, or yo
Re:ethics (Score:2)
Please back up your "facts". So far the estimates that the US armed forces directly contributed/caused more than 100,000 deaths in Iraq alone (since invasion)http://politics.slashdot.org/article.pl? s id=04/10/29/138232&tid=103&tid=219 [slashdot.org]
The amount of deaths caused directly (bombing) or indirectly in 1990s is unknown. If US took care of Saddam back in 1990,
Re:ethics (Score:2)
I prefer Theo de Raadt's hypothetical baby mulching machines [neohapsis.com].
Re:ethics (Score:2)
http://www.htmlbible.com/abortstats.htm
http:/
More people have been killed in fighting over land than in the name of that "stupid Christian god". That doesn't make land evil, but by your implications, we should abolish all land.
Re:ethics (Score:2)
neither did the workers at Auschwitz, eh?
It's easy to de-humanize, isn't it. It's usually the first step in justifying murder.
Re:ethics (Score:2)
Re:ethics (Score:2)
Do you really believe that your experiences and relationships are all that makes you more than just a "mass of cells"?
Do you even know when neural activity develops in people? 45 days, dude.
At 8 weeks in the womb you were completely formed: all of your organs were functioning, you even urinated and had finger prints. At this age you felt pain (you would have moved away from a needle had it been inserted at this point), you kicked, moved your feet, toes and fingers, and even made a strong fi
Re:ethics (Score:2)
And if the bum beneath the bridge doesn't think, nor remember his past, nor has friends nor dreams, don't bother 'aborting' him, he'
Re:ethics (Score:2)
Personally, I am not "pro-life". I am "pro-choice", but there should be consequences for getting abortions. I mean, if people are stupid enough to get/cause pregnancy and do not *want* the child (ie. not a medical reason), then they should be able to get an abortion. Then you sterilize them so they will not make the mistake again.
Is this is a fair compromise for "your side"?
PS. Many "workers" in Au
Re:ethics (Score:2)
Is this is a fair compromise for "your side"?
Not quite. It still results in a life being ended with no wrong done on their part, and them having no say in the matter. That is
Re:ethics (Score:2)
Good to hear (Score:3, Insightful)
CRADAs (Score:5, Interesting)
I came in at the last part of one CRADA were we deveolped a new way of doing geologic testing. By the time the finalists had been selected we began testing, running qual/quant analysis on the data, and made improvements to increase productivity. The product was offered almost immediately for private work. That was the great promise of the CRADA; faster time to market for high frontier scientific advances.
It has been 12 years since that CRADA was completed and the technology is just now beginning to adapt to the demands that the orignal development agreement envisioned. While the time to commercialize the product outside has been slow, we did use the technology for selected drilling projects.
The second one started about when the last one ended. We are just now (10 years later) getting to the field with our other remote sensing projects. And as in the case of the drilling CRADA, the only customer at this point is the federal government.
Which brings up an interesting question: "Would the development happen faster or slower without the government involvement?" I think the getting the govenment involved just muddies the water. The only benefit to government agencies from a CRADA is the intellectual property aspects. But if you only had only one customer in the world, would you make your IP an issue, or you you just quote a price?
Know what I mean?
That's right folks (Score:2, Informative)
Just like NT did with a naval destroyer a few years back.
Linux has just reached at the very least the NT level of complexity.
Cruiser, Not Destroyer (Score:2)
Re:That's right folks (Score:2)
I guess I really screwed up the joke if you took it that seriously.
I apologize to the entire slashdot community.
I will keep my day job.
Re:That's right folks (Score:2)
Instead it is getting modded as Insightful.
Oh, bother.
Navy's been doing great for a while (Score:5, Informative)
For instance, the Navy's Proteanforge [navy.mil] is fantastic on so many levels it's not even funny. Besides being one of the few public Sourceforge deployements outside of sf.net, the code there is just wildly interesting, and has been for several years now.
Not to mention the funding the Navy put into Onion Routing Research [onion-router.net] and it's very popular implementation [eff.org].
Nothing new, but a really big step (Score:5, Insightful)
Just a little background info first. I was stationed as Naval Air Station Meridian as the air wing's network administrator for 3-1/2 yrs starting in 2001. (I was also an instructor for the jet program.) So, my comments are from direct, personal experience.
Things have probably changed in the last year since I left, I'm sure, but a little perspective might be in order.
While I was there, I did software development for personal interest, fun, and the thrill of making something that would help everyone. No glory, no money, just because I enjoyed it. I also did some development for some Coalition projects for multinational forces, basically because they needed it and no one else had anything that was even close to being finished ("close" meaning a beta version in less than a year.) I've used a lot of different OSS, but my own personal favorites were Java or Java+Tomcat. (Go ahead and email me directly if you want to criticise those choices; I can take it.)
During my tenure, internal software development was on the run. The NMCI project (Google for "EDS" and "NMCI" and you'll find out plenty) worked to specifically kill any applications that weren't "approved." There were legitimate reasons for this, but the end result was that practically only MS and MS-compatible products were allowed...bad news for anyone who wanted to write software.
One of the reasons I left (amongst many, none bitter) was that I enjoyed working with software but knew that I would have absolutely no future in it if I stayed in. Glad to find out I was wrong.
It's a very small step, but to have it officially announced that OSS is being used for a project shows that someone, somewhere, is paying attention to the (God forgive me for using this term...personally, I hate it) changes in "paradigms" about how software is developed, used, and implemented.
I like to program; I know dozens of other military guys/gals who also like it. It's good to see that they may have a future that allows them to do some good and enjoy it.
The navy and OSS (Score:5, Informative)
Since then, I've discovered that they've been involved in multicasting, network testing suites and a whole bunch of other stuff. They've a site based on the Sourceforge software for developing such projects, called ProteanForge [navy.mil].
So far, so good. They're obviously into Open Source in a big way. Despite the fears of some posters, this has not caused the end of the world. Yet, anyway.
Two drawbacks, though. They may be good coders - and they are! - but they are LOUSY at keeping projects going and even worse at posting news items. The last news posting is dated November 14, 2003. Ok, sure, they might have decided to put their efforts elsewhere. That happens. So why not hand the code over to someone else? The stuff isn't classified, it's Open Source, why not keep the good stuff alive?
Make that three things. They're lousy at letting anyone know they ARE doing Open Source work. I happen to keep a close eye on groups I know are involved in Open Source, but I only found out about the newer projects relatively recently and I'm damn sure that most people don't know about them at all.
(Well, up until this post on Slashdot, anyway.)
True, nothing is "owed", but this isn't about owing. This is about establishing yourself as a credible source, thereby not only increasing the interest of coders who might be of value, but also enhancing the testing of these products, and finally establishing a rapport with a sector of the IT industry that has become wary of Government involvement.
It wasn't so long ago that IBM was the "Evil IT Baron". These days, their relationship has mellowed, their older product lines have a new lease of life, their reputation has recovered and they've even made some impressive strides into the extreme high-performance computing world.
This is where the US Navy could have been, seven or eight years ago. They were already releasing Open Source products then, and may well have been years earlier. Instead, their Open Source products are shrouded in secrecy, even though they're plastered over the Internet and GPLed/BSDed to boot! Instead of learning from their own experiences, they are pulling away.
Yes, I find that annoying. There are some damn good projects out there, that they're letting rot for no reason at all. (Like I said, even if they didn't want to maintain them, they could always hand them to someone else. As IBM did recently, for example.)
It's good that the Navy is now starting to back Open Source R&D, but I will only believe that they understand what that means when I see some real understanding from them over what they already have.
Oh lovely...... (Score:5, Insightful)
Bottom line (from the book anyway): the Navy is an insular community of officious, small minded, power hungry folks who value a project on two things: How many men will I command, and how much does it cost? Bigger, high budget projects obviously mean better projects.
Doing things cheaper, better, faster, and more efficiently doesn't seem to be the Navy way. I'd like to be wrong, but i seriously doubt I will be. The Navy was born to use NT 4.0.
Real Products in the Fleet (Score:4, Interesting)
Already in use? (Score:4, Informative)
zerg (Score:2)
Re:Uhh, so? (Score:2, Interesting)
Re:What happens when (Score:3, Interesting)
Re:What happens when (Score:3, Interesting)
Re:redhat is only better (Score:2, Funny)
Re:Just curious (Score:2)
Re:Just curious (Score:2)
That's not the biggest reason (Score:3)
Granted, sometimes this isn't possible (e.g. national security), but it ought to be factored into the cost/benefit analysis.
Re:That's not the biggest reason (Score:2, Insightful)
Re:That's not the biggest reason (Score:2)
Re:Just curious (Score:2)
Have you looked at Red Hat pricing lately?
Re:Just curious (Score:2, Insightful)
Re:Just curious (Score:2)
Re:NMCI ? (Score:2)
Re:NMCI ? (Score:5, Insightful)
Not EDS, the contractor that trashed 60,000 MSFT
computers at Britain's Health Services earlier
this year?
Not EDS, the contractor that is nearly 2 years
behind schedule in the deployment of new MSFT
servers and desktops to the US Marine Corps?
I cannot help but wonder if these problems are
what has led up to this OSS initiative. Glad
to see that the US military is not quite as
pig-headed as the DHS (Dept. of Homeland Security)
who have spent/committed over $6 Billion USD
(multi-year contract) for MSFT's products as the
basis for their unified IT infrastructure.
Parent
Re:nice work (Score:2)