Zen and the Art of Open Source  ## Metadata - Author: [[OpenJS Foundation]] - Full Title: Zen and the Art of Open Source - Category: #articles - Document Note: --- tags: [#opensource, #organization, #zen] - #opensource - #organization - #zen Author: Cody Zuschlag Source: YouTube / OpenJS Collab Summit Reference: [Zen and the Art of Open Source](https://www.youtube.com/watch?v=eG_6DmhCmzw) date created: 2025-08-24 22:00 --- # Title: Zen and the Art of Organizational Open Source ## Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) --- ## 📝 Summary: Cody Zuschlag reframes his talk to explore how organizations can achieve "Zen" through open source engagement. He outlines five maturity levels—Denial, Fear, Bargaining, Acceptance, Enlightenment—and explains how moving up these levels creates exponential value for organizations. Benefits include talent retention, reduced costs, improved developer experience, brand recognition, and alignment with corporate values. Full enlightenment involves strategic investment, an OSPO, and participation in open source foundations. --- ## 📖 Main Content: The talk blends humor (cute animal imagery, parody graphs) with serious strategy. Cody positions open source as a cultural and organizational asset, not just a technical choice. By investing in open source, organizations transition from consumers of software to active contributors shaping their own future. ### 🗒️ Notes - [00:00](https://www.youtube.com/watch?v=eG_6DmhCmzw&t=0) Renamed talk to *Zen and the Art of Organizational Open Source*. - [04:19](https://www.youtube.com/watch?v=eG_6DmhCmzw&t=259) Effort in open source → exponential org value. - [08:20](https://www.youtube.com/watch?v=eG_6DmhCmzw&t=500) Benefits: talent retention, reduced commercial software fees, better docs, branding. - [15:29](https://www.youtube.com/watch?v=eG_6DmhCmzw&t=929) Fear-based supply chains (e.g., Artifactory) slow productivity, create "shadow IT." - [18:51](https://www.youtube.com/watch?v=eG_6DmhCmzw&t=1131) Bargaining = inner source cop-out; Acceptance = empowered devs, ad hoc contribs. - [24:00](https://www.youtube.com/watch?v=eG_6DmhCmzw&t=1440) Enlightenment = strategic OSPO, sponsorship, standards participation. - [25:41](https://www.youtube.com/watch?v=eG_6DmhCmzw&t=1541) Call to action: assess org level, reinvest maintenance fees, differentiate via OSS. --- ## 📖 References: - OpenJS Foundation - NearForm open source sponsorship (Fastify, Orama, etc.) - Industry OSPO practices --- ## 🗣️ Paraphrase: 1. **Original**: “Investing in open source creates exponential organizational value.” **Paraphrase**: Organizations that commit to contributing in open source see value snowball, with early investment compounding into outsized returns. 2. **Original**: “Inner source is often just a cop-out for not embracing open source.” **Paraphrase**: Companies that hide behind inner source without real external contributions limit impact and miss the transformative benefits of true OSS engagement. --- ## 📰 Newsletter: 🐧 **Zen and the Art of Open Source** At the OpenJS Collab Summit, Cody Zuschlag shared a playful yet sharp roadmap for how orgs can achieve "Zen" through open source. His 5-stage maturity model (Denial → Enlightenment) shows that companies move from closed-source fear to strategic innovation by embracing OSS. ✨ Key takeaways: - Open source retains talent and slashes maintenance costs. - Fear-driven restrictions (like locked-down Artifactory) harm productivity. - True "Zen" requires an OSPO, sponsorship, and engagement with foundations. 👉 [Watch the full talk](https://www.youtube.com/watch?v=eG_6DmhCmzw) --- ## ✅ Action Items: - Position GoDaddy’s **OSPO formation** as the step toward "Level 5 Enlightenment." - Educate WordPress and FAIR communities on **Zen levels of OSS maturity.** - Frame **sustainable contributor funding** as part of leveling up from Acceptance → Enlightenment. - Use Cody’s metaphor (renting vs buying software) in **talks with execs** to highlight OSS ROI. --- ## 🧪 Hypotheses: - OSS engagement correlates with **employee retention >20%** longer than closed-source orgs. - Reallocating maintenance fees to OSS sponsorship yields **faster feature delivery**. - Organizations with OSPOs score higher on **developer experience metrics**. ### 📊 Methodology: - Survey retention rates in OSS-contributing vs non-contributing firms. - Compare ROI of OSS sponsorship vs proprietary software costs. - Analyze CHAOSS metrics before/after OSPO establishment. ### ❓ Questions: - How do different OSS maturity levels affect recruitment pipelines? - Can inner source ever be a valid stepping stone? - What measurable KPIs define “Zen” maturity beyond anecdotes? ### 🔮 Future Research: - Standardized Zen scale for OSS org maturity. - Longitudinal studies on OSS investment vs market differentiation. - Role of OSS maturity in reducing supply chain risk. ### 💡 Implications: - Could influence corporate policy to prioritize OSS over licensing. - Helps executives see OSS as **strategic, not optional.** - Shapes **WordPress governance** by modeling maturity scale. --- ## 🧠 Learning Styles Assessment: - **Visual**: Humor via animals and graphics ✅. - **Aural**: Delivered as talk ✅. - **Verbal**: Strong metaphors (“rent vs. buy”) ✅. - **Kinesthetic**: Lacking ❌ (add OSS maturity workshop). - **Logical**: Clear progression of levels ✅. - **Social**: Community call-to-action ✅. - **Solitary**: Limited ❌ (add self-assessment exercises). - **Naturalistic**: None ❌ (could add sustainability angle). --- ## 📊 Accessibility Assessment: - Transcript exists ✅. - Visual slides lacked alt-text ❌. - Recommend: screen-reader-friendly slides + captioning. --- ## 🌍 DEIB Assessment: - Inclusive tone ✅. - Examples Western-centric ❌. - Representation skewed (mostly male leaders cited) ❌. - Suggest: highlight global OSS case studies + diverse leaders. --- ## ✅ Logical Validity: - **Strong inductive reasoning**: Curve metaphor supports “exponential return” claim. - **Causal reasoning**: Ties OSS adoption to talent retention. - **Weakness**: Strawman-ish dismissal of inner source as *always* a cop-out. - Tone: Playful, humorous, lightly satirical, yet strategic. --- ## 🔍 DARVO Analysis: - **Deny**: None. - **Attack**: Mild dismissal of inner source. - **Reverse Victim**: None. 👉 Overall: No DARVO tactics—tone is constructive. --- ## 🔍 SEO Evaluation: - **Keywords**: open source, OSPO, Zen maturity, developer experience ✅. - **Meta description**: Missing ❌ (suggest: *“Cody Zuschlag outlines 5 levels of open source maturity to drive organizational value.”*). - **Headers**: Structured well ✅. - **Length**: 2,500+ words equivalent ✅. - **Links**: Few ❌ → add OpenJS, CHAOSS, OSPO Alliance. - **Schema**: Missing → add “Event/Presentation” schema. --- ## 🎯 Conclusion: Cody Zuschlag reframes OSS adoption as a journey toward “Zen.” His 5-level model illustrates how orgs evolve from fear and denial to strategic enlightenment. The central message: investing in open source isn’t charity—it’s a **differentiator, a recruitment tool, and a path to exponential organizational value.** - Summary: The speaker starts a livestream talk about applying open source in organizations to drive value. They change the original title to "The Zen and the Art of Organizational Open Source" and present a chart showing the potential exponential value that can be gained by investing in open source. The speaker describes various benefits to the organization, such as retaining talent, cost savings, improving brand recognition, and reinforcing corporate values. A metaphor of renting versus owning a home is used to describe the difference between using commercial software and investing in open source. The speaker proposes a scale of open source maturity levels and challenges the audience to evaluate their organization's level and work towards the next level. - URL: https://www.youtube.com/watch?v=eG_6DmhCmzw&list=PLyspMSh4XhLO15jJD9Sj069fN18j12AbQ&index=14&ab_channel=OpenJSFoundation uh thanks everyone for coming and anyonewho might watch this later uh I don'tknow if this I guess this is a livestream now and we'll be recording thissuper excited to be here super thankfulto all the organizers for for makingthis happen and uh really excited to betalking aboutuh this subject today so let's getstarted I created this talk and theoriginal idea of the talk was about uhhow we can you know make changes in an organization when we Embrace open sourcebut actually decided like that's thewrong title for this talk uh it justwasn't really A fitting title so I saidyou know we're going to start over and Iwant to you know rework this talk so youactually know the new name new titlethis talk uh this is the one that Iactually put on the schedule decided I'mgoing to change it to the Zen and theArt of organizational open source soreally how can we uh apply open source in our organizations and drive value inorganizations honestly is what what Iwant to do and what I strive to doduring this uh presentationso uh why did I rename it because uh atthe end of the day I thought thispresentation uh would be a lot better ifI put in a lot of really cute uh animalpictures so any kind of Zen animalpicture I thought that would be reallyimportant uh to drive home this the the point of this organization uh and youknow talking about these subjects it'salways a little bit more fun we havecute animals so let's get a little bitmore serious uh my name is Cody zushlogI'm a stack developer relations engineerat near form I also teach at localUniversity where I live in France soheads up it is midnight where I'mlocated doing this talk remotely so I'ma little tired you can probably see myeyes uh when we do my best to bring someenergy here uh and just really thankful to be here and to be talking to everyoneuh you can scan that QR code now I'llput that QR code up at the end tooif you want to know more about thesesubjects if you want to you know accessthe slides for this talk uh if you wantto know more about me more about myemployer near form feel free to scanthat QR code and if you didn't have timeto scan it now I'll put it up again atthe end of The Talkalso I have to give a little shout outto uh somebody uh important that helped make this talk uh become a reality asPaula Pauluh she does all kinds of amazing thingsuh not to mention that she is more orless my boss well more or less she is myboss and she's also a board member atopengs foundation so you may you mayknow her I may have heard her may haveseen her around uh at the conference uhshe does lots of other amazing things uharound the the grease Hopper which isjust this really inclusive uh Community for for bringing people uh into Tech uhplenty of other things go check outPaula Paul if you want to know moreabout her and some of the amazing thingsuh that she's doing and like I said thistalk wouldn't be possible without herso uh why should organizations careabout open source right that's that'swhy we're here uh that's that's what wecame for that's the question that we'regoing to try to answer todayand I was considering this uh question at at work and you know coming up withthis talkand what we did is we went out and we uhhired a team of researchers and datascientistsand they developed you know the mostadvanced models and simulations and theydid a meta study with super Atomiccomputers Atomic computers to come to uhthis conclusion which is the more effort that your organization puts intoopen source and the more they directthat effort towards having in an impacton the community the more value it'sgoing to bring to the organizationuh and we can see that here in that redzone you know we modeled this this studythat we did so that's just a reallyridiculous joke uh that I'm making uh Ijust stole this graphic off of GoogleImages and renamed the axes uh there was no no study no nothing like that but thepoint that this graphic really pointsout is uh that we can we I'm going toconvince you today that we can bringvalue back to an organization byinvesting in open source and we want tobe up there in that that red zone orthat Pink Arrow is like that's that'sour that's our goal and this graphicalso is cool because you know it showsthat it's exponential too right at thebeginning you're gonna you know put in alot of effort and you're going to put inFocus that on the community and you might not get as much value back butonce you get moving like it's it's aslow it's a slow process to get movingbut once you move it's going to growexponentially and the further you moveup in your open source experience themore you know the more in the more valueit'll bring back to your organizationso uhwhat does it mean to to be Zen and youknow if we can maximize that open sourceeffort have an impact and the value whatwhat can we do we can be Zen like that's that's or our goal is here right uh andI'm talking about curating communitiesand contributing to open source projectsso what does it mean to be Zen when I'mtalking about open source when we applythat to an organizationso to reach like full open source Zenuh we could do all kinds of interestingthings to organization like attractingand retaining Talent uh I'm thinkingabout my job experiences right like when I'm going and searching for a new job uhI want to work as a place where I get towork on open source tools and contributeto open source projects and if not onlythat but when you have you know Talentat your organizationit's going to help retain them if theycan work on those types of projects I Ispeak from you know personal experiencethe jobs where I stayed the longest forwhen you know I was able to work on opensource projects uh something moretangible that we can you know count withwith numbers is uh you know this the maintenance cost that comes along withcommercial you know non-open Sourcecommercial software and this issomething that we don't always isn'talways clear to to us the consumers ofthose that software but usually uhnon-open Source commercial softwarecarries like 18 to 20 annual maintenancefee and this goes towards like featuresand a road map that's opaque that youhave no control over right like youdon't know what features are going tocome out in next year's you know office suite uh or you know name your yourcommercial software license that yourorganization use like you don't havecontrol or impact over that roadmapso imagine if we could take that 18 20and we could invest that in working onyou know an open source project thatserves the same the same uh goals andfunctionality and all of a sudden we canhave you know impact on the roadmap andthe features because we're investing inthat open source project so we can take that money that 18 to 20 and we caninvest that to get more features out ofthose projects so this is somethingreally cool and something important thatit sometimes is overlooked when we'retalking about open sourceand if we have like a healthy opensource community and you know asuccessful open source project we needto have a great developer experienceright we need to have documentation uhreadme's uh you know a CI Pipeline with automations uh if you're putting yourcode in GitHub you have tags great forbeginners and people are willing to helppeople get started and work on a projectlike the developer experience isessential to have a healthy open opensource project so if you're willing toinvest in that it means you're going tohave a great uh developer experience forinternal folks for new hires peoplecoming on they'll be able to work onthat project I'm thinking how many timesI've worked at a company and a newdeveloper uh comes on to the onto the team and they asked me whereare the docs they're like oh yeah thedocumentation well you know that justgot de-prioritized you know we had thatshipment mentality so the docs like theydon't really exist they're really out ofdate so why don't you just Shadow me fora couple weeks and you know your firsttask will be to go and write thatdocumentation this is something I'veactually said to people coming andworking on my team so I want to you knowchallenge us to get away from that like let's make a qualitypublic project and then you know we'llbenefit from that internally to ourorganization alsonowuh we have to give you know do somethingalso for the marketing folks andorganization right so by investing inopen source and maybe bringing workingon a project that's well known uh it'screating brand recognition so obviouslyI'll name the big players right if I'mthinking of you know react or a reactnative right who am I thinking ifobviously Facebook meta uh however you want to say that if I'm thinking ofmaterial UI or you know plenty of otheropen source projects like we think of acertain brand rightso by getting involved or or sponsoringlike a successful open source project wecan build brand recognition fororganization alsonow this presentation wouldn't be uhcomplete if I didn't also think about uhthe executive folks too right so byworking on open source we can you know reinforce our corporate goals and valuesto keep all the executives happy thatare bringing their their corporatevalues uh diagram and and creating thecorporate goals for for thatorganizationuh they can do that uh we can reinforcethose values in a concrete way so we'renot just they're not just talking totalk but they're also walking the walkespecially around things aroundsustainability and Community uh here'slike a real opportunity for them for usthe organizations reinforce those goals and valuesuhso I also like to think of this as likea metaphor too right because uh themetaphor that I want to present to youis the difference between you knowrenting uh an apartment versus likebuying a home right and if you buy ahouse or buy a home uh you're gonna beyou know living and investing in thatCommunity with your neighbors and tryingto you know better that Communitywhereas if you're just renting anapartment somewhere maybe it's temporarymaybe you don't feel quite as you knowyou don't have your roots as deep in that uh environment so I think that's agreat metaphor when we're thinking aboutyou know using commercial softwareversus you know investing in open sourceuh software now you know I talked aboutthe maintenance fees and I mentionedMicrosoft the office or whatever and wecan't control what's coming in the nextversion not even around patches or fixeslike we don't have control over that wetalked about an open source softwarelike we can actuallydo do those things and we can rely onthe community to hopefully surface bugs and Bug fixes much faster uh when we'retalking about an open source projectso uhhow do we reach that open source Zenlike that's that's what I want to talkabout for the rest of this presentationin order to do that though we need tocreate some sort of scale like some sortof measurement system uh so we need toDefine you know what are the open sourcematurity levels like what are the levelsthat we could achieve to reach opensource Zen because we can't just go from zero to full on Zen right there's plentyof steps in betweenand then I would I'm going to challengeyou at the end of this organization togo back and think about where does yourorganization sit like what's the currentlevel of your organization what's itscurrent Zen leveland how could you work towards you knowreaching the next Zen level like that'sthat's what we want to do we want tolevel up right so what are the reasonsto level up that's what I'm going to tryto present uh for the rest of thispresentation so real quick let's talk about the levels the first level isn'tgoing to be denial uh all closed Sourcecommercially licensed software I'm goingto Deep dive into these levels in just asecond so I'm going to go over them alittle bit quickly right nowuh the next level is going to be fearstep two level two and here you knowmaybe you're gonna have block downdependencies so like you're using soopen source software but you're reallyhesitant about itlevel threes we're going to callbargaining now here you might have moreof an open dependency Tree open dependency system but you're not youknow creating an environment where youcan contribute to open sourcenext Zen level level four acceptance sohere you're empowering your devs and toto use open source in the way that bestyou know solves the the solutions thatyou're trying to createand you're also contributing back to anecosystem and then the final full Zenlevel level five enlightenmentwhere you're using open source and a strategic way to differentiate yourorganization from the competition rightso it's just differentiating investmentin open source so that's the full Zenlevel so let's dive in a little bitdeeper on each of those levelslevel one denial uh this is where we'retalking about no open source likethere's a policy no open source and uhyou're using all closed Sourcecommercial commercially licensedsoftware rightand someone you know decided like theyjust they really see this open source as something dangerous you know they'rescared about there's fears aboutSecurity in the supply chain and and Ilove this idea of no open source I'veworked at a company like this uh but theend of the day you have to ask like doyou have a website uh do you have any doyou build any internal software or doyou build anything for that website doyou have any mobile applications likethey're using open source software eventhough they don't know it right so theymay have this no open source policy butit's it's really just something major fiction because you know any any moderntools are built upon the open sourcefoundations that they get us get us towhere we need to be uh today and like Isaid I've worked for employers like thiswho just rejected all ideas open sourcemeaning you wanted to own all the sourcecode and they really saw the source codeas you know a core value and of the oftheir product and I feel like that'sjust a fallacy right like if you're if your most important part of your productis is the source code uh like you'relimiting the potential right like youcan't well have a really big impact onyour users if you think like the sourcecode is the most important thing uh I Itruly believe this so next level uhis going to be level two the fearand here we could uh you know you'regonna have a really tightly controlledsupply chain and the devs are going tostruggle to be productive in this kind of environment so I'm thinking abouthaving something like artifactory that'slocked down that's you know cloning uhcontrolling what's happening what thedependencies are coming off of npm we'retalking about you know node.jsdevelopmentuh you know so they have like a mirrorof npm and like somebody gets controlwhat dependencies get downloaded becausethey want to control the whole uh supplychain like I've worked at a player justlike thisuh and it was kind of funny because whenwe were developing software we realized like we need another dependency we haveto go and create like a support ticketto get dependencies added in theartifactory and it was kind of hilariousbecause the answer is always like okayoh that's the dependency no problem likeWe'll add it right away so it was reallycreating this false sense of securityright it was just creating theseboundaries to slow down our productivitybecause the end of the day like nobodyever said oh no that dependency is likeway too dangerous uh that never reallyhappeneduh uh so and the other thing that I sawis I had co-workers and myself like we'd come up with this kind of Shadow I.T uhthese ways to get around therestrictions of artifactory so we'reusing you know reverse proxies or vpnsthat you know connect to the real uh npmbecause it was you know locked down bythe firewall that if you could connectto like a reverse proxy you could accessit and we're doing all these weirdthings to try to uh get around the therestrictions because developers justwant to build stuff at the end of theday right they just want to beproductive so I find this fear level to be be kindof funny also uh oh and I keep skippingover these but we're moving up thegraphic right if I go back to level onewe're way down here and low level atlevel one so now we're at level twowe're starting to move up thatexponential curve but we're not gettinga lot of value yet right that's gonnahappen later so level three going backto bargaininguh at this level we might have a realopen supply chain right and the devs arefree contribute uh but only to only to like a supplied uh I'm sorry only to acontrol supply chain so I'm thinking ofprivate forks and things like that tomake changes and make fixes to codeuh there's no uh contributions to publicopen source projectsand maybe your organization I've heardthis before is throwing on buzzwordslike inner source and I'm calling this abuzzword because I feel like it's it's kind of a cop-out in in my opinion andI'm sure if your whole organization canEmbrace inner sourcing that could bringsomething really interesting to yourorganization but in my personalexperience working in a lot of differentorganizations that is generally kind ofa cop-out for you know why we're notusing open source we're embracing innerSource I think this is kind of abuzzword that gets thrown aroundso in my own experiences I've worked foremployers like this and they just youknow their their devs were empowered to use open source but we couldn'tcontribute back right they always preferthose private Forksand in my Consulting work I've also youknow had clients that you know weren'tready for open source and they said okaybut we're gonna do inner source so we'regoing to embrace open source values butwe're going to keep the code so privateto the organization but at the end ofthe day like they didn't have buy-infrom all the the management and there'sa lot of lack of trust in the devs andthey weren't empowered to contribute back to that inner source project andand the date was like a side low teamyou know working on one project thatnobody else in that organization wascontributing or working on it so thisbargaining level everybody's trying toadvance a little bit like they see thethe value in open source but there'sbarriers to making that happenuh you know and here again we're movingup that curve a little bit uh getting alittle bit higher on the Curve uh Irealized technically I think accordingto the schedule I probably only have about two minutes left but I'm gonna goa little bit over because we started alittle bit late uhso let's move on to level fouracceptance so here uh the developers arereally empowered uh to use andcontribute to open source projectsum but it's kind of in this like ad hocthere's not really an optimized ororganized manner right when we'retalking about Community contributionsand uh it could be part of the opensource ecosystem but like I said it'snot organized it's not an organized initiative and I've had other otheremployers like this and I feel like thisis where my current employer was for along time and we're you know trying tomake the transition to the next leveluh so in some previous experiences I'vehad employers that you know trulyempowered employees to use andcontribute to back to open sourceprojects but I was working at a startupand we still haven't just ship itmentality right so it's prettyfrustrating for me because I didn't havetime to always go back and you know make contributions in the right way rightlike make sure that my my fixes were upmet the contribution guidelines and Ichecked all the boxes and those issuesthose PR's when I was creating them thatreally get merged one day it was like ohwe don't have time for that like if it'sjust changing one file go ahead feelfree to you know make a PR but if ittakes any more time than that like wedidn't have time to do itlike I said I think my current employernear form they've been at this level fora long time they've embraced andcontributed to open source things likenode.js fastify mercurius there's lots of interesting projects they'responsored by by uh near Forum uh but itwasn't always in a really organizedmanner rightand client projects the billboardbillboard billable hours always hadpriority and I feel like we're makingthis transition now to this level levelfive I'll talk about in just a second soat this level though it's not asstrategic as possible and uh you're notgetting the same potential uh bringingback the same potential value to the company or the ecosystemso let's move on a little bit quickerhere we're moving up the curve rightwe're starting to get a lot of return onour investment we're getting a lot ofvalue in our Organization for what we'reinvesting in open sourceso level five Enlightenment like this isthe goal right this is where we all wantto beand here you know or we're using uh opensources you know strategic and it'sdriving Innovation and efficiency in theorganization so you know we're using open source projects because we see thatas being something more efficient forfor our organizationthe organization is sponsoring opensource projects so near form sponsors uhfastify uh Pinot lots of otherinteresting projects uh orama previouslyknown as liraso uh your organization is sponsoringyou don't have to be like the you knowthe author of a project but you cansponsor projects rightand maybe you have an open source program office I think this is somethingreally important so that everybody inthe organization knows where to turn andthey need advice on you know gettinginvolved open source and licenses andcontribute contributor uh agreements uhsugar license agreements clas sorryuh and they've identified you know whatare the Strategic open source projectsfor for that organization so if you wantto go and contribute to open sourcewhile you're working for for thatemployer like here's the projects thatare most strategic perhaps like this is where we need to be investing to bringmore value back to our organizationuh and they have an open source policyright so their education educating sorryuh their employees and devs or not justdevs anybody can contribute open sourceright uh on aspects on different opensource aspects legal legal aspis aspectsof that like I said the clas andlicenses they're also allowing timeright for people to contribute opensource this is something I think really important that you know you really onlyget that level five is actually havingtime to go and work on open sourceprojectsand they're also finding a way to youknow measure uh those contributions andtheir internal investment that they'regetting from there uh not only uh forthe organization but also to thecommunity itselfand you know actively participating inopen source foundations and standardsgroups there's tons of them right we'rehere I'm here at the opengs collab Summit uh part of the Linux Foundationbut there's so many foundations uh andthese are going to help bring more valueback to uh an organization because it'sgoing to help it be more well known andbe more effective in the community andthere's you know so many places to getstarted if you're interested in gettingworking on open source although in thisaudience I think most everybody hereknows that because we're here for theopengs foundationand like I said I think uniform had been level five four for a long time or youknow starting to reach this level fiveuh you know Lira which is now known as arama the search engine like this issomething that was created by anemployee working at Michaela Riva to beexact working at at uh near form and wewe have uh full-time employees thatcontribute to node.js which is just likeamazing right uh but we still the opensource program office is still in itsEmbassy something that's starting to getworking you know trying to define the Strategic open source projects so youknow open source obviously so much morethan just making a a repo public it'sabout building a real communityso try to speed up this up a little bitso don't go too much over time for uh Ibelieve it's my uh colleague Marco isgoing to be speaking just after meuh here we're reached that red level inour uh exponential curve uh kind of animportant pointso what about your organization right like what what level is yourorganization at now that we've you knowDefine these different levels of OpenSource Zenuhand you know if this was a real audienceI would have people raise their hands ifyou know where they're at and in mypersonal experience you know mostorganizations are at that three to fourlevel right the levels one and two likeI feel like this is kind of the pastlike most organizations have movedbeyond that although I've still seen afew that are still at that one or twolevel but I think the majority oforganizations realize the importance of Open Source so remote usually aroundthree or four so how can we make theleap how can we make that step to levelfiveuh and don't forget that commercialsoftware has maintenance fees right solet's take those fees and let's investthat in an open source alternative andwhat I mean invest I'm talking aboutpeople and resources right that's that'sthe kind of investment that we should bemaking in open source projects and opensource of alternatives to thatcommercial softwareand if we do that that's going todifferentiate our organization from the competition and allow us to innovate wecan you know Define you can Define yourcompetitive advantage of you know what'sthe advantage over your your competitorsand it's the way that you use opensource and the way you get value fromopen sourceso this can be a differentiating factorfor for your organizationuh andhelp you innovate even further in inyour organization so let's I want tochallenge everybody here you know measure your your organization and howhow can we uh reach the next leveluh souh this is my open source call to actionuh assess the current level of yourorganization understand you know the thecurrent strategic dependencies and let'slevel up like that's why we're here likelet's do this like let's make that stepsnext place and go out and connect tocommunity a great place is here uh atthe open.js foundation uh it's it's an open Community with withopen Slack and calendars and themeetings the meetings are open toeverybody and anyone it's all publicright like that's what happens openjsFoundation uh anybody can join and seehow things work behind the scenesuh so let's go out and do it and getinvolved and let's help reach that opensource Zen level and if we do we'll besomewhere like this final last cuteanimal brain or whatever he's doing with his pause cross uh we'll be reachingthat open source Zen uh maximum souh just real quick before I wrap up likeI said I work at near form we like wehave full-time employees that contributeto no JS you probably know a few of themRafael Silva Marco polutoPaulo and Sonia uh doing amazing thingsand we have tons of npm packages thatare downloaded someyou know incomprehensible number of timesuh and you know we're always hiringuh so if you want to talk about that orif you want to talk about bringing opensource to your organization feel free toreach out to me uh you can find us onthe socials uh you can scan this QR codeyou can learn more about me you canlearn more about your form love to talkto anybody aboutthis about open source I love talkingabout these topics and uh reach out andwe'll chat some more thank you so much for uh listening thank you so much forbeing here and thank you so much formaking this happen and uh hope to talkto you all soon see you next time, Zen and the Art of Open Source, OpenJS Foundation, 01h3j60zz4w6t9y6j7eb35mtzs.