caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "David Allsopp" <dra-news@metastack.com>
To: "OCaml List" <caml-list@inria.fr>
Subject: [Caml-list] Project hosting for new OCaml projects
Date: Wed, 5 Mar 2014 15:13:14 -0000	[thread overview]
Message-ID: <000b01cf3885$6f1ef7a0$4d5ce6e0$@metastack.com> (raw)

I've got a bit of code in a library which seems worth putting online. I'm
trying to consolidate the steps that should be taken to accomplish that
(beyond simply putting a tarball online!) and wondering if anyone can
confirm if what I've come up with is the "best/obvious" course of action.
Indeed, are there already "idiot"'s guides for this - I couldn't see
anything like it on ocaml.org et al?

So, this particular library is a pure OCaml library, which simplifies things
somewhat. At present it's built using GNU make and of course it is managed
using findlib.

It seems that the following are worth doing:

* Support OASIS (and in so doing, I believe that will migrate its build
system to ocamlbuild)
* Support OPAM (which looks incredibly straightforward - being primarily a
Windows user, the OPAM typhoon has flowed past me thus far)
* Put the SCM online somewhere; submit a pull request for opam-repository;
announce it

So, apart from any obvious errors/omissions in those steps, I have two
questions:

1. What are the differences, politely, in terms of things you can and can't
do between using GitHub and the OCaml Forge for the project pages? The Forge
seems the obvious choice, even ignoring the offensive name of the other!
2. Given that, is there any benefit/different to hosting the git repository
on the Forge vs hosting it on github and simply linking to it from the
Forge?

Thanks!


David


             reply	other threads:[~2014-03-05 15:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05 15:13 David Allsopp [this message]
2014-03-05 15:24 ` Simon Cruanes
2014-03-05 15:33   ` Yotam Barnoy
2014-03-05 18:00   ` Hezekiah M. Carty
2014-03-06  1:58     ` Francois Berenger
2014-03-05 20:00 ` Daniel Bünzli
     [not found]   ` <20140305.211003.1668243541649395876.Christophe.Troestler@umons.ac.be>
2014-03-06  9:48     ` Daniel Bünzli
2014-03-06 11:55       ` Sylvain Le Gall
2014-03-06 12:05         ` Daniel Bünzli
2014-03-06  0:20 ` Sylvain Le Gall

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='000b01cf3885$6f1ef7a0$4d5ce6e0$@metastack.com' \
    --to=dra-news@metastack.com \
    --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).