<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (earth2marsh)</title>
    <link>https://pinboard.in/u:earth2marsh/public/</link>
    <description>recent bookmarks from earth2marsh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="https://www.jwz.org/blog/2016/10/they-live-and-the-secret-history-of-the-mozilla-logo/"/>
	<rdf:li rdf:resource="https://words.filippo.io/standard-of-care/"/>
	<rdf:li rdf:resource="https://github.com/langchain-ai/agent-inbox"/>
	<rdf:li rdf:resource="https://lists.llvm.org/pipermail/llvm-dev/2019-June/133308.html"/>
	<rdf:li rdf:resource="https://redmonk.com/sogrady/2025/08/06/cra-five-alarm-fire/"/>
	<rdf:li rdf:resource="https://github.com/kubernetes/community/blob/master/communication%2Fslack-migration-faq.md"/>
	<rdf:li rdf:resource="https://cryptpad.org/"/>
	<rdf:li rdf:resource="https://wallabag.org/"/>
	<rdf:li rdf:resource="https://github.com/microsoft/markitdown"/>
	<rdf:li rdf:resource="https://htmx.org/essays/vendoring/"/>
	<rdf:li rdf:resource="https://kdenlive.org/en/"/>
	<rdf:li rdf:resource="https://antonin.delpeuch.eu/posts/off-the-shelf-governance-models-for-small-foss-projects/"/>
	<rdf:li rdf:resource="https://docs.gitlab.com/ee/user/application_security/api_security/api_discovery/"/>
	<rdf:li rdf:resource="https://youtu.be/rmhYHzJpkuo"/>
	<rdf:li rdf:resource="https://berthub.eu/articles/posts/open-source-by-itself-is-no-alternative-for-big-tech/"/>
	<rdf:li rdf:resource="https://snikket.org/"/>
	<rdf:li rdf:resource="https://ente.io/auth/"/>
	<rdf:li rdf:resource="https://blog.mattcen.com/2023/07/04/stop-using-discord-for-your-open-source-communities/"/>
	<rdf:li rdf:resource="https://john.onolan.org/democratising-publishing/"/>
	<rdf:li rdf:resource="https://lineageos.org/"/>
	<rdf:li rdf:resource="https://google.github.io/rejoiner/"/>
	<rdf:li rdf:resource="https://blog.zmh.org/2024/10/07/private-equity-ruins.html"/>
	<rdf:li rdf:resource="https://cdibona.substack.com/p/when-open-source-goes-proprietary?triedRedirect=true"/>
	<rdf:li rdf:resource="https://gotosocial.org/"/>
	<rdf:li rdf:resource="https://techcrunch.com/2024/09/22/some-startups-are-going-fair-source-to-avoid-the-pitfalls-of-open-source-licensing/"/>
	<rdf:li rdf:resource="https://opencoreventures.com/blog/2024-05-open-charter-gives-open-source-users-predictability-admist-licensing-change-trend/"/>
	<rdf:li rdf:resource="https://redmonk.com/jgovernor/2024/09/13/open-source-foundations-considered-helpful/"/>
	<rdf:li rdf:resource="https://www.baldurbjarnason.com/2024/the-slow-evaporation-of-the-foss-surplus/"/>
	<rdf:li rdf:resource="https://lobste.rs/s/qeqgiq/why_yaak_is_not_open_source#c_k7tr74"/>
	<rdf:li rdf:resource="https://redmonk.com/rstephens/2024/08/26/software-licensing-changes-and-their-impact-on-financial-outcomes/"/>
	<rdf:li rdf:resource="https://opaonaws.io/docs/techdocs/architecture/"/>
	<rdf:li rdf:resource="https://github.com/PostHog/posthog"/>
	<rdf:li rdf:resource="https://paragliderproject.io/"/>
	<rdf:li rdf:resource="https://patterns.innersourcecommons.org/"/>
	<rdf:li rdf:resource="https://medium.com/processing-foundation/making-space-for-the-future-of-p5-js-d3c6bd3da9ac"/>
	<rdf:li rdf:resource="https://github.com/daveshanley/vacuum"/>
	<rdf:li rdf:resource="https://github.com/bufbuild/knit"/>
	<rdf:li rdf:resource="https://newsletter.goodtechthings.com/p/why-didnt-google-cloud-buy-hashicorp"/>
	<rdf:li rdf:resource="https://www.youtube.com/watch?v=hNcBk6cwim8"/>
	<rdf:li rdf:resource="https://martin.kleppmann.com/2021/04/14/goodbye-gpl.html"/>
	<rdf:li rdf:resource="https://www.hbs.edu/ris/Publication%20Files/24-038_51f8444f-502c-4139-8bf2-56eb4b65c58a.pdf"/>
	<rdf:li rdf:resource="https://www-computerworld-com.cdn.ampproject.org/v/s/www.computerworld.com/article/3714821/software-vendors-dump-open-source-go-for-the-cash-grab.amp.html?amp_gsa=1&amp;amp_js_v=a9&amp;usqp=mq331AQGsAEggAID#amp_tf=From%20%251%24s&amp;aoh=17116539803021&amp;csi=0&amp;referrer=https%3A%2F%2Fwww.google.com&amp;ampshare=https%3A%2F%2Fwww.computerworld.com%2Farticle%2F3714821%2Fsoftware-vendors-dump-open-source-go-for-the-cash-grab.html"/>
	<rdf:li rdf:resource="https://github.com/apigee/registry-experimental/blob/main/lint/style_guide_documentation.md"/>
	<rdf:li rdf:resource="https://radapp.io/"/>
	<rdf:li rdf:resource="https://www.volunteeramnestyday.net/"/>
	<rdf:li rdf:resource="https://telemetry.go.dev/"/>
	<rdf:li rdf:resource="https://github.com/cncf/toc/pull/1254"/>
	<rdf:li rdf:resource="https://wundergraph.com/"/>
	<rdf:li rdf:resource="https://ghost.org/"/>
	<rdf:li rdf:resource="https://playbook.dxw.com/"/>
	<rdf:li rdf:resource="https://ben.balter.com/2018/01/02/why-you-probably-shouldnt-add-a-cla-to-your-open-source-project/"/>
	<rdf:li rdf:resource="https://appflowy.io/"/>
	<rdf:li rdf:resource="https://www.linuxfoundation.org/research/state-of-open-standards-2023"/>
	<rdf:li rdf:resource="https://openpm.ai/"/>
	<rdf:li rdf:resource="https://github.com/Adyen/adyen-web/tree/bfc2dccc85d4b194f63d2cd3848ffa4dfcea6318/packages/playground"/>
	<rdf:li rdf:resource="https://github.com/serverlessworkflow/specification/blob/main/GOVERNANCE.md"/>
	<rdf:li rdf:resource="https://github.com/apioo/fusio"/>
	<rdf:li rdf:resource="https://github.com/Azure/azure-rest-api-specs/tree/main/documentation/api-scenario"/>
	<rdf:li rdf:resource="https://github.com/postman-open-technologies/gsoc-2023"/>
	<rdf:li rdf:resource="https://github.com/openclarity/apiclarity"/>
	<rdf:li rdf:resource="https://github.com/cisco-developer/api-insights"/>
	<rdf:li rdf:resource="https://github.com/readme/guides/shopify-github-actions"/>
	<rdf:li rdf:resource="https://giventofly.github.io/pixelit/"/>
	<rdf:li rdf:resource="https://github.com/pseudomuto/protoc-gen-doc"/>
	<rdf:li rdf:resource="https://github.com/karatelabs/karate"/>
	<rdf:li rdf:resource="https://markdoc.io/"/>
	<rdf:li rdf:resource="https://medium.com/teaxyz/tea-brew-478a9e736638"/>
	<rdf:li rdf:resource="https://github.com/apideck-libraries/portman"/>
	<rdf:li rdf:resource="https://www.jwz.org/gruntle/nomo.html"/>
	<rdf:li rdf:resource="https://www.infoworld.com/article/3632142/how-docker-broke-in-half.amp.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://www.jwz.org/blog/2016/10/they-live-and-the-secret-history-of-the-mozilla-logo/">
    <title>jwz: They Live and the secret history of the Mozilla logo</title>
    <dc:date>2025-12-17T00:21:44+00:00</dc:date>
    <link>https://www.jwz.org/blog/2016/10/they-live-and-the-secret-history-of-the-mozilla-logo/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>There's an artist you may have heard of, Shepard Fairey. He did the Obama "Hope" poster in 2008. But long before that, in the early 90s he had this semi-anonymous graffiti campaign, "Andre the Giant Has a Posse". It was everywhere. Stickers, stencils, wheat-paste posters, I saw them in every city I ever visited. It was a global propaganda campaign whose goals and meaning, if any, were completely obscure. I loved the mindfuckery of it, a campaign with no purpose, for which he had somehow managed to mobilize a worldwide army of helpers, primarly by intentionally giving up control of it and allowing it to take on its own life.



In the mid 90s, his Andre the Giant has a Posse campaign morphed into OBEY GIANT. Andre glowers out at you from under his enormous brow in a style referencing the Big Brother posters from the 1956 film of 1984 as well as the Futurist propaganda art of the 1930s and 40s.

