Bruce, thank you for this explanation of the ITAR issues. It looks like AMSAT is at a fork in the road here regarding how to deal with it.
I see the positives of having an open-source policy as 1) AMSAT will be able to work with international partners, which would probably not be allowed under a proprietary ITAR policy. 2) It may help keep old satellites running in the future. AO-27 required an extensive software fix to be brought online. I'm not sure if this was open source or not, but having the software and hardware information public would definitely give more people a chance to develop solutions. 3) It's in the spirit of amateur radio and helps avoid debates regarding proprietary hardware and software, like the never-ending arguments over PACTOR.
I can see negatives as well 1) Manufacturers of space-rated hardware may want certain aspects kept private, and it might not be possible to easily find or make an open-source replacement. How extensive is the ITAR carve-out? If you use just one proprietary component, does that take you out of the carve-out? 2) It may force AMSAT to abandon long-standing relationships (whatever's in those NDAs), which could greatly affect ongoing projects.
I'd like to hear a response from those wanting to keep a proprietary policy. What about it outweighs an open policy? Would an open policy work, but maybe further down the road?
If AMSAT won't call BOD meetings to have civilized discussions, maybe we can do it over the BB :)
-Stephen, N8URE