Making something available to US Citizens obviously does not mean you have to make it available to every citizen of the world, unless you think it is the responsibility of our government to provide for the world, which it appears you do.

Make it no different than any other form of federal aid, they apply, they might receive, but not if they're an illegal alien, much less living and working in Iran or North Korea.

Why do you keep insisting on giving them equal access to our own citizens, they certainly didn't pay any of our taxes, and might use the technology against us or our allies militarily.

You're incredible, you know that? Can't see the forrest for the trees.

Listen up; the technology genie is long out of the bottle, and by sharing little ideas like Beowulf, they can grow bigger and better. I know you want to lock up all information here in the US, cause we all know that the poor dumb basterds in the rest of the world couldn't scratch their ass' unless we showed them how to do it.

I suppose NASA shouldn't work with and share ideas with Russia's space agency. I mean what could we possibly learn from the folks that first put a satellite, dog, and a man in orbit, and built and operated the first permanantly manned space station, and set endurance records for a man in space.

Nope you're right, we should be sharing anything with them. Nothing to see there, please move along.

And I guess any and all military, economic and political ties we have with friends and allies around the world should be out too. What do we have to learn or gain from such endevours. After all, we wouldn't want any of our ideas to find their way out of our country. No tangible bennefits from them at all.

Ummm.... in such a light; shouldn't your boy Bill; master of all that is holy, pull back from outsourcing code work to places like India? I mean, sure all the code work done there is covered by confidentiality agreements, and M$ patent lawyers are submitting applications for every line of code ever written (in the history of the world if they could) by their Indian development center, but the ideas and methodologies those coders learn from doing that work will be with them for the rest of their lives, and might - God forbid - spawn new ideas and methodologies that might find their way into (the horror) other products from other companies in other countries.

We're DOOMED!!

Oh and since the subject of NASA and computing came up, well I hesitate to share this with you; I wouldn't want to to have an attack or anything.... This is from last year. It was an open conference. My God, do you know how many foreigners could have attended. I mean, who are these people to share our state secrets with others of like mind.

SEW-29

29^th Annual IEEE/NASA Software Engineering Workshop

Greenbelt Marriott Hotel, Greenbelt, MD, USA

6-7 April 2005

(Tutorials 3& 8 April 2005)

Co-located with 12^th Annual IEEE International Conference on Engineering of Computer-Based Systems, http://sel.gsfc.nasa.gov/ECBS2005, as part of Systems and Software Week

Sponsored by NASA Goddard Space Flight Center, Software Engineering Laboratory

IEEE Computer Society, Technical Council on Software Engineering

Background

The 29^th Annual IEEE/NASA Software Engineering Workshop will be held at the Greenbelt Marriott Hotel, Greenbelt, Maryland, in Metropolitan Washington DC, 6-7 April 2005, as part of Systems and Software Week

Scope

[Emphasis added for GE] The workshop aims to bring together NASA technical staff, contractors, academics and industrial practitioners interested in the advancement of software engineering principles and techniques. The workshop provides a forum for reporting on past experiences for describing new and emerging results and techniques, and for exchanging ideas on best practice and future directions. Of particular importance is relevance to NASA’s mission and goals, and how techniques might be applied, or adapted for use, at NASA, or how NASA’s techniques might be used or adapted for more generic use. [ I'm sure you know that this is NOT the way scientists and engineers behave, it must be some secret conspiracy ]

Topics of interest include, but are not limited to:

Ø Metrics and experience reports

Ø Software quality assurance

Ø Formal methods and formal approaches to software development

Ø Software engineering processes and process improvement

Ø CMM and CMMI

Ø Requirements engineering

Ø Software Architectures

Ø Real-time Software Engineering

Ø Software maintenance, reuse, and legacy systems

Ø Agent-based software systems

Submissions

Both full papers (maximum 10 pages in IEEE format, or equivalent length in free format) and extended abstracts/ industrial experience reports (4 to 6 pages, free format) should be submitted electronically (plain-text, .doc, .pdf or .ps formats only, please) . A link to an electronic submission site will be available here shortly.

Deadlines

1 December, 2005	Full Papers and Extended Abstracts/Industrial Experience Reports Submissions
1 February, 2005	Notification to Authors
6-7 April, 2005	SEW-29 in Greenbelt
8 May, 2005	Camera Ready Copy due for Post Proceedings

Both full papers and abstracts will be reviewed by the Program Committee, and full versions of selected papers will be due one month after the workshop (8 May ,2005) to be included in the workshop proceedings that will be published by IEEE Computer Society Press. At least one author per paper will be required to register and present at the workshop.

Any inquiries should also be directed by email to Michael.G.Hinchey@nasa.gov; for faster responses, please include “SEW” in the subject line.

Tutorials

Tutorials will be held on 3^rd April and 8^th April; proposals for full-day and half-day tutorials should be sent electronically to Mike Stark, Michael.E.Stark@nasa.gov by 1 November, 2005.

Conference Organizers

Conference Chair: Mike Hinchey

Program Committee Chair: Margaret Caulfield

Finance Chair: Don Jamison

Registration Chair: John Cook

Tutorials Chair: Mike Stark

Publication Chair: Chris Rouff