Since then, the OBEY brand has grown tremendously, nearly outstripping even Hot Topic in our suburban malls. It has become the go-to fashion statement for backwards-baseball-cap-wearing bros across the nation. But let us not forget! It is a direct reference to They Live.</blockquote>
<blockquote>And do you see that poster over my shoulder there? That's a poster for Alamo Drafthouse's 2011 revival of They Live... this poster created by Shepard Fairey, specifically for that event. Shepard said at the time, "They Live was the basis for my use of the word 'obey,' The movie has a very strong message about the power of commercialism and the way that people are manipulated by advertising. [...] One of my main concepts with the Obey campaign as a whole was that obedience is the most valuable currency. People rarely consider how much power they sacrifice by blindly following a self-serving corporation's marketing agenda, and how their spending habits reflect the direction in which they choose to transfer power."</blockquote>]]></description>
<dc:subject>obey Mozilla history opensource branding</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a14c52753b8f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:obey"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Mozilla"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:history"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:branding"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://words.filippo.io/standard-of-care/">
    <title>The Geomys Standard of Care</title>
    <dc:date>2025-10-23T19:58:31+00:00</dc:date>
    <link>https://words.filippo.io/standard-of-care/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>One of the most impactful effects of professionalizing open source maintenance is that as professionals we can invest into upholding a set of standards that make our projects safer and more reliable. The same commitments and overhead that are often objected to when required of volunteers should be table stakes for professional maintainers.

I didn’t find a lot of prior art, so to compile the Geomys Standard of Care I started by surveying recent supply chain compromises to look for mitigable root causes. (By the way, you might have missed that email because it includes the name of a domain used for a phishing campaign, so it got flagged as phishing. Oops.) I also asked feedback from experts in various areas such as CI security, and from other Geomys maintainers.</blockquote>]]></description>
<dc:subject>opensource stewardship steward bestpractices maintenance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:14bbf683b693/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:stewardship"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:steward"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:bestpractices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:maintenance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/langchain-ai/agent-inbox">
    <title>GitHub - langchain-ai/agent-inbox: 📥 An inbox UX for interacting with human-in-the-loop agents.</title>
    <dc:date>2025-10-19T18:48:59+00:00</dc:date>
    <link>https://github.com/langchain-ai/agent-inbox</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>An inbox UX for interacting with human-in-the-loop agents.</blockquote>]]></description>
<dc:subject>ai llms inbox humans automation assistance opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:4b229429dbfa/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:inbox"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:humans"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:automation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:assistance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://lists.llvm.org/pipermail/llvm-dev/2019-June/133308.html">
    <title>[llvm-dev] A libc in LLVM</title>
    <dc:date>2025-10-19T18:05:32+00:00</dc:date>
    <link>https://lists.llvm.org/pipermail/llvm-dev/2019-June/133308.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Second, corporate development teams are uniquely qualified to utterly
botch a libc, yet still push it into widespread use, and the cost is
painful compatibility hacks in all applications. Apple did this with
their fork of BSD libc code. Google has done it once already with
their fork of musl in Fuchsia -- a project which I contributed
significant amounts of free labor to in terms of tracking down folks
for license clarification their lawyers wanted, only to have them
never bother to ask me why technical things were done they way they
were before making random useless and broken changes in their fork. A
corporate-led project does not have to answer to the community, and
will leave whatever bugs they introduce in place for the sake of
bug-compatibility with their own software rather than fixing them.
</blockquote>]]></description>
<dc:subject>opensource Google governance monoculture development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:97710b4a797f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:governance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:monoculture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://redmonk.com/sogrady/2025/08/06/cra-five-alarm-fire/">
    <title>The Cyber Resilience Act: A Five Alarm Fire – tecosystems</title>
    <dc:date>2025-08-06T13:57:40+00:00</dc:date>
    <link>https://redmonk.com/sogrady/2025/08/06/cra-five-alarm-fire/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Based on the financial downsides here, optimistic observers are concluding that the CRA could be a game changer in open source economics. As companies digest the potential penalties involved, they will be obligated to establish commercial relationships with open source projects they currently rely on at no cost. That means more money going from vendors relying on open source to those producing it, which would be a boon for developers. It also raises the question of what happens to product prices when manufacturers are compelled to pay for software they have to date consumed at no cost, but that’s outside the scope of this exercise.</blockquote>]]></description>
<dc:subject>security resilience opensource licensing Europe regulation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:1157a1627dbc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:resilience"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Europe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:regulation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/kubernetes/community/blob/master/communication%2Fslack-migration-faq.md">
    <title>community/communication/slack-migration-faq.md at master · kubernetes/community</title>
    <dc:date>2025-06-16T17:52:09+00:00</dc:date>
    <link>https://github.com/kubernetes/community/blob/master/communication%2Fslack-migration-faq.md</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Kubernetes Slack will lose its special status and will be changing into a standard free Slack on June 20, 2025. Sometime later this year, our community will likely move to a new platform. If you are responsible for a channel or private channel, or a member of a User Group, you will need to take some actions as soon as you can.</blockquote>]]></description>
<dc:subject>slack opensource community kubernetes k8s</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:3e487618ec5a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:slack"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:kubernetes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:k8s"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cryptpad.org/">
    <title>CryptPad.org</title>
    <dc:date>2025-05-16T04:53:50+00:00</dc:date>
    <link>https://cryptpad.org/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>CryptPad is a collaborative office suite that is end-to-end encrypted and open-source.</blockquote>
Google docs and workspace replacement]]></description>
<dc:subject>software office tools opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:5889c0126bdb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:office"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://wallabag.org/">
    <title>Save the web, freely | wallabag: a self hostable application for saving web pages</title>
    <dc:date>2025-05-07T00:31:16+00:00</dc:date>
    <link>https://wallabag.org/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Save and classify articles. Read them later. Freely.</blockquote>
Supports annotations! And Pinboard import.]]></description>
<dc:subject>bookmarks reading articles archives opensource tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f6f903375702/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:bookmarks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:reading"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:articles"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:archives"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/microsoft/markitdown">
    <title>GitHub - microsoft/markitdown: Python tool for converting files and office documents to Markdown.</title>
    <dc:date>2025-04-25T06:10:32+00:00</dc:date>
    <link>https://github.com/microsoft/markitdown</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>MarkItDown is a lightweight Python utility for converting various files to Markdown for use with LLMs and related text analysis pipelines. To this end, it is most comparable to textract, but with a focus on preserving important document structure and content as Markdown (including: headings, lists, tables, links, etc.) While the output is often reasonably presentable and human-friendly, it is meant to be consumed by text analysis tools -- and may not be the best option for high-fidelity document conversions for human consumption.

At present, MarkItDown supports:

PDF
PowerPoint
Word
Excel
Images (EXIF metadata and OCR)
Audio (EXIF metadata and speech transcription)
HTML
Text-based formats (CSV, JSON, XML)
ZIP files (iterates over contents)
Youtube URLs
EPubs
... and more!</blockquote>]]></description>
<dc:subject>tools text markdown Python opensource conversion files llms documents</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ce590acc39a4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:text"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Python"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:conversion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:files"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:documents"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://htmx.org/essays/vendoring/">
    <title>&lt;/&gt; htmx ~ Vendoring</title>
    <dc:date>2025-04-20T21:10:57+00:00</dc:date>
    <link>https://htmx.org/essays/vendoring/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>“Vendoring” software is a technique where you copy the source of another project directly into your own project.

It is an old technique that has been used for time immemorial in software development, but the term “vendoring” to describe it appears to have originated in the ruby community.

Vendoring can be and is still used today. You can vendor htmx, for example, quite easily.</blockquote>]]></description>
<dc:subject>dependencies management software opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:96a2412f7140/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:dependencies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://kdenlive.org/en/">
    <title>Kdenlive - Video Editing Freedom</title>
    <dc:date>2025-03-28T18:59:05+00:00</dc:date>
    <link>https://kdenlive.org/en/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Free and Open Source Video Editor
</blockquote>]]></description>
<dc:subject>editing opensource video linux macos windows</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:fad678be6368/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:editing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:linux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:macos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:windows"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://antonin.delpeuch.eu/posts/off-the-shelf-governance-models-for-small-foss-projects/">
    <title>Off-the-shelf governance models for small FOSS projects? | Antonin Delpeuch</title>
    <dc:date>2025-02-16T04:31:03+00:00</dc:date>
    <link>https://antonin.delpeuch.eu/posts/off-the-shelf-governance-models-for-small-foss-projects/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Off-the-shelf governance models for small FOSS projects?
Dec 20, 2024
A one-person open source project with a governance model, is that ridiculous? In this blog post I want to convince you it isn’t, and it could be key to solving widespread problems in the FOSS (Free and Open Source Software) ecosystem.

The problems
The free software movement is successful in many ways, but there are still annoying aspects to it. There are many situations where I feel like there is no shortage of people with goodwill, but we still fail to work together.

