🚀 go-pugleaf

In article <865335020snz@wash.demon.co.uk>
           john@wash.demon.co.uk "John Washington" writes:

> All good stuff I'm sure, but AIUI there's no TextWin version of
> JNOS/DNOS available.  And even users of Demon std Ka9q may well
> be reluctant to switch to a (perhaps very?) different version of Ka9q.
> 
> All this divergence is very worrying. [...]

The only time when this divergence does NOT happen is when
only binaries are distributed. Publishing sourcecode eventually
leads to divergence. I once read an interview about 'the best
programmable editor' and the last remark was: 'programmable editor?
just give me the source!'. That says it all.

> Even worse, the Demon std version is left with a serious bug and
> there seems no chance that Demon will release an upgrade even if
> volunteers amongst us do the legwork.

Which brings me to the conclusion that the volunteers could still do
the legwork (even without Demon's consent) and this unified bootleg
version could be uploaded in /pub/incoming (including sourcecode,
naturally). That makes _sure_ MM sees it since he has to post the
appropriate article in demon.archives.announce <g>.

The first thing to be done is to compile a list of 'known bugs and
anomalies' for the latest official release (if this does not yet
exist). That list could be annotated with possible cures
if there is someone here that has solved it (either in the form of
a text or in the form of a piece of replacement-sourcecode).
After that, well, it is 'just' a matter of integrating all the cures
into a single set of sourcefiles. But then again, I may be dreaming...

--Peter Fokker