Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: "lwn" <lwn@lwn.net>, caml-list@inria.fr
Subject: [Caml-list] Attn: Development Editor, Latest OCaml Weekly News
Date: Tue, 18 Feb 2025 15:33:17 +0100	[thread overview]
Message-ID: <m2tt8rgw5u.fsf@mac-03220211.irisa.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 11076 bytes --]

Hello

Here is the latest OCaml Weekly News, for the week of February 11 to 18,
2025.

Table of Contents
─────────────────

Learn Programming with OCaml (new book)
Ocsigen's 2024 recap
OCaml GADTs for Authentication Tokens
OCaml language committe launched
Dune dev meeting
Asking For Community Feedback on the OCaml Platform Communications
Old CWN


Learn Programming with OCaml (new book)
═══════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/learn-programming-with-ocaml-new-book/16111/1>


Jean Christophe Filliatre announced
───────────────────────────────────

  Dear OCaml community,

  A long time ago, Sylvain and I wrote a French book on [learning
  programming with OCaml].  Recently, the OCaml Software Foundation
  funded its translation to English. The book is available here:

  [Learn Programming with OCaml]

  Many thanks to [Urmila] for a translation of high quality.

  The book is available as a PDF file, under the [CC-BY-SA license]. The
  source code for the various programs contained in the book are
  available for download, under the same license.

  The book is structured in two parts.  The first part is a
  tutorial-like introduction to OCaml through 14 small programs,
  covering many aspects of the language.  The second part focuses on
  fundamental algorithmic concepts, with data structures and algorithms
  implemented in OCaml. This is also a nice way to learn a language!

  The book does not cover all aspects of OCaml.  It is ideally
  complemented by [other books on OCaml].


[learning programming with OCaml]
<https://usr.lmf.cnrs.fr/programmer-avec-ocaml/>

[Learn Programming with OCaml] <https://usr.lmf.cnrs.fr/lpo/>

[Urmila] <https://www.aropefastenedbetween.fr/>

[CC-BY-SA license]
<https://creativecommons.org/licenses/by-sa/4.0/deed.en>

[other books on OCaml] <https://ocaml.org/books>


Ocsigen's 2024 recap
════════════════════

  Archive: <https://discuss.ocaml.org/t/ocsigens-2024-recap/16117/1>


William Caldwell announced
──────────────────────────

  Hi all!

  2024 was a busy year for the Ocsigen ecosystem, in case you missed any
  of it, here are the important highlights:

  wasm_of_ocaml has been merged in its parent project js_of_ocaml,
  making your Ocsigen projects that much closer to being served as WASM
  instead of JavaScript. In the meantime you can build your own WASM by
  using wasm_of_ocaml to get a taste of the future.

  Major work has been undertaken on Ocsigen:

  • Ocsigen Server 6
  • Eliom 11
  • Ocsigen Start 7

  Ocsigen server no longer needs a configuration file to start your
  project, you can instead start Ocsigen server in your project and
  handle the configuration yourself.  If you're eager to
  `Ocsigen_server.start ...' you can learn more in the following
  announcements:

  • [ocsigen server 6]
  • [Eliom 11 and Osigen Start 7]

  Ready for 2025? We certainly are!  Our efforts to make the Ocsigen
  ecosystem more modular are ongoing: next on the list is ocsigen-i18n,
  making easier to pick and choose what bits of Ocsigen you want to
  include in your project, and allowing to use it for any OCaml
  application.  The biggest evolution of the Ocsigen project is underway
  & soon to be announced, and that's not even including wasm\_of\_ocaml.
  Also keep an eye out for our public meeting announcements in which we
  discuss our current tasks, ask for public feedback, and answer
  whatever Ocsigen related questions you might have.


[ocsigen server 6]
<https://discuss.ocaml.org/t/ann-ocsigen-server-6-0-0/15265>

[Eliom 11 and Osigen Start 7]
<https://discuss.ocaml.org/t/ann-eliom-11-and-ocsigen-start-7/15487>


OCaml GADTs for Authentication Tokens
═════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/blog-ocaml-gadts-for-authentication-tokens/16128/1>


Maxim Grankin announced
───────────────────────

  Hi everyone! 👋

  My name is Max, I've been using OCaml for a while during my years at
  Bloomberg and at some moment decided to dig a little bit into GADTs. I
  found couple of use cases for them and decided to write down one in
  detail:

  • [OCaml GADTs for Authentication Tokens]

  I hope it would help newcomers to find application for GADTs in their
  projects.

  Huge thanks to @chshersh for reviewing this blog post!

  Enjoy and let me know what you think in the comments!


[OCaml GADTs for Authentication Tokens]
<https://dev.to/maxim092001/ocaml-gadts-for-authentication-tokens-57be>


OCaml language committe launched
════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/ocaml-language-committe-launched/16129/1>


octachron announced
───────────────────

  It is my pleasure to announce the launch of the OCaml language
  committee. This committee is intended as collegial instance with the
  aim to facilitate discussions and consensus making about the evolution
  of the OCaml language and its standard library.

  Over the years, it has become a common shared grievance among both
  maintainers and contributors to the OCaml language that, sometimes,
  the review process for changes grinds to a halt, either because
  consensus is elusive or because no one feels empowered enough to take
  a decision single-handed.

  In order to reduce the number of those instances of decision
  paralysis, the OCaml maintainers have decided to experiment with an
  OCaml language committee: [a subgroup of the OCaml community]
  organised to discuss evolution of the OCaml language in a timely
  fashion.

  In practice, if someone feels that a contribution (a Pull Request,
  issue, Request For Comment) might be stuck or might benefit from a
  wider discussion, they may ask the committee to take the contribution
  under consideration by mentioning it to the committee chair (which is
  currently me, aka @Octachron on github).

  Then the committee will deliberate on this contribution both on the
  [archived] public mailing list `ocaml-language-committee@inria.fr' for
  internal committee discussion [^1] and possibly on the relevant
  community channels ([ocaml/ocaml] or [here on discuss]). At the end of
  this collegial discussion, the committee will publish a consultative
  decision on the matter. We expect that having such a collegial
  consultative decision would be enough to unblock most situations.

  For more details, the intended working of the committee is described
  at <https://github.com/ocaml/RFCs/blob/master/Committee.md> .

  Happy hacking, Florian Angeletti for the OCaml Language Committee

  [^1]: Anyone is welcome to subscribe to the mailing list to attend to
  the discussions, but please do not flood the mailing list so that we
  can keep it fully open.


[a subgroup of the OCaml community]
<https://github.com/ocaml/RFCs/blob/master/Committee.md#who-is-the-committee>

[archived] <https://sympa.inria.fr/sympa/arc/ocaml-language-committee>

[ocaml/ocaml] <https://github.com/ocaml/ocaml/>

[here on discuss] <https://discuss.ocaml.org>


Dune dev meeting
════════════════

  Archive: <https://discuss.ocaml.org/t/ann-dune-dev-meeting/14994/23>


art-w announced
───────────────

  Hello! The next Dune Dev Meeting will be on *Wednesday, February, 19th
  at 4pm CET* for an hour long discussion.

  Whether you are a maintainer, a regular contributor, a new joiner or
  just curious, you are welcome to join: these discussions are opened!
  The goal of these meetings is to provide a place to discuss the
  ongoing work together and synchronize with the Dune developers.

  The agenda is available on the [meeting dedicated page]. Feel free to
  add more items in it.

  • Meeting link: [zoom]
  • Calendar event: [google calendar]
  • Wiki with informations and previous notes: [dune wiki on github]


[meeting dedicated page]
<https://github.com/ocaml/dune/wiki/dev-meeting-2025-02-19>

[zoom]
<https://us06web.zoom.us/j/85096877776?pwd=cWNhU1dHQ1ZNSjZuOUZCQ0h2by9Udz09>

[google calendar]
<https://calendar.google.com/calendar/u/0/embed?src=c_5cd698df6784e385b1cdcdc1dbca18c061faa96959a04781566d304dc9ec7319@group.calendar.google.com>

[dune wiki on github] <https://github.com/ocaml/dune/wiki>


Asking For Community Feedback on the OCaml Platform Communications
══════════════════════════════════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/asking-for-community-feedback-on-the-ocaml-platform-communications/16142/1>


Sabine Schmaltz announced
─────────────────────────

  Hi all,

  I'm looking for feedback on the OCaml Platform communications,
  especially the Platform Newsletter and the [OCaml.org] Changelog.

  For this, I have prepared a Google form survey (you can send me your
  responses by email if you prefer):

  <https://docs.google.com/forms/d/e/1FAIpQLSctTt-WtWEU9heJixGAcAxeUxZhPeX0ioTnaPk6VKTwYHHs9A/viewform>

  The survey aims to improve both the *process* and the *usefulness* of
  the *OCaml Platform communications* and to help me create a handbook
  that gives a clear picture of all our developer-focused communication
  channels, as well as how the *new Developer Advocate role* at Tarides
  can support the maintainers in these communications.

  A major aim of this effort is to *adapt the process* around the
  communications to minimize the amount of friction imposed on engineers
  and to maximize the *usefulness to the readers*.

  Thanks for your help!


