Mozart development

[Denys Duchier]

Torsten Anders <torstenanders at gmx.de> writes:

> My suggestion was that orphaned Mozart applications which are as important for
> Mozart in general as ozh can become somehow part of Mozart itself. For example,
> in svn we may have a new folder trunk/mogul-applications/ozh? That way, every
> Mozart developer can apply patches.

It still needs to be in some sense "adopted" by the UCL/INGI GForge powers that
be.  I think that it would make sense for ozh.  However, it should probably be a
separate project.  Not one that lives in the Mozart/Oz svn.  It is not an
official part of the distro.

Any such project needs to have an "adoptor" if only because someone needs to
apply patches and correspondingly make releases.  It's not a big job, but
someone _has_ to do it.  If there were no "adoptor", we'd be in the same
situation as we are now... and you can't dump these duties into the laps of
Mozart/Oz maintainers/developers: that's neither fair nor realistic.

Cheers,

--Denys