The point is not that the code be somewhere safe in case of disaster, rogue employees, or loss of a backup, but rather that the code be legally accessible by customers in the event that the company abandons, for whatever reason, its ongoing maintenance.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> And there's the pleasant thought of the day!!! ;-) I am willing to pay my share of the flight insurance for (where the heck are they this weekend - Plano Texas?) but somebody else needs to pitch in for the next rally, okay? Personally, I don't think they should ever travel together and we should have some skin flecks from each of them in case we need to clone one of them down the road. We should also ask them if we make more of them if it would help production or slow it down. Hmmmm. ??? In addition, I'd like to take odds on which one, Eric or Wayne would go rogue first, assuming Lisa has not been overworked in their absence of late. That's the wild card in this deal. 73, de my call at yaoo dot com 73, Don RE: [Elecraft] K2: Firmware Escrow from [Craig Rairdin] [Permanent Link][Original] To: "'Elecraft'" <[email protected]> Subject: RE: [Elecraft] K2: Firmware Escrow From: "Craig Rairdin" <[EMAIL PROTECTED]> > It's called Disaster Preparedness..... You guys are all missing the point of the original post, which was excellent by the way. _______________________________________________ Elecraft mailing list Post to: [email protected] You must be a subscriber to post to the list. Subscriber Info (Addr. Change, sub, unsub etc.): http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/subscribers.htm Elecraft web page: http://www.elecraft.com
