Slashdot Mirror


NASA Report Advocates Switch to Open Source

vortimax writes "A new technical report from the NASA Ames Research Center advocates the adoption of Open Source Software internally by NASA for some projects. The paper also proposes modifications to NASA's "external software release" policies to allow OSS and proposes the use of the Mozilla Public License as the license of choice for NASA software."

263 comments

  1. NASA by Anonymous Coward · · Score: 3, Funny

    Will it help their aim at Mars?

    1. Re:NASA by Anonymous Coward · · Score: 0

      Will it help their aim at Mars?
      It would help if NASA's suppliers understand the difference between pounds and newtons. Someone was asleep at the wheel that year.

    2. Re:NASA by Anonymous Coward · · Score: 0, Funny

      Yea, and what about open sores on Uranus?

    3. Re:NASA by daveatwork · · Score: 1

      GEEEEENIOOOOUS!!!! well done!! hehe, i lurve Uranus jokes :-)

    4. Re:NASA by shaitand · · Score: 1

      Actually according to copyright law anything NASA produces is public domain. According to the freedom of information act anything non classified produced by NASA has to be turned over if requested... perhaps we should request a bit more source from NASA before they implement open source licensing that could never be as open as public domain?

  2. "Because we can't screw up much worse." by Anonymous Coward · · Score: 0

    Open source has fewer bugs, right?

    1. Re:"Because we can't screw up much worse." by zakezuke · · Score: 3, Insightful

      It's not the fact that open source has fewer bugs.

      Open source has the advantage of being able to be picked through with a fine tooth comb, and bugs can be resolved by onsite or offsite staff.

      Imagine if the geek community had the ability to actually test Nasa software, simulations, flight plans. Some guy in Nambia might discover a bug that could save a mission. While Nasa has a trained staff of people... it is no match the joint effort of thousands, or millions of people.
      While it's almosts assured that nasa has machines that *whips the llamas* ass, it no were matches the joint computing power of the planet earth.

      --
      There is no sanctuary. There is no sanctuary. SHUT UP! There is no shut up. There is no shut up.
    2. Re:"Because we can't screw up much worse." by infinite9 · · Score: 1

      Some guy in Nambla might discover a bug that could save a mission.

      I didn't realize the National Marlon Brando Look-alike Association had that many geeks.

      --
      Disconnect your television. Do your own research. Draw your own conclusions. They're probably lying. Don't be a sheep.
  3. MPL? by Anonymous Coward · · Score: 0, Interesting

    Can someone give a short plain English summary of the differences between the Mozilla license and the most popular ones (GPL, LGPL, BSD)? I am afraid diff'ing the legalese is not my strong suit.

    1. Re:MPL? by Bigby · · Score: 3, Informative

      If you just cast a magical spell "gpl mpl bsd apache" on google.com, you get:

      http://www.linuxworld.com/linuxworld/expo/lw-thurs day-copyright.html
    2. Re:MPL? by 0x0d0a · · Score: 2, Informative

      Try this page.

  4. International Collaboration by Ikeya · · Score: 5, Interesting

    It's good to see this kinda thing start to happen. I feel that space exploration is humanity's job as a whole. What a great way to promote all humanity contributing to the space exploration effort than by contributing source code. Granted, I know this doesn't mean it's all gonna be done open source-like, but hey, it's still cool and in a way, allows everyone to participate.

    ikeya

    --
    ---- Move SIG...For great justice!
    1. Re:International Collaboration by Anonymous Coward · · Score: 0, Flamebait

      Are you really that stupid? Do you really envision NASA saying "Hey everybody, lets get together with some pizza and beer and hammer out some shuttle code"

      You really are not that stupid, are you?

    2. Re:International Collaboration by Anonymous Coward · · Score: 0

      Why not?

      Apart from the pizza, of course....

    3. Re:International Collaboration by jafac · · Score: 3, Funny

      . . . because you sure as hell can't find decent pizza in either Cocoa Beach, Houston, OR Pasadena. . .

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    4. Re:International Collaboration by Dan-DAFC · · Score: 1

      This article about how NASA develops software for the shuttle makes for interesting reading. It's a whole different world to the way most commercial (and open source software) is developed.

      --
      Suck figs.
    5. Re:International Collaboration by Anonymous Coward · · Score: 0

      Not true... Excellent pizza in Houston can be found at Napoli's... Several locations...

    6. Re:International Collaboration by TedTschopp · · Score: 1

      I don't think you know what you are talking about.

      There are several amazing places to get Pizza in Pasadena.

      Ted

      --
      Fantasy remains a human right; we make in our measure and in our derivative mode... -- JRR Tolkien
  5. Asking for trouble.... by freeze128 · · Score: 3, Funny

    Just make sure that all of your coders are using the same measurment system.

    1. Re:Asking for trouble.... by ElectricRook · · Score: 1, Offtopic

      You actually believe the published results of a government accident report?

      --
      - High Tech workers, please say NO to Union Carpenters, their Union sees fit to control our compensation.
    2. Re:Asking for trouble.... by Anonymous Coward · · Score: 0

      YOU FAILURE!!! You actually buy in to that government conspiracy crap?

    3. Re:Asking for trouble.... by Anonymous Coward · · Score: 0

      I do not believe in any of these conspiracy theory. For there to be a conspiracy, the two main requirements are organization and intelligence. As these qualities tend to be lacking at the government level, conspiracy is rather unlikely.

    4. Re:Asking for trouble.... by lightspawn · · Score: 2, Insightful

      Just make sure that all of your coders are using the same measurment system.

      Or write a class that has both .value and .unit members, and math functions that perform conversions whenever necessary.

    5. Re:Asking for trouble.... by Jugalator · · Score: 1

      You actually believe the published results of a government accident report?

      No, it's probably a lie to hide an even more stupid mistake than using the wrong units. Like... uhh...

      --
      Beware: In C++, your friends can see your privates!
    6. Re:Asking for trouble.... by Anonymous Coward · · Score: 0

      What I've heard here *hands you a salt-lick* is that the error was made by Boeing engineers contracted out by NASA. NASA uses metric and the Boeing guys used empirical (I guess). So, make sure your contractors use the same system as you do (and the same as the rest of the world).

    7. Re:Asking for trouble.... by ElectricRook · · Score: 1

      I tend to believe its to cover some one with good political connections. I cannot believe that several people don't calculate flight paths independantly, and compare the results.

      --
      - High Tech workers, please say NO to Union Carpenters, their Union sees fit to control our compensation.
    8. Re:Asking for trouble.... by Anonymous Coward · · Score: 0

      That well reported problem was not caused my using a number as the wrong type of unit. It was caused by continouslly converting units and the inherent error that crept it.

      Look it up.

    9. Re:Asking for trouble.... by shaitand · · Score: 1

      NASA uses the metric system... as well as most of the rest of the world. Ok I admit that the metric system is definately a superior system, but why should people in the united states be barred from using their national standards and measuring systems when contributing to their own space administration?

    10. Re:Asking for trouble.... by lightspawn · · Score: 1


      That well reported problem was not caused my using a number as the wrong type of unit. It was caused by continouslly converting units and the inherent error that crept it.


      So the approach needed may be something like "save all values in the original units and convert to the necessary units just before computing the final result every time". Or eliminate the error by using fractional numbers instead of floats whenever possible. Or any one of a number of other approaches.

      I never could figure out why there are almost no languages/libraries with fractional types. That way, you can multimply and divide all you want and still come up with the right result - just convert to float/double whenever you need to, which may be never.

    11. Re:Asking for trouble.... by timeOday · · Score: 1

      But how far are you really going to get before trigonometry rears its ugly head?

  6. Would you fly with windows CE? by earthforce_1 · · Score: 2, Funny

    Given that the Thai finance minister had to be rescued from his BMW with sledgehammers after his WinCE powered iDrive computer crashed, methinks I would prefer to fly on open source software.

    --
    My rights don't need management.
    1. Re:Would you fly with windows CE? by potp · · Score: 3, Insightful

      Maybe if Microsoft had opened up its source, as NASA seems to be saying it might allow for some code, may be the Thai Minister would now be happily cruising the streets in his BMW without a care in the world.

      A lot of public money has gone into NASA over the years, so to some people's way of thinking, the people already own that source code. I'm suprising some National Security types aren't stamping all over this already though ...

      --
      find more potp = www.planetofthepenguins.com
    2. Re:Would you fly with windows CE? by gwernol · · Score: 3, Informative

      Given that the Thai finance minister had to be rescued from his BMW with sledgehammers after his WinCE powered iDrive computer crashed, methinks I would prefer to fly on open source software.

      Unfortunately this seems to be a hoax:

      CNET reports that, contrary to rumours that the BMW that trapped a Thai minister inside earlier this week was "the famously glitchy BMW 745i car, and its Windows CE-powered iDrive car computer", it was, according to a spokeswoman from BMW Thailand, the 10-year old BMW 520i model that "suffered a simple electronic failure".

      (from Looswire)

      --
      Sailing over the event horizon
    3. Re:Would you fly with windows CE? by Waffle+Iron · · Score: 3, Funny
      the 10-year old BMW 520i model that "suffered a simple electronic failure".

      That reminds me of the time I had circa 1991. I was out shopping for cars, and I thought I would have a look at the BMW 5 series. They had one in a color I liked, and I asked if I could look inside. This one had just come in, and its battery was dead. Turns out, the car had some kind of all-electronic door locks, and there was no mechanical way to unlock the car. The battery would have to be charged first; there was a plug under the bumper to do that in just this situation. Here we were at the BMW dealer, and they couldn't get inside their own car. Not good.

    4. Re:Would you fly with windows CE? by ssstraub · · Score: 2, Funny

      After reading the article, it makes me want a BMW even more!

      Doors won't open w/o power, windows are hard to break with a HAMMER... Sounds like I've found a car that won't be broken into like all of the cars around my house!

    5. Re:Would you fly with windows CE? by Anonymous Coward · · Score: 0

      Wow this is great! So idiots like you can contribute source code to projects NASA uses! I bet we can expect a lot more glitches.

      The BMW was 10 years old, it was not WinCE powered.

    6. Re:Would you fly with windows CE? by Junks+Jerzey · · Score: 1

      Given that the Thai finance minister had to be rescued from his BMW with sledgehammers after his WinCE powered iDrive computer crashed, methinks I would prefer to fly on open source software.

      Though this is a hoax, you still missed the point. For embedded systems, it's not Windows vs. Linux, it's "small, 100% completely understandable and predicatable systems" vs. general, complex operating systems. The latter includes all desktop OSes, period. You absolutely would not want Linux controlling the systems in a jet, for example. Nor would any open source programmers want to touch the system if they knew it was going to be used in jets. Embedded systems is a much different world than the desktop.

    7. Re:Would you fly with windows CE? by orac2 · · Score: 1

      Actually Linux is becoming a big player in the embedded world. Several companies offer both hard real time, and near real time OS's that are either modified Linux kernels, or preserve binary compatibility with Linux, or provide a hard real time kernel, which then runs a instance of Linux as one of its tasks.

      Check out these articles from IEEE Spectrum
      http://www.spectrum.ieee.org/WEBONLY/resource/mar0 1/nlinu.html

      http://www.spectrum.ieee.org/WEBONLY/publicfeature /dec01/embed.html

      for more on why the "small, 100% completely understandable and predicatable systems" vs. general, complex operating systems battle ground is shifting, and why Linux is getting design wins.

      --
      "Just once, I'd like to meet an alien menace that wasn't immune to bullets." -- The Brigadier, Dr. Who
    8. Re:Would you fly with windows CE? by zogger · · Score: 1

      --pitiful. Can't tell ya how many used car guys I insulkted and walked away from when out shopping before and encountered the same thing. Too cheap and too busy crasmking in fried chicken or something to put a new 30$ battery in a car, but they want to make a grand or two profit on them. As soon as I see they need to jump it, I walk away, I tell them why, "hey buddy, you are just too cheap, sorry". And NEW? That must have been embarassing for that dealer, for a luxury car.

      Me, I'll stick to window cranks as long as they are available, I understand the benefits of electric windows, but, I guess I'll "struggle by" with cranks anyway. Along with simpler engines I can work on.

      Man, what ther HECK am I saying, my windows on the jeep are ZIPPERS! HAHAHAHA! I know, I need linux embedded servo actuated zippers! No wait, microsoft with patches and a license to think about using the zippers as long as I am the original installer and have them activated over the net! No wait, bsd so I don't get my window zippers owned! No wait......GNUFIREMOZIPpers, rats, the name is probably taken, don't need long flame wars and lawyers involved... no wait! Mac zippers, that come in a rainbow of colors and do floating point tooth matching in .2 nanoseconds in 3D!.. no wait....

      Gadgets, gotta love em.. and hate em sometimes.

    9. Re:Would you fly with windows CE? by earthforce_1 · · Score: 1


      So the initial report was wrong, but, you didn't read down further in the link you provided:

      > According to previous reports, BMW recalled 15,000 iDrive-equipped 7-series > cars, one of its most luxurious sedans, globally last May and 286 more in
      > Korea two months after. Linux proponents have said that BMW engineers may be >turning to embedded Linux as an alternative operating system.

      That particular initial report was in error, (honest mistake) but the problems with those computers are well documented, including an earlier slashdot article:

      http://slashdot.org/article.pl?sid=02/05/12/2217 24 8&mode=thread

      See also:
      http://www.hotbimmer.net/forum/topic.asp?TO PIC_ID= 2832

      Damned shamed actually - I actually like the looks of it, once they get the bugs out. (Saw one at work the other day)

      --
      My rights don't need management.
    10. Re:Would you fly with windows CE? by Anonymous Coward · · Score: 0

      Just because a battery needs to be jumpstarted does not indicate that it needs to be replaced. If you don't start a car for a while, that's just what happens. Or do you replace your battery every time you come back from a vacation?

    11. Re:Would you fly with windows CE? by Junks+Jerzey · · Score: 1

      Actually Linux is becoming a big player in the embedded world. Several companies offer both hard real time, and near real time OS's that are either modified Linux kernels, or preserve binary compatibility with Linux, or provide a hard real time kernel, which then runs a instance of Linux as one of its tasks.

      That's "embedded" in the sense of "embedded control of kiosks and building heating systems" and such, which is different than embedded control of jet engines.

    12. Re:Would you fly with windows CE? by orac2 · · Score: 1

      People who build " kiosks and building heating systems" are not driving the demand for hard real time Linuxes (for which soft real time is sufficient). So we can assume the companies described in the IEEE Spectrum articles have customers with needs that go beyond those of kiosks and heating systems.

      You might be interested in the following descriptions of Lynuxworks embedded Linux based OS, use in mission critical, aerospace applications :

      http://www.lynuxworks.com/solutions/milaero/mila er o.php3

      http://java.sun.com/industry/news/story/40340.do

      http://www.eetimes.com/story/OEG20000810S0027

      As, say, fighter jets develop increasingly powerful self-monitoring capabilities, etc, the need for a network friendly embedded OS to run sub systems like engines, etc, will make Linux style OS's even more popular. I'd say it's just a matter of time before you get to sit in a commercial passanger jet, with engines run by Linux-based hard real time controllers.

      --
      "Just once, I'd like to meet an alien menace that wasn't immune to bullets." -- The Brigadier, Dr. Who
  7. Coincidence? by f97tosc · · Score: 0, Troll

    Remember the article yesterday.

    Tor

    1. Re:Coincidence? by stoolpigeon · · Score: 1

      Troll? I don't think so. That's an excellent point and as NASA is a political entity a valid question.

      --
      It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
  8. My open source contribution to NASA by product+byproduct · · Score: 5, Funny

    double Feet2Meters(double feet)
    {
    return feet * 0.3048;
    }

    1. Re:My open source contribution to NASA by jeffy124 · · Score: 1

      i'm surprised a moderator hasn't picked up on this yet. recall taht the a mars explorer system was lost because of a imperial/metric conversion error.

      --
      The One Rule Of Chess You'll Ever Need: Don't play someone who carries a kit in their bookbag.
    2. Re:My open source contribution to NASA by krog · · Score: 5, Funny

      Again, in Ada please.

    3. Re:My open source contribution to NASA by sporty · · Score: 4, Interesting

      Careful of any rounding errors. Just stick with one "thing" and be done /w it :)

      Reminds me when i worked with sin's/cos's with a particular language. Instead of creating a table of sin's and cos's, which were functions that mapped back and forth properly, i used the actual sin and cos function.

      Due to rounding errors, my object would spin and then shrink. Kinda .. amusing.

      -s

      --

      -
      ping -f 255.255.255.255 # if only

    4. Re:My open source contribution to NASA by Amazing+Quantum+Man · · Score: 4, Informative
      It's been a while, but I'll give it a shot.
      type Feet is new float;
      type Meters is new float;
      function Feet_To_Meters(Number_of_Feet : in Feet) return Meters is
      var
      Temp : float;
      begin
      Temp := Feet;
      Temp := Temp * 0.3048;
      Feet_To_Meters = Temp;
      end Feet_To_Meters;
      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    5. Re:My open source contribution to NASA by Amazing+Quantum+Man · · Score: 1
      Whoops! That should be
      Feet_To_Meters <B>:=</B> Temp;
      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    6. Re:My open source contribution to NASA by titzandkunt · · Score: 1

      Looks like you'll fit right in at NASA already.

      "Meters", indeed.

      T&K.

      --
      Political language ... is designed to make lies sound truthful and murder respectable...
    7. Re:My open source contribution to NASA by Anonymous Coward · · Score: 0
      Or, better yet, put it in the best programming language around; Python:
      def Feet2Meters(feet): return feet * 0.3048
      I heard somewhere that NASA is using Python for some stuff. Good choice.
    8. Re:My open source contribution to NASA by The+Dobber · · Score: 4, Funny


      Dear Applicant:

      Upon review, we have decided not to accept your application for employment with NASA

      Thank You ..

    9. Re:My open source contribution to NASA by Anonymous Coward · · Score: 5, Funny
      Dear Employer,


      Upon review, I have decided not to accept your rejection. I will be reporting to work on Monday.

    10. Re:My open source contribution to NASA by fredrikj · · Score: 2, Informative

      I heard somewhere that NASA is using Python for some stuff. Good choice.

      You mean this:

      "NASA is using Python to implement a CAD/CAE/PDM repository and model management, integration, and transformation system which will be the core infrastructure for its next generation collaborative engineering environment. We chose Python because it provides maximum productivity, code that's clear and easy to maintain, strong and extensive (and growing!) libraries, and excellent capabilities for integration with other applications on any platform. All of these characteristics are essential for building efficient, flexible, scalable, and well-integrated systems, which is exactly what we need. Python has met or exceeded every requirement we've had," said Steve Waterbury, Software Group Leader, NASA STEP Testbed.

      From http://www.python.org/Quotes.html.

    11. Re:My open source contribution to NASA by jbridge21 · · Score: 0, Redundant

      ADA RULES!!!!!!!

    12. Re:My open source contribution to NASA by Anonymous Coward · · Score: 0

      You could #define it in C, just as easily, and you even speed it up (on top of the whole interpretted nonsense).

    13. Re:My open source contribution to NASA by zonix · · Score: 2, Funny
      Due to rounding errors, my object would spin and then shrink. Kinda .. amusing.

      I know I ain't getting any, but am I the only one who misread this part? :-)

      z
      --
      What would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
    14. Re:My open source contribution to NASA by sporty · · Score: 1

      You know what I meant, damnit. :)

      --

      -
      ping -f 255.255.255.255 # if only

    15. Re:My open source contribution to NASA by Anonymous Coward · · Score: 0
      Due to rounding errors, my object would spin and then shrink. Kinda .. amusing.

      In high school, I apparently wrote the same program as you did with the same effect!

    16. Re:My open source contribution to NASA by niom · · Score: 1

      Nope. That won't even compile. The correct soluction:

      function Feet_To_Meters(Length_In_Feet : in Feet) return Meters is
      begin
      return Length_In_Feet * 0.3048;
      end Feet_To_Meters;

      --
      -- Repeat with me: "There is no right to profits".
    17. Re:My open source contribution to NASA by Amazing+Quantum+Man · · Score: 1

      Yeah, I realized I had some more typos, and I couldn't remember the rules for derived types, hence the temporary float variable.

      Bummer.

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    18. Re:My open source contribution to NASA by vsprintf · · Score: 1

      Eewww. Now I understand the high suicide rate for Ada programmers. It's Pascal and COBOL thrown in a blender with none of the redeeming qualities of either. :)

    19. Re:My open source contribution to NASA by Guppy06 · · Score: 1

      Change the * to a / and multiply your conversion factor by 10 and you'll be correct.

      Would you, by any chance, be a Lockheed-Martin employee?

    20. Re:My open source contribution to NASA by Guppy06 · · Score: 1

      Nobody can make an idiot out of me like I can. This is where I smile and wave to all the folks who are about to point out my error.

    21. Re:My open source contribution to NASA by Guppy06 · · Score: 1

      "Careful of any rounding errors."

      There would be no rounding errors; US units are defined by metric units. An inch is defined as 2.54 centimeters, which means a foot is exactly as 0.3048 meters and a mile is exactly 1.609344 kilometers. And if normal gravitation acceleration is defined as 9.80665 m/s^2, a pound is defined as 4.4482216152605 Newtons. Everything else can be extrapolated to infinite precision.

    22. Re:My open source contribution to NASA by nacks1 · · Score: 1

      Actually... if you know anything about scientific computing you would want fortran (believe me I know...)

    23. Re:My open source contribution to NASA by Anonymous Coward · · Score: 0

      Again, you've just smacked into the surface of Mars or headed off into deep dark space.

      - return feet * 0.3048;
      + return feet * 0.304801;

      Rounding error's a bitch over 150 million miles. It adds up.

    24. Re:My open source contribution to NASA by blancolioni · · Score: 1

      Close! But why use the temporary?


      type Feet is new Float;
      type Metres is new Float;

      function Feet_To_Metres (Number_Of_Feet : Feet) return Metres is
      begin
      return Metres (Number_Of_Feet * 0.3048);
      end Feet_To_Metres;


      Notice that in the Ada version, it's much harder to hand out Feet to something that expects Metres. However, applying the type system to this sort of dimensional stuff has some interesting subtleties, which sadly this comment is far to short to go into.

      (I'm aware that the ISO standard spelling for metre is meter, but I'm ignoring that, just as I ignore that pesky way you yanks spell sulphur)

    25. Re:My open source contribution to NASA by Amazing+Quantum+Man · · Score: 1

      Close! But why use the temporary?

      Because I couldn't remember the syntax for casting between derived types (it's been several years).

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    26. Re:My open source contribution to NASA by Alsee · · Score: 1

      There would be no rounding errors... a foot is exactly as 0.3048 meters

      A foot is 0.3048006096012(...) meters. Your Mars orbiter is now many miles off course and has burnt up in the atmosphere.

      You were saying something about no rounding errors? :D

      -

      --
      - - You can't take something off the Internet! That's like trying to take pee out of a swimming pool.
    27. Re:My open source contribution to NASA by Guppy06 · · Score: 1

      "A foot is 0.3048006096012(...) meters."

      What you're referring to is the "US survey foot," which is a dinosaur from the nineteenth century. But even then, it's defined by a metric unit multiplied by a rational number, with a survey foot being defined as (1200/3937) meters. You're still able to convert with infinite precision.

      In the 1950's the US changed the definition of "foot" and "yard" and such to come into line with other countries that used the same units. They adopted the "international foot," which is defined as 0.3048 meters. The only people who use the "survey foot" nowadays are essentially surveyors who work with figures recorded over a hundred years ago.

      Of course, there's little reason to get quite that picky. The "international foot" is 0.999998 "survey feet" exactly (do the math yourself if you don't believe me), which means a difference of exactly 0.0002%.

    28. Re:My open source contribution to NASA by SETIGuy · · Score: 1
      The problem wasn't not knowing how to convert, but forgetting which units they were using. Therefore, I offer the following
      #include "unit.h"

      class meters : public unit<length> {
      public:
      explicit meters(double v=1.0);
      meters(const unit<length> &v);
      }

      meters::meters(double v) : unit<length>(v,1.0) {};
      meters::meters(const unit<length> &v) : unit<length>(v,1.0) {};

      class feet : public unit<length> {
      public:
      explicit feet(double v=1.0);
      feet(const unit<length> &l);
      };

      feet::feet(double l) : unit<length>(v,0.3048) {}
      feet::feet(const unit<length> &v) : unit<length>(v,0.3048) {}

      Unfortunately "unit.h" is a bit too large for this message.

  9. So... by American+AC+in+Paris · · Score: 5, Funny

    ...is it "GNASA" now?

    --

    Obliteracy: Words with explosions

    1. Re:So... by Anonymous Coward · · Score: 1, Funny

      Thats pronounced GNU/nasa

    2. Re:So... by Anonymous Coward · · Score: 4, Funny

      No, it'd be GNU/NASA if they used the GPL license. But they seem to prefer Mozilla's license, so it will be NAZILLA.

    3. Re:So... by mahdi13 · · Score: 4, Funny

      It would be gNASA if they were using the gnome/GTK libraries, and kNASA if it is the KDA/QT libraires

      Then as mentioned, Richard Stallman would make everyone call it GNU/NASA

      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    4. Re:So... by rusty0101 · · Score: 4, Funny

      would the extraction of GNASA be GNASAs Not A Space Agency by any chance?

      --
      You never know...
    5. Re:So... by mahdi13 · · Score: 1

      I'm such a bonehead!!
      That's kNASA using KDE not KDA!

      Ahhh MAN!!! Maybe I should skip seeing the new Matrix movie tonight and get some sleep!
      Riiigghhtt....like that's going to happen!

      --
      "Some things have to be believed to be seen." - Ralph Hodgson
    6. Re:So... by sketerpot · · Score: 1

      If Stallman insisted on getting GNU in there anywhere, I'm pretty sure it would be the more logical (and less easy to mindlessly troll about) NASA/GNU[/Linux/whatever]. Anyway, RMS would, I'm sure, leave NASA alone on this unless they tried making, say, a GUI on top of GNU and calling it an operating system. Then he would be on them like a dog. ;-)

    7. Re:So... by Billly+Gates · · Score: 1
      ...then SCO will sue Nasa and force it to call itself SCO/Nasa.

    8. Re:So... by vsprintf · · Score: 1

      Unix:Making the easy things hard and the hard things possible.Windows:Making the hard things $29.95

      So, you haven't upgraded since Windows 2.0? That should be:

      Windows: Making the easy things $229.95. Making the slightly harder things $429.95. We reserve the right to modify the ease or difficulty of things and their respective costs at our whim.

    9. Re:So... by spanky555 · · Score: 1

      How about giving it some oomph? How about NADzilla? :)

  10. What took NASA so long to get this far ... by Katalyzt · · Score: 0, Troll

    .. maybe it's all that highly customised flight software, after all how many people have got spacecraft they need to control.

    given their resources NASA can make a great contribution to the open source world as they transform away from a government agency.

    --
    version 0.0002
  11. Open Source for a closed system by Davak · · Score: 1, Insightful
    Please, somebody explain to me how open source on a closed, specific system helps...

    If I am crunching shuttle code at home, how do I test it? Wouldn't be a security problem to publically report the hooks and calls to write such code?

    Of course, NASA does office stuff, networking, etc... I guess "some projects" would have to be highly specific. But if you are gonna help NASA, who wants to help the secretary? I wanna help the shuttle fliers get in on the P2P action... (heck, pinging the shuttle would probably be faster than pinging some of the servers I've been using lately.)

    Davak

    1. Re:Open Source for a closed system by gosand · · Score: 1
      Please, somebody explain to me how open source on a closed, specific system helps...

      Instead of writing things from scratch, they can take existing OSS code and tweak it. It could also be a cost saving measure, since tweaking code is cheaper than starting a project from scratch. They don't necessarily have to release it back to the world if their modifications are just for "in-house" software.

      --

      My beliefs do not require that you agree with them.

    2. Re:Open Source for a closed system by JordanH · · Score: 4, Informative
      • Please, somebody explain to me how open source on a closed, specific system helps...

        ...

        Of course, NASA does office stuff, networking, etc... I guess "some projects" would have to be highly specific. But if you are gonna help NASA, who wants to help the secretary?

      Ever work in a large software shop? I didn't think so.

      Any operation of any size at all generates lots of software tools and libraries that are more or less generic.

      In addition, NASA does lots of Scientific Visualization, materials engineering, simulations, data acquisition and other stuff that is not directly related to embedded flight control systems. Lot's of good science that's not just "Office Stuff".

      I'm probably missing more than a few, but just these examples are things that could be opened up.

    3. Re:Open Source for a closed system by ElectricRook · · Score: 2, Interesting

      If you are operating on the cutting edge of some new technology, you are probably writing your own tools. Else, off-the-shelf tools are suitable for following in the footsteps of others. And you trust the software actually performs as specified.

      --
      - High Tech workers, please say NO to Union Carpenters, their Union sees fit to control our compensation.
    4. Re:Open Source for a closed system by anonymous+loser · · Score: 4, Interesting

      The submitter said "some" projects.

      What on earth makes you think they'd use linux or other OSS to develop the space shuttle software? First of all, the development process for space shuttle software is quite possibly the most rigorous software development process in the world (it is , BTW). There isn't a chance in hell open-source software would be allowed into a level 5 process, because it's not controlled properly. They would essentially have to rewrite any OSS software they used from scratch, just to meet CMM level 5 requirements.

      Second, suppose despite point #1, they decide to use the linux kernel on the space shuttle. Obviously, they'd have to adapt the kernel to suit their needs, since most of the hardware on the shuttle is custom designed and built for it. Under the GPL they would have to release any changes they make to the kernel back into the public domain. This would be equivalent to providing a very detailed blueprint of how all the critical systems on the space shuttle function. Especially given the current political environment, do you really think the administration is going to divulge this kind of information to the public?

    5. Re:Open Source for a closed system by Anonymous Coward · · Score: 0
      Troll?

      Offtopic?

      What's the mods smoking?!?

      Good conversation going on here...

      AC

    6. Re:Open Source for a closed system by Anonymous Coward · · Score: 0

      Your example is wrong.

      How does OSS help NASA:

      1) Many eyes make bugs shallow. How would the conversion factor have survived to crash the Mars probe?

      2) Why should they expend energy keeping the source closed?

      3) They can now use OSS as a base of their software (note itwasn't necessarily that they would make contributions back...)

      4) Why not?

    7. Re:Open Source for a closed system by Anonymous Coward · · Score: 0


      They don't necessarily have to release it back to the world if their modifications are just for "in-house" software.


      I dunno. Doesn't sending it to mars count as "distribution?"

    8. Re:Open Source for a closed system by budgenator · · Score: 1

      NASA uses some seriuos image manipution techniques, that would fit into some GIMP plugins off the top of my head. Maybe some navigation stuff for aircraft and oceanliners. Having an extra set of eyeballs on the code might even same a space probe from unit of measure convertion crashes. Space shuttle code might even be the basis for a killer space game.

      --
      Apocalypse Cancelled, Sorry, No Ticket Refunds
    9. Re:Open Source for a closed system by johannesg · · Score: 1
      Flight software is not quite the only type of software in use in the space industry. I work for a company that writes test software for spacecraft, for example. These are pretty big systems, used to simulate input to and analyze output from the tested spacecraft.

      Could you run these at home? Sure - right now a major shift is going on, 'old' UNIX systems are being displaced more and more by cheap, powerful PC's running GNU/Linux. Would it be useful? Well, not really (raise hands all who have a spare spacecraft in their garage they need to test / control). But these packages are fairly generic, flexible, high powered industrial control applications. You could use them for lots of things outside the space industry. When I get back to the office next monday I'll ask how they feel about Open Source. Don't get your hopes up: the property rights to much of the software is tied up among numerous owners.

      Similar systems are used in ground control centers. These are more or less the same as the test systems I described above, but with more checks and validations on the input parameters. You wouldn't want your spacecraft to take a wrong turn once they are launched, they are pretty expensive after all ;-)

      To put things in perspective, IIRC the ATV spacecraft (which is what I'm working on right now) has 32MB of onboard RAM, and is using a 20MHz CPU (ERC32, which is a space-hardened SPARC). A typical test system has something like half a million to a million lines of code, and requires multiple powerful machines to be able to run a test at full speed. There is much, much more software in the ground segment then there is in the spacecraft.

      Would you be interested in seeing this kind of software opened up, even though it has limited use to the average hacker? What would you do with it, if you had access to it?

    10. Re:Open Source for a closed system by Elitist+Snob · · Score: 2, Informative

      Obviously, they'd have to adapt the kernel to suit their needs, since most of the hardware on the shuttle is custom designed and built for it. Under the GPL they would have to release any changes they make to the kernel back into the public domain.

      No, they wouldn't. This is just FUD. See the GPL FAQ:

      The GPL does not require you to release your modified version. You are free to make modifications and use them privately, without ever releasing them. [...] If you release the modified version to the public in some way, the GPL requires you to make the modified source code available to the users, under the GPL

      They'd only have to make the source public if they were also distributing the customised kernel. Chances are, they're only going to use their executable in this custom hardware of theirs.

    11. Re:Open Source for a closed system by Angry+White+Guy · · Score: 1

      Then I wish they'd 'distribute' XP home and get it the hell out of here.

      --
      You think that I'm crazy, you should see this guy!
    12. Re:Open Source for a closed system by geekoid · · Score: 1

      then they would take the initial product, and modify it. Hell, if they can make on OS meet CMM level 5, I hope to hell the do distribute it.

      According to the GPL they would not have to release changes unless they distributed the kernel.

      That said, what the heck would be the problem with releasing a blueprint of the critical systems?
      what, you going to build one? since the software would be changed and tested by there own people, they would have control of there software destiny. Its not like they would grab the latestes version of source forge and just toss it into there system. If someone wants to go after the shuttle, it would have to be done externally, like a surface to air attack.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    13. Re:Open Source for a closed system by dsplat · · Score: 1

      Under the GPL they would have to release any changes they make to the kernel back into the public domain.

      You are correct that no current open source project is going to make it as CMM level 5. That doesn't mean that everything about open source is incompatible. There is nothing about CMM level 5 that I'm aware of that would prevent releasing the code under an open source license. It is the organization and project that are CMM level 5. The code is a product of that. Accepting code into the project from outside, as you said, wouldn't cut it.

      As for having to release any deltas to the Linux kernel. Nope, the GPL doesn't require that. You can modify anything released under the GPL for your own use. Have fun with it. The requirement is that if you modify it, and release the modifications, you have to release the source as well and the modifications are also covered by the GPL.

      --
      The net will not be what we demand, but what we make it. Build it well.
    14. Re:Open Source for a closed system by CyberGarp · · Score: 1

      I tell you what some peopel would do. See my previous post: Free Software Reviews.

      --

      I used to wonder what was so holy about a silent night, now I have a child.
    15. Re:Open Source for a closed system by ianezz · · Score: 1
      Under the GPL they would have to release any changes they make to the kernel back into the public domain.

      If and only if they distribute such derived works. There is no obligation in the GPL to redistribute derived works (there can't be, being the GPL a permission to distribute copyrighted material at certain conditions, permission which you normally don't have).

      Of course, if they don't redistribute the modified sources, they also get the burden of mantaining them. That sounds fair to me.

    16. Re:Open Source for a closed system by frodo+from+middle+ea · · Score: 2, Insightful
      There isn't a chance in hell open-source software would be allowed into a level 5 process, because it's not controlled properly.
      Well, they can use OSS, customise it as they want and control it with their onw internal policies which meet CMM level 5. Though they would need a CMM level 5 mechanism to include the newer versions of the code, with their own maintained one.

      The change management mechanism /version control policies have to internal and strictly controlled.

      They are not required to sync their local copy of code, with nigthly builds or daily CVS snap-shots.

      Your second point is another gross mis-conception about GPL.

      Please read this carefully

      • GPL doesn't require the changes to be resubmitted if the changes are not distributed. I can obtaine source for linux kernel and change it to what i want and use it internally for my personal or business . As long as i don't distribute (sell/give away free) my kernel modifications, I don't have to submit back the changes
      • Also they are thinking of using the Mozilla license, which is significantly different from GPL or LGPL to be precise.
      Please don't spread FUD about something that you don't understand.
      --
      for the last time people, I am "frodo from middle eaRTH", not "middle eaST".
    17. Re:Open Source for a closed system by anonymous+loser · · Score: 1

      My mistake on misunderstanding the GPL.

      However my first point was that up until this point, the linux kernel has not been controlled under a CMM level 5 process (far, far from it), and thus incorporating it into the space shuttle software would basically require rewriting it from scratch just to make sure it met CMM level 5 requirements. Since they would have to rewrite anything from scratch anyway, there is no point in using OSS that I can think of, unless an OSS project comes along that happens to be certified CMM level 5.

      p.s. also sorry about the broken HTML, my / key seems to be a little stiff.

    18. Re:Open Source for a closed system by UnknowingFool · · Score: 1
      Please, somebody explain to me how open source on a closed, specific system helps...

      OSS helps NASA like it helps any large organization or company. Cost is a factor in government as it is in business. Customization is another. NASA also has the raw geek talent to do their own code.

      Probably we will never actually work on shuttle code. Mostly likely, contributions to NASA will be in general OS things like networking and streaming audio.

      Right now the document is more of a declaration of a coherent IT policy. There's no guarantee that they will adopt OSS.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    19. Re:Open Source for a closed system by anonymous+loser · · Score: 1
      That said, what the heck would be the problem with releasing a blueprint of the critical systems?


      I didn't say there's a specific problem with it. I said that under the current political environment there's no way it would happen. Public documents are being pulled off shelves faster than you can say "national security." Do you really expect the current administration would allow such sensitive information to be openly published?

    20. Re:Open Source for a closed system by Glock27 · · Score: 1
      However my first point was that up until this point, the linux kernel has not been controlled under a CMM level 5 process (far, far from it), and thus incorporating it into the space shuttle software would basically require rewriting it from scratch just to make sure it met CMM level 5 requirements. Since they would have to rewrite anything from scratch anyway, there is no point in using OSS that I can think of, unless an OSS project comes along that happens to be certified CMM level 5.

      Bear in mind that CMM Level 5 is a process, not a product. It would be perfectly possible to install the Linux kernel sources in a NASA software repository, and begin maintaining it as a CMM L5 product. This would essentially result in a fork, since NASA engineers would have to rigorously test and merge any changes from the outside after that.

      This might be a cool way to maintain a "super-stable" kernel, for high-availability applications. Interesting.

      --
      Galileo: "The Earth revolves around the Sun!"
      Score: -1 100% Flamebait
    21. Re:Open Source for a closed system by Realistic_Dragon · · Score: 1

      In addition, NASA does lots of Scientific Visualization, materials engineering, simulations, data acquisition and other stuff that is not directly related to embedded flight control systems. Lot's of good science that's not just "Office Stuff".

      My biggest hope is that they will pick up Octave over the closed source Matlab.

      Octave is already really good, but needs more libraries written for it, and NASA are really good at things like CFD libraries for numerical tools...

      It wouldn't make the folks at Mathworks happy, but they deserve it:
      I can buy Matlab (full license) for UNIX
      I can buy Matlab (student license) for Windows
      I can't buy Matlab (student license) for UNIX

      Given that all that is required is a quick recompile as their code is already UNIX safe, this really gets my goat.

      --
      Beep beep.
    22. Re:Open Source for a closed system by anonymous+loser · · Score: 2, Insightful

      While I agree that in theory it's possible, I'm not so sure you can just incorporate outside sources so easily into a CMM L5 project, since all of the previously existing development isn't up to snuff. There would be no design documents or QA for the kernel until it was brought in-house, so you'd have to spend several man-years just doing QA on the existing code to "prove" that it was safe.

    23. Re:Open Source for a closed system by Bombcar · · Score: 1

      Wouldn't putting the customized kernel all over Texas be considered "distributing?"

      (Moderation -1 Sick Joke)

    24. Re:Open Source for a closed system by SurfTheWorld · · Score: 1

      You're absolutely correct Jordan. There are lots of scientific and astronomical calculations that would be immensely valuable in the open source world. One part of the analysis that I think most reports fail to recognize is the fringe benefits of using open source.

      I work on an "enterprise" project for NASA, and we currently use several closed source COTS products (most notably WebLogic, TopLink, and Wasp). We also use several open soruce projects (most notably Xalan, Dom4J, and Tomcat). We have an immensely difficult configuation we must manage - the mapping of our object model to a relational data model. We use TopLink (closed source) to help us manage this challenge. TopLink is tightly coupled with WebLogic (another closed source product). We *very frequently* receive ambiguous error messages, NullPointerExceptiosn, InvocationTargetExceptions, and similar non-sensical and non-intuitive error messages out of our Closed Source projects. When this happens, luckily we have a stack trace that we can look at. To fix the problem, we employ the following strategy:

      1.) Report the bug to the vendor
      2.) Quietly, unjar the closed source product
      3.) Quietly, decompile the class
      4.) Quietly, re-compile it (to get line number debugging info)
      5.) Re-produce our problem
      6.) Quietly, open the decompiled source code in an editor
      7.) Quietly, locate the line number that threw the exception
      8.) Examine the if and try-catch'es that produced the exception
      9.) Continue up through the stack until you determine the problem

      For example ...
      We mapped our object model using TopLink and named the project "foo". Our bean deployment descriptors used a project name of "FOO". The old version of TopLink was case insensitive. The new versions are case sensitive. Instead of erroring with "You referenced a project named 'FOO' in your bean deployment descriptor, but no project named 'foo' exists in your TopLink configuration.", TopLink gave us a NullPointerException. We would never have been able to determine the cause of the NPE without examining the code. We would've had to wait until our CSR responded to us (which ended up taking 4 days by the way) in order to resolve our problem.

      That's the fundamental problem with closed source software. If TopLink and WebLogic were open, we would not have had to take steps 2 - 5 (that's 50% of our procedure!). And, this problem was simple. We could resolve it ourselves. But lots of other times there are more complex problems where you have some notion of what's going on (because you look at the internals), and you'd like to be helpful to the CSR folks on the other end by telling them your findings, but in doing so you may violate your end user license agreement because you decompiled their code. Net result: you (the customer) lose because you have to wait on an external entity for problem resolution (which is a risk). The CSR tech on the other end loses because they have to re-do all of your steps and do not get the benefit of your research (because you have to hide your knowledge from them). The only entity that wins is the vendor.

      Now, compare this to open source where I can examine and post my diagnosis to usenet and receive feedback and/or ideas from hundreds of other developers. We're doing the same thing either way (examining source code). Why keep it closed?

      Similarly, we've come across the situation where politics and financials from the vendor has negatively impacted our project's ability to satisfy the customer. For example - We discover a bug in WebLogic 6.1 SP2 that causes forces us to upgrade to SP4. We discover that TopLink 3.6 doesn't work with SP4. We look at some WebLogic internals, do some research, and determine that the reason why TopLink doesn't work with SP4 is because WebLogic added a callback function that all beans must implement. The callback function just stores a boolean value. We talk to TopLink about it. Their response: wait for the next patch. Our question

      --
      Do it for da shorties
    25. Re:Open Source for a closed system by pyrrho · · Score: 1

      they would not have to release their modifications. You only have to do that if you sell or distribute your system. So if they sold or gave their system to ESA it would have to come with the code.

      --

      -pyrrho

    26. Re:Open Source for a closed system by shaitand · · Score: 1

      ok, you flippin idiot, don't let ignorant moderation get to your head, in case you didn't read the other 500 responses... THEY DON"T HAVE TO RELEASE THEIR MODIFICATIONS. They only have to do that if they distribute the software to 3rd parties, internally they can pass it around all day long. If they release the software to the public... yes, they have to give the public the code (it's not too tough to figure out that there is NO reason to do this with the software that runs on the space shuttle). If they distribute to a 3rd party developer... DUH the developer would need the code anyway.

    27. Re:Open Source for a closed system by anonymous+loser · · Score: 1

      This is why I love slashdot.

      Thanks, I already understand that perfectly, and you'd know that if YOU had bothered to read my other responses in this thread. It is not my practice to respond to essentially the exact same post 500 times (as you put it), but I thought the irony here was particularly funny.

    28. Re:Open Source for a closed system by vsprintf · · Score: 1

      If I am crunching shuttle code at home, how do I test it? Wouldn't be a security problem to publically report the hooks and calls to write such code?

      Fer cryin' out loud. They aren't talking about running the shuttle on OSS code. IIRC, the shuttles use 20-year-old, rad-hard processors and other ancient but stable (and hard to replace) gear. They are talking about the advantages of using OSS for regular projects - and like any large organization, there are hundreds or thousands of separate projects. One of those advantages is that the code/information is available in a non-proprietary format.

  12. MPL - can it be used in commercial software? by Anonymous Coward · · Score: 0

    Sorry if this is a repost - Slashdot ate my first one.

  13. Isn't government owned software public domain? by pecosdave · · Score: 5, Interesting

    I thought the government couldn't copywrite anything. Or does NASA not count?

    --
    The preceding post was not a Slashvertisement.
    1. Re:Isn't government owned software public domain? by WPIDalamar · · Score: 0

      The mere act of creating a creative work grants it some copyright protections. So unless we're not letting the government create anything, I don't see how we can avoid it.

    2. Re:Isn't government owned software public domain? by b0r1s · · Score: 1

      Yes.

      Things the have come out of JPL and NASA, as well as the national laboratories, have consistently been in the public domain. Adding the restrictions of the Mozilla license is a step backwards.

      --
      Mooniacs for iOS and Android
    3. Re:Isn't government owned software public domain? by pecosdave · · Score: 5, Informative

      Here we go


      Publications Incorporating U. S. Government Works

      Works by the U. S. Government are not eligible for U. S. copyright protection. For works published on and after March 1, 1989, the previous notice requirement for works consisting primarily of one or more U. S. Government works has been eliminated. However, use of a notice on such a work will defeat a claim of innocent infringement as previously described provided the notice also includes a statement that identifies either those portions of the work in which copyright is claimed or those portions that constitute U. S. Government material.

      Example: © 2002 Jane Brown. Copyright claimed in Chapters 7-10, exclusive of U. S. Government maps

      Copies of works published before March 1, 1989, that consist primarily of one or more works of the U. S. Government should have a notice and the identifying statement.

      --
      The preceding post was not a Slashvertisement.
    4. Re:Isn't government owned software public domain? by The+Jonas · · Score: 1

      True, however, there are some things that have not come out such the NSA's crypto technology and the like. Also, nothing related to national security is supposed to make it into the public domain.

    5. Re:Isn't government owned software public domain? by pecosdave · · Score: 2, Insightful

      I think the word "classified" over-rules the idea of copywrite. Government owned crypto I guess would still be public domain, they're just not showing it to us.

      Hmm, wonder if I can get the source to Carnivore under the Freedom of Information Act?

      --
      The preceding post was not a Slashvertisement.
    6. Re:Isn't government owned software public domain? by kuroth · · Score: 1
      This is a *big* deal, and it's not because we get to do the happy dance around the OSS tree.

      Information created by the federal government is not subject to copyright protection. WPIDalamar is wrong, and needs to go read Title 17, Chapter 1, Section 105:
      Copyright protection under this title is not available for any work of the United States Government,
      but the United States Government is not precluded from receiving and holding copyrights transferred
      to it by assignment, bequest, or otherwise.
      Section 3.4.3.2 of NPG 2210.1A, referenced in the article, mentions this lack of copyright protection:
      "3.4.3.2. Copyrights - Software created solely by an officer or employee of the U. S. Government as part
      of that person's official duties is a work of the U. S. Government. Copyright protection is not currently
      available in the United States for a work of the U. S. Government. However, the Government can claim
      foreign copyrights for software created by its employees and can receive and hold copyrights transferred
      to it by assignment.
      The sticky part of this is the overlap between national security/IP precautions and Title 17. The policies regarding the release of NASA's software are defined in NPG 2210.1A. Section 2.2 of this document outlines several possible release levels. The least restrictive level is "Approved for Public Domain Release"; All other levels are more restrictive than that due to security, patent, or export control issues.

      What these jokers are trying to do is get the most open form of release - "Approved for Public Domain Release" - switched to "Approved for Release Under [Some] License". This is less freedom than before. They practically state this explicitly when they say "...Open Source and Public Domain are not the same thing. We want the protections that an Open Source license can give us."

      This is not a Good Thing.

      Fortunately, it's pretty obvious that it's a violation of Title 17, and it'll probably never fly.
    7. Re:Isn't government owned software public domain? by Anonymous Coward · · Score: 0

      I thought the government couldn't copywrite anything.

      The USA government can certainly copywrite. They do plenty of it, routinely. They can't copyright anything of course, but that's a completely separate issue that only illiterates would mix up.

      Or does NASA not count?

      Well NASA can copywrite as much as they like. Or are you talking about copyright? External organisations that are hired by the USA government can copyright works, I don't know whether NASA falls into this category or not.

    8. Re:Isn't government owned software public domain? by sean23007 · · Score: 1

      If you asked you would get a big red "Terrorist" flag next to your name. I wouldn't try it.

      --

      Lack of eloquence does not denote lack of intelligence, though they often coincide.
  14. Re:Funny Thing... by Anonymous Coward · · Score: 0

    damn! I think you've found the next big category for spam!

  15. Plain English of Licenses? by johnynek · · Score: 4, Interesting
    I know some karma-whore can answer this:

    Is there some page which compares all the licenses in some table, or in english language terms?

    Something like: the Creative Commons explains for their licenses would be very helpful for comparing: MIT X11, BSD, GPL, LGPL, BSD, OSL, Mozilla PL, Apple PL, etc...

    If this does not exist, the community would benefit from it!

    --
    jabber: johnynek@jabber.org
    1. Re:Plain English of Licenses? by TwistedSquare · · Score: 1

      Yep that would be very useful if someone could provide it.

    2. Re:Plain English of Licenses? by Anonymous Coward · · Score: 0

      MIT: We own the changes.
      BSD: You own the software. Please thank us.
      GPL: You own the changes, So do we
      LGPL: You can keep your changes to yourself, if you take care
      MPL: Give us your changes
      APL: Give us the changes, and we might keep them ours

      A very rough idea of the difference.

    3. Re:Plain English of Licenses? by Anonymous Coward · · Score: 1, Informative

      (1) I am no karma whore
      (2) Check with these folks

    4. Re:Plain English of Licenses? by jaaron · · Score: 1

      Good idea.
      I'm starting to put something together on my wiki site.

      --
      Who said Freedom was Fair?
    5. Re:Plain English of Licenses? by Some+Bitch · · Score: 1

      This would be the one you want I think :)

    6. Re:Plain English of Licenses? by Anonymous Coward · · Score: 0
      Microsoft had such a thing in one of the Halloween documents.

      Try http://www.medienkultur.org/sm2/org/tragik/hallowe en-taxonomy.html

  16. Re:NASA is obsolete by Katalyzt · · Score: 1

    well i still trust NASA to continue the greatest space program in the world even though they screw up now and then and need continous improvement. don't slam them too hard, their successes far outweigh their failures.

    --
    version 0.0002
  17. Not a wholesale switch by Anonymous Coward · · Score: 5, Insightful

    This is a remarkably balanced report for a government. It advocates a mix of internally developed and external software, including both open source and proprietary software, depending upon the situation.

    You'd think this was a pretty obvious take, but far too often government processes are hijacked by either open source zealots or commercial interests. Leaning in either direction can cause great technical difficulty and cost to the public.

    Keep in mind that NASA has no great software policy, but a huge amoung of software in place. A policy to ensure consistency and fairness over much of the existing software uses could have great advantages in efficiency for the organization. Of course, what you think of the existance of NASA in the first place or its usefulness in its current form is up to you...

    1. Re:Not a wholesale switch by thelexx · · Score: 1

      "but far too often government processes are hijacked by either open source zealots..."

      An example or two of this would be nice.

      "Leaning in either direction can cause great technical difficulty and cost to the public."

      In what specific ways would 'leaning' toward open source incur "great technical difficulty and cost"?

      --
      "Gold still represents the ultimate form of payment in the world." - Alan Greenspan, 1999
  18. Re:NASA is obsolete by Timesprout · · Score: 3, Insightful

    Hate to break it to you but manned space flight has already been pioneered.

    A small private company would want to invest the billions necessary to go to Mars because ?? What possible financial gain gould they possibly realise within any realistic timeframe for a company's survival. Who would back them, who would insure them? Would they go and claim Mars for themselves if they got there in the best capitalist manner ?

    Proper space exploration is better left to the big boys and international co operation for the time being. Hopefully they can learn something from the independent efforts in the meantime

    --
    Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
    What truth?
    There is no dupe
  19. Why not Public Domain? by hobbs · · Score: 2, Insightful

    Excepting anything that might be considered secret and confidential (like missile guidance software ... which probably never gets released anyway), why isn't all NASA software public domain?

    I'm going on the assumption that we are talking solely about all the US taxpayer funded engineers making software there. Why isn't this stuff by definition public?

    1. Re:Why not Public Domain? by shaitand · · Score: 1

      By law it is, the government does not own a us copyright on their works, in the US it is public domain (they can enforce foreign copyrights though, and by treaty some of those are enforceable here... this needs fixed, if it's not already fixed somewhere I don't know about). But there is nothing that says they have to show them to the public to begin with...

  20. Hmmm by Anonymous Coward · · Score: 0

    Well NASA proper doesn't have much to hide as far as i know in terms of the software they use. Most of the stuff that's interesting to the public at large is now in use in day to day life. I keep seeing you people say oh gosh oh gosh look at how basly they (nasa) hndle issues. I'd like to just one of you get get beyoned basic training. YOu have to be in reasonable good health, assess situations in an instant and deal with alot of genuine stress (no I don't meen DSL vs Cable.) It's also true that nasa is probably advcating for this for some PR,but on the other hand who's to say OSS bs GPL? Might be a BSD Licence or something else.

  21. NASA by burdicda · · Score: 1

    Bout time they quit wasting taxpayer's money
    on "Intellectual Property" !!!

    Think where we'd be if everything ever discovered
    by NASA using taxpayer's money was patented
    and copyrighted as "Intellectual Property"

    Hmmmm If "Intellectual Property" was created
    or found and documented with taxpayer's money
    who does it belong to then ?

    If the taxpayer own's it doesn't it then
    become property of the people hence
    making it GPL by proxy ?????

  22. According to RMS... by Anonymous Coward · · Score: 0

    the correct terminology would be "GNU/NASA"
    Get it right.

  23. Re:Funny Thing... by Anonymous Coward · · Score: 0
    Tits up to the Trolls(tm)!! 6th post!

    Y00 F4!1 !7
    Next itme, just forget about posting, because you can't even make a good troll.

  24. Someone help me out here... by alchemist68 · · Score: 2, Interesting

    I seem to remember a long time ago about an incident where Bill Gates of Borg toured NASA and offered to GIVE AWAY PCs with M$ Windows on them so that NASA essentially ran on Windows. NASA supposedly did a long term study on Windows and determined that it was not stable enough to run the Space Shuttle and mission control equipment. There would be no way to recover the Space Shuttle during a launch in the event of a Blue Screen Of Death. This is supposedly the reason why Linux is so prevalent inside NASA. I may some facts wrong here, but this is pretty much what I heard through the grape vine.

    1. Re:Someone help me out here... by zakezuke · · Score: 2, Informative

      WARNING, DANGER WILL ROBINSON

      This software is not fault tolerant and is not designed, manufactured, or intended for use or resale as on-line control equipment in hazadours enviroments requiring fail-safe peformance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air trafic control, direct life support machines, or weapons systems, in which case the failure of the software could lead directly to death, personal injury, or severe physical or enviromental damage --Microsofts typical phrasing quoted loosly from "Java support" segment

      --
      There is no sanctuary. There is no sanctuary. SHUT UP! There is no shut up. There is no shut up.
    2. Re:Someone help me out here... by Spamhead · · Score: 1


      That verbage is originally from Sun, not Microsoft. They had to include it in the license if they wanted to distribute a JVM. It's a leftover from so much Sun hardware being used in critical situations. I believe that they have removed that requirement from all current implementations (at least I couldn't find it in the current license.

      --
      Everybody Wang-Chung tonight!
  25. Re:In case of slashdotting by Azureflare · · Score: 2, Funny
    Government Worker #1: "Sir, it appears terrorists are attacking our servers. NASA just went down."

    Government Superior #1: "Were you able to trace it?"

    Government Worker #1: "No, it's coming from all over the place, sir! We can't stop it!"

    Government Superior #1: "Hmm... Perhaps... No, it can't be.. Not the dreaded SlashDotting..."

    *RED ALERT*

  26. Finally, NASA moves to open source! by Cereal+Box · · Score: 1

    NASA's software will have all the bugs it would've had under a closed source model, but at least the space shuttle's interface will have skins and GNOME support!

    1. Re:Finally, NASA moves to open source! by Anonymous Coward · · Score: 0

      the space shuttle's interface will have skins and GNOME support!

      Not sure what you meant in that light joke, but Gnome already has theme support, so using skins over it wouldn't be nice. Think about xmms's interface.

  27. Open Source is not GPL by Anonymous Coward · · Score: 1, Informative

    First of all open source is not GPL. Second promoting the use of it for nonessecntial stuff sort of makes sense, and chances are people are alreading using it and know it. TCP/IP comes to mind some parts of the internet to.

  28. Needless to say... by Otter · · Score: 4, Interesting
    The site www.nasa.gov is running Apache/2.0.45 (Unix) mod_perl/1.99_09-dev Perl/v5.6.1 covalent_auth/2.3 DAV/2 CovalentSSL/2.3.3 RSA/SSLC mod_jk/1.2.2-beta-1 on Linux.

    Like anyone waits for these reports to be written. At least it gave an intern something to do.

    1. Re:Needless to say... by Anonymous Coward · · Score: 0

      Pat Moran isn't an intern. I know, because I used to work at that very NASA site. It's been a while, but I think he works at the NAS division of NASA. (Here's a profile of the division.) I probably bumped into him at a few meetings, since the the NAS building was across the parking lot from my building.

      Anyway, not only does NASA's Ames Research Center use a bunch of open-source software, but they've been using it for a long time. When I got there in 1994, everything in my building that wasn't a Mac was all Unix stuff, with gcc, emacs, X11, etc., etc. (Well, except for a few old Symbolics LISP machines, and a MicroVAX that one guy couldn't bear to get rid of.) Mostly SGI and Sun equipment.

      In fact, we had exactly ZERO Windows machines in a building of more than 100 people. That changed when someone came up from NASA JPL and brought a Windows machine with him. He kept wanting to connect to our printers, etc., and we couldn't help him unless he could speak lpd or Appletalk. (I was a systems admin.) Supposedly NASA JPL is (or was then) the oddball NASA center because it didn't use lots of open-source software. But then, it's also supposed to be basically 100% contractors instead of NASA employees.

      Of course, that could all have changed, since I left there in 1997, but they have had a pretty good record of using open-source software.

      Not only that, but they've been a good Internet citizen as well. For a while, one of the root DNS servers was at NASA Ames Research Center, and I think it may have been in the NAS building. (In fact, I think NASA may still have one of the root nameservers. I remember talk of them giving it up, but I don't know if that every happened.)

      By the way, the paper was about releasing (some) NASA-developed software as open source. And that's not a new idea. For example, the batch-queueing system PBS was developed for the very same division of NASA (NAS) and released as open-source. And (before that?) was another batch-queueing system developed by NASA and released to the public, called NQS.

    2. Re:Needless to say... by Otter · · Score: 1
      Not only that, but they've been a good Internet citizen as well. For a while, one of the root DNS servers was at NASA Ames Research Center, and I think it may have been in the NAS building.

      Yup. In fact, my old DECnet email address was at nasa.gov before my department at UCLA got clueful enough to have their own domain and POP/SMTP system instead of whatever gateway voodoo they were doing.

  29. UGHH... by Anonymous Coward · · Score: 0

    Who friggin' cares about skins and 'GNOME support' - I sure as hell don't.

  30. We might be jumping the gun ... by McAddress · · Score: 3, Funny
    We might be jumping the gun here. Maybe someone said they are swiitching to X11 spacecraft and some geek presumed that that meant open source.

    just my personal theory.

  31. HA!HA!HA! HA!HA!HA! by Anonymous Coward · · Score: 0

    no.

  32. NASA is a big MS shop by saintjab · · Score: 3, Insightful

    I used to work for Microsoft and was asked to help NASA several times with support/dev issues they were experiencing. I've visited the Space Center in Cape Canaveral, as well as some other external NASA locations, and they are using a lot of MS technologies. This is definitely a step in the right direction for the Open Source movement, but NASA has a long way to go before any Open Source initiative has any real impact on their development. Don't get me wrong, I'm very excited they made this decision, but it's a very small step. Besides, NASA has an extremely rigorous testing campaign for all new hardware and software, so these changes won't be noticed for some time to come. Otherwise this is a great step forward for OSS and I'm very pleased to hear about it! When I was working with them there was a huge aversion to OSS and it gave me the impression that they were diehard MS. There may still be hope for America's space development!

    --
    "Reality is a crutch for people who can't handle drugs" - George Bernard Shaw (1856 - 1950)
    1. Re:NASA is a big MS shop by Anonymous Coward · · Score: 0

      > I've visited the Space Center in Cape Canaveral, > as well as some other external NASA locations

      Funny, I work at a NASA location, and the building I'm in is almost exclusively Solaris/Linux. Most of the secretary types use Macs. A few people use windows, but very few of the technical types.

    2. Re:NASA is a big MS shop by saintjab · · Score: 1

      I was working mainly on their nasa.gov web farm.. Which is all Windows 2000, using Windows 2000 based RAID filers, and MS SQL. Don't know where you work or what you do, and I'm not claiming to know everything about NASA, but I didn't see anything other than MS while I was there. There were of course some mainframes about, and some random dev boxes, but all the servers around me were MS based OSs. Then again, seeing as I was representing MS at the time, that probably had something to do with it. Anyway, this is good news for OSS and for NASA, as long as their interests continue and they don't abondon the idea.

      --
      "Reality is a crutch for people who can't handle drugs" - George Bernard Shaw (1856 - 1950)
    3. Re:NASA is a big MS shop by internic · · Score: 2, Informative

      I also worked at NASA doing astrophysics and bearly even saw a windows machine the whole time. A few individuals (mostly those who did outreach work for the mostly windows using public) has Windows and I think there was one public one for running Powerpoint. :) Other than that is was all Solaris/SunOS/Digital Unix for older computers and almost exclusively Linux and MacOS for newer computers. And most of the ftp and web servers there will also running on some flavor of *nix.

      --
      "You call it a new way of thinking; I call it regression to ignorance!" -- Operation Ivy
    4. Re:NASA is a big MS shop by spasm · · Score: 1

      If NASA has an extremely rigorous testing campaign, how the hell did MS get an exclusion?

    5. Re:NASA is a big MS shop by Anonymous Coward · · Score: 0

      It depends what site you were working at. Johnson Space Center is nearly 100% Microsoft and Kennedy was going that way. Microsoft did a clever thing by basically giving away licenses to the OS and Exchange back in the late 90's. Of course that didn't cover upgrade costs. So after both centers converted and then upgrades were necessary, both were hosed big time.

      Other centers like Ames and Goddard lean a bit more towards OSS and *nix, at least they did when I worked at Goddard. Of course there were lots of old Linux servers around running NCSA 1.5 too so it ain't no panacea. Every script kiddie on the planet was targetting us. I should know, I ran the network and spent a great deal of time pleading with people to tighten things up, but being a contractor I was mostly ignored. If if makes you feel better I never saw a non-*nix machine in the Space Operations Center.

      NASA has since outsourced lots of it's network operations. This is driving the move to Microsoft because its "easier." Outlook is such a great mail client.

    6. Re:NASA is a big MS shop by Anonymous Coward · · Score: 0

      I used to work at Space Telescope Science Institute, and I can tell you that the only people who were using MS then were the business office. All of the technical folks, all of the software developers were using Sun and DEC stuff (and yes, the last time I talked to them, less than a year ago, they were still using VMS). Maybe it was different at Cape Canaveral, but I'd be EXTREMELY surprised if anyone but the secretaries and business folks used it. The technical folks know better.

  33. Re:Sounds good by b17bmbr · · Score: 1

    X11 needs to be brought back to life.

    guess you didn't read yesterdays story

    --
    My problem? I was perfectly gruntled, until some numbnuts came by and dissed me.
  34. Re:Sounds good by rusty0101 · · Score: 1

    What do a new rocket, and ditching the shuttle have to do with a windowing system? I'm confused. :-)

    -Rusty

    --
    You never know...
  35. It was all good, until the MPL part. by RealAlaskan · · Score: 4, Interesting
    From the FSF's license page (about halfway down the page):
    The Mozilla Public License (MPL). This is a free software license which is not a strong copyleft; unlike the X11 license, it has some complex restrictions that make it incompatible with the GNU GPL. That is, a module covered by the GPL and a module covered by the MPL cannot legally be linked together. We urge you not to use the MPL for this reason.
    This means that any MPL program may be distributed with GPL software, but cannot be reused with it. That is, Mozilla and Linux may be distributed together, but you can't take any substantial code from Mozilla and use it to make Gimp better.

    I just can't see how this particular choice of license makes things better for the Linux community. NASA seems to be deliberately slapping us in the face with this.

    It seems, from the PDF document (page 8) that their intent is to enable commercial exploitation of their code:

    The Mozilla Public License (MPL) attempts to strike a middle ground between promoting free source development by commercial enterprises and protecting free source developers. Like the GPL, it requires that any and all changes to code (derivative works) covered by the license must be made publicly available. [snip]
    I think that since I've paid once for this proposed code, through my taxes, that there's something fundamentally wrong with allowing NASA to give the code to a business which will ask me to pay for it a second time.

    I'm sure that NASA hopes to collect a fat bribe ... no, a fat license fee ... no, a ``contribution to the Space Program''. That's what I said above, in the preceeding paragraph: this robbery is motivated by a desire to gouge me a second time for the work I paid for once.

    1. Re:It was all good, until the MPL part. by no+reason+to+be+here · · Score: 1

      So, the mozilla developers slapped the linux community in the face when they wrote the MPL.

      Would you react this way if NASA had decided to release all of the code under a BSD-type license, creating essentially the same situation, but without quite as much benefit to NASA? Before you answer, please keep in mind that most gov't projects that release source code do so under a BSD-type license. Some would argue that such a license makes the most sense for gov't projects, since it is the most "free" (i.e., puts the least amount of restrictions upon others) license available.

    2. Re:It was all good, until the MPL part. by RealAlaskan · · Score: 3, Insightful
      So, the mozilla developers slapped the linux community in the face when they wrote the MPL.

      I'd say that the only difference between Mozilla developers and NASA is that the Moz developers paid their own way, while NASA has been funded by me (and you too, if you're in the US). That gives me a right to criticise NASA which I really don't have for Mozilla. The vital difference is that when the Moz developers license their code, it's really their code. When NASA licenses ``their code'', it's partly mine, in the sense that you and I paid for it.

      I think there's one other difference, too: didn't Mozilla at least attempt to dual-license, using MPL and GPL? So, I'd say that NASA is morally bound to behave better than this, and isn't living up to their moral obligations, while the Moz team has behaved rather better than they absolutely had to.

      Would you react this way if NASA had decided to release all of the code under a BSD-type license, ...

      No. The BSD license, or public domain, would allow us to actually USE the code we paid to develop, in the sense of incorporating it into our own works. The MPL precludes that sort of use. That's what makes it a slap in the face of the Linux community, specifically.

      ... creating essentially the same situation, ...

      In essence, the situation is totally different, as I just explained.

      ... but without quite as much benefit to NASA?

      Here's an important but apparently subtle distinction: NASA exists to serve the US citizens, and is funded by them. NOT ``We exist to serve them, and fund them.''

      Again, I, and every other citizen, have paid for the work NASA has done. We should be allowed to make use of it on equal terms. GPL licensing would allow that: everyone could use the work equally, and no-one could obtain a monopoly over it. We start equal, and stay that way. That's fair to all. RedHat and Cygnus and Trolltech show us that you can build a business on the GPL, and IBM and others have shown that existing megacorps can profit from the GPL.

      A BSD-style license would allow authors of GPL'd software to reuse the code, but would allow, at least potentially, someone to obtain a monopoly using the code. I object to that.

      The MPL has at least the same problems as the BSD licese, plus at least the additional problem that MPL'ed code cannot be linked to GPL'ed code. I keep saying ``at least'' because unlike the GPL, the MPL is full of lawyer-speak, and will require long and careful parsing, with a copy of Black's close at hand.

      I object to using such a license as the MPL for code for which I have been forced to pay. The GPL seems an acceptable choice for code which we have ALL been forced to pay for, with the BSD license running a very distant second. MPL really isn't in the running, as far as I'm concerned.

    3. Re:It was all good, until the MPL part. by ryants · · Score: 1
      That is, Mozilla and Linux may be distributed together, but you can't take any substantial code from Mozilla and use it to make Gimp better.
      Mozilla is actually available under serveral licenses at once:

      Mozilla licensing is a "dual" (or even "triple") license scheme... to quote:

      At the moment, parts of the source are available under either the Netscape Public License (NPL) or the Mozilla Public License (MPL), often in combination with either the GNU General Public License (GPL) or the GNU Lesser General Public License (LGPL), or both. mozilla.org is working towards having all the code in the tree licensed under a MPL/LGPL/GPL tri-license
      So what you're saying may be true for MPL-ed code, but Mozilla isn't (strictly) MPL-ed.
      --

      Ryan T. Sammartino
      "Ancora imparo"

    4. Re:It was all good, until the MPL part. by Anonymous Coward · · Score: 0

      Yep. I mentioned this in a followup to my original post. That's part of why it's a slap in the face when NASA does it, but not when Mozilla does it.

    5. Re:It was all good, until the MPL part. by IcePic · · Score: 1

      No. The BSD license, or public domain, would allow us to actually USE the code we paid to develop, in the sense of incorporating it into our own works. The MPL precludes that sort of use. That's what makes it a slap in the face of the Linux community, specifically.

      Well, you'd be able to use it REALLY REALLY much,
      if you just license your stuff in an MPL-compatible
      way, exactly as with any other free/open license.
      You may use it if your license is compatible, otherwise
      not. So your bug-up-the-ass is that they chose one
      that you didn't use yourself. Tough luck.

      --
      -- I'm as unique as everyone else.
    6. Re:It was all good, until the MPL part. by Anonymous Coward · · Score: 0
      The vital point here is that I've already paid for the software NASA has developed. I don't see anything unreasonable in asking to be able to use, freely, this software I've paid for.


      If you write something on your own nickle, you can do whatever you please with it. When someone else has paid you to do it, the situation is radically different: the Golden Rule applies. The one(s) who supply the gold make the rules. That's us taxpayers.


      NASA's work is work for hire, done for us and at our expense, and I find it obscene that they would try to lock out so many potential users and contributers. It's doubly obscene because those potential users and contributors have paid at least their fair share of the bill in the first place.

  36. in other news... by Beatbyte · · Score: 5, Funny

    43 more moons were discovered orbiting Jupiter. All of which are now named Firebird.

    1. Re:in other news... by sean23007 · · Score: 1

      Except for one, which is to be named Phoenix. This will be used to browse the Interplanetary Internet. Wailing and gnashing of teeth is scheduled to begin at the second syzygy after the hour.

      --

      Lack of eloquence does not denote lack of intelligence, though they often coincide.
  37. Free scientific software is commonplace already by Anonymous Coward · · Score: 1, Informative

    For example, the SPICE library or various treecode programs for n-body simulations. So this is nothing new, though it is certainly welcome.

  38. Short summary of MPL quoted from the NASA Report by HighOrbit · · Score: 1

    Here is a cut-n-paste contrast-compare from the NASA report:

    The Mozilla Public License (MPL) attempts to strike a middle ground between promoting free source development by commercial enterprises and protecting free source developers. Like the GPL, it requires that any and all changes to code (derivative works) covered by the license must be made publicly available. However, it also allows you to combine covered code with other code to create a larger work without requiring that other code to be covered by the license. This is similar to, but even less restrictive, than the LGPL

  39. They already use open source software by witten · · Score: 3, Informative
    I used to work at NASA Ames, starting back in 1996. On a daily basis, I used Perl, Apache, and all the GNU tools I could get my hands on. And this wasn't just a lone coder using this software either. Everyone on the project used open source software either directly or indirectly.

    So it's really great that some people within NASA are making a more formal push for open source software, and are even discussing releasing some of their own, but open source within NASA is hardly new!

  40. Re:Thai Minister Link by pHDNgell · · Score: 1
    --
    -- The world is watching America, and America is watching TV.
  41. Sorry... by Anonymous Coward · · Score: 0

    ... when I first read the "Subject Line" of this thread I thought it said:

    We might be humping the gnu

    ;)

  42. easy question by uncadonna · · Score: 1
    Think where we'd be if everything ever discovered by NASA using taxpayer's money was patented and copyrighted as "Intellectual Property"

    No more Tang, right?

    --
    mt
  43. And the european program...... by botzi · · Score: 1

    Well,
    I hope europeans (Ariane or whatever), will also consider switching to some OSS or similar license.....
    Oh wait... it doesn't really matter.... they should first quit the tests on using floating point numbers in incompatible registers.....or the take off will definnitely be a problem.....

    --
    1. No sig. 2. ???? 3. Profit!!!
  44. How about this? by BigBir3d · · Score: 4, Interesting

    Why not advocate choosing the best possible package? Who cares if it is open / closed / hybrid source, as long as it functions properly?

    1. Re:How about this? by mackstann · · Score: 1

      This is slashdot, remember? Such logic does not exist here. But linux rulez dude! Go GPL!

    2. Re:How about this? by djcinsb · · Score: 1

      Well, one serious issue that NASA runs into is determining what the best possible package is. To do that for missions that have not been flown before, the mission analysts would like to know how core pieces are implemented. In a closed source world, that information is difficult to obtain from the vendors. And "just trust me" doesn't cut it.

      --
      A signature always reveals a man's character - and sometimes even his name. -- Evan Esar
    3. Re:How about this? by extrasolar · · Score: 1

      Because I want to see how this software works that NASA is using.

  45. Mod parent down... by b0r1s · · Score: 2, Informative

    But when contacted by CNETAsia, a spokeswoman from BMW Thailand said the car at fault was a 10-year old BMW 520i that had suffered a simple electronic failure. She declined to reveal if the firm received identical reports from other users in the country.

    You can't complain about Microsoft FUD when the Anti-Microsoft FUD is just as bad.

    --
    Mooniacs for iOS and Android
    1. Re:Mod parent down... by Anonymous Coward · · Score: 0

      Yes you can. They stazrted it, they have the better position and they have the money to buy laws.

      When they lose that, THEN we can complain about Anti-MS FUD.

      And it isn't FUD anyway, it may be wrong or anecdotal, but not FUD

    2. Re:Mod parent down... by b0r1s · · Score: 1

      You think that claiming WinCE computers are responsible for people being trapped inside cars doesn't constitute as "Fear" or "Doubt" (the F and D in FUD)?

      If nothing else, the fact that it was modded up to 5 qualifies it as spreading "Uncertainty."

      Yes, it's FUD. It may not be intentional, but it's still FUD.

      --
      Mooniacs for iOS and Android
  46. They just switched to Windows by ArhcAngel · · Score: 2, Informative

    If memory serves there was a big stink about NASA (Johnson Space Center Houston) switching their administrative desktops from Macs to Windows just a few years ago. If they kept all of the Mac hardware they could probably ressurect them as Linux terminals.

    --
    "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
  47. Nice to hear about this, but I doubt... by vought · · Score: 3, Informative

    that Dan Goldin, a.k.a. "the man who replaced all the Macs" at NASA would stand for it. He is FIRMLY in the Microsoft camp, and in 1997 appeared as a booster in Microsoft advertisements for Windows NT 4.0.

    Goldin replaced perfectly good I.T. infrastructure with Microsoft equipment in the name of standardization; it says a lot about the entrenched bullshit beaurocracy at NASA that he rose so meteorically through the ranks at the Space Administration.

    1. Re:Nice to hear about this, but I doubt... by orac2 · · Score: 2, Informative

      Well, if Dan Goldin was still NASA Administrator you might have a point, but Sean O'Keefe has been in charge for about, oh, 18 months now...

      Also, Goldin didn't rise through the ranks at NASA. He came over from 25 year career at TRW to head up the agency, although he had worked at NASA in the early 1960s.

      --
      "Just once, I'd like to meet an alien menace that wasn't immune to bullets." -- The Brigadier, Dr. Who
    2. Re:Nice to hear about this, but I doubt... by NeoNormal · · Score: 1

      And where is Dan Goldin now? Ever heard of Sean O'Keefe?

    3. Re:Nice to hear about this, but I doubt... by vought · · Score: 1

      Whoops. My bad. Could've sworn I saw his name mentioned in context as administrator very recently.

      My apologies for besmirching NASA's golden reputation by associating his name with that fine space agency.

    4. Re:Nice to hear about this, but I doubt... by NeoNormal · · Score: 1

      Well unless you have NASA Television or go out of your way to find out stuff about NASA, you're excused for not knowing. NASA, unfortunately, seems to only get press when it's bad press.

      As for myself, I spend waaaaay too much time watching NASA TV ;-)

  48. Re:Have a fun weekend with this list by Anonymous Coward · · Score: 0

    Stab the clown with a big knife. Blood will ooze out everywhere.

  49. MOD PARENT DOWN by Anonymous Coward · · Score: 0

    I didn't want to know that yet!

  50. Re:NASA is obsolete by the1brian · · Score: 2, Interesting

    Manned spaceflight and new civilization on Venus? Would you volunteer for this? Venus is the hottest planet in the Solar System, with an average surface temperature of 854.33F. In addition to this, it's atmosphere is a poisonous combination of sulfuric acid and Carbon Dioxide. It is completely unihabitable, several, if not most of the unmanned probes we have sent there have just completely melted, and you want us to send someone there? How about you go to Venus. Now, Mars is a possibility. The main limiting factor right now keeping us from going to Mars is the distance. Then again though, the reason NASA hasn't sent anyone there yet it lack of money, and as someone else has already said, do you think a private corporation is going to send someone there, when there is little or nothing for them to gain out of the billions, possibly trillions of dollars they would have to spend on it?

    --

    ~Brian
  51. MPL by orrinrule · · Score: 1

    As I am currently doing my senior seminar project on various open source licenses and intellectual property. I am guessing that I will advocate MPL as opposed to GPL or any other license. It is very liberal open source, yet is still favorable from a business standpoint.

  52. What LOC? by JaseOne · · Score: 1

    Lines of Code is the only measurement that matters with OSS isn't it?

    1. Re:What LOC? by juan2074 · · Score: 1

      I can see it now:
      Sir, we have replace all the Space Shuttle code with a single-line of Perl script.

    2. Re:What LOC? by vsprintf · · Score: 1

      I can see it now: Sir, we have replace all the Space Shuttle code with a single-line of Perl script.

      That's ridiculous. It would take an entire Perl module to replace all that deprecated, legacy code.

  53. News at 11. by torpor · · Score: 1

    NASA reported today that a software bug in their ODEEFUS hiring software system, a module intended to convert from metric to feet, has resulted in nation-wide employee panics, stupidity, and hysteria.

    This marks the 2nd (or, in NASA terminology, 1.99996th) time that such a software bug has occurred. A NASA official, who asked not to be named, said that "It was just a lousy misplaced colon".

    --
    ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    1. Re:News at 11. by Anonymous Coward · · Score: 0

      A misplaced colon can be painful. Ask your doctor.

  54. Mod parent up! by Anonymous Coward · · Score: 0

    Mod grandparent down. That such FUD continues to be modded up as interesting on /. is disturbing.

  55. Surprised? by tundog · · Score: 1


    It doesn't take a rocket scientist to figure out that OSS makes sense for government projects.

    --
    All your base are belong to us!
  56. Free Software Reviews by CyberGarp · · Score: 1

    I know someone who is obsessed with reading source code. He keeps printouts in his bathroom for some light reading. He knows the Linux kernel inside and out. He regularly submits patchs all over the place. He would drool over the idea of reading code for satellites and the shuttle.

    An old ledged has it that Djkstra saved the Apollo moon landing, because he happened across some code at NASA and questioned a minus sign in the thrust calculation. Turns out that the lander was set to thrust into the moon and not away from it on landing. I don't know if this story is true or not, or how distorted this nth retelling is, but it makes one think how many bugs could be caught by open sourcing. There are those who would love to read the code.

    NASA's process relies on many many code audits, it only makes sense to get a few for free.

    --

    I used to wonder what was so holy about a silent night, now I have a child.
  57. Haven't they done this already? by larien · · Score: 1
    IIRC, the code in some of the network drivers in the linux kernel have been written and/or modified by NASA in the past. Also, they also started the Beowulf stuff giving rise to all those wonderful "imagine..." posts we get round here.

    The more imaginative may notice a link here; essentially, NASA needed good networking in their Beowulf nodes, so they tweaked the drivers.

  58. Getting tools open sourced from NASA by owenomalley · · Score: 5, Insightful
    I work at NASA/Ames as a senior software engineer in the Automated Software Engineering group and I reviewed Patrick's report a month ago. Patrick's report is the result of his efforts to convince management that it would be a good thing to release the scientific computing software that he had written to the public.

    I am in a research lab working on software engineering tools and most of us would love to release the tools that we develop as Open Source. Unfortunately, we need to get the administration's support. (We've been trying for over a year on a software model checker named Java Path Finder and haven't had any luck yet.) We have other stuff like an C++ AST language model (in XML/Java) that we are currently developing that would also be nice to release.

    I can understand the administration's desire to keep the software ownership for itself, but the greater good would be for us to release the tools under GPL. Especially, since the opportunities for commericialization are much more limited than they were a few years ago. Releasing the tools as Open Source would make them available to many more people and dramatically increase the impact of the work. A further complication was mentioned in the report is that we have a lot of contractors (~40%?) and the IP ownership is determined by the particular contract. *sigh*

    We also use a lot Open Source code, including linux, x11, xemacs, ssh, gcc, cvs, etc. and it would be nice to give something back to the community.

    1. Re:Getting tools open sourced from NASA by retiarius · · Score: 2, Interesting

      let's wax nostalgic for the pre-berne convention
      days (1988) where, given usenet, at nasa ames
      we never asked for management permission.

      at least that's how 'fastfind' (1983) (now the
      new-fangled 'slocate'), 'compress' (1984),
      and '[ef]?grep' (1986) snuck out of there.

      copyright scholars note that when the
      states adopted berne, things became instantly
      copyrighted "when fixed in a tangible medium
      of expression". before that, actual registration
      was necessary to preserve rights, so few
      managements and even fewer programmers bothered.

      most famously, r. crumb saw his "keep on truckin'"
      art get converted to rubberized 18-wheeler
      mudflaps this way...

      ames!jaw

      p.s. hey, sorry for all that trouble with sperry/unisys!

    2. Re:Getting tools open sourced from NASA by stephanruby · · Score: 1
      "A further complication was mentioned in the report is that we have a lot of contractors (~40%?) and the IP ownership is determined by the particular contract. *sigh* "

      Why the "sigh"? When we use Microsoft Excel or the Java VM -- we don't necessarily own all the Intellectual Property related to it. Why should it be any different for NASA? It sure would be nice if NASA could reinvent or repurchase all the commercial software in the world, but it sure wouldn't be practical.

  59. Open Source Nasa Software. by Lakers · · Score: 1

    I'm not a big follower of the space program itself, but common sense seems to lend itself to this idea. One would think that if NASA's software was open-sourced and being contributed to by people all over the world, it would greatly reduce the number of million dollar mishaps. This wouldn't help with hardware problems (malfunctioning sensors, etc...) but I strongly believe this move would make our space program that much better.

    I truly hope this isn't a public relations ploy to take attention away from the shuttle disaster. I hope that this is a smart move to help keep a similar event from happening again.

  60. Now I know... by MrTangent · · Score: 1

    Now I know why I've always loved NASA.

  61. Fiddling while Rome Burns by Anonymous Coward · · Score: 0
    A new technical report from the NASA Ames Research Center advocates the adoption of Open Source Software internally by NASA for some projects.

    How nice. NASA is worried about whay _kind_ of software to run when they SHOULD be worried about exploring deep space, allowing private enterprise to manage Shuttle and Shuttle II and their myriad Operational Failures.

    I can't find the energy to be enraged.

    Clap. Clap. Clap. Good!

  62. open source, but the story is PDF by Cheeze · · Score: 0, Troll

    Why use a closed source media such as PDF when the article is about using open source software?

    wouldn't html be much easier and faster (less bandwidth) than using a PDF?

    just doesn't make sense.

    --
    Why read the article when I can just make up a snap judgement?
    1. Re:open source, but the story is PDF by Anonymous Coward · · Score: 0

      Adobe's PDF spec is a completely open spec.

    2. Re:open source, but the story is PDF by istartedi · · Score: 2, Interesting

      1. Go to SourceForge and search for PDF
      2. ???
      3. Profit.

      BTW, if you don't like the licenses and/or the code available there, do what I did: get the PDF spec and "clean room" it. The spec is, for the most part, quite lucid. I've probably spent 50-60 man-hours digesting the spec and coding. I've got scalable graphics working nicely now. That was all I really wanted, but now that I'm familiar with it, text and images are just an incremental upgrade. I've coded for text, but I haven't tested it. Inline images will require you to link in some encoding and compression but once you've done that it's all good.

      I agree with you that HTML is much better for screen viewing. PDF is for printing, not screen-viewing. Improper use of PDF on the web has probably killed as many trees as Dutch Elm disease. Adobe's crappy free viewer pisses me off. It defaults to jerky page-viewing. I switch to "continuous" and whenever I move, it leaves bit-barf on the screen, and if I allow it to embed in IE it crashes half the time. The open spec almost makes up for that. Try doing a Google search to find the document. Google will sometimes provide an HTML version of PDFs.

      --
      For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
    3. Re:open source, but the story is PDF by Anonymous Coward · · Score: 0

      There are open source ways to make PDFs. The report looks like it was made with Latex (open source), and you can create PDFs from that using dvips and Ghostscript.

      Hmmm, if you look inside the PDF, you can find "/Producer (GNU Ghostscript 6.51)".

    4. Re:open source, but the story is PDF by Anonymous Coward · · Score: 0

      Can you please know what you are talking about before you start blabbering and complaining? Thank you.

  63. JON KATZ, WHERE ARE YOU? by Anonymous Coward · · Score: 0

    Have you been imprisoned for molesting little boys yet, or are you still one step ahead of Johnny Law?

  64. In other news by Anonymous Coward · · Score: 0

    A User was reportedly using Linux.

  65. A long-term issue by real+gumby · · Score: 3, Interesting

    NASA Ames was Cygnus's first customer back in 1989. Support for GCC, GDB and the binutils. I know, I signed the contract.

    Most of the parts of NASA that aren't politicized are really very good. NASA will go for anything that really gets the job done.

  66. It's more about publishing software than using it by JacobKreutzfeld · · Score: 3, Insightful
    Most of the discussion here has focused on NASA using OSS but it IMHO misses the point. The author is talking about publishing or releasing NASA-developed code, and what types of licenses are compatible with NASA's federally-mandated mission. NASA develops quite a bit of code, including generally-useful tools as part of larger projects. It would be great if this was easily accessible to the public.

    It's disappointing seeing how much bureaucracy I'd have to go through to release our secure HTTP and CIFS proxy/portal. We don't have time to work on it any longer and superior commercial products exist now. So why not give our code away, let interested hackers turn it into something really cool. But it would be a nightmare of approvals, especially his citation from the NASA Procedures and Guideline ( http://nodis3.gsfc.nasa.gov/library/displayDir.cfm ?Internal_ID=N_PG_2210_001A_&page_name=main&search _term=2210 )

    This release category indicates there are no export restrictions on the software and should be approved with great care and requires concurrence by Agency Export Control officials.
    I don't expect officials are really gonna want to read our code to ensure there's nothing of value to cryptoporn terrorists.

    So the code with just languish in our CVS repo, and die due to lack of interest. :-(

  67. NASA has been there for a while by einhverfr · · Score: 1

    Imagine a beowulf cluster of these....

    Well, NASA did, and hence we can make that crummy joke. Don't believe me? Check your Beowulf cluster history ;)

    The fact remains, NASA has been involved open source software for a while and actually were the ones that contributed the idea of node-based parallel computing when they built the Beowulf project as a supercomputer on a budget.

    --

    LedgerSMB: Open source Accounting/ERP
  68. More "impressive" name for Americans by Ra5pu7in · · Score: 1

    About the only way this is a coup for OSS is that most Americans could care less if some other country they can't find on a map makes a decision to go open source. (Seeing as how many can't find Canada on a map, let alone a state they don't live in, this makes sense.)

    --
    I was taking one day at a time, but then several days got together and ambushed me. (from a Rhymes with Orange comic)
  69. Everyone knows... by jmv · · Score: 3, Funny

    ...it's just a plan by NASA to get Microsoft to pay for a new Shuttle program.

    1. Re:Everyone knows... by crusher-1 · · Score: 1

      More likely they want to get in on some of that free money and upgrades M$ has been passing out to the other foreign governments and agencies. :)

  70. GPL by Anonymous Coward · · Score: 0

    Wouldn't it make more sense for NASA to use a free software license? It seems that the GPL would be more compatible with the goals stated in the report. And, as someone else stated, we have already paid for it's development, so why not ensure that it remains free (as in freedom)?

  71. That's what we DON'T need by ssajous · · Score: 1

    Great after the way it was revealed that things do not work as smoothly over there as most of us believed now they are going to use software whith no, very little or very confusing documentation and no support. :)

  72. SCO suing Nasa? by mwing · · Score: 1

    Wasn't Nasa also involved in the development and testing of NSA secure Linux ?

    Does this mean that SCO is going to sue the government too?

    1. Re:SCO suing Nasa? by crusher-1 · · Score: 1

      Give them a chance, it's still early! There too busy catching up with the list of who's currently using OSS. No doubt they'll be taking scheduled breaks from their "strategy" meetings to update the list so they can figure out who else they may want to have served a summons.

  73. Internationally? by Anonymous Coward · · Score: 2, Interesting

    At work (I'm a scientist) we wanted to use some software developed by NASA. It was available for 200 hundred dollars, which is fine. What isn't fine is that in the end we couldnt buy it because our lab is based in the UK and thus "our tax dollars" hadnt gone into its creation.

    No great shakes, I wrote my own version over a weekend (which tells you something about how sensitive or proprietry this stuff was, *and* it was about 12 years old) but it was a weekend I would rather have had off work.

    Point is this, I'll be impressed with this change if it means that NASA will be conforming with the standard scientific practices of sharing data and (within reason) tools as most European researchers do as a matter of course.

  74. Re:NASA is obsolete by Anonymous Coward · · Score: 0

    Don't worry. There will always be a place on Earth for lazy bastards like yourself who are too afraid to explore the unknown. If our forefathers hadn't taken a chance and set out into the vast Atlantic ocean America might still be a continent infested with primitives.

  75. NASA has multiple charters? by bstadil · · Score: 1
    Why not advocate choosing the best possible package?

    Even if such a thing existed, NASA is public funded and has a duty to promote science and understanding. Using open source SW and contribute to FOOS, dovetails with that charter. Buying closed source does not.

    --
    Help fight continental drift.
  76. as a matter of fact, YES... by zogger · · Score: 2

    ..YES, I see no problem with the first humans there to claim it, and also declare their independence. This deal where only the currently established nations are IT, like no new ones are "allowed" some how, is bogus. I can see a group of investors and pioneers claiming mars, why shouldn't they? If no one else wants to go there, and they expend the energy and cost and take the huge risks? I see no moral claim to the current monopoly holders, none, hardly a nation out there that has the same borders it started out with. And I'll go further, NASA and the US government doesn't "own" space, it's none of their business if anyone decides to travel there. I think if someone can come up with a launching place someplace that the trajectory doesn't interfere or pose a risk to other people, say out over the 'free" ocean, then that's their lookout then. Launch away, and don't ask NASAs permission. This is like when they tried to squash space tourism, ta heck with that noise! Adventure, tourism, that's part of what builds exploration. It's not all of it, but back through human history a lot of places got explored almost just "because", it's what adventursome people DO. Ya, they would look for sponsors back then, swell, we can still use that technique. As to who, no idea, but I bet a nickle you could get interest in it. shares? How about colonize mars shares? buck a apiece? who knows, someone IS going there, I hate to have it only the few big governments we have now though, seems sort of bogus, because none of them are really all that great.. they mostly suck. US, china, russia, etc, none of them have a great track record, except exploitation.

    When the explorers and pilgrims came to north america, they just really wanted to be free, to be rid of the old kings and weirdness, to just have a chance to start over, be themselves. Not perfect, not by a long shot, but that was a major part of it. Some were just looters and mercenaries and soldiers from some bogus regime, but a lot more were just.. pioneers. Space is the same deal. And I'd rather it was free of current established government controls and manipulations if at all possible. Dangerous and expensive? Yes! That's part of adventure! Risks and maybe some rewards? You bet, that's great!

    And the MAIN deal to go there, what the reward is-it's ANOTHER PLANET, it's *not* "the earth".

    We done ran out of continents to discover and colonize, you can't even colonize antarctica, because the monopoly governments all said "no mining", which you would need to do to live there full time, just to have adequate energy and raw materials, and they would send their bogus militaries to kill you, so that's out. Space, the deck might be stacked more evenly. Maybe,maybe not, but we won't know unless we try, and my guess is, humans will try it. I just hope it's free and independent humans, that's all.

  77. Hypocrites by Anonymous Coward · · Score: 0

    Now that would be nice, but maybe they should start doing it with their own software instead of trying to sell it.
    <A HREF="tco.gsfc.nasa.gov">tco.gsfc.nasa.gov</A&g t;

  78. Re:NASA is obsolete by Anonymous Coward · · Score: 0

    I wish your forefathers were lazy bastards, then they wouldn't have mated and brought out such a bigoted asshole like you.

  79. New Project: OpenSSHuttle by SoulDrift · · Score: 1

    "Only two security vulnerabilities in 17 years!"

  80. Can public domain code be subjected to any license by donheff · · Score: 1

    I concurred in the release under a modified BSD style license of a Java Application Monitor developed for the US General Services Administration by a Sybase software engineer. At the time we were not clear about whether Government owned software could be released uinder an open source license and never fully resolved the issue. It was not clear whether this software was fully "Government" software or whether the engineer or Sybase had IP interests in it. The engineer, with concurrence from me and Sybase, ultimately released it under the above described license because that seemed to be the best way to allow others to use it and not abuse it.

    It is still not clear to me whether the Government really has the right to limit use of its code under any sort of license. As others have pointed out here, and as the NASA software release guidelines state, most non-classified Government software is viewed as being in public domain. It would seem that anyone could ask for and (eventually) get such code through a Freedom of Information Act request. They would then be free to do anything they wanted except copyright the material -- use it for themselves, publish it, sell it, modify it, whatever. Any restrictions on use of the code such as are imposed by OS licenses would seem incompatible with the public domain nature of the material. It is trully free to use or abuse. It may be that the Government needs legislation to limit use of its software with an open source license.

    Any Government lawyers out there with an IP background?

    Don Heffernan

  81. Slap in the face? by mindstrm · · Score: 1

    If they decide to release *ANY* of the code they wrote under a license that lets you use it at all, you should be happy.

    How is it a slap in the face? IF it's *derived* from GPL code, obviously it has to be GPL. IF it's NOT, which is more likely the case, ie: It's their own original code, what right do you have to bitch about how they release it to you?

    Just because they used linux?

    1. Re:Slap in the face? by Anonymous Coward · · Score: 0
      IF it's *derived* from GPL code, obviously it has to be GPL. IF it's NOT, which is more likely the case, ie: It's their own original code, what right do you have to bitch about how they release it to you?

      I paid for it. So did you, if you pay taxes in the US. What right does NASA have to try to lock me out? What right does NASA have to give someone else a monopoly on the code I paid for?

      It's `` ...their own original code ...'', WHICH I PAID FOR. That gives me every right to comment on their licensing scheme.

  82. phuh by Anonymous Coward · · Score: 0

    yawn. What a stupid idea.

  83. Revolution OS by generationxyu · · Score: 1

    if you've seen Revolution OS, which is a pretty good flick to begin with, Bruce Perens (leader of the Debian project) talks about how he got an email asking how to use some sort of serial console with debian. he played with it, got something to work, and replied to the guy's post. the guy wrote back "Thanks, that works! I'll use it in the Space Shuttle." so there ya go.

    --
    I mod down pyramid schemes in sigs.