caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Maxence Guesdon <Maxence.Guesdon@inria.fr>
To: caml-list@inria.fr
Subject: Please provide at least one page for your ocaml projects
Date: Wed, 25 Aug 2010 11:26:05 +0200	[thread overview]
Message-ID: <20100825112605.1c7f0f27@alcazar.inria.fr> (raw)

Hello,

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


             reply	other threads:[~2010-08-25  9:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25  9:26 Maxence Guesdon [this message]
2010-08-25 15:46 ` Sylvain Le Gall
2010-08-25 16:01   ` Sylvain Le Gall
2010-08-25 16:58   ` [Caml-list] " Maxence Guesdon
2010-08-26  7:18 ` [Caml-list] " David MENTRE
2010-08-26 14:59   ` Grant Rettke
2010-08-26 20:10 ` Florent Monnier
2010-08-27 10:29   ` Mehdi Dogguy
2010-08-28 10:43     ` Florent Monnier
2010-08-28 10:56       ` Mehdi Dogguy
2010-08-28 11:06         ` Mehdi Dogguy
2010-08-28 12:04           ` Florent Monnier
2010-08-28 11:03       ` bluestorm
2010-08-28 11:58     ` Florent Monnier
2010-08-28 17:33       ` Mehdi Dogguy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100825112605.1c7f0f27@alcazar.inria.fr \
    --to=maxence.guesdon@inria.fr \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).