caml-list - the Caml user's mailing list
 help / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Sébastien Hinderer <Sebastien.Hinderer@inria.fr>,  caml-list@inria.fr
Subject: Re: [Caml-list] Ask questions on the mailing lists too
Date: Wed, 19 Jan 2022 22:43:17 +0100
Message-ID: <CAPFanBFKvU+nfSUgovQvdgkJ2Zqrd1cynsB9AxWkVeTP+Vd=rg@mail.gmail.com> (raw)
In-Reply-To: <YegvYb9U3VuqKP2k@prajna.paris.inria.fr>

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

Hi list,

Gabriel Scherer (2022/01/17 22:06 +0100):
> If you know people who would be willing to work on improving the
> accessibility of Discourse, we should think about funding this work.
Please
> get in touch!

On Wed, Jan 19, 2022 at 4:34 PM Sébastien Hinderer <
Sebastien.Hinderer@inria.fr> wrote:

> If somebody would volunteer, how would that work? You'd need some
> guarantees that the contributions you fund get both upstreamed and
> deployed, right?
>

First of all, I cannot make decisions alone, every action/expense of the
Foundation has to be approved by the executive committee (
http://ocaml-sf.org/about-us/ ).  So what I mention in this thread are just
hypotheses based on my preferences.

Now on the idea of "guarantees that contributions get upstreamed": whether
a contribution gets upstreamed depends on the work and the communication of
the contributor, but also on many factors outside their control. We
wouldn't ask a contributor to provide guarantees they can't give, and in
particular we would not condition the funding on upstreaming. If we approve
an action, and the contributor works to the best of their ability, I
believe they should be paid for their time even if it doesn't work out.

I don't have any experience with Discourse contributions, but a key to a
successful upstream contribution is always good communication (early and
often) with the upstream maintainers. In fact, I guess that the first
course of action would be to survey what has already been done
accessibility-wise for Discourse (see for example
https://meta.discourse.org/t/accessibility-audit-and-shepherd-for-making-improvements/66620/6
, https://meta.discourse.org/t/discourse-with-a-screen-reader/178105/27)
and understand the current status.

After looking a bit more at this: it looks like the Discourse people are
taking accessibility seriously, and it's possible that just nobody pointed
out the issues with the mailing-list registration to them. Just doing this
(studying how accessibility feedback is given, what information maintainers
are asking form, and then sending feedback on the mailing-list registration
question) could be a good first step before working on contributing the
code ourselves. And this good first step is already non-trivial work that
one could consider funding.

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

  reply index

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 18:57 [Caml-list] Type Error in OCaml Code mukesh tiwari
2022-01-15 21:19 ` Nicolás Ojeda Bär
2022-01-16  9:40   ` [Caml-list] Ask questions on the mailing lists too orbifx
2022-01-16 14:32     ` Sam Kuper
2022-01-17  9:20       ` Sébastien Hinderer
2022-01-17  9:34         ` Daniil Baturin
2022-01-17 14:30           ` Sam Kuper
2022-01-17 14:56             ` Daniil Baturin
2022-01-17 17:36               ` Sam Kuper
2022-01-17 21:08                 ` Gabriel Scherer
2022-01-18  1:51                   ` Sam Kuper
2022-01-19 15:46                     ` Sébastien Hinderer
2022-01-18  9:49                   ` orbifx
2022-01-18 15:55                     ` Simon Cruanes
2022-01-19 16:31                       ` Sébastien Hinderer
2022-01-19 17:55                         ` Sam Kuper
2022-01-19 18:09                           ` Sam Kuper
2022-01-19 19:09                             ` Sébastien Hinderer
2022-01-19 20:53                               ` Sam Kuper
2022-01-19 18:43                           ` Simon Cruanes
2022-01-19 19:03                           ` Sébastien Hinderer
2022-01-19 20:50                             ` Sam Kuper
2022-01-20 20:56                         ` Edwin Török
2022-03-11  8:46                           ` Sébastien Hinderer
2022-03-11  9:38                             ` Vasilis Goumas
2022-03-11  9:43                               ` Gabriel Scherer
2022-01-19 15:33                   ` Sébastien Hinderer
2022-01-19 21:43                     ` Gabriel Scherer [this message]
2022-01-19 22:02                       ` Sam Kuper
2022-01-19 22:38                         ` Sébastien Hinderer
     [not found]                 ` <50AF4FEF-5CD6-40E7-9FA3-78814CBEE230@etorok.eu>
2022-01-17 22:47                   ` Sam Kuper
2022-01-17  9:54         ` Alan Schmitt
2022-01-17 13:53           ` Sam Kuper
2022-01-19 15:18             ` Sébastien Hinderer
2022-01-19 15:54           ` Sébastien Hinderer
2022-01-20  9:13             ` Alan Schmitt
     [not found]             ` <87pmom7sz7.fsf@m4x.org>
2022-01-20 14:16               ` Sébastien Hinderer

Reply instructions:

You may reply publically 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='CAPFanBFKvU+nfSUgovQvdgkJ2Zqrd1cynsB9AxWkVeTP+Vd=rg@mail.gmail.com' \
    --to=gabriel.scherer@gmail.com \
    --cc=Sebastien.Hinderer@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

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror https://inbox.ocaml.org/caml-list

AGPL code for this site: git clone https://public-inbox.org/ public-inbox