Re: Moving Gnus development to Emacs?

Lars Magne Ingebrigtsen <[email protected]> writes:

> After the discussion here, I think I've decided to move Gnus development
> to Emacs and Emacsify the code for greater readability.

We moved MH-E to Emacs a few years ago. One welcome consequence of this
is that we have had more developers improving the code.

Lars, will you continue to have separate Gnus version numbers? Will you
move the bug tracker?

MH-E still maintains separate version numbers and we're still using
SourceForge for our bug tracking and a Git repository for MH-E files
that may not be appropriate for the Emacs repository (contrib, Debian
files, maintainers guide, web pages, tests, files for independent MH-E
releases).

Have you also considered moving Gnus to ELPA someday?

> If {S,}XEmacs wants to keep tracking Gnus development, this
> unfortunately means that the onus is on the {S,}XEmacs maintainers to
> add an ever-growing number of Emacs compat functions, and expand
> function call lists to keep up with Emacs function call lists.

We still have a small file with compatibility functions for older
Emacsen and XEmacs. It would be better if XEmacs provided the
compatibility so each package wouldn't have to.

-- 
Bill Wohler <[email protected]> aka <[email protected]>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD