<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Licensing on Percona Community</title><link>https://percona.community/talk_tags/licensing/</link><description>Recent content in Licensing on Percona Community</description><generator>Hugo</generator><language>en-us</language><copyright>© Percona Community. MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.</copyright><atom:link href="https://percona.community/talk_tags/licensing/index.xml" rel="self" type="application/rss+xml"/><item><title>What Makes Open Source Work: Licensing and Beyond</title><link>https://percona.community/talks/2026/2026-10-19-what-makes-open-source-work-licensing-and-beyond/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://percona.community/talks/2026/2026-10-19-what-makes-open-source-work-licensing-and-beyond/</guid><description>&lt;p&gt;The term “Open Source” typically refers to the license a project uses, but is having an Open Source license sufficient for a project to embody all the values commonly associated with Open Source Software? Perhaps not.&lt;/p&gt;&#10;&lt;p&gt;In this talk, Peter looks at what else decides whether a project is worth adopting for the long term: availability of binaries, quality of documentation, governance structure, community size and activity, and other criteria that matter once you move past the license file. If you evaluate open source for production use — or maintain a project yourself — this is a sharper set of questions to ask.&lt;/p&gt;</description></item></channel></rss>