3 years ago · 3edee6d041
--- a/david/2021/06/20/index.html
+++ b/david/2021/06/20/index.html
 <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&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="/david/cache/2021/34dbd7a73608c6cde4adf12c4a7084c0/">cache</a>)</cite></p>
 </blockquote>
 <nav>
  <p class="center">
--- a/david/2021/sources/2021-06-20
+++ b/david/2021/sources/2021-06-20
 > <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>
--- a/david/log/index.xml
+++ b/david/log/index.xml
 &lt;p&gt;&lt;cite&gt;&lt;a href=&quot;https://github.com/benbjohnson/litestream#open-source-not-open-contribution&quot;&gt;Open-source, not open-contribution&lt;/a&gt;&lt;/cite&gt;&lt;/p&gt;
 &lt;/blockquote&gt;
 &lt;p&gt;Je ne crois pas avoir déjà croisé une annonce du genre. Je ne suis pas sûr de savoir quoi en penser. Toujours &lt;a href=&quot;https://larlet.fr/david/2021/06/04/&quot;&gt;cet entre-deux&lt;/a&gt; incertain entre les différentes échelles et prises de soins respectives.&lt;/p&gt;
 &lt;p&gt;&lt;mark&gt;Note après publication&amp;nbsp;:&lt;/mark&gt;&lt;/p&gt;
 &lt;p&gt;Mathieu m’indique que le &lt;a href=&quot;https://elm-lang.org/&quot;&gt;langage Elm&lt;/a&gt; a un mode de contribution un peu similaire par «&amp;nbsp;paquets&amp;nbsp;»&amp;nbsp;:&lt;/p&gt;
 &lt;blockquote lang=&quot;en&quot;&gt;
 &lt;p&gt;The major benefit of batching is that the review process is &lt;em&gt;structured&lt;/em&gt; 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.&lt;/p&gt;
 &lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://github.com/elm/expectations/blob/master/batching.md#batching&quot;&gt;Batching&lt;/a&gt;&lt;/em&gt; (&lt;a href=&quot;https://larlet.fr/david/cache/2021/34dbd7a73608c6cde4adf12c4a7084c0/&quot;&gt;cache&lt;/a&gt;)&lt;/cite&gt;&lt;/p&gt;
 &lt;/blockquote&gt;
 &lt;hr/&gt;&lt;p&gt;&lt;a href=&quot;mailto:david@larlet.fr&quot;&gt;Réagir ?&lt;/a&gt;&lt;/p&gt;</summary>
        </entry>