@@ -75,6 +75,13 @@ | |||
<p><cite><a href="https://github.com/benbjohnson/litestream#open-source-not-open-contribution">Open-source, not open-contribution</a></cite></p> | |||
</blockquote> | |||
<p>Je ne crois pas avoir déjà croisé une annonce du genre. Je ne suis pas sûr de savoir quoi en penser. Toujours <a href="/david/2021/06/04/">cet entre-deux</a> incertain entre les différentes échelles et prises de soins respectives.</p> | |||
<p><mark>Note après publication :</mark></p> | |||
<p>Mathieu m’indique que le <a href="https://elm-lang.org/">langage Elm</a> a un mode de contribution un peu similaire par « paquets » :</p> | |||
<blockquote lang="en"> | |||
<p>The major benefit of batching is that the review process is <em>structured</em> for coherent design. By allowing time for folks to share their experiences and suggestions, it becomes possible to consider them all together and better balance their needs. Shifting towards real-time responses on everything would necessarily degrade the overall design quality.</p> | |||
<p><cite><em><a href="https://github.com/elm/expectations/blob/master/batching.md#batching">Batching</a></em> (<a href="/david/cache/2021/34dbd7a73608c6cde4adf12c4a7084c0/">cache</a>)</cite></p> | |||
</blockquote> | |||
<nav> | |||
<p class="center"> |
@@ -9,3 +9,12 @@ | |||
> <cite>[Open-source, not open-contribution](https://github.com/benbjohnson/litestream#open-source-not-open-contribution)</cite> | |||
Je ne crois pas avoir déjà croisé une annonce du genre. Je ne suis pas sûr de savoir quoi en penser. Toujours [cet entre-deux](/david/2021/06/04/) incertain entre les différentes échelles et prises de soins respectives. | |||
==Note après publication :== | |||
Mathieu m’indique que le [langage Elm](https://elm-lang.org/) a un mode de contribution un peu similaire par « paquets » : | |||
> [en] The major benefit of batching is that the review process is *structured* for coherent design. By allowing time for folks to share their experiences and suggestions, it becomes possible to consider them all together and better balance their needs. Shifting towards real-time responses on everything would necessarily degrade the overall design quality. | |||
> | |||
> <cite>*[Batching](https://github.com/elm/expectations/blob/master/batching.md#batching)* ([cache](/david/cache/2021/34dbd7a73608c6cde4adf12c4a7084c0/))</cite> |
@@ -27,6 +27,13 @@ | |||
<p><cite><a href="https://github.com/benbjohnson/litestream#open-source-not-open-contribution">Open-source, not open-contribution</a></cite></p> | |||
</blockquote> | |||
<p>Je ne crois pas avoir déjà croisé une annonce du genre. Je ne suis pas sûr de savoir quoi en penser. Toujours <a href="https://larlet.fr/david/2021/06/04/">cet entre-deux</a> incertain entre les différentes échelles et prises de soins respectives.</p> | |||
<p><mark>Note après publication&nbsp;:</mark></p> | |||
<p>Mathieu m’indique que le <a href="https://elm-lang.org/">langage Elm</a> a un mode de contribution un peu similaire par «&nbsp;paquets&nbsp;»&nbsp;:</p> | |||
<blockquote lang="en"> | |||
<p>The major benefit of batching is that the review process is <em>structured</em> for coherent design. By allowing time for folks to share their experiences and suggestions, it becomes possible to consider them all together and better balance their needs. Shifting towards real-time responses on everything would necessarily degrade the overall design quality.</p> | |||
<p><cite><em><a href="https://github.com/elm/expectations/blob/master/batching.md#batching">Batching</a></em> (<a href="https://larlet.fr/david/cache/2021/34dbd7a73608c6cde4adf12c4a7084c0/">cache</a>)</cite></p> | |||
</blockquote> | |||
<hr/><p><a href="mailto:david@larlet.fr">Réagir ?</a></p></summary> | |||
</entry> | |||