Steve Youngs <steve@xxxxxxxxxxx> writes:
> For quite a while now I've felt that only having 2 one true editors
> wasn't enough. So I have created a third.
Buh!
> o Use GNU/arch (tla) for revision control instead of CVS.
> This is already done. My repo is at steve@xxxxxxxxxxxxxxxxx
> http://arch.sxemacs.org/2004/
Good.
> o Have a written procedures and policies manual. (partially
> completed)
Sounds like a recipe for "lawyering". But you can of course get
around it by being ultimate authority (and not the written stuff) like
RMS is for GNU Emacs. With GNU/arch, that might even be a better way
to run a project than the "core consensus" style which cvs encourages.
GNU/arch encourages both making branches and merging them, which fit
better with the dictator style.
> o Use a PostgreSQL'd Bugzilla for issue tracking. (we have it
> in place but unfortunately the guy I have handling it for
> us broke something and currently we can't connect to it)
Good. (Not good that it is broken, of course).
> o Move away from GNU coding standards in the C code and write
> code in a manner that the gods intended. I'm following fairly
> closely the Linux kernel in this regard. I have already run
> indent(1) over all the C code.
Stupid. It just makes merging harder for no measurable benefit.
> o autoconf 2.5x compatible. (not begun)
Good.
> o Remove every scrape of Windoze code. (not begun) SXEmacs
> will _NOT_ run on Windoze.
Bad. One major benefit of Emacs is that it runs everywhere.
> o Back port Mike Sperber's KKCC garbage collector from XEmacs
> 21.5. And at a later stage look at using the Boehm GC.
>
> o Back port Jerry James' DSO, bignum, bigfloat, and ratio work
> from XEmacs 21.5.
Why not just branch from 21.5?
> o Multi-threading
Good luck! Desperately needed.
> o Do away with the idea of a buffer being nothing more than a
> string.
I'd prefer a string being nothing less than a buffer :-)
> o FFI -- Foreign Function Interface (pretty much like DSO's
> but far more flexible)
Don't know them, but a good plug-in abi would be useful.
> o Possibly move to a client/server model
Huh?
> o A package system where the package tells SXEmacs where and
> how to get updates.
Part of a "good plug-in abi"...
|