From: "Hans-Peter F. Oeste" <hoeste@shaw.ca>
Cc: node@packages.debian.org, nodejs@packages.debian.org,
debian-hams@lists.debian.org, linux-hams@vger.kernel.org
Subject: RE: Node.js and it's future in debian
Date: Thu, 3 May 2012 16:10:05 -0700 [thread overview]
Message-ID: <025201cd2981$e0c46620$a24d3260$@shaw.ca> (raw)
In-Reply-To: <20120503185129.GA18768@burratino>
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
next prev parent reply other threads:[~2012-05-03 23:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACxjfDH5zYth6Q-ZDLDafqNEczbF3BqaGRcAhsaiPEnApbiUuA@mail.gmail.com>
[not found] ` <20120501205524.GI30521@flying-gecko.net>
[not found] ` <20120501215305.GA1250@burratino>
[not found] ` <20120501221659.GA11430@flying-gecko.net>
[not found] ` <20120502065003.GB2410@burratino>
[not found] ` <20120502165031.GC7390@flying-gecko.net>
[not found] ` <20120502171349.GA23806@burratino>
2012-05-02 20:04 ` Node.js and it's future in debian Patrick Ouellette
2012-05-02 20:31 ` Jonathan Nieder
2012-05-03 15:29 ` David Ranch
2012-05-03 15:33 ` David Ranch
2012-05-03 16:17 ` Marius Petrescu
2012-05-03 17:08 ` Patrick Ouellette
2012-05-03 17:05 ` Patrick Ouellette
2012-05-03 18:51 ` Jonathan Nieder
2012-05-03 19:48 ` Gordon JC Pearc e
2012-05-03 23:10 ` Hans-Peter F. Oeste [this message]
2012-05-04 4:09 ` David Ranch
2012-05-04 4:28 ` Ray Wells
2012-05-04 4:46 ` Jonathan Nieder
2012-05-04 12:31 ` DL1SIG
2012-05-04 13:29 ` [Pkg-javascript-devel] " Emilien Klein
2012-05-04 14:31 ` Patrick Ouellette
2012-05-04 7:38 ` walter harms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='025201cd2981$e0c46620$a24d3260$@shaw.ca' \
--to=hoeste@shaw.ca \
--cc=debian-hams@lists.debian.org \
--cc=linux-hams@vger.kernel.org \
--cc=node@packages.debian.org \
--cc=nodejs@packages.debian.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.