Adding functions to octave base?

[fork]

Is there a policy on adding new functions the octave base?  We have a
"miscellaneous" in the m/ directory where they could go, or extras/ or
nonmatlabcompliant/ etc, etc.  

I have a couple of infrastructure routines (pushd and popd, ifelse(), and
testall(), at the moment) that I use fairly regularly that I can imagine would
be useful to people besides myself.  Plus I would love to not have to worry
about where did I put my latest copy of these m-files...

I realize that I could start a new package on S-Forge or try to find a package
in which to stuff them, but that just smells, I don't know, silly; there is at
least some redundancy between packages that makes all of them hard to take
seriously. It smells even sillier to post them to the list or use some random
file thing like file exchange on the MW site, especially for fairly core
functions.  If the routines are good enough for a core library they should go
there; if not, either they belong to an edge case, or should be worked over
collaboratively until they are good enough to expand the core library.

(Standard libraries should not be treated as second class citizens, but Octave
Forge definitely is, unfortunately. And unmanaged file exchange systems aren't
even citizens at all... I would love to see a slightly formalized standard
library process, with RFQ's, for Octave.)

I would think that a "non matlab compliant" warning would be appropriate in
these routines, too.

I would happily fill out bug reports w patches for these routines if anyone
cares enough to look and possibly patch.

Thanks!