As a user of open source software, I often need to make a pick from a bunch of roughly equivalent solutions. Why do I need to choose between KeePass, KeePassX and KeePassXC? Why so many Linux distributions? Why all those open source navigation apps? If only their authors could work together to offer one real alternative to Google Maps, as functional and well rounded!

As a contributor to FOSS projects, I struggle with getting my changes accepted. My proposals routinely go unreviewed for months, if they ever get reviewed at all. When I consider contributing a change, I need to factor in this risk, so I regularly give up because the backlog of open pull requests left to rot is a red flag. I could imagine helping with maintenance of some of my dependencies, but there is often no way to even apply for that in the first place.

As a maintainer, I struggle to attract new contributors to my projects. If I do get some contributions, their authors do not stick around much. I get tired of this maintenance work. I feel lonely and depressed.

Why is it that way? There are surely many factors, but to me, a crucial one is cultural. We don’t really have the culture of setting up structures for team work. When I start a new open source project, I primarily think about the use case I want to support. I want the tool to be really good: easy to use, reliable, architecturally sound, well tested. I make it open source because I want to make it maximally useful to people. I don’t have a plan for its sustainability, because I just assume that if my tool is sufficiently useful to enough people, contributors will somehow come and help out - isn’t that the point of open source? Look, I have even added a CODE_OF_CONDUCT.md document to my repository, so I’m a nice and polite guy that people should be able to work with!

Open source is full of people like me. I have been trained to solve technical problems, and to consider human problems as basically not in my department. To build communities around the projects I am involved in, I essentially hope that we’ll just bond over our common love for good software and that the rest will follow. This is the core of the problem I want to tackle: this assumption that team work will just succeed on its own if people come to help. In my experience it’s really not the case.

It’s not a ground-breaking thesis either. The essay “The tyranny of structurelessness” by Jo Freeman did such a great job (in 1970!) at explaining why formal roles and decision procedures are helpful to make teams function properly, even at a small scale.

A lot of established open source projects know that, and have indeed formal governance models that shape the day-to-day decisions, onboarding processes and other procedures. The FOSS Governance Collection contains plenty of examples of tried and tested models which were likely instrumental in the popularity of the projects which adopted them.

The problem is: none of those governance models seem tailored to small projects that just got published and don’t have a community yet. As someone who just started a small FOSS project, I can’t start requiring “three +1 votes from members of the Project Management Committee” to publish a release - I am on my own! So I don’t choose a governance model yet and just let the forge platform shape the permissions and interactions in my project.

The default governance model that forges push us into
In the absence of a conscious choice of governance model, the default workflows defined by the forge (such as GitHub or GitLab) are the de-facto governance model of the project. Let’s see what that looks like.

When I publish a new open source project on GitHub, the repository gets created under my own user account by default. I am the one and only “Owner” of the repository. I am able to add “Collaborators” in the settings. They do not have the same privileges as I have: for instance, they are not able to add other collaborators themselves. The list of collaborators on a repository is also not displayed publicly, nor is it possible to apply to become a collaborator via GitHub. If someone wants to help maintain my project, the options they have are fishing for my email address, or communicate by opening an “Issue”. Isn’t that a great metaphor? The fact that they offer their help is treated as an issue by the platform!

To be able to add co-owners, one needs to create an organization and tranfer the ownership of the repository to that organization. It does give more governance options, with the ability to create teams and assign rather granular permissions to them, but I am mostly left on my own to define those teams (I need to take the initiative to set them up) and it still does not let people apply to join them.

To summarize, in GitHub’s default governance model, the project has one leader and they are there to stay. It’s called implicit feudalism and corresponds rather well to the notion of Benevolent Dictator For Life (BDFL) used in the free software movement. While some projects make a conscious decision to adopt that model, it isn’t very helpful to grow a community and avoid maintainer burnout.

Needless to say, the default settings offered by forges have a huge impact on the overall ecosystem. I would be interested in working on improving those defaults, and Forgejo feels like a fitting project where to explore interventions around this problem.

Licenses and the “just fork it” mentality
Another reason for the lack of interest in governance models is, I think, the belief that an open source license is the only real governance model a project needs. It goes like this: if you are not happy with the way the project is run, you can “just fork it” and you have a copy that you can run the way you want. If you just stick to what most licenses say, publishing an open source project isn’t a promise to review and integrate other people’s changes in it, nor to onboard anyone on the team. Obviously, advising people to fork a project if they’re unhappy isn’t exactly ideal for community building. There are other issues with this stance, which are by now well known, such as the importance of certain assets (domain names, coordinates in package repositories…) that cannot be retained in a fork, or the difficulty for users to keep an overview of the fork landscape of a project.

Still, one nice achievement of the open source movement is that we have a common understanding of the importance of licenses. We understand that assigning licenses to software projects is crucial to enable their adoption, both for users and contributors. Many forge platforms will explicitly encourage you to add one when creating a project.

You wouldn’t publish a repo without a license

Can we grow the same sort of awareness for governance models? Can we get to a stage where most open source developers would have the reflex of systematically adding a governance model to their projects when publishing them, even for the tiniest, most insignificant libraries? The first step towards that goal is to convince you, reader, that it would be a worthwhile pursuit.

When I told a friend that I had adopted a governance model for a project I had just published and where I was the only contributor, their reaction was to ask: “what is there to govern?”. I think that’s a pretty natural reaction! So here’s my response. I wanted to:

make it clear to prospective contributors that they are welcome to get involved, by showing a clear path to co-maintainership,
make it clear to myself how I hope to integrate people in the project and make myself eventually redundant, so that I keep this as a goal even at the initial stage of the project where I have a lot of enthusiasm for working on it and taking responsibility for things;
set up a basis for collective decision making before the need for it arises, because it’s a lot easier that way.
The main problem is: the existing FOSS governance models are designed for mature projects and it feels like a lot of effort to design one from scratch. Why should I reinvent the wheel? My project isn’t that special, and I am not a governance specialist so I wish I could adopt an off-the-shelf model. Just like I am not a copyright lawyer and wouldn’t want to write a new license for every project I publish.</blockquote>]]></description>
<dc:subject>opensource governance models</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:236103a5098e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:governance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:models"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://docs.gitlab.com/ee/user/application_security/api_security/api_discovery/">
    <title>API Discovery | GitLab</title>
    <dc:date>2025-01-09T02:08:54+00:00</dc:date>
    <link>https://docs.gitlab.com/ee/user/application_security/api_security/api_discovery/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>API Discovery
Tier: Ultimate
Offering: GitLab.com, Self-managed, GitLab Dedicated
History 
API Discovery analyzes your application and produces an OpenAPI document describing the web APIs it exposes. This schema document can then be used by the API security testing analyzer or API Fuzzing to perform security scans of the web API.

Supported frameworks
Java Spring-Boot
When does API Discovery run?
API Discovery runs as a standalone job in your pipeline. The resulting OpenAPI document is captured as a job artifact so it can be used by other jobs in later stages.

API Discovery runs in the test stage by default. The test stage was chosen as it typically executes before the stages used by other security features such as API security testing and API fuzzing.</blockquote>]]></description>
<dc:subject>apis discovery opensource pipelines security platformengineering</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:4b1eba46e2d0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:discovery"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:pipelines"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platformengineering"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://youtu.be/rmhYHzJpkuo">
    <title>Reimagining OSS Licensing and Commercialization with Fair Source Adam Jacob, System Initiative</title>
    <dc:date>2025-01-05T06:40:08+00:00</dc:date>
    <link>https://youtu.be/rmhYHzJpkuo</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[2:10 - The difference between free software, open source, and fair Source.
11:34 - How to choose a business model.
16:08 - Pricing and packaging.
16:58 - Licensing.
17:43 - Examples of different business models.
29:27 - Competition.]]></description>
<dc:subject>opensource licensing distribution productmanagement business models</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:99e900e693ce/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:distribution"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:models"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://berthub.eu/articles/posts/open-source-by-itself-is-no-alternative-for-big-tech/">
    <title>Open Source on its own is no alternative to Big Tech - Bert Hubert's writings</title>
    <dc:date>2025-01-05T00:54:19+00:00</dc:date>
    <link>https://berthub.eu/articles/posts/open-source-by-itself-is-no-alternative-for-big-tech/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Experimenting is useful, but know that Open Source is the underdog, and there are many people waiting for an opportunity to enthusiastically declare that it has failed. This is due to commercial or conservative considerations - let’s stick with what we have, then we don’t need to change anything!

So, only start if at least the following conditions are met:

Achievable scope - very carefully determine how much you can do with the time, budget and people you have.
Change management - people participating in the trial must be able to come forward early. Set up a test environment months in advance where everyone can try out whether everything works. Listen carefully to all concerns raised. Verify that the experiment can overcome the designated challenges. Because, yes, there is still an old label printer that really needs to keep working. And there are also visually impaired people in your organization who need high-contrast support and screen readers.
Training sessions - </blockquote>]]></description>
<dc:subject>opensource enterprise services</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:80d6adeabd5e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:enterprise"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:services"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://snikket.org/">
    <title>Snikket Chat | Simple, secure and private messaging</title>
    <dc:date>2024-12-27T15:49:04+00:00</dc:date>
    <link>https://snikket.org/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Chat that is simple, secure, and private
