Bug#614907: nodejs/node command conflict: who does the work?
- To: firstname.lastname@example.org
- Subject: Bug#614907: nodejs/node command conflict: who does the work?
- From: Jonathan Nieder <email@example.com>
- Date: Wed, 2 May 2012 19:24:25 -0500
- Message-id: <20120503002425.GA552@burratino>
- Mail-followup-to: firstname.lastname@example.org
- In-reply-to: <20120502205554.GA32001@burratino>
- References: <20110224084728.GA13381@elie> <20120502205554.GA32001@burratino>
Jonathan Nieder wrote:
> I'd be happy to talk about work so far, transition plans,
> complications and possible ways forward in a separate message.
After all this conversation with tentative agreements, why hasn't a
transition to a new command name started? I think this goes to the
heart of the problem: it is very hard to convince someone to do work
when they don't believe that what they are doing is the right thing to
do. Any proposed fix should take this into account.
Pat Ouellette wrote:
| Here is my proposal:
| Node.js people, put forth a reasonable and workable plan to allow
| hundreds or thousands of ham radio users to transition from
| /usr/sbin/node to /usr/sbin/axnode, including reliable shell scripts
| to verify all the files on the system are identified and allowed to
| be patched or manually modified. You created the situation, you
| provide the manpower to resolve it in the way you prefer.
My response was some regrettable and snarky reply about how I started
to work on exactly that but cannot do much without cooperation from
My will to work on fixing node and ax25d has gone away pretty quickly.
Hopefully once the discussion is over I could work with someone else
on the maintenance team, or maybe Pat's attitude would soften. Or
someone else can pick up the work --- it doesn't look _too_ hard.
On the Node.js side, Jérémy seems quite enthusiastic but I am guessing
he is not motivated to work on the details unless it is clear that it
is necessary. I think that once there is a clear plan there will not
be problems getting the work done. If it doesn't get done in time,
Node.js can enter Debian in wheezy+1 instead of wheezy.