From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Hans-Peter F. Oeste" Subject: RE: Node.js and it's future in debian Date: Thu, 3 May 2012 16:10:05 -0700 Message-ID: <025201cd2981$e0c46620$a24d3260$@shaw.ca> References: <20120501205524.GI30521@flying-gecko.net> <20120501215305.GA1250@burratino> <20120501221659.GA11430@flying-gecko.net> <20120502065003.GB2410@burratino> <20120502165031.GC7390@flying-gecko.net> <20120502171349.GA23806@burratino> <20120502200426.GF7390@flying-gecko.net> <4FA2A557.1080103@trinnet.net> <20120503170521.GD19468@flying-gecko.net> <20120503185129.GA18768@burratino> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120503185129.GA18768@burratino> Content-language: en-ca Sender: linux-hams-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Cc: node@packages.debian.org, nodejs@packages.debian.org, debian-hams@lists.debian.org, linux-hams@vger.kernel.org I thought I'd also chime in with one aspect that perhaps hasn't been articulated. This could have a huge impact in 'Health and Public Safety', a place where many hams use the tools and the debian distribution as an appliance. The node and ax25 package is used worldwide providing communications infrastructure that may people rely on in times of disaster and emergency, be it a forwarding of medical information to gain insight to people health problems to local floods or fires to events like Katrina. Hams often provide the backbone to the communications for these events. That they treat the Debian distribution as an appliance says that they trust the distribution to not break down, and this is something to be proud of. That they use it as an appliance should not be considered a stupidity,. Consider how many of us nowadays make changes to the engine in their vehicles themselves. Not many, it's done by enthusiasts. The package node and its attendant packages is an engine for many ham operators. So please, be very careful in your consideration in making changes. The ramifications could affect you personally inadvertently. If you are going to muck with it, please consider a phased in approach that gives warning of potentially at least year, if not longer, so that warning is give and propagated to the mentors that these ham operators use, so that customizations can be 'fixed' and any migrations and mitigation is flawlessly executed. This may mean that you yourselves may be asked to help troubleshoot issues/problems that arise. Please be patient. While I am a ham, I am also a mediocre programmer, so I can see both sides of this argument. In addition, I've used Linux longer than I've been a ham. Hans Oeste VE7OES