Everything you expect from an easy-to-use messaging platform, but now under your control.</blockquote>]]></description>
<dc:subject>protocol privacy security chat messaging opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:eea55781fef6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:protocol"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:chat"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:messaging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ente.io/auth/">
    <title>Ente Auth - Open source 2FA authenticator, with E2EE backups</title>
    <dc:date>2024-12-05T22:14:27+00:00</dc:date>
    <link>https://ente.io/auth/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Open source 2FA authenticator, with end-to-end encrypted backups</blockquote>
<blockquote>
Authy has dropped all support for its desktop apps. It is no longer possible to export data from Authy using methods 1 and 2. You will either need a rooted android phone or you will need to reconfigure 2FA for each of your accounts.
</blockquote>]]></description>
<dc:subject>2fa mfa authentication privacy security opensource tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:69cc3173070d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:2fa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mfa"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:authentication"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:security"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.mattcen.com/2023/07/04/stop-using-discord-for-your-open-source-communities/">
    <title>Stop Using Discord for Your Open source Communities | mattcen's mumblings</title>
    <dc:date>2024-10-31T20:33:51+00:00</dc:date>
    <link>https://blog.mattcen.com/2023/07/04/stop-using-discord-for-your-open-source-communities/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>This is not a post about community management or content moderation. I have lots of opinions on those, but this post is primarily to address why I am frustrated with Discord as a platform for managing specifically open source software communities, and to offer some potential alternatives.

The short version of why I don’t like Discord for this use-case is:

I need to join Yet Another Server to be able to see chat history for a given community
I need an account to join that server
I need to use the Discord website or app, which often has flashy distractions and “What’s new” pop-ups1
Searching history to see if my question has already been answered is hard
If a community decides to move from Discord to another platform down the line, it is likely tricky (if not impossible) to export all that discussion content elsewhere, given Discord is a walled garden
There are many pros and cons this list doesn’t account for. In the rest of this post, I’ll try to cover these off a bit more thoroughly, and offer some alternatives as well as some of their pros and cons.</blockquote>]]></description>
<dc:subject>community tools discord criticism opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:168536f12cb4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:discord"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:criticism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://john.onolan.org/democratising-publishing/">
    <title>Democratising publishing</title>
    <dc:date>2024-10-30T20:50:11+00:00</dc:date>
    <link>https://john.onolan.org/democratising-publishing/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Ghost is a distributed non-profit foundation which gives away all of its intellectual property under a permissive MIT license. The company has no investors and, in fact, no owners of any kind. I don't own any part of Ghost, and neither does my co-founder Hannah.

We currently generate around $7.5M in annual revenue, and have been profitable and sustainable for the past 12 years.

"Wait, what?"

I'm glad you asked.</blockquote>]]></description>
<dc:subject>business opensource cms licensing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ff69d8553286/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://lineageos.org/">
    <title>LineageOS – LineageOS Android Distribution</title>
    <dc:date>2024-10-26T04:43:21+00:00</dc:date>
    <link>https://lineageos.org/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.</blockquote>]]></description>
<dc:subject>mobile android opensource os alternative</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e928a3c7bd33/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:android"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:os"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:alternative"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://google.github.io/rejoiner/">
    <title>Rejoiner · Uniform GraphQL schema from gRPC microservices</title>
    <dc:date>2024-10-18T23:43:53+00:00</dc:date>
    <link>https://google.github.io/rejoiner/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Uniform GraphQL schema from gRPC microservices</blockquote>]]></description>
<dc:subject>apis google graphql protobuf grpc opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:0ad498d19b1f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:google"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:graphql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:protobuf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:grpc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.zmh.org/2024/10/07/private-equity-ruins.html">
    <title>Private Equity Ruins Tech Companies | Zachary Hamed</title>
    <dc:date>2024-10-07T23:50:44+00:00</dc:date>
    <link>https://blog.zmh.org/2024/10/07/private-equity-ruins.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>PE firms raise money from institutional investors and high net worth individuals to buy companies, restructure them, and sell them later for a profit. They’re all about maximizing returns ASAP, usually in a 3-7 year window. That’s a shorter timeframe than the typical founder or public company shareholder, and far shorter than Matt’s time horizon:

I would like future generations to grow up with a web that is more open, more free, gives more liberty, and so open source is really my life’s work, even above WordPress and anything else. I hope to work on it the rest of my life.</blockquote>]]></description>
<dc:subject>finance equity opensource business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7629096e1ce8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:finance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:equity"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://cdibona.substack.com/p/when-open-source-goes-proprietary?triedRedirect=true">
    <title>When Open Source goes proprietary, or starts thinking about the law...</title>
    <dc:date>2024-10-05T18:43:22+00:00</dc:date>
    <link>https://cdibona.substack.com/p/when-open-source-goes-proprietary?triedRedirect=true</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>These often come down to confusing open source software development with a business model.  It’s almost banal to say it, but releasing your software under an open source license means, simply, you will not be able to make per copy software revenue from it. Your points of control are constrained in ways that proprietary software licensing does not.</blockquote>]]></description>
<dc:subject>opensource licensing business productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:af49afc539da/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gotosocial.org/">
    <title>GoToSocial - Fast, fun, ActivityPub server, powered by Go.</title>
    <dc:date>2024-09-30T18:42:29+00:00</dc:date>
    <link>https://gotosocial.org/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>GoToSocial is an ActivityPub social network server, written in Golang.

GoToSocial provides a lightweight, customizable, and safety-focused entryway into the Fediverse.

With GoToSocial, you can keep in touch with your friends, post, read, and share images and articles. All without being tracked or advertised to!</blockquote>]]></description>
<dc:subject>fediverse golang opensource activitypub social</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:68aa466e4668/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:fediverse"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:golang"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:activitypub"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:social"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://techcrunch.com/2024/09/22/some-startups-are-going-fair-source-to-avoid-the-pitfalls-of-open-source-licensing/">
    <title>Some startups are going ‘fair source’ to avoid the pitfalls of open source licensing | TechCrunch</title>
    <dc:date>2024-09-23T06:21:06+00:00</dc:date>
    <link>https://techcrunch.com/2024/09/22/some-startups-are-going-fair-source-to-avoid-the-pitfalls-of-open-source-licensing/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The fair source concept is designed to help companies align themselves with the “open” software development sphere, without encroaching into existing licensing landscapes, be that open source, open core, or source-available, and while avoiding any negative associations that exist with “proprietary.”

However, fair source is also a response to the growing sense that open source isn’t working out commercially.

“Open source isn’t a business model — open source is a distribution model, it’s a software development model, primarily,” Chad Whitacre, Sentry’s head of open source, told TechCrunch. “And in fact, it places severe limits on what business models are available, because of the licensing terms.”</blockquote>]]></description>
<dc:subject>licensing opensource source business alternatives</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:207df2a732bd/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:alternatives"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://opencoreventures.com/blog/2024-05-open-charter-gives-open-source-users-predictability-admist-licensing-change-trend/">
    <title>Open Charter gives open source users predictability amidst the licensing change trend | Open Core Ventures</title>
    <dc:date>2024-09-19T01:58:55+00:00</dc:date>
    <link>https://opencoreventures.com/blog/2024-05-open-charter-gives-open-source-users-predictability-admist-licensing-change-trend/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>For users to trust commercial open-source software (COSS), companies can no longer simply say their code will be open source forever; they need to have a way to hold themselves accountable. One way to do this is to adopt OCV’s Open Charter, a legal statement of a company’s commitment to open source that protects open-source code as a public benefit. Open-source companies that adopt the Open Charter will be more predictable than those that don’t—users can feel assured that the company is committed to maintaining the open source for the long haul and won’t pull a bait and switch. </blockquote>]]></description>
<dc:subject>opensource charters licenses oss business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:452bb78e5abb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:charters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licenses"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:oss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://redmonk.com/jgovernor/2024/09/13/open-source-foundations-considered-helpful/">
    <title>Open Source Foundations Considered Helpful – James Governor's Monkchips</title>
    <dc:date>2024-09-15T03:02:28+00:00</dc:date>
    <link>https://redmonk.com/jgovernor/2024/09/13/open-source-foundations-considered-helpful/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>There is a paradox here that mirrors that of open source. While open source is a phenomenal distribution and community model, it is not in itself a business model. While open source foundations are a fantastic way to encourage the growth of a community around a project, they do not in themselves drive revenue to the commercial companies building those projects.</blockquote>]]></description>
<dc:subject>opensource licensing foundations governance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c3df94995c75/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:foundations"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:governance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.baldurbjarnason.com/2024/the-slow-evaporation-of-the-foss-surplus/">
    <title>The slow evaporation of the free/open source surplus – Baldur Bjarnason</title>
    <dc:date>2024-09-13T05:43:29+00:00</dc:date>
    <link>https://www.baldurbjarnason.com/2024/the-slow-evaporation-of-the-foss-surplus/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[good post, though I take issue with calling a supportive community "lucky" 
