Development of jed

[G. Milde]

On 19.05.08, Jörg Sommer wrote:
> how do we want to continue with the maintenance of the jed package? I've
> created a new branch jo-0.99.19 as a suggestion of how we could continue.
> I've merged in the upstream source and the changes from the 0.99.18
> series. Than I've done some changes. Maybe someone can review and comment
> on them.


> What do you think about the etch branch? 
...
> I would like to drop this branch. This doesn't mean the tags are lost.
> Only these last two commits. Objections?

None (if the changes done in this commits are preserved in the current
trunk).


> I'm using the xjed version from unstable everyday and I suspect John
> releases 0.99.19 soon. What do you think about cleaning up the 0.99.19
> branch and upload this package? 

The last time I tried xjed from the experimental package (0.99-19-117),
it was (for me) unusable as every mouse-action had very unexpected
results. Is this fixed now?


> This is the list of my changes. The commit script might have failed.

> commit 730c9db837214d0cc0f1135bccfc39b31a017bbf
> Author: Jörg Sommer <joerg at alea.gnuu.de>
> Date:   Sun May 18 00:47:03 2008 +0200

>     Remove in files in info/

>     Upstream doesn't provide the source aka ‘the prefered form for
>     modifikations’ of these files. Therefore, they are not conform with
>     the Debian Free Software Guidelines and we aren't allowed to ship
>     these files.

Are you sure there is a "hidden" source for these files?
John E D usually produces documentation from tm files - this might
also be the case for these.

OTOH, I think the info files are not that important and appear to
be no longer maintainged as well, so dropping them is OK with me.

> commit e36201b615ff66b42840e7c97ff54263dd7a3509
> Author: Jörg Sommer <joerg at alea.gnuu.de>
> Date:   Sat May 17 23:55:17 2008 +0200

>     Replace (C) by © and update copyright year

>     The string ‘(C)’ or ‘(c)’ is not a valid copyright sign. A lawer treat
>     only the sign © as a valid copyright sign. See
>     http://en.wikipedia.org/wiki/Copyright

The given URL says: 

  In all countries where the Berne Convention standards apply, copyright
  is automatic,
  
i.e. copyright does not depend on the any copyright notice at all if a
published work meets minimal standards of originality.
  
  In 1989, the U.S. enacted the Berne Convention Implementation Act,
  amending the 1976 Copyright Act to conform to most of the provisions of
  the Berne Convention. As a result, the use of copyright notices has
  become optional to claim copyright, because the Berne Convention makes
  copyright automatic. However, the lack of notice of copyright using
  these marks may have consequences in terms of reduced damages in an
  infringement lawsuit — using notices of this form may reduce the
  likelihood of a defense of "innocent infringement" being successful.


> commit a85635b8e500adc5c72dda03e32d9ae05ce753eb
> Author: Jörg Sommer <joerg at alea.gnuu.de>
> Date:   Sun May 18 00:16:37 2008 +0200

>     Enable hardening support

>     This was suggested in [1] and I'm using it in the package slrn since some
>     versions and didn't discover any problems. I think it's very useful and
>     might bring up some bugs. I didn't discover any big performance loose in
>     slrn and jed and I think a little performance loose might be acceptable
>     for jed.

Is there some data available about the performance loss?
Is jed startup time affected?


> commit 13958e4937c1c311febddedef3000a98c0dcdeac
> Author: Jörg Sommer <joerg at alea.gnuu.de>
> Date:   Mon May 19 00:34:05 2008 +0200

>     Move the FAQ from README.Debian to jed_faq.txt

>     This was already done in 62c6578fa47204d20ca62cfead24f031cdfa861e, but
>     the merge of the 1:0.99.18 series brought it back to README.Debian and
>     included some changes. I've integrated these changes in the patch for
>     jed_faq.txt in the hope we can push it to upstream.

Some answers of the README.Debian faq are Debian specific - we should
split them off and document in README.Debian (not necesserily in FAQ
format).

Günter