I usually prefer packages be installed as subtrees, but in the case of
large packages like this one, it makes more sense to install it as an
"external" which is more like a submodule (it's actually just
a separate branch in the same repository).
> Since we don't have push rights to the ELPA repository we would need that.
That's easy to arrange. Request membership in the "emacs" group from
your Savannah page.
Right. The Git repository is empty and the Hg repository seems to only
go up to 2013, so I can't give an opinion on the current code.
I'll just assume the general shape hasn't changed much. Any reason why
the real code is still not in there?
One of the main limitations of ELPA is that it doesn't really like Elisp
files other than in the root directory. If I look at the Hg repository,
all Elisp files except for the kotl/*.el are in the root dir, so it
looks OK (and it'd be easy to move those kotl/* files to the root).
Stefan