[part 2 of the mail: quotes of former threads here]
On Aug 13, 2007, at 10:05 AM, Filip Konvička wrote:
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
<MOGUL.zip>
<ATT00001>
On Aug 13, 2007, at 11:57 AM, Filip Konvička wrote:
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.
Hm, I don't recall reading anything about this in the MOGUL doc..
As I
said, I am completely new to MOGUL. The doc appears to suggest that
one first gets a MOGUL id and then sets things up doing
ozmake --config=put --mogulrootid=$MOGULID
ozmake --config=put --moguldir=$MOGULDIR
ozmake --config=put --mogulurl=$MOGULURL
see http://www.mozart-oz.org/mogul/node11.html#sec.own.section.new
I may be wrong, but I think that this is only how you build your
package, not how you set up MOGUL librarian.
The thing about first publishing to the web and only then
activating the
account is that if the librarian is unable to download a package, it
crashes (every night, hence not updating anything, even from the other
mogul_ids). So it is best if you first make sure that the librarian
won't die and only then actually activate the mogul_id. And this is
also
why I propose to use a single mogul_id - simply because it's more
error-prone.
Anyway, it appears we should first figure out what our public URL
could be, and how we can access the data there. If we need to call
ozmake in that directory, than we need to install Mozart on the
machine in question and we would need a ssh access or something
similar.
Any comments?
I think you're right about this.
Cheers,
Filip
______________________________________________________________________
___________
mozart-users mailing list mozart-
[EMAIL PROTECTED]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
On Feb 18, 2008, at 3:48 PM, Boriss Mejias wrote:
Mmm... I don't feel with the authority to take decisions about the
MOGUL
project. To me, this remain as an open question until someone makes
a very
concrete proposal we can decide on (sorry if this has been already
done).
cheers
Boriss
Torsten Anders wrote:
Dear Boriss,
this reminds me: we still have not sorted out yet how to make
Collozeum
project releases available via MOGUL. Also, we now have two ozh
projects: the original one at MOGUL and the one fixed for Mozart
1.3.*
as a Collozeum project. The new ozh branch points at least to the
original (see
http://gforge.info.ucl.ac.be/plugins/wiki/index.php?
ozh&id=31&type=g),
but in MOGUL there is no pointer to the newer version. What shall
we do
here?
Thanks!
Best
Torsten
On Feb 11, 2008, at 8:52 PM, Boriss Mejias wrote:
Thanks.... I already did my commit following this convention. I also
added
some bug reports and requested features. I used the tracker for
this,
adding
every collozeum project to the "Product" category (opi_gedit,
ozcurl,
ozh,
ozjs and ozxsb).
Cheers
Boriss
Pavel wrote:
The correct process is:
1) check out collozeum.
2) create required directories under collozeum directory. The
recomended
path would be collozeum/foo/trunk/foo
3) from collozeum directory svn add foo
4) commit
5) enjoy
/pavel
On Sun, 10 Feb 2008 22:56:55 +0100, Boriss Mejias
<[EMAIL PROTECTED]> wrote:
Dear Torsten and Mozart users,
Yves Jaradin started to develop a plugin for using gedit as OPI
for
Mozart. Gedit is the official text editor of GNOME
(http://www.gnome.org/projects/gedit/), and it would simplify
the life
of new comers that are not used to the funky keyboard short
cuts of
Emacs :-) Of course, it would also be useful for senior Mozart
users
that only use Emacs when they want to use Mozart, cof, cof...
So, I wanted to add this as a Collozeum project, to allow other
users
to contribute with this plugin, which is in pre-alfa status....
If I understand correctly, I only have to create a subdirectory
gedit-opi with its correspondent trunk subdirectory in the
Collozeum
repository.... is that correct?
cheers
Boriss
--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
Office: +44-1752-586219
Private: +44-1752-558917
http://strasheela.sourceforge.net
http://www.torsten-anders.de
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
