I'd like to add to our list of desiderata the improvements that Steve
Young made in SXEmacs --- if they haven't already been included. We
can pick and choose, of course, and I'd certainly like to hear from
Steve which improvements he thinks worked out well, and which didn't
or were not worth the effort.
(For some reason as yet undetermined, I can't get to his site in order
to attach the list.)
--- Vladimir
on 02/23/2009 06:29 PM Stephen J. Turnbull said the following:
Mats Lidell writes:
> Fighting about who is right about what happened is really a dead
> and.
Probably so. <sigh />
> Let's focus on our vision and our goals instead.
Well, what are they?
Ben had his huge blueprint of the future at
http://www.xemacs.org/Architecting-XEmacs/.
Mike has his long-range plans regarding garbage collection and
replacing the Lisp engine.
Jamie has a list of ten items from like 1997, all of which are at
least partly relevant to XEmacs today.
http://www.xemacs.org/Releases/Public-21.2/wishes/jwz-wishlist.html
I've published a number of desiderata. The only one getting active
attention at the moment is Unicode support, where Aidan is doing work
these days. Some of my ideas are in the 21.4 release plan:
http://www.xemacs.org/Releases/Public-21.2/planned.html
http://www.xemacs.org/Releases/Public-21.2/first-draft.html
http://www.xemacs.org/Releases/Public-21.2/execution.html
Speaking for myself, there has not been much enthusiasm for my
proposals, not expressed in code contributions, anyway. I'm not able
to execute the larger ones myself, not for delivery in the near
future. So I'd be willing to put in administrative support and do
patch reviews in support of other people's goals.
But what are other people's goals? And who's going to do the work? I
can do some, Aidan will do some it would seem. But we need more
people coding. Even if you don't feel comfortable contributing code
yet, you can read Architecting XEmacs, and look at the task lists
above, and post what you think is important here.
Or start a page on the EmacsWiki. I suspect that will be most
effective if somebody takes responsibility for editing it, and putting
it into a form that looks like a release proposal (not necessarily
like first-draft.html cited above, but definitely it has to look like
there is some action coming). But it won't hurt to just start one if
you're a wiki-oriented person.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
--
Vladimir G. Ivanovic
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org