<blockquote>I have been worried about the state of FOSS in general and having read these two posts is a good an excuse as any for getting the rudimentary outline of the worry out onto the page.

Short version: my mental model of FOSS is that it’s a function of industry and labour surplus:

Industry. The software industry has extremely high margins (products that are both non-rivalrous and non-excludable will do that) and historically easy access to investment because of both low interest rates and the pervasive belief among the financial class that successful tech companies grow exponentially for extended periods.
Labour. Even though coders come from varying backgrounds, once they have a career many, if not most, become relatively high income middle class with significant spare time. A non-trivial number of coders in California also have moderate wealth from being secondary or tertiary beneficiaries of industry liquidity events which lets them work on FOSS as much as they want. (This is what keeps a surprising number of FOSS projects afloat.)
Industry surplus also leads to labour surplus in that companies let coders work on related FOSS projects during work.</blockquote>]]></description>
<dc:subject>opensource sustainability trends</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:526de1794163/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sustainability"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:trends"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://lobste.rs/s/qeqgiq/why_yaak_is_not_open_source#c_k7tr74">
    <title>Why Yaak is not open source | Lobsters</title>
    <dc:date>2024-09-12T05:12:59+00:00</dc:date>
    <link>https://lobste.rs/s/qeqgiq/why_yaak_is_not_open_source#c_k7tr74</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>I’ll put the bottom line up front: don’t conflate “open source”/“free software” with github’s specific social model of drive-by contributions, or even contributions at all. @gschier, if you reply only thinking about that, I’d be happy.

I really don’t buy this as an explanation of why open source doesn’t work. Many of the points made are a false dichotomy - for example, “Features will be added - Difficult in reality […] often quicker for the maintainer to just implement the feature themselves.”.

If you’re closed source, you’re making the decision to always do it yourself, but you can be open source and still do this, if that’s what you want. You aren’t obligated to accept anyone else’s contributions.</blockquote>]]></description>
<dc:subject>opensource licensing business productmanagement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cc576d40ac6e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://redmonk.com/rstephens/2024/08/26/software-licensing-changes-and-their-impact-on-financial-outcomes/">
    <title>Software Licensing Changes and Their Impact on Financial Outcomes – Alt + E S V</title>
    <dc:date>2024-08-26T18:53:11+00:00</dc:date>
    <link>https://redmonk.com/rstephens/2024/08/26/software-licensing-changes-and-their-impact-on-financial-outcomes/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>While in our sample we see revenue grow post-license change, we don’t see a notable change in the rate of growth. We also see very mixed results in company valuation, and there does not seem to be a clear link between moving from an open source to proprietary license and increasing the company’s value.</blockquote>]]></description>
<dc:subject>licensing oss opensource changes revenue business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a9df8aa73d4e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:oss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:changes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:revenue"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://opaonaws.io/docs/techdocs/architecture/">
    <title>Architecture | OPA on AWS</title>
    <dc:date>2024-08-12T17:56:51+00:00</dc:date>
    <link>https://opaonaws.io/docs/techdocs/architecture/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The below diagram illustrates the major components of the OPA platform.

The platform creation is automated by way of executing an AWS CDK script that will provision the needed resources in your AWS account. After running the script, you will have the Backstage developer portal running on AWS and it will be set up to persist its configurations to an RDS database. Backstage will be integrated with an identity provider to facilitate user logins. The default identity provider is Okta, but you can customize this to use a different one.

Backstage is also integrated with a version control system. It is configured to discover entity definition files in existing Git repositories so that these entities will show up in the portal. Backstage will also be able to create new repositories to hold the source code of applications and other resources that are created by portal users.

The default OPA version control system is GitLab. The platform creation scripts will set up a Community Edition of GitLab that runs on AWS, so that it can be used for demonstration purposes. It is possible through code modifications to switch to a different version control vendor that can be hosted on or outside of the AWS cloud.</blockquote>]]></description>
<dc:subject>backstage opensource platforms platformengineering aws</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7947eb2b8179/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:backstage"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platforms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platformengineering"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:aws"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/PostHog/posthog">
    <title>PostHog/posthog: 🦔 PostHog provides open-source product analytics, session recording, feature flagging and A/B testing that you can self-host.</title>
    <dc:date>2024-07-08T15:45:35+00:00</dc:date>
    <link>https://github.com/PostHog/posthog</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>PostHog is an all-in-one, open source platform for building better products
Specify events manually, or use autocapture to get started quickly
Analyze data with ready-made visualizations, or do it yourself with SQL
Only capture properties on the people you want to track, save money when you don't
Gather insights by capturing session replays, console logs, and network monitoring
Improve your product with A/B testing that automatically analyzes performance
Safely roll out features to select users or cohorts with feature flags
Send out fully customizable surveys to specific cohorts of users
Connect to external services and manage data flows with PostHog CDP
PostHog is available with hosting in the EU or US and is fully SOC 2 compliant. It's free to get started and comes with a generous monthly free tier:</blockquote>]]></description>
<dc:subject>analytics opensource productmanagement metrics webmetrics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:9dffa6b8826b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:analytics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:webmetrics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://paragliderproject.io/">
    <title>Paraglider documentation</title>
    <dc:date>2024-05-28T04:04:41+00:00</dc:date>
    <link>https://paragliderproject.io/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Paraglider is a cross-cloud control plane for configuring cloud networks</blockquote>
Paraglider is a control plane for cloud networking resources designed to simplify the tenant networking experience. The Paraglider Controller exposes the Paraglider API to tenants and uses public cloud APIs to manage the tenant’s cloud network.]]></description>
<dc:subject>clouds networking opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:b59f8a1b6b9a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:clouds"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:networking"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://patterns.innersourcecommons.org/">
    <title>Introduction | Patterns - Production, Innersource</title>
    <dc:date>2024-05-27T22:31:36+00:00</dc:date>
    <link>https://patterns.innersourcecommons.org/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>What is InnerSource?
We define InnerSource as:

The use of open source principles and practices for software development within the confines of an organization.</blockquote>]]></description>
<dc:subject>source Innersource opensource words patterns design</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6b4f82c4e3e2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:source"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:Innersource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:words"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:patterns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:design"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/processing-foundation/making-space-for-the-future-of-p5-js-d3c6bd3da9ac">
    <title>Making Space for the Future of p5.js | by Lauren Lee McCarthy | Processing Foundation | Medium</title>
    <dc:date>2024-05-26T07:18:45+00:00</dc:date>
    <link>https://medium.com/processing-foundation/making-space-for-the-future-of-p5-js-d3c6bd3da9ac</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>The dream I have for this project is to move to a model of rotating leadership. I want to see a one-year project lead fellowship position through the Processing Foundation that offers a paid opportunity to steward and lead the project in whichever direction this person chooses. Former project leaders would act as mentors for them, helping with handoffs and transition from year to year. I believe rotating leadership would best facilitate new ideas and perspectives guiding the project. It would open opportunities for more people to lead and learn from this experience in a supported and sustainable way.</blockquote>]]></description>
<dc:subject>opensource leadership rotation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:07292086d4a1/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:rotation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/daveshanley/vacuum">
    <title>daveshanley/vacuum: vacuum is the worlds fastest OpenAPI 3, OpenAPI 2 / Swagger linter and quality analysis tool. Built in go, it tears through API specs faster than you can think. vacuum is compatible with Spectral rulesets and generates compatible repor</title>
    <dc:date>2024-04-29T21:24:39+00:00</dc:date>
    <link>https://github.com/daveshanley/vacuum</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>vacuum is the worlds fastest OpenAPI 3, OpenAPI 2 / Swagger linter and quality analysis tool. Built in go, it tears through API specs faster than you can think. vacuum is compatible with Spectral rulesets and generates compatible reports.</blockquote>]]></description>
<dc:subject>apis tools linting linters opensource openapi</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:0426c969a07e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:linting"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:linters"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:openapi"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/bufbuild/knit">
    <title>bufbuild/knit: GraphQL-like capabilities to services using Protocol Buffers, gRPC, and Connect</title>
    <dc:date>2024-04-29T21:23:59+00:00</dc:date>
    <link>https://github.com/bufbuild/knit</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Knit brings GraphQL-like capabilities to RPCs. Knit has type-safe and declarative queries that shape the response, batching support to eliminate the N+1 problem, and first-class support for error handling with partial responses. It is built on top of Protobuf and Connect.

Deploy the Knit gateway to call all of your Connect/gRPC services from the web with the Knit client over HTTP/1.1 or HTTP/2. No changes to your services are needed to use type-safe declarative queries, response masking, or the error handling. Use more advanced feature like relations and partial responses as the need arises.</blockquote>]]></description>
<dc:subject>graphql apis gateways rpc opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ffb2744d6411/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:graphql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:gateways"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:rpc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://newsletter.goodtechthings.com/p/why-didnt-google-cloud-buy-hashicorp">
    <title>Why didn't one of the big clouds buy HashiCorp?</title>
    <dc:date>2024-04-29T19:25:06+00:00</dc:date>
    <link>https://newsletter.goodtechthings.com/p/why-didnt-google-cloud-buy-hashicorp</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>IBM has become such a shadowy afterthought1 that I don’t think too many people have strong feelings about them anymore. The big question is whether they will ditch HashiCorp’s new BUSL licensing scheme and go back to a true open-source model for products like Terraform and Vault, and I think it speaks to people’s lack of a handle on what IBM is up to these days that a plausible sentiment is “hey, they might do it!”

