[Collozeum] How to release via Mogul?
Filip Konvička
filip.konvicka at logis.cz
Mon Aug 13 11:05:02 CEST 2007
> 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?
I don't know whether this Gforge capabilities will suffice. You need to
expose a directory-like structure similar to mine, see
http://sweb.cz/filip.konvicka/mogul/
These files are the result of my build process and AFAIK exactly what
the librarian expects to find.
Regarding MOGUL ids, you have to decide whether to get one for
Collozeum, or one for each subproject. The tricky part about getting a
new id is that you have to expose the web structure prior to making the
request (and it must contain valid data), so that when the id gets
activated, the librarian does not choke. So I recommend getting just
single id, if possible.
>>> 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...
I don't know, but if there is some collaboration going on, and in case
that people share some common repository, it's best if all agree to some
sufficiently non-restrictive license. But this is just what popped into
my mind, I don't want to stress this.
>
>> 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.
See the attachment. The results of the build go into "/publish", which
is what appears at the URL mentioned above.
>
>>> 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...).
As I said, I don't know if it's enough.
>
>> 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.
OK, if you have some (semi-?)public svn, and set up some nightly (maybe
eveningly) builds & result upload (in case all goes well), it might
work. My point is that, if you have just one MOGUL id for Collozeum, you
can automate the task and make contributions easier, as publishing the
"binaries" to MOGUL will be automatic and will require no extra effort.
Cheers,
Filip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MOGUL.zip
Type: application/x-zip-compressed
Size: 325447 bytes
Desc: not available
Url : http://lists.gforge.info.ucl.ac.be/pipermail/mozart-users/attachments/20070813/eba991af/MOGUL-0001.bin
More information about the mozart-users
mailing list