On Sun, 4 Apr 1999, Steve Dimse K4HG wrote:
} On 4/3/99 1:33 PM Mike Bilow ([EMAIL PROTECTED]) wrote:
}
} >
} >
} >Steve Dimse wrote in a message to Mike Bilow:
} >
} internet would need to be upgraded, wouldn't they?
snip
}
} > SD> One of the things you have to promise to become an "official
} > SD> APRS software author" is never to release your source code.
} >
} >Really? That's insidious. What could be the point of that?
} >
} Per Bob, the primary reason is that if people could modify the code and
} get on the air, the protocol would break down. And he does have a point.
That is stupid logic. All of Linux that is under the GNU license
has the source code and it's not hacked but rather improved.
} Given the present state of the documentation on the protocol, and the way
} he changes it when he feels the urge, it is hard enough for the four
} major versions (Mac/WinAPRS [common codebase], APRSdos, APRS+SA, and
} javAPRS) to keep in sync. The more authors in a situation like that, the
} more chances for confusion. My argument that the answer is not to lock up
} the source code, but rather to formalize the protocol, has fallen on deaf
} ears.
Well I think your in for an education your going to enjoy Steve.
When the guys writing on APRS this very minute get the application to the
Alpha stage it will appear on a web-page somewhere. We all hit that page
and d/l the thing and compile it and start playing.
Something doesn't work quite right and the user either just sends
a bug report or if capable he hacks the source code until the bug
disappears. Then he sends the fix with the bug report. Since the internet
is involved this whole thing can happen on 1 day.
}
} Money is the other less often admitted reason he opposes source code
} release.
}
He does not use Linux, he has never been exposed to the GNU
License and might not like it if he did.
} Steve K4HG
}
Best wishes
- Karl F. Larsen, [EMAIL PROTECTED] (505) 524-3303 -
