For those who don't know, I'm the maintainer of the Caml Hump.
For this reason, I have a look at every project announced on the caml-list
and it seems to me that there are more and more projects providing only
links to tarballs or git repositories.
I think these projects would take advantage of having at least one web page
giving all basic information: description, status, license, author(d),
download links.
Indeed, having to look for this information in a tarball of a git repos
(with gitweb) is not very convenient. Even the project page on a forge is
not the best way to get the information quickly. It's more a view for a
developer/contributor, not for a potential user.
Even if this main web page should point to the developer ressources
(repository, forge project, ...), the main access to the project should
be a web page with hand-written text, even a simple one.
Regards,
--
Maxence Guesdon
_______________________________________________
Caml-list mailing list. Subscription management:
http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
Archives: http://caml.inria.fr
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
On 25-08-2010, Maxence Guesdon <Maxence...@inria.fr> wrote:
>
> For this reason, I have a look at every project announced on the caml-list
> and it seems to me that there are more and more projects providing only
> links to tarballs or git repositories.
>
> I think these projects would take advantage of having at least one web page
> giving all basic information: description, status, license, author(d),
> download links.
>
I am working on OASIS and OASIS-DB. The latter aims to translate _oasis
file into simple web pages (including markdown translation).
Have a look at:
http://oasis.ocamlcore.org/dev/browse?ver=0.2.0~alpha1&pkg=oasis
This web page has been translated from:
http://darcs.ocamlcore.org/cgi-bin/darcsweb.cgi?r=oasis;a=headblob;f=/_oasis
(this package is pretty complex, so there is a lot a library/exec/tests
but what is translated is basically Synopsis + Description).
If you add an _oasis file to your project and upload it to
oasis.ocamlcore.org it will generate this kind of pages.
Maxence, does it fit your requirement?
(the project is still at an early stage, but the upload is working)
> Indeed, having to look for this information in a tarball of a git repos
> (with gitweb) is not very convenient. Even the project page on a forge is
> not the best way to get the information quickly. It's more a view for a
> developer/contributor, not for a potential user.
>
Every project on forge.ocamlcore.org can upload a simple webpage and it
will be displayed on http://PROJECT.forge.ocamlcore.org. Just add html
files to /home/groups/PROJECT/htdocs on ssh.ocamlcore.org, same ssh key
as git/darcs/svn login. You can use rsync, scp or unison.
Feel free to contact me if you need further utilities for your project.
Regards,
Sylvain Le Gall
Examples of web pages:
http://oasis.forge.ocamlcore.org/
http://ocaml-lua.forge.ocamlcore.org/
http://ounit.forge.ocamlcore.org/
http://pa-do.forge.ocamlcore.org/
http://ocamlviz.forge.ocamlcore.org/
http://cmdline-args.forge.ocamlcore.org/
http://camlbz2.forge.ocamlcore.org/
http://ocaml-autoconf.forge.ocamlcore.org/
If you lack inspiration, just copy/adapt these webpages. They are all
accessible on /home/groups/PROJECT/htdocs/.
> Hello,
>
> On 25-08-2010, Maxence Guesdon <Maxence...@inria.fr> wrote:
> >
> > For this reason, I have a look at every project announced on the caml-list
> > and it seems to me that there are more and more projects providing only
> > links to tarballs or git repositories.
> >
> > I think these projects would take advantage of having at least one web page
> > giving all basic information: description, status, license, author(d),
> > download links.
> >
>
> I am working on OASIS and OASIS-DB. The latter aims to translate _oasis
> file into simple web pages (including markdown translation).
>
> Have a look at:
> http://oasis.ocamlcore.org/dev/browse?ver=0.2.0~alpha1&pkg=oasis
>
> This web page has been translated from:
> http://darcs.ocamlcore.org/cgi-bin/darcsweb.cgi?r=oasis;a=headblob;f=/_oasis
>
> (this package is pretty complex, so there is a lot a library/exec/tests
> but what is translated is basically Synopsis + Description).
>
> If you add an _oasis file to your project and upload it to
> oasis.ocamlcore.org it will generate this kind of pages.
>
> Maxence, does it fit your requirement?
The page at your first url seems to contain the minimal information, indeed.
--
Maxence Guesdon
2010/8/25 Maxence Guesdon <Maxence...@inria.fr>:
> I think these projects would take advantage of having at least one web page
> giving all basic information: description, status, license, author(d),
> download links.
As a simple OCaml user, I agree with Maxence. If an announcement is
not provided without those minimal information, I skip it. Available
time is so constrained.
Sylvain, your OASIS project and the generated web page is very
interesting in that regard.
Regards,
david
OASIS looks *very* nice.
I would say that when packagers write patches that add new features it would
be nice if they set up such a basic web-page too.
--
Regards
Florent
FWIW, in Debian, we have:
http://patch-tracker.debian.org/
which lists and shows applied patches to any Debian package.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://www.pps.jussieu.fr/~dogguy
Tel.: (+33).1.44.27.28.38
I don't see any way to display the added features
I don't see any description either
it is only a basic listing
--
Regards
Florent
Well, we really don't need more than that. Distributed packages aren't
supposed to be a forked version of the original one. We write patches to
fix problems. Some of the written patches introduce minor features (in
which case, it should be very easy to understand by simply looking at
the patch). But, that's all… If you want more than that (detailed
descriptions of each patch), it's not going to happen because it's a lot
of work. Besides, we try to send to our upstreams each written patch…
So, in an ideal world, those patches are there only for a limited amount
of time.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://www.pps.jussieu.fr/~dogguy
Tel.: (+33).1.44.27.28.38
_______________________________________________
> > FWIW, in Debian, we have:
> >
> > http://patch-tracker.debian.org/
> >
> > which lists and shows applied patches to any Debian package.
>
> I don't see any way to display the added features
> I don't see any description either
>
> it is only a basic listing
>
Well, there is a (concise) description of patches. For example, from
http://patch-tracker.debian.org/package/ocaml/3.11.2-1 (the list of patches
for the 3.11.2 version), if you click on the "View" link of one of those
patches, you'll get the patch and possibly a description. For example, with
http://patch-tracker.debian.org/patch/series/view/ocaml/3.11.2-1/0002-Call-ld-with-proper-flags.patch
:
> Filter linkflags passed to ld by ocamlopt -pack and -output-obj
> to remove the "-Wl," parts, which are only used when ocamlopt calls
> gcc.
ha yes indeed sorry!
but one question, I see now on this page that there this related link
http://packages.debian.org/lenny/advi
but not one this one:
http://packages.debian.org/sid/advi
why?
(indeed when I watch at package information I watch at sid)
--
Regards
Florent
That's called a "bug" :)
--
Mehdi Dogguy مهدي الدڤي
http://www.pps.jussieu.fr/~dogguy
Tel.: (+33).1.44.27.28.38
_______________________________________________