<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>community &amp;mdash; Webmink In Draft</title>
    <link>https://the.webm.ink/tag:community</link>
    <description>Things cooking in the Minkiverse. They move elsewhere when the oven pings.</description>
    <pubDate>Wed, 29 Apr 2026 17:33:23 +0100</pubDate>
    <item>
      <title>A Note On Who To Pay</title>
      <link>https://the.webm.ink/who-to-pay</link>
      <description>&lt;![CDATA[In the context of my earlier essays about volunteering and social framing, the question recently arose of who should get paid when an open source project receives donations. The short answer is &#34;people who make it happen but wouldn&#39;t get paid otherwise&#34; but the thinking behind that is more complex than you might expect. !--more--&#xA;&#xA;Open source is not meant to be free of charge. It is just meant to have no internal ledger (everyone contributor bears their own costs and derives their own benefit from the greater work) - but since open source has to make no distinction (internal=external) that also resolves as no external ledger, by accident. (Aside: This by the way is a major issue legislatively, where the &#34;internal&#34; development of open source code ends up regulated much more than that of proprietary code.)&#xA;&#xA;But that&#39;s unfortunately led to a worldview that wants to treat all engagement with open source as philanthropic, denying those engaging in supporting roles any means of compensation and guilt-tripping anyone who needs support into silence. I call that &#34;dictating other people&#39;s sacrifices&#34; - it happens all over the charity sector too, where people seem to think skilled workers should work for peanuts &#34;because it&#39;s a charity&#34;.  I try to make sure that all the places where I have a say pay as many people as they can all they should, and then leave it up to those people how to spend (or donate) the resulting income. &#xA;&#xA;----&#xA;&#xA;Tags, Links and Mentions&#xA;&#xA;#OpenSource #Community #Sustaining #PayTheMaintainers #FreeSoftware #SoftwareFreedom #Governance #Notes&#xA;&#xA;Follow @webmink@the.webm.ink to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include @webmink@meshed.cloud as WriteFreely still doesn&#39;t display replies. a href=&#34;/About&#34;More/a.]]&gt;</description>
      <content:encoded><![CDATA[<p>In the context of my earlier essays about <a href="https://the.webm.ink/on-volunteering">volunteering</a> and <a href="https://the.webm.ink/getting-back-to-a-social-frame">social framing</a>, the question recently arose of who should get paid when an open source project receives donations. The short answer is “people who make it happen but wouldn&#39;t get paid otherwise” but the thinking behind that is more complex than you might expect. </p>

<p>Open source is not meant to be free of charge. It is just meant to have no internal ledger (everyone contributor bears their own costs and derives their own benefit from the greater work) – but since open source has to make no distinction (internal=external) that also resolves as no <em>external</em> ledger, by accident. (Aside: This by the way is a major issue legislatively, where the “internal” development of open source code ends up regulated much more than that of proprietary code.)</p>

<p>But that&#39;s unfortunately led to a worldview that wants to treat all engagement with open source as philanthropic, denying those engaging in supporting roles any means of compensation and guilt-tripping anyone who needs support into silence. I call that “dictating other people&#39;s sacrifices” – it happens all over the charity sector too, where people seem to think skilled workers should work for peanuts “because it&#39;s a charity”.  I try to make sure that all the places where I have a say pay as many people as they can all they should, and then leave it up to those people how to spend (or donate) the resulting income.</p>

<hr>

<h3 id="tags-links-and-mentions">Tags, Links and Mentions</h3>
<ul><li><a href="https://the.webm.ink/tag:OpenSource" class="hashtag"><span>#</span><span class="p-category">OpenSource</span></a> <a href="https://the.webm.ink/tag:Community" class="hashtag"><span>#</span><span class="p-category">Community</span></a> <a href="https://the.webm.ink/tag:Sustaining" class="hashtag"><span>#</span><span class="p-category">Sustaining</span></a> <a href="https://the.webm.ink/tag:PayTheMaintainers" class="hashtag"><span>#</span><span class="p-category">PayTheMaintainers</span></a> <a href="https://the.webm.ink/tag:FreeSoftware" class="hashtag"><span>#</span><span class="p-category">FreeSoftware</span></a> <a href="https://the.webm.ink/tag:SoftwareFreedom" class="hashtag"><span>#</span><span class="p-category">SoftwareFreedom</span></a> <a href="https://the.webm.ink/tag:Governance" class="hashtag"><span>#</span><span class="p-category">Governance</span></a> <a href="https://the.webm.ink/tag:Notes" class="hashtag"><span>#</span><span class="p-category">Notes</span></a></li></ul>

<p><em>Follow <code><a href="https://the.webm.ink/@/webmink@the.webm.ink" class="u-url mention">@<span>webmink@the.webm.ink</span></a></code> to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include <code><a href="https://the.webm.ink/@/webmink@meshed.cloud" class="u-url mention">@<span>webmink@meshed.cloud</span></a></code> as WriteFreely still doesn&#39;t display replies. <a href="/About">More</a>.</em></p>
]]></content:encoded>
      <guid>https://the.webm.ink/who-to-pay</guid>
      <pubDate>Wed, 27 Nov 2024 23:00:00 +0000</pubDate>
    </item>
    <item>
      <title>The Commission MUST Consult The Open Source Community</title>
      <link>https://the.webm.ink/the-commission-must-consult-the-open-source-community</link>
      <description>&lt;![CDATA[Update: Graduated to the OSI Blog!--more--&#xA;&#xA;I wrote recently about the possible origin of a serious defect in terminology in the Impact Assessment of the Cyber Resilience Act (CRA). But this is not the only problem with the Impact Assessment. A crucial one appears in Annex 2 (on page 4 of the Part 2 pdf), where it becomes clear from sections 2-4 that no open source communities or community fiduciaries were consulted as stakeholders. &#xA;&#xA;Top portion of sculpture at Brussels South Station. Topped by a gold weathervane, a black support structure on a ribbed black obelisk has the text &#34;In Your Own Time&#34;&#xA;&#xA;In the comments by the European Commission&#39;s policy officers given during a FOSDEM Main Stage panel it became clear they had been working on the language of the updates to the Public Liability Directive (PLD) and CRA for a significant time. When asked why they had not consulted the community until now (at 1:27:45 on the video), they replied it was the community&#39;s responsibility to find out about their work and show up to published consultations.&#xA;&#xA;It is not enough to expect the open source ecosystem to spontaneously show up - it is not structured in a way that makes that likely. In any case the consultation process has no category for individuals who make economically significant works outside the role of &#34;Company&#34; or &#34;Workforce&#34;. In other words, there were no consultations aimed at the community. At best we will show up late in the process asking why no-one called, as we are now.&#xA;&#xA;It is not unreasonable to ask to be treated in a way respectful of these realities; the process does so for SMEs. Section 4 of Annex 2 observes &#34;However, it has been very difficult to get substantial input from SMEs.&#34; As a result there was extensive, targeted outreach to SMEs resulting in significant inputs. No equivalent effort was made to reach out to open source charities like OSI, or to significant fiduciaries like Apache, Eclipse or Python.&#xA;&#xA;There are some inputs all the same. It&#39;s great that companies in the open source ecosystem do show up in consultations, and I know of a number who have lobbyists in Brussels. But they cannot be relied on to explain or even consider the perspectives of the significant number of community participants either outside their interest area or even opposed to it. &#xA;&#xA;It is very important to find ways to give a voice to the true community and not just its corporate members. Open source is a social movement with software artifacts and market consequences. Paying heed only to the latter (or even the latter two) is an inadequate approach. You can&#39;t proxy through SMEs, let alone multinationals and their lobbyists.&#xA;&#xA;This is a serious and persistent issue with the Commission&#39;s work; they need to become aware that when proposals affect the open source ecosystem (of which the open source software market they value is a part but not the whole), it is essential for them to treat the members of that ecosystem as key stakeholders and make at least as much of an effort to reach out to them as they do to SMEs -- possibly more. &#xA;&#xA;#CRA #PLD #Policy #OpenSource #Community #4thSector&#xA;&#xA;[MI-LD]: https://meshedinsights.com/2018/07/02/the-legislative-disconnect-of-the-meshed-society/&#xA;&#xA;Follow @webmink@the.webm.ink to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include @webmink@meshed.cloud as WriteFreely still doesn&#39;t display replies. a href=&#34;/About&#34;More/a.]]&gt;</description>
      <content:encoded><![CDATA[<p><em>Update:</em> Graduated to the <a href="https://blog.opensource.org/why-the-european-commission-must-consult-the-open-source-communities/">OSI Blog</a></p>

<p>I <a href="https://the.webm.ink/the-comprehension-error-behind-the-cra-issue">wrote recently</a> about the possible origin of a serious defect in terminology in the <a href="https://digital-strategy.ec.europa.eu/en/library/cyber-resilience-act-impact-assessment">Impact Assessment</a> of the Cyber Resilience Act (CRA). But this is not the only problem with the Impact Assessment. A crucial one appears in Annex 2 (on page 4 of the Part 2 pdf), where it becomes clear from sections 2-4 that <strong>no open source communities or community fiduciaries were consulted as stakeholders</strong>.</p>

<p><img src="https://pix.webm.ink/storage/m/_v2/528856369903823094/42a8ecf32-5a8865/3GfLqQLFGgCL/7IwVHTPo7RluA8WraxvIoac6RwsBXZy1lArh9Xyd.jpg" alt="Top portion of sculpture at Brussels South Station. Topped by a gold weathervane, a black support structure on a ribbed black obelisk has the text &#34;In Your Own Time&#34;" title="In Your Own Time sculpture, Brussels"></p>

<p>In the comments by the European Commission&#39;s policy officers given during <a href="https://fosdem.org/2023/schedule/event/cyber_resilience/">a FOSDEM Main Stage panel</a> it became clear they had been working on the language of the updates to the Public Liability Directive (PLD) and CRA for a significant time. When asked why they had not consulted the community until now (at 1:27:45 on the video), they replied it was the community&#39;s responsibility to find out about their work and show up to published consultations.</p>

<p>It is not enough to expect the open source ecosystem to spontaneously show up – it is not structured in a way that makes that likely. In any case the consultation process <a href="https://meshedinsights.com/2018/07/02/the-legislative-disconnect-of-the-meshed-society/">has no category</a> for individuals who make economically significant works outside the role of “Company” or “Workforce”. In other words, there <em>were</em> no consultations aimed at the community. At best we will show up late in the process asking why no-one called, as we are now.</p>

<p>It is not unreasonable to ask to be treated in a way respectful of these realities; the process does so for SMEs. Section 4 of Annex 2 observes “However, it has been very difficult to get substantial input from SMEs.” As a result there was extensive, targeted outreach to SMEs resulting in significant inputs. No equivalent effort was made to reach out to open source charities like OSI, or to significant fiduciaries like Apache, Eclipse or Python.</p>

<p>There are some inputs all the same. It&#39;s great that companies in the open source ecosystem do show up in consultations, and I know of a number who have lobbyists in Brussels. But they cannot be relied on to explain or even consider the perspectives of the significant number of community participants either outside their interest area or even opposed to it.</p>

<p>It is very important to find ways to give a voice to the true community and not just its corporate members. Open source is a social movement with software artifacts and market consequences. Paying heed only to the latter (or even the latter two) is an inadequate approach. You can&#39;t proxy through SMEs, let alone multinationals and their lobbyists.</p>

<p>This is a serious and persistent issue with the Commission&#39;s work; they need to become aware that when proposals affect the open source ecosystem (of which the open source software market they value is a part but not the whole), it is <em>essential</em> for them to treat the <a href="https://meshedinsights.com/2018/07/02/the-legislative-disconnect-of-the-meshed-society/">members of that ecosystem</a> as key stakeholders and make at least as much of an effort to reach out to them as they do to SMEs — possibly more.</p>

<p><a href="https://the.webm.ink/tag:CRA" class="hashtag"><span>#</span><span class="p-category">CRA</span></a> <a href="https://the.webm.ink/tag:PLD" class="hashtag"><span>#</span><span class="p-category">PLD</span></a> <a href="https://the.webm.ink/tag:Policy" class="hashtag"><span>#</span><span class="p-category">Policy</span></a> <a href="https://the.webm.ink/tag:OpenSource" class="hashtag"><span>#</span><span class="p-category">OpenSource</span></a> <a href="https://the.webm.ink/tag:Community" class="hashtag"><span>#</span><span class="p-category">Community</span></a> <a href="https://the.webm.ink/tag:4thSector" class="hashtag"><span>#</span><span class="p-category">4thSector</span></a></p>

<p><em>Follow <code><a href="https://the.webm.ink/@/webmink@the.webm.ink" class="u-url mention">@<span>webmink@the.webm.ink</span></a></code> to be informed of new posts. To discuss this post please reply from Mastodon etc. (search for the URL) &amp; include <code><a href="https://the.webm.ink/@/webmink@meshed.cloud" class="u-url mention">@<span>webmink@meshed.cloud</span></a></code> as WriteFreely still doesn&#39;t display replies. <a href="/About">More</a>.</em></p>
]]></content:encoded>
      <guid>https://the.webm.ink/the-commission-must-consult-the-open-source-community</guid>
      <pubDate>Thu, 16 Mar 2023 09:46:34 +0000</pubDate>
    </item>
  </channel>
</rss>