caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: caml users <caml-list@inria.fr>
Cc: "Jérémie Dimino" <jeremie@dimino.org>,
	"Mark Shinwell" <mshinwell@janestreet.com>
Subject: Re: [Caml-list] Jbuilder design and hacking session on September 9th in Oxford, UK
Date: Fri, 8 Sep 2017 11:47:56 +0100	[thread overview]
Message-ID: <CAPFanBFNF4JgvGfGtbPcWsajzia4L5YJKpnUBkOWVsMpz99_Uw@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBF_7zZft06GJZU=EBjf14R_xuKwNeRPB3dT66t_gbeTfw@mail.gmail.com>

Dear all,

We updated the webpage with location information for the event:

  http://gallium.inria.fr/~scherer/tmp/jbuilder-design-session-sep-09-2017.html

The event will be held between 9am and 5pm at:

  Malmaison Oxford
  Oxford Castle
  3 New Rd
  Oxford OX1 1AY


On Tue, Aug 1, 2017 at 11:22 AM, Gabriel Scherer
<gabriel.scherer@gmail.com> wrote:
> Dear all,
>
> Jérémie Dimino, Mark Shinwell and myself are organizing a "jbuilder
> design and hacking session" during the day of September 9th
> in Oxford, UK -- the day after the OCaml Workshop on September 8th.
>
> Jbuilder is a promising new build system that has already been adopted
> by some OCaml projects and attracted external contributors. Now may be
> a good time to discuss short- and medium-term design plans for the
> tool to guide potential contributors and avoid growing pains in the
> future -- helping it serve the needs of as wide a part of the OCaml
> ecosystem as reasonable.
>
> In the morning we plan to have high-level discussions on the current
> design and what evolutions are important. Ideas coming from other
> OCaml tools, or developments benefitting jbuilder and some other
> tools, may also be discussed. The afternoon would be more of a hacking
> session, along with low-level discussions on the jbuilder codebase
> structure and indications for specific new features.
>
> An unfortunate aspect of design discussions is that larger attendance
> does not always improve their quality. While the event is open to all,
> we would like to ask you to be considerate in deciding to attend in
> the morning -- in particular, existing experience with an OCaml build
> tool or a ecosystem-wide tool that interacts with build systems
> (such as merlin, oasis, odig, topkg...) is preferred. We will do our
> best to take notes of the discussion and publish a summary or minutes,
> so that any idea or result is open to everyone.
> Feel free to come for the hacking in the afternoon.
>
> Further location information will be anounced later on the following webpage:
>
>   http://gallium.inria.fr/~scherer/tmp/jbuilder-design-session-sep-09-2017.html
>
> Cheers

      parent reply	other threads:[~2017-09-08 10:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01 10:22 Gabriel Scherer
2017-08-01 10:54 ` [Caml-list] Jbuilder design and hacking session SF Markus Elfring
2017-09-08 10:47 ` Gabriel Scherer [this message]

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=CAPFanBFNF4JgvGfGtbPcWsajzia4L5YJKpnUBkOWVsMpz99_Uw@mail.gmail.com \
    --to=gabriel.scherer@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=jeremie@dimino.org \
    --cc=mshinwell@janestreet.com \
    /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).