The main reaction from the community about HashiCorp spinning an increasingly narrow set of options into a $6.4 billion exit is “Welp … good for them.” And when a community says good for them, it’s quite conspicuous what they’re not saying: good for us.

But I want to raise a different question today: how the heck did we get to this point? Why was HashiCorp not snapped up long ago by a more viable cloud provider? Specifically: why did they not get bought by Google Cloud?</blockquote>]]></description>
<dc:subject>ibm hashicorp acquisitions analysis opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a814532d3f8a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ibm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hashicorp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:acquisitions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:analysis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.youtube.com/watch?v=hNcBk6cwim8">
    <title>Corporate Open Source is Dead - YouTube</title>
    <dc:date>2024-04-25T17:34:11+00:00</dc:date>
    <link>https://www.youtube.com/watch?v=hNcBk6cwim8</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Great point about CLAs, too.
<blockquote>Nobody likes being rugpulled. But lately, it's going around like a virus.

Why are so many former open source darlings selling out or relicensing? And is there anything you can do to fight back against these anti-open-source practices?</blockquote>]]></description>
<dc:subject>opensource licensing hashicorp videos clas</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:c8c32ddcb499/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hashicorp"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:videos"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:clas"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://martin.kleppmann.com/2021/04/14/goodbye-gpl.html">
    <title>It's time to say goodbye to the GPL — Martin Kleppmann’s blog</title>
    <dc:date>2024-04-24T16:57:24+00:00</dc:date>
    <link>https://martin.kleppmann.com/2021/04/14/goodbye-gpl.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Open source software has been tremendously successful, and it has come a long way since the origins of the free software movement born from 1990s anti-Microsoft sentiment. I will acknowledge that the FSF was instrumental in getting this all started. However, 30 years on, the ecosystem has changed, but the FSF has failed to keep up, and has become more and more out of touch. It has failed to establish a coherent response to cloud software and other recent threats to software freedom, and it just continues to rehash tired old arguments from decades ago. Now, by reinstating Stallman and dismissing the concerns about him, the FSF is actively harming the cause of free software. We must distance ourselves from the FSF and their worldview.

For all these reasons, I think it no longer makes sense to cling on to the GPL and copyleft. Let them go. Instead, I would encourage you to adopt a permissive license for your projects (e.g. MIT, BSD, Apache 2.0), and then focus your energies on the things that will really make a difference to software freedom: counteracting the monopolising effects of cloud software, developing sustainable business models that allow open source software to thrive, and pushing for regulation that prioritises the interests of software users over the interests of vendors.</blockquote>]]></description>
<dc:subject>gpl criticism copyleft licensing opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:49a54fea985e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:gpl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:criticism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:copyleft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.hbs.edu/ris/Publication%20Files/24-038_51f8444f-502c-4139-8bf2-56eb4b65c58a.pdf">
    <title>The Value of Open Source Software</title>
    <dc:date>2024-04-23T21:13:20+00:00</dc:date>
    <link>https://www.hbs.edu/ris/Publication%20Files/24-038_51f8444f-502c-4139-8bf2-56eb4b65c58a.pdf</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Harvard Business School paper from Hoffmann, Nagle, and Zhou on the estimated monetary value of open source is kind of an incredible feat.

$8.8 trillion, btw. 

That's the estimated value of open source, according to these researchers' excellent work. </blockquote>]]></description>
<dc:subject>opensource economics market value papers impact</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:2b4a34f16a33/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:economics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:market"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:value"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:papers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:impact"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www-computerworld-com.cdn.ampproject.org/v/s/www.computerworld.com/article/3714821/software-vendors-dump-open-source-go-for-the-cash-grab.amp.html?amp_gsa=1&amp;amp_js_v=a9&amp;usqp=mq331AQGsAEggAID#amp_tf=From%20%251%24s&amp;aoh=17116539803021&amp;csi=0&amp;referrer=https%3A%2F%2Fwww.google.com&amp;ampshare=https%3A%2F%2Fwww.computerworld.com%2Farticle%2F3714821%2Fsoftware-vendors-dump-open-source-go-for-the-cash-grab.html">
    <title>Software vendors dump open source, go for the cash grab | Computerworld</title>
    <dc:date>2024-03-28T19:29:17+00:00</dc:date>
    <link>https://www-computerworld-com.cdn.ampproject.org/v/s/www.computerworld.com/article/3714821/software-vendors-dump-open-source-go-for-the-cash-grab.amp.html?amp_gsa=1&amp;amp_js_v=a9&amp;usqp=mq331AQGsAEggAID#amp_tf=From%20%251%24s&amp;aoh=17116539803021&amp;csi=0&amp;referrer=https%3A%2F%2Fwww.google.com&amp;ampshare=https%3A%2F%2Fwww.computerworld.com%2Farticle%2F3714821%2Fsoftware-vendors-dump-open-source-go-for-the-cash-grab.html</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>opensource licensing business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:359d97f20d14/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/apigee/registry-experimental/blob/main/lint/style_guide_documentation.md">
    <title>registry-experimental/lint/style_guide_documentation.md at main · apigee/registry-experimental</title>
    <dc:date>2024-03-05T22:06:33+00:00</dc:date>
    <link>https://github.com/apigee/registry-experimental/blob/main/lint/style_guide_documentation.md</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>One of the topics in the scope of governing APIs that is often overlooked is the importance of providing and enforcing concrete styling rules on API specs. There are many ways to write an API spec. Depending on the type of the spec (OpenAPI, AsyncAPI, Protobuf, etc.), it is easy to simply look up how to write a spec for your API, write it, and then forget about it. However, individuals and organizations often overlook the importance of enforcing good style in their API specs. The spec specifies the API. It lays down the exact endpoints, descriptions, requirements, licenses, operations, and other metadata related to the API. Consequently, it is crucial to ensure the correctness of the API spec and to make sure that it is following industry-standard best practices.

The project I worked on during my internship at Google examines the importance of enforcing styling rules on API specs, and provides concrete data structures and a system through which organizations can declaratively enforce important styling rules on their API specs. The project in which my domain of work is used is the open-source API Registry project on Github. We define an API Style Guide as the data structure through which organizations can declare style rules on their API specs.</blockquote>]]></description>
<dc:subject>opensource apis standards style enforcement</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f98fff68e86e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:style"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:enforcement"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://radapp.io/">
    <title>Radius</title>
    <dc:date>2024-03-01T19:26:23+00:00</dc:date>
    <link>https://radapp.io/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Radius is an open-source, cloud-native, application platform that enables developers and the operators that support them to define, deploy, and collaborate on cloud-native applications across public clouds and private infrastructure</blockquote>]]></description>
<dc:subject>microsoft opensource kubernetes applications orchestration platformengineering</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:da787c2b59d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:kubernetes"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:applications"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:orchestration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:platformengineering"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.volunteeramnestyday.net/">
    <title>Volunteer Responsibility Amnesty Day</title>
    <dc:date>2024-02-23T15:19:04+00:00</dc:date>
    <link>https://www.volunteeramnestyday.net/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Volunteer Responsibility Amnesty Day is about checking with yourself, and ending the commitments you need to end – maybe by taking a break, or by rotating it on to someone else, or by sunsetting a project.</blockquote>]]></description>
<dc:subject>burnout activism opensource habits</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f25ee48fb454/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:burnout"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:activism"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:habits"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://telemetry.go.dev/">
    <title>Go Telemetry</title>
    <dc:date>2024-02-16T03:39:13+00:00</dc:date>
    <link>https://telemetry.go.dev/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Go Telemetry is a way for Go toolchain programs to collect data about their performance and usage. Uploaded data is used to help improve the Go toolchain and related tools. Go Telemetry is not built into users' binaries. See what Go Telemetry collects.</blockquote>]]></description>
<dc:subject>opensource metrics telemetry examples</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:d85c2750f549/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:telemetry"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:examples"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/cncf/toc/pull/1254">
    <title>Crossplane Graduation Proposal by jbw976 · Pull Request #1254 · cncf/toc</title>
    <dc:date>2024-02-05T20:12:26+00:00</dc:date>
    <link>https://github.com/cncf/toc/pull/1254</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Why are we ready to graduate?
Crossplane was initially accepted into the CNCF Sandbox in June 2020 then progressed to Incubation in September 2021. Since the promotion to Incubation, the Crossplane project has grown considerably and made significant strides along
multiple dimensions of maturity.

We are currently in the top 10% of all CNCF projects for contributor authors, at position 18 out of 173. Across all of the Crossplane projects there are 120 companies with “committers” (maintainers with merge permissions) in the period since Incubation. The overall number of contributors to the project is now almost 1,900.

Crossplane is in use in production environments at scale by several end-user organizations, which are documented in the public ADOPTERS.md. Some notable public adopters include Autodesk, Grafana, NASA Science Cloud, SAP, IBM, VMWare Tanzu, and Nokia.

