{"id":18076,"date":"2025-09-15T17:00:00","date_gmt":"2025-09-15T15:00:00","guid":{"rendered":"https:\/\/plus.maciejpiasecki.info\/index.php\/2025\/09\/15\/keep-changing-how-open-source-has-to-continually-evolve\/"},"modified":"2025-09-15T22:23:12","modified_gmt":"2025-09-15T20:23:12","slug":"keep-changing-how-open-source-has-to-continually-evolve","status":"publish","type":"post","link":"https:\/\/plus.maciejpiasecki.info\/index.php\/2025\/09\/15\/keep-changing-how-open-source-has-to-continually-evolve\/","title":{"rendered":"Keep changing: How Open Source has to continually evolve"},"content":{"rendered":"<p>When I became OSI\u2019s first executive director in 2021, some people thought OSI\u2019s work was done. The Open Source Definition had \u201cwon,\u201d embraced even by organizations that once resisted it. Our list of OSI-approved licenses was stable. In their eyes, there was nothing left to do.<\/p>\n<p>I didn\u2019t see it that way.<\/p>\n<p>Technology was (and still is) evolving in ways that test how we apply the Open Source Definition in practice. The launch of the Apple Store for the iPhone for example, made it impossible for users to modify and run an Open Source application on the device (see FSF\u2019s opinion of 2008.) In 2015 smart contracts in the blockchain raised new questions. In October 2021 GitHub announced Copilot, immediately presenting an even bigger challenge: in a world where systems aren\u2019t traditionally \u201cprogrammed,\u201d what does \u201csource code\u201d mean?<\/p>\n<p>I brought OSI into a leadership role in these conversations, to try to keep them from being pulled apart by competing interests. That\u2019s why we focused on Open Source AI, and why we\u2019ve built OSI into a stronger, more resilient organization ready for the next wave of challenges.<\/p>\n<p>Now it is time to expand OSI\u2019s community and reach out to those unfamiliar with the Open Source principles. We need to apply what we\u2019ve learned about software and technology to the rest of the world where there are many misconceptions about AI and its role in society.\u00a0\u00a0<\/p>\n<p>Defining Open Source AI\u2014Why it matters<\/p>\n<p>One of the most important things we\u2019ve done together is deliver the first Open Source AI Definition. We took this on because we saw a critical gap: without a clear, community-driven definition, multiple versions would inevitably emerge. Policymakers might adopt one\u2014or invent their own\u2014without the input of the Open Source community. That could have chipped away at the Open Source Definition itself, which for decades has been our shared foundation.<\/p>\n<p>From the start, we knew this work had to reflect OSI\u2019s values. We ran the broadest, most inclusive process possible given the urgency of the issue: engaging over 50 global experts, hosting public town halls, and listening to the voices of researchers, developers, corporations, advocacy organizations from across the ecosystem. We did this without the luxury of massive staff, budget, or time, choosing instead to make the best use of what we had to ensure the process stayed open, transparent, and principled.<\/p>\n<p>The result is more than a definition; it\u2019s a testament to the power of community-led collaboration. It proves that the global Open Source community can come together, bridge competing interests, and agree on a shared vision for AI.<\/p>\n<p>For legislators and policymakers, the OSAID provides a clear and trusted framework for navigating complex AI policy debates. It demonstrates that Open Source principles can\u2014and must\u2014guide the development of AI, even in a world of significant technical constraints.<\/p>\n<p>What we built together<\/p>\n<p>Over the past four years, with gratitude to our members, sponsors, volunteers, and partners, we\u2019ve:<\/p>\n<p>Grown OSI\u2019s capacity \u2013 Expanded from a staff of one to a professional team with expertise in policy, licensing, communications, and sustainability.<\/p>\n<p>Increased our impact \u2013 Engaged policymakers from the U.S. to the European Union to the United Nations, helping shape laws and standards that affect the entire Open Source ecosystem.<\/p>\n<p>Expanded our reach \u2013 Grew membership from hundreds to thousands, tripled website visitors, and launched new community resources like the refreshed Opensource.net and member forums.<\/p>\n<p>We also managed to settle the very important debate about the hyphenation in Open Source (it\u2019s never hyphenated and always capitalized, too.)<\/p>\n<p>The work isn\u2019t done<\/p>\n<p>If there\u2019s one message I am taking into my work in the future, it\u2019s this: keep changing.<\/p>\n<p>Open Source is not a finished project. New technologies, regulations, and societal pressures will keep testing our shared principles. New licenses will emerge. New legal and policy challenges will require attention. The OSAID must continue to evolve. But OSI is still a single organization in a relatively small community of dedicated believers. The challenge is moving beyond and outside of that close-knit world to bring an understanding of Open Source for AI to those in leadership positions across industries, governments, and regions. Policies are being written and decisions being made right now that will have widespread impact to those outside of the current community. The Open Source Definition will need ongoing interpretation. The whole concept of \u201cdata\u201d needs to be better understood, and why we\u2019re dedicating another Deep Dive to data governance in October (register for the online conference.)\u00a0<\/p>\n<p>Everyone from big tech to Melania Trump are trying to make sense of AI and the potential for damage is high. This is where we must now turn our attention.<\/p>\n<p>Thank you, and let\u2019s stay connected<\/p>\n<p>Leading OSI as executive director for a four-year term has centered me in the modern era of Open Source, where regulation has a stronger role for collaboration and impact. I\u2019ll still be part of this movement\u2014Join me in exploring the broader set of challenges in bringing these values to those still unfamiliar with open source and struggling to understand AI.\u00a0<\/p>\n<p>Keep up with my new endeavors at maffulli.net.<\/p>\n<p>Let\u2019s keep the conversation going. And above all, let\u2019s keep changing.&#013;<br \/>\n&#013;<br \/>\nSource: opensource.org&#013;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When I became OSI\u2019s first executive director in 2021, some people thought OSI\u2019s work was done. The Open Source Definition [&hellip;]<\/p>\n","protected":false},"author":61,"featured_media":0,"comment_status":"false","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-18076","post","type-post","status-publish","format-standard","hentry","category-mp"],"_links":{"self":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/18076","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/users\/61"}],"replies":[{"embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/comments?post=18076"}],"version-history":[{"count":1,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/18076\/revisions"}],"predecessor-version":[{"id":18077,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/posts\/18076\/revisions\/18077"}],"wp:attachment":[{"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/media?parent=18076"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/categories?post=18076"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/plus.maciejpiasecki.info\/index.php\/wp-json\/wp\/v2\/tags?post=18076"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}