Requirements for releasing the STK toolbox as an Octave forge package ?

[Julien Bect]

Dear Octave forge maintainers,

A while ago I announced a new release of the STK, version 2.1.0, a 
toolbox developped and maintained by my colleague Emmanuel Vazquz and 
myself :

http://octave.1599824.n4.nabble.com/STK-2-1-0-released-td4660018.html

I would love to see our toolbox distributed as an Octave forge 
package... what would be the requirements for that ?

Our project is currently hosted on Sourceforge 
(http://sourceforge.net/projects/kriging) and we want to keep it that 
way, so I'm thinking of something like the LTFAT, which is distributed 
as an Octave forge package but hosted on a separate repository.

I have started to write a Python script that prepares a tar.gz with all 
the required files for an Octave package (DESCRIPTION, PKG_ADD, PKG_DEL 
and so on). It is not finished yet, but already produces a valid package 
that can be installed using Octave's pkg command :

http://sourceforge.net/p/kriging/code/HEAD/tree/trunk/admin/make_octave_package.py

Our documentation is currently in plain text format, but I can wrap it 
in @deftypefn + @verbatim texinfo environments (again, as done in the 
Octave package release of the LTFAT package).

Would there be any other requirement for our toolbox to be distributed 
as an octave forge package ?

@++
Julien