[Collozeum] How to release via Mogul?

[Torsten Anders]

Dear Filip,

thank you for your feedback.

On Aug 13, 2007, at 7:33 AM, Filip Konvička wrote:
> Hi again,
>
>> Dear all,
>>
>> released Collozeum projects should be easily accessible via Mogul. I
>> have no experience with Mogul releases yet. The process is described
>> at http://www.mozart-oz.org/mogul/node8.html#chap.contrib, but I
>> recall earlier posts here which described certain problems like that
>> it was meanwhile hard to get a Mogul ID (couldn't find the email
>> anymore..). Could someone just summarise recent experiences? Filip?
>
> from my point of view the current process is rather complicated. The
> problem is that the MOGUL librarian actively downloads the libraries
> from some host sites. So this is (as Denys said in the past) the
> pull-model, and requires that the contributors maintain public web  
> sites
> with the libraries (I use a free public web host) and also there  
> must be
> an admin that assigns mogul IDs (currently probably Denys again).
>
> I think that the better way would be hosting the libraries at a common
> place, like gforge, and re-writing the librarian to support the  
> push-model.

OK, Collozeum releases will be hosted at Gforge. I assume that the  
pull-model should work for the projects hosted there, because this  
website and its URLs are likely to remain. For every new release of a  
Collozeum project, however, we probably need to inform MOGUL about  
its new URL. Do you see any major problems for Collozeum projects,  
except that getting a Mogul ID may take some time?

>> More specifically, what should be the mogul root id for Collozeum
>> projects? Should every Collozeum contributor become registered at
>> MOGUL and get a MOGUL ID? Or would it be sufficient (for now at  
>> least)
>> if only Collozeum is registered as a meta author, and further authors
>> are then just listed with their names as strings instead of MOGUL  
>> IDs?
>
> IMHO, it would suffice if the project got a meta id. You would just  
> need
> to ensure that the contributors adhere to some common license.

Hm, would we need to have a common licence in that case? What about  
the Mozart licence then? However, it is less strict than the GPL...

> If you want, I can show you the build makefiles that I use for  
> creating
> the distribution packages. Once created, the distribution packages  
> must
> be uploaded to the web host that the MOGUL librarian knows of and from
> which it will download the new versions during the nightly runs.

Please share these files.

>> Where should release files be stored? I assume it would be best to  
>> use
>> the Gforge release mechanism for storing file releases and just
>> telling ozmake/MOGUL where to find these.
>
> You need to make the files accessible via http, so if you can do this
> within Gforge this would be probably the best option.

It appears that Gforge does provide a direct URL for each download  
(not yet tested with own releases, only confirmed by looking at the  
releases of other projects...).

> My idea of the
> process is that each contributor maintains her package(s) and uploads
> just those packages to the repository, as needed, not touching the  
> others.

Within Collozeum, I would welcome if the situation gets different: I  
would welcome if people contribute to projects which are not  
originally "theirs", e.g., for scratching some personal itch. After  
all, the whole idea of Collozeum is a platform of collaborative  
development, somewhat like a wiki.

Thanks!

Best
Torsten

--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
strasheela.sourceforge.net
www.torsten-anders.de