[OCaml.org] <http://ocaml.org/>


Old CWN
═══════

  If you happen to miss a CWN, you can [send me a message] and I'll mail
  it to you, or go take a look at [the archive] or the [RSS feed of the
  archives].

  If you also wish to receive it every week by mail, you may subscribe
  to the [caml-list].

  [Alan Schmitt]


[send me a message] <mailto:alan.schmitt@polytechnique.org>

[the archive] <https://alan.petitepomme.net/cwn/>

[RSS feed of the archives] <https://alan.petitepomme.net/cwn/cwn.rss>

[caml-list] <https://sympa.inria.fr/sympa/info/caml-list>

[Alan Schmitt] <https://alan.petitepomme.net/>


[-- Attachment #2: Type: text/html, Size: 21238 bytes --]

             reply	other threads:[~2025-02-18 14:33 UTC|newest]

Thread overview: 236+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 14:33 Alan Schmitt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-15  9:51 Alan Schmitt
2025-04-08 13:14 Alan Schmitt
2025-04-01  9:12 Alan Schmitt
2025-03-25  8:06 Alan Schmitt
2025-03-18 10:18 Alan Schmitt
2025-03-11 15:00 Alan Schmitt
2025-03-04 14:01 Alan Schmitt
2025-02-25 10:36 Alan Schmitt
2025-02-11  7:17 Alan Schmitt
2025-02-04 12:05 Alan Schmitt
2025-01-28 13:24 Alan Schmitt
2025-01-21 15:47 Alan Schmitt
2025-01-14  8:20 Alan Schmitt
2025-01-07 17:26 Alan Schmitt
2024-12-31  8:03 Alan Schmitt
2024-12-24  8:55 Alan Schmitt
2024-12-17 13:05 Alan Schmitt
2024-12-10 13:48 Alan Schmitt
2024-12-03 14:44 Alan Schmitt
2024-11-26  8:30 Alan Schmitt
2024-11-19  6:52 Alan Schmitt
2024-11-12 15:00 Alan Schmitt
2024-11-05 13:22 Alan Schmitt
2024-10-29 13:30 Alan Schmitt
2024-10-22 12:42 Alan Schmitt
2024-10-15 13:31 Alan Schmitt
2024-10-08 10:56 Alan Schmitt
2024-10-01 13:37 Alan Schmitt
2024-09-24 13:18 Alan Schmitt
2024-09-17 14:02 Alan Schmitt
2024-09-10 13:55 Alan Schmitt
2024-09-03  8:24 Alan Schmitt
2024-08-27  9:02 Alan Schmitt
2024-08-20  9:29 Alan Schmitt
2024-08-13 13:21 Alan Schmitt
2024-08-06  9:00 Alan Schmitt
2024-07-30 13:26 Alan Schmitt
2024-07-23 13:30 Alan Schmitt
2024-07-16  6:24 Alan Schmitt
2024-07-09  9:19 Alan Schmitt
2024-07-02  7:30 Alan Schmitt
2024-06-25 13:58 Alan Schmitt
2024-06-18 13:05 Alan Schmitt
2024-06-11 15:04 Alan Schmitt
2024-06-04 13:26 Alan Schmitt
2024-05-28  9:07 Alan Schmitt
2024-05-21 13:07 Alan Schmitt
2024-05-14 13:25 Alan Schmitt
2024-05-07  7:30 Alan Schmitt
2024-04-30  7:22 Alan Schmitt
2024-04-23 12:17 Alan Schmitt
2024-04-16 12:00 Alan Schmitt
2024-04-09  9:15 Alan Schmitt
2024-04-02 14:31 Alan Schmitt
2024-03-26  6:32 Alan Schmitt
2024-03-19 15:09 Alan Schmitt
2024-03-12 10:31 Alan Schmitt
2024-03-05 14:50 Alan Schmitt
2024-02-27 13:53 Alan Schmitt
2024-02-20  9:12 Alan Schmitt
2024-02-13  8:42 Alan Schmitt
2024-02-06 15:14 Alan Schmitt
2024-01-30 14:16 Alan Schmitt
2024-01-23  9:45 Alan Schmitt
2024-01-16 10:01 Alan Schmitt
2024-01-09 13:40 Alan Schmitt
2024-01-02  8:59 Alan Schmitt
2023-12-26 10:12 Alan Schmitt
2023-12-19 10:10 Alan Schmitt
2023-12-12 10:20 Alan Schmitt
2023-12-05 10:13 Alan Schmitt
2023-11-28  9:09 Alan Schmitt
2023-11-21  7:47 Alan Schmitt
2023-11-14 13:42 Alan Schmitt
2023-11-07 10:31 Alan Schmitt
2023-10-31 10:43 Alan Schmitt
2023-10-24  9:17 Alan Schmitt
2023-10-17  7:46 Alan Schmitt
2023-10-10  7:48 Alan Schmitt
2023-10-03 13:00 Alan Schmitt
2023-09-19  8:54 Alan Schmitt
2023-09-12 13:21 Alan Schmitt
2023-09-05  9:00 Alan Schmitt
2023-08-29 13:04 Alan Schmitt
2023-08-22  9:20 Alan Schmitt
2023-08-15 16:33 Alan Schmitt
2023-08-08  8:53 Alan Schmitt
2023-08-01  7:13 Alan Schmitt
2023-07-25  8:45 Alan Schmitt
2023-07-11  8:45 Alan Schmitt
2023-07-04  9:18 Alan Schmitt
2023-06-27  8:38 Alan Schmitt
2023-06-20  9:52 Alan Schmitt
2023-06-13  7:09 Alan Schmitt
2023-06-06 14:22 Alan Schmitt
2023-05-30 15:43 Alan Schmitt
2023-05-23  9:41 Alan Schmitt
2023-05-16 13:05 Alan Schmitt
2023-05-09 11:49 Alan Schmitt
2023-05-02  8:01 Alan Schmitt
2023-04-25  9:25 Alan Schmitt
2023-04-18  8:50 Alan Schmitt
2023-04-11 12:41 Alan Schmitt
2023-04-04  8:45 Alan Schmitt
2023-03-28  7:21 Alan Schmitt
2023-03-21 10:07 Alan Schmitt
2023-03-14  9:52 Alan Schmitt
2023-03-07  9:02 Alan Schmitt
2023-02-28 14:38 Alan Schmitt
2023-02-21 10:19 Alan Schmitt
2023-02-14  8:12 Alan Schmitt
2023-02-07  8:16 Alan Schmitt
2023-01-31  6:44 Alan Schmitt
2023-01-24  8:57 Alan Schmitt
2023-01-17  8:37 Alan Schmitt
2022-11-29 14:53 Alan Schmitt
2022-09-27  7:17 Alan Schmitt
2022-09-20 14:01 Alan Schmitt
2022-09-13  8:40 Alan Schmitt
2022-08-23  8:06 Alan Schmitt
2022-08-16  8:51 Alan Schmitt
2022-08-09  8:02 Alan Schmitt
2022-08-02  9:51 Alan Schmitt
2022-07-26 17:54 Alan Schmitt
2022-07-19  8:58 Alan Schmitt
2022-07-12  7:59 Alan Schmitt
2022-07-05  7:42 Alan Schmitt
2022-06-28  7:37 Alan Schmitt
2022-06-21  8:06 Alan Schmitt
2022-06-14  9:29 Alan Schmitt
2022-06-07 10:15 Alan Schmitt
2022-05-31 12:29 Alan Schmitt
2022-05-24  8:04 Alan Schmitt
2022-05-17  7:12 Alan Schmitt
2022-05-10 12:30 Alan Schmitt
2022-05-03  9:11 Alan Schmitt
2022-04-26  6:44 Alan Schmitt
2022-04-19  5:34 Alan Schmitt
2022-04-12  8:10 Alan Schmitt
2022-04-05 11:50 Alan Schmitt
2022-03-29  7:42 Alan Schmitt
2022-03-22 13:01 Alan Schmitt
2022-03-15  9:59 Alan Schmitt
2022-03-01 13:54 Alan Schmitt
2022-02-22 12:43 Alan Schmitt
2022-02-08 13:16 Alan Schmitt
2022-02-01 13:00 Alan Schmitt
2022-01-25 12:44 Alan Schmitt
2022-01-11  8:20 Alan Schmitt
2022-01-04  7:56 Alan Schmitt
2021-12-28  8:59 Alan Schmitt
2021-12-21  9:11 Alan Schmitt
2021-12-14 11:02 Alan Schmitt
2021-11-30 10:51 Alan Schmitt
2021-11-16  8:41 Alan Schmitt
2021-11-09 10:08 Alan Schmitt
2021-11-02  8:50 Alan Schmitt
2021-10-19  8:23 Alan Schmitt
2021-09-28  6:37 Alan Schmitt
2021-09-21  9:09 Alan Schmitt
2021-09-07 13:23 Alan Schmitt
2021-08-24 13:44 Alan Schmitt
2021-08-17  6:24 Alan Schmitt
2021-08-10 16:47 Alan Schmitt
2021-07-27  8:54 Alan Schmitt
2021-07-20 12:58 Alan Schmitt
2021-07-06 12:33 Alan Schmitt
2021-06-29 12:24 Alan Schmitt
2021-06-22  9:04 Alan Schmitt
2021-06-01  9:23 Alan Schmitt
2021-05-25  7:30 Alan Schmitt
2021-05-11 14:47 Alan Schmitt
2021-05-04  8:57 Alan Schmitt
2021-04-27 14:26 Alan Schmitt
2021-04-20  9:07 Alan Schmitt
2021-04-06  9:42 Alan Schmitt
2021-03-30 14:55 Alan Schmitt
2021-03-23  9:05 Alan Schmitt
2021-03-16 10:31 Alan Schmitt
2021-03-09 10:58 Alan Schmitt
2021-02-23  9:51 Alan Schmitt
2021-02-16 13:53 Alan Schmitt
2021-02-02 13:56 Alan Schmitt
2021-01-26 13:25 Alan Schmitt
2021-01-19 14:28 Alan Schmitt
2021-01-12  9:47 Alan Schmitt
2021-01-05 11:22 Alan Schmitt
2020-12-29  9:59 Alan Schmitt
2020-12-22  8:48 Alan Schmitt
2020-12-15  9:51 Alan Schmitt
2020-12-01  8:54 Alan Schmitt
2020-11-03 15:15 Alan Schmitt
2020-10-27  8:43 Alan Schmitt
2020-10-20  8:15 Alan Schmitt
2020-10-06  7:22 Alan Schmitt
2020-09-29  7:02 Alan Schmitt
2020-09-22  7:27 Alan Schmitt
2020-09-08 13:11 Alan Schmitt
2020-09-01  7:55 Alan Schmitt
2020-08-18  7:25 Alan Schmitt
2020-07-28 16:57 Alan Schmitt
2020-07-21 14:42 Alan Schmitt
2020-07-14  9:54 Alan Schmitt
2020-07-07 10:04 Alan Schmitt
2020-06-30  7:00 Alan Schmitt
2020-06-16  8:36 Alan Schmitt
2020-06-09  8:28 Alan Schmitt
2020-05-19  9:52 Alan Schmitt
2020-05-12  7:45 Alan Schmitt
2020-05-05  7:45 Alan Schmitt
2020-04-28 12:44 Alan Schmitt
2020-04-21  8:58 Alan Schmitt
2020-04-14  7:28 Alan Schmitt
2020-04-07  7:51 Alan Schmitt
2020-03-31  9:54 Alan Schmitt
2020-03-24  9:31 Alan Schmitt
2020-03-17 11:04 Alan Schmitt
2020-03-10 14:28 Alan Schmitt
2020-03-03  8:00 Alan Schmitt
2020-02-25  8:51 Alan Schmitt
2020-02-18  8:18 Alan Schmitt
2020-02-04  8:47 Alan Schmitt
2020-01-28 10:53 Alan Schmitt
2020-01-21 14:08 Alan Schmitt
2020-01-14 14:16 Alan Schmitt
2020-01-07 13:43 Alan Schmitt
2019-12-31  9:18 Alan Schmitt
2019-12-17  8:52 Alan Schmitt
2019-12-10  8:21 Alan Schmitt
2019-12-03 15:42 Alan Schmitt
2019-11-26  8:33 Alan Schmitt
2019-11-12 13:21 Alan Schmitt
2019-11-05  6:55 Alan Schmitt
2019-10-15  7:28 Alan Schmitt
2019-09-03  7:35 Alan Schmitt

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=m2tt8rgw5u.fsf@mac-03220211.irisa.fr \
    --to=alan.schmitt@polytechnique.org \
    --cc=caml-list@inria.fr \
    --cc=lwn@lwn.net \
    /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