Crossplane completed both a fuzzing security audit and a general security audit in 2023.

In light of the achievements outlined in this proposal, we recommend that the project is now ready for full Graduation.</blockquote>]]></description>
<dc:subject>opensource cncf crossplane graduation incubation lifecycle</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:a22846219843/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cncf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:crossplane"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:graduation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:incubation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:lifecycle"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://wundergraph.com/">
    <title>WunderGraph Cosmo: The Open-Source GraphQL Federation Solution - WunderGraph</title>
    <dc:date>2024-01-19T20:24:49+00:00</dc:date>
    <link>https://wundergraph.com/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote></blockquote>]]></description>
<dc:subject>graphql opensource apis</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:20b30280bdd4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:graphql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ghost.org/">
    <title>Ghost: Independent technology for modern publishing</title>
    <dc:date>2023-11-13T19:24:55+00:00</dc:date>
    <link>https://ghost.org/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[substack alternative ]]></description>
<dc:subject>blogging cms opensource services</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:678ef09465ae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:blogging"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:services"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://playbook.dxw.com/">
    <title>dxw’s Playbook - Playbook - dxw</title>
    <dc:date>2023-11-03T15:31:55+00:00</dc:date>
    <link>https://playbook.dxw.com/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>This Playbook is our reference for who we are and the way we do things. Something canonical that tells us what the current “right way” to do things is.

If you’re a current or potential client, this Playbook is also for you. To help you understand us and how we can work together.</blockquote>]]></description>
<dc:subject>playbooks companies company culture opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:985cc833edd4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:playbooks"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:companies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:company"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://ben.balter.com/2018/01/02/why-you-probably-shouldnt-add-a-cla-to-your-open-source-project/">
    <title>Why you probably shouldn’t add a CLA to your open source project | Ben Balter</title>
    <dc:date>2023-10-12T00:13:05+00:00</dc:date>
    <link>https://ben.balter.com/2018/01/02/why-you-probably-shouldnt-add-a-cla-to-your-open-source-project/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>If one of the most common reasons to open source a project (and indicators of success) is to receive contributions from others, why then would a project maintainer add significant friction to advancing one of their primary goals? CLAs require that the first interaction between an open source project and a potential contributor to involve a formal and complex legal agreement which signs away their legal rights — not exactly a warm welcome. Submitting one’s first contribution to an open source project is already scary enough as it is, even without the threat of a lawsuit as the first volley.

Most open source developers aren’t lawyers, and they shouldn’t have to be to contribute. If a project is optimizing for the developer experience in hopes of maximizing contributions, it would be antithetical then, to require a contributor to hire outside counsel to properly evaluate what they’re agreeing to, or in many cases, also get the sign off from their employer’s corporate counsel before they are allowed to contribute, a frustrating experience that can shift even the smallest contributions from minutes to weeks, assuming the developer ultimately gets approval, an outcome that’s not guaranteed in many corporate cultures.</blockquote>]]></description>
<dc:subject>cla contributions licensing opensource law legal</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:78c327e060a3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cla"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:contributions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:licensing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:law"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:legal"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://appflowy.io/">
    <title>AppFlowy.IO</title>
    <dc:date>2023-09-06T00:23:32+00:00</dc:date>
    <link>https://appflowy.io/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[open source notion alternative]]></description>
<dc:subject>collaboration notebook opensource wiki notion alternatives</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:7420339c10f7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:collaboration"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:notebook"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:wiki"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:notion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:alternatives"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.linuxfoundation.org/research/state-of-open-standards-2023">
    <title>The 2023 State of Open Standards</title>
    <dc:date>2023-07-20T23:11:08+00:00</dc:date>
    <link>https://www.linuxfoundation.org/research/state-of-open-standards-2023</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Standards are a part of the fabric of our technical systems and have important influence over decision-making and innovation. To better understand how these standards come to be, the Linux Foundation set out to research the practices currently used to develop and adopt standards in the information and computing technology sector.
 
This report synthesizes findings from a survey that asked LF and survey partner communities about their involvement in standards, the value of and growth in standards, and what challenges they have experienced in this practice. Overall, we found that our respondents prefer open standards over closed, that they see significant organizational value in using open standards, and that there are important challenges to consider when adopting standards.
 
Author: Jory Burson, The Linux Foundation
With a foreword by Dr. Jochen Friedrich, IBM</blockquote>]]></description>
<dc:subject>standards report opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:d94cd6d93ddf/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:report"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://openpm.ai/">
    <title>openpm</title>
    <dc:date>2023-07-12T16:25:29+00:00</dc:date>
    <link>https://openpm.ai/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[OpenAPI package manager
For AI plugins

<blockquote>Our purpose
AI is fundamentally changing the way we live, work, and build software. It has the potential to be the biggest platform shift since the iphone and mobile.

With mobile we learned the painful lesson of the Apple app-store, controlled by a single monopolistic company, stifling innovation and entrepreneurship.

AI, our new platform, needs it's own app-store. An unrestricted app-store built upon the open web and the OpenAPI specification.

We engineers currently have a slim chance of creating this app-store layer before some large corporation does it. We must seize this chance.

That's why we're building openpm.ai, an open source package-manager for OpenAPI files. AIs can use consume packages from openpm in a similar fashion to how ChatGPT plugins work. Ultimately, AIs can use openpm to discover and interact with the world via APIs.

Everything we release is under the MIT license. We will never charge a transaction fee for our services. We will never wield editorial control. We will only remove packages that are scams or illegal under US law. At any point you can choose to export all of our packages and run them on your own server.
</blockquote>]]></description>
<dc:subject>ai plugins llms opensource openapi</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:6587a662e040/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:ai"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:plugins"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:llms"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:openapi"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/Adyen/adyen-web/tree/bfc2dccc85d4b194f63d2cd3848ffa4dfcea6318/packages/playground">
    <title>adyen-web/packages/playground at bfc2dccc85d4b194f63d2cd3848ffa4dfcea6318 · Adyen/adyen-web · GitHub</title>
    <dc:date>2023-05-10T21:51:06+00:00</dc:date>
    <link>https://github.com/Adyen/adyen-web/tree/bfc2dccc85d4b194f63d2cd3848ffa4dfcea6318/packages/playground</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[presumably the source for the Adyen API playground: https://docs.adyen.com/api-explorer]]></description>
<dc:subject>opensource apis explorer tools documentation interactive</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:cf449ef3681a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:explorer"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:interactive"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/serverlessworkflow/specification/blob/main/GOVERNANCE.md">
    <title>specification/GOVERNANCE.md at main · serverlessworkflow/specification</title>
    <dc:date>2023-04-27T19:43:07+00:00</dc:date>
    <link>https://github.com/serverlessworkflow/specification/blob/main/GOVERNANCE.md</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[nice, clean governance doc]]></description>
<dc:subject>opensource governance maintainers examples</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:efc11010fa2c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:governance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:maintainers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:examples"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/apioo/fusio">
    <title>apioo/fusio: Open source API management platform</title>
    <dc:date>2023-03-24T01:23:41+00:00</dc:date>
    <link>https://github.com/apioo/fusio</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Fusio is an open source API management platform which helps to build and manage REST APIs. It can help you with the following use cases:

API-Product
Fusio helps you to create a great API product, besides building an API it provides a developer portal where developers can register and a way to monetize your API
API-Gateway
Fusio can be used as gateway to your internal API and microservices. It handles all common features like Authorization, Rate-Limiting and Schema-Validation
SPA-Backend
Fusio can be used as backend to build SPAs using popular Javascript-Frameworks like i.e. Angular, React or Vue. It provides a powerful code generator which can automatically generate a SDK for your API
Low-Code-Platform
Fusio allows you to build API endpoints without coding knowledge. I.e. it provides an Entity generator which you can use to easily create complete CRUD APIs.
API-Framework
For more complex use cases you can use Fusio also as framework to build complete APIs from scratch. This means you build custom actions where you can use the wide PHP ecosystem to solve your task</blockquote>]]></description>
<dc:subject>apis opensource gateways</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:1c6aa96e201d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:gateways"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/Azure/azure-rest-api-specs/tree/main/documentation/api-scenario">
    <title>azure-rest-api-specs/documentation/api-scenario at main · Azure/azure-rest-api-specs</title>
    <dc:date>2023-03-22T20:02:42+00:00</dc:date>
    <link>https://github.com/Azure/azure-rest-api-specs/tree/main/documentation/api-scenario</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>API Scenario is a YAML file defining RESTful API usage scenarios of your service with a sequence of API calls. API scenario can be used for service API functional test, API quality validation and SDK/CLIs test generation.</blockquote>]]></description>
<dc:subject>workflows APIs azure opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:b6d18143aa78/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:workflows"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:APIs"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:azure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/postman-open-technologies/gsoc-2023">
    <title>postman-open-technologies/gsoc-2023: Postman Open Technologies' repo for Open Source contributions during Google Summer of Code 2023</title>
    <dc:date>2023-03-06T23:43:40+00:00</dc:date>
    <link>https://github.com/postman-open-technologies/gsoc-2023</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>Postman Open Technologies' repo for Open Source contributions during Google Summer of Code 2023</blockquote>]]></description>
