Mozart development

[Denys Duchier]

Torsten Anders <torstenanders at gmx.de> writes:

> Would you -- and others -- agree that also some Mogul projects (e.g. ozh) are
> suitably maintained by the community. For example, Filip  provided a patch for
> porting ozh to Mozart 1.3.* which never was merged  in.

I have no idea.  As you know, I was out of touch with the project for some time.
It seems to me that if (1) a project is orphaned, (2) someone wants to adopt it,
(3) the original author does not object, then we should make it happen.  If
UCL/INGI GForge can offer hosting, then all the better.  In the case of ozh, I
don't expect any objections.

> So here is my Mogul-related question: community maintained projects are best
> hosted by some versioning system such as svn. It appears to me,  however, that
> the mogul librarian expects some plain data at some URL.  Could the librarian
> instead execute some simple script (which may be  user-defined) in order to
> retrieve a snapshot of the source from some  versioning system?

That doesn't make much sense.  The MOGUL database records _releases_ of
packages; that's quite different from whatever happens to be in a VCS.  I am not
quite sure what you are trying to fix with your suggestion.  Furthermore, if
changes are to be made to MOGUL, then (as I have described in the past), I'd
rather replace the current PULL model by a PUSH model.

Cheers,

--Denys