<dc:subject>opensource gsoc postman projects</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:dd22fc246b56/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:gsoc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:postman"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:projects"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/openclarity/apiclarity">
    <title>openclarity/apiclarity: An API security tool to capture and analyze API traffic, test API endpoints, reconstruct Open API specification, and identify API security risks. </title>
    <dc:date>2023-01-03T23:59:02+00:00</dc:date>
    <link>https://github.com/openclarity/apiclarity</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>APIClarity is structured in a modular architecture, which allows to easily add new functionalities.

In the following a brief description of the modules currently implemented:

Spec Diffs This module compares the API traces with the OAPI specifications provided by the user or previously reconstructed. The result of this comparison provides:
List of API endpoints that are observed but not documented in the specs, i.e. Shadow APIs;
List of API endpoints that are observed but marked as deprecated in the specs, i.e. Zombie APIs;
List of difference between of the APIs observed and their documented specification.
Trace Analyzer This module analyzes path, headers and body of API requests and responses to discover potential security issues, such as weak authentications, exposure of sensitive information, potential Broken Object Level Authorizations (BOLA) etc.
BFLA Detector This module detects potential Broken Function Level Authorization. In particular it observes the API interactions and build an authorization model that captures what clients are supposed to be authorized to make the various API calls. Based on such authorization model it then signals violations which may represent potential issues in the API authorization procedures.
Fuzzer This module actively tests API endpoints based on their specification attempting in discovering security issues in the API server implementation.
</blockquote>
(kong, tyk) does drift detection, spec generation, and undocumented opes]]></description>
<dc:subject>apis tools opensource generator openapi drift</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:9799dcb0ea45/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:generator"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:openapi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:drift"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/cisco-developer/api-insights">
    <title>GitHub - cisco-developer/api-insights: API Insights is an open-source tool that helps developers improve API quality and security.</title>
    <dc:date>2023-01-03T23:45:51+00:00</dc:date>
    <link>https://github.com/cisco-developer/api-insights</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[<blockquote>API Insights is a tool to enable organizations to manage versioned API specifications (Swagger 2.0/OpenAPI Spec 3.x) for services. It also does static analysis of API spec files for compliance against REST API best practices guidelines, document completeness, inclusive language check and runtime API drift from documented spec. To help API consumers and developers, API Insights service also supports generating an API changelog including identification of backward compatibility breaking changes between 2 versions of API spec files.

API Specifications Challenges
As the number of services increases, no common place for storing versioned API specs.
Inconsistency in API specifications across teams. Makes it difficult for API consumers that integrate across multiple APIs.
API changes across versions could result in breaking backward compatibility.
Lack of consistent documentation of API changes across multiple releases.</blockquote>]]></description>
<dc:subject>apis tools opensource cisco openapi versions versioning</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f1b663f105d9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cisco"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:openapi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:versions"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:versioning"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/readme/guides/shopify-github-actions">
    <title>Untitled (https://github.com/readme/guides/shopify-github-actions)</title>
    <dc:date>2022-07-16T01:51:12+00:00</dc:date>
    <link>https://github.com/readme/guides/shopify-github-actions</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[In 2021, Shopify released Hydrogen, a React-based framework for building custom storefronts based on modern capabilities, best practices, and the latest tooling in web development. Oxygen, meanwhile, is our hosting platform for Hydrogen-based custom storefronts. It gives developers the performance, security, scaling, and stability they need to focus on developing storefronts, not maintaining infrastructure.

To make deploying customer storefronts to Oxygen as simple as possible, we opted to use GitHub Actions. By default, any Hydrogen storefront repository (repo) integrated with Oxygen will be injected with a GitHub Action workflow. All it takes to deploy is a push of the button.]]></description>
<dc:subject>storefronts commerce shopify sites opensource</dc:subject>
<dc:source>https://twitter.com/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ca830d37a411/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:storefronts"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:commerce"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:shopify"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sites"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://giventofly.github.io/pixelit/">
    <title>Pixel It - Create pixel art from an image</title>
    <dc:date>2022-06-21T15:44:20+00:00</dc:date>
    <link>https://giventofly.github.io/pixelit/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Pixel It allows you to take an image and convert into pixel art. You can define the "pixel" size, create a pixel image using a color palette and also convert to a pixel grayscale image.

You can use Pixel It to be your jump start to make some pixel art. Check the documentation for all the available api methods.

"]]></description>
<dc:subject>javascript opensource images converter pixels pixelization tools art fun</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f18ae5f871b5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:images"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:converter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:pixels"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:pixelization"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:art"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:fun"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/pseudomuto/protoc-gen-doc">
    <title>pseudomuto/protoc-gen-doc: Documentation generator plugin for Google Protocol Buffers</title>
    <dc:date>2022-06-15T21:43:31+00:00</dc:date>
    <link>https://github.com/pseudomuto/protoc-gen-doc</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["This is a documentation generator plugin for the Google Protocol Buffers compiler (protoc). The plugin can generate HTML, JSON, DocBook, and Markdown documentation from comments in your .proto files.

It supports proto2 and proto3, and can handle having both in the same context (see examples for proof)."]]></description>
<dc:subject>markdown generator generation grpc protobuf opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:00c979826667/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:generator"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:generation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:grpc"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:protobuf"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/karatelabs/karate">
    <title>karatelabs/karate: Test Automation Made Simple</title>
    <dc:date>2022-06-06T17:34:53+00:00</dc:date>
    <link>https://github.com/karatelabs/karate</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Karate is the only open-source tool to combine API test-automation, mocks, performance-testing and even UI automation into a single, unified framework. The BDD syntax popularized by Cucumber is language-neutral, and easy for even non-programmers. Assertions and HTML reports are built-in, and you can run tests in parallel for speed.

There's also a cross-platform stand-alone executable for teams not comfortable with Java. You don't have to compile code. Just write tests in a simple, readable syntax - carefully designed for HTTP, JSON, GraphQL and XML. And you can mix API and UI test-automation within the same test script.

A Java API also exists for those who prefer to programmatically integrate Karate's rich automation and data-assertion capabilities."]]></description>
<dc:subject>apis testing opensource tools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:21fe2abc6328/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:apis"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://markdoc.io/">
    <title>Markdoc</title>
    <dc:date>2022-05-25T16:56:21+00:00</dc:date>
    <link>https://markdoc.io/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Markdoc powers Stripe documentation
Stripe created Markdoc to power its largest and most detailed content site. Since then, we have adopted it across the company, writing hundreds of thousands of lines of Markdoc to create thousands of pages of expressive, custom documentation.]]></description>
<dc:subject>markdown documentation stripe opensource tools content</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:07a82ef72c61/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:markdown"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:documentation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:stripe"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:tools"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:content"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/teaxyz/tea-brew-478a9e736638">
    <title>Something new is brewing. I created Homebrew nearly 13 years ago… | by Max Howell | teaxyz | Mar, 2022 | Medium</title>
    <dc:date>2022-05-04T03:24:06+00:00</dc:date>
    <link>https://medium.com/teaxyz/tea-brew-478a9e736638</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>crypto homebrew opensource</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:f2b62b4c04e0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:crypto"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:homebrew"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/apideck-libraries/portman">
    <title>apideck-libraries/portman: Port OpenAPI Specs to Postman Collections, inject test suite and run via Newman 👨🏽‍🚀</title>
    <dc:date>2021-12-02T01:45:28+00:00</dc:date>
    <link>https://github.com/apideck-libraries/portman</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["Port OpenAPI Spec to Postman Collection, with contract & variation tests included!

Portman leverages OpenAPI documents, with all its defined API request/response properties, to power your Postman collection. Let Portman do all the work and inject contract & variation tests with a minimum of configuration. Customize the Postman requests & variables with a wide range of options to assign & overwrite variables."]]></description>
<dc:subject>postman openapi collections convert conversion opensource</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:67a4a24a98a9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:postman"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:openapi"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:collections"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:convert"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:conversion"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.jwz.org/gruntle/nomo.html">
    <title>nomo zilla</title>
    <dc:date>2021-09-24T05:55:59+00:00</dc:date>
    <link>https://www.jwz.org/gruntle/nomo.html</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[epic

you can divide our industry into two kinds of people: those who want to go work for a company to make it successful, and those who want to go work for a successful company. Netscape's early success and rapid growth caused us to stop getting the former and start getting the latter.]]></description>
<dc:subject>mozilla firefox opensource resignation letter innovation culture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:39ff45f1ed81/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mozilla"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:firefox"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:resignation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:letter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:innovation"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:culture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.infoworld.com/article/3632142/how-docker-broke-in-half.amp.html">
    <title>How Docker broke in half | InfoWorld</title>
    <dc:date>2021-09-17T15:56:14+00:00</dc:date>
    <link>https://www.infoworld.com/article/3632142/how-docker-broke-in-half.amp.html</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>opensource community business productmanagement failure</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:df04fa3e9d03/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:opensource"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:community"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:productmanagement"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:failure"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>