 Welcome to Drupalcon again. Thanks for coming. I get the I get the bleary-eyed one more coffee session now I guess and I have another one tomorrow so I get the very earliest thing in the morning on the first day Tuesday 8 a.m. at Drupalcon and apparently I get to close the close the days other way. So I know some of you in the audience how many of you are developers how many of you are business agency owners and how many are sort of end users of Drupal businesses who your actual business isn't Drupal nobody how many of you are named you good thank you all right so I saw this tweet and I thought it was interesting you know if you're not paying for it don't base your business model on it and then and then well that's a funny question when we don't pay money for the software we use right so I clarified if we if we contribute is that does that count as payment and you know luckily the internet told me yes sweat equity counts as as paying for what we do I want to talk about the the business value of contribution from from a couple of different standpoints we are here because of open source and it makes sense to us probably intuitively that we need to contribute but a lot of us struggle with perhaps explaining to management or explaining to our friends and colleagues why we should do it and I contend that it's not a set of moral or emotional arguments I think there's real strong business value in it the other side of this session is how to integrate contribution organically into developer workflows unfortunately my good friend Chris Jansen is sick today and not able to be in Vienna and not able to do the session with us Chris Chris got a new job and he's the competence he's the Drupal competence lead at a company called Ordina in Holland and that's a big classic IT delivery organization 1500 people and he is a pretty senior person in the Drupal unit now and he got a really cool job he about 50% of his time is development a quarter of his time is doing pre-sales support so telling the open source story and telling the technical story of Drupal to potential clients and a quarter of his job is to be to work on team development right so his actual job and he's gonna have KPIs around it is to ensure and raise the competence and professionalism of his team and for us for him that ties directly into contribution interacting with OS communities makes you the best possible developer I'm quoting him and he got his job because of his reputation and commitment to contribution as well as his you know he's a shit hot developer so he's so technical expertise plus his really strong commitment to quality and and contribution got a nice job so unfortunately Chris can't be here today he would be really really so the structure of the presentation it's gonna be probably a little heavier on my side of things a little lighter on his side of things because I know what his slides are about but they're not my slides he'd be really really happy to talk with any of you and go into much more depth about the developer processes and the measuring that side of things there's his email there's his Twitter and his Drupal.org ID is also Legolas Bo so you know please please feel free to get in touch with him most people call me jam I've been around in Drupal for a long time two eleven twelve years and I am the co-founder of a marketing strategy communication company called open strategy partners and we do we talk about this stuff in a lot of different ways this space between business value and open source and and communities and all of that is is what we're about and yeah I'm pretty easy to find online Horn Cologne on Twitter and Drupal.org so let's get right into this can someone tell me when we actually have to stop is it at 5 45 at 6 okay so this is a luxury presentation no this is awesome so the thing is that usually I have like 35 minutes to get through this but right now who that's awesome okay so in the next 40 slides I want to talk I want to talk just to make sure that we're on the same page about the benefits of using open source and it should be familiar to all of us but it would it's good to just make sure that we're all in the same place and then want to talk about in principle why we contribute why we should contribute what are roadblocks to contribution from a business management perspective and from an operational development perspective how we remove those and now go how to go contribute what to do to contribute what sort of contribution is effective and interesting and then I'd be happy to talk about any of this if we have any time left at the end guy called Edmund Burke who living in the 18th century said the only thing necessary for the triumph of evil is for good men to do nothing so I take that to be a call to action to contribute right the worst thing that we could do for Drupal or PHP or any part of open source is sit back and eat it and not ever come to a conference again and not ever write a patch again right and we have to remember that you know when we download Drupal right we're getting millions of hours of coding for free like minute zero of any client project we are delivering literally millions billions of euros of value out of the gate that's kind of exciting that's an interesting sales point I think so how many of you can have contributed to open-source software okay and how many of you think you haven't contributed to open-source software have you ever filed a bug report you filed a bug report so you help somebody fix it right and and have you ever asked a question in a con you wait a minute but you've been to Drupal con right did you buy a ticket okay so you're well we're off the hook there did you ever ask a question at this event all right so but see being here and being part of this community is already a contribution and there's it's so much more than just code right and that's a really really important thing to remember so let's just remember what we're talking about the benefits of using open-source software well we don't have to pay money to get the license to use the software so we have a license fee of zero it's not free and if you tell your clients it's free you're gonna set bad expectations right because IT is an expensive game you have reduced development costs because you don't have to pay a license fee you don't have to pay for the development tools I mean you have to buy a computer and stuff but right everybody does if they want to be online you can get your project to market faster because we have a grand tradition of reuse and and so on in open source we have an improved project ROI for a couple of reasons but fundamentally right we don't have to pay money to ask permission to see if this thing is going to work at some point down the road for us we can simply tell you know Tommy download Drupal you have a week's time to see if you can make a work working concept and that costs your salary for the week and that's that's very little risk right I'm gonna pay your salary anyway hopefully so we have a improved return on investment reduced costs over the lifetime of the project and reduced vendor lock it is important there's no you know licensed Vienna dealer of Drupal that we have to go through to get our services all of us as Drupal service providers we have to do that give the best service possible open-source service providers anyone can walk away and find another one of a project that critical mass so so that there's a lot of people out there and it helps open-source saw the projects past the truck test right the project is going to survive even without us if we pay zero money to have the license to use open-source software our IT project still costs money we still have people we still have to host it we still have to pay for bandwidth and so on so it doesn't matter in the comparison between proprietary and open-source that the license fee is zero it's just an IT project all these aspects is gonna cost the same amount of money but when we come to using open-source we can create or improve the features we need when we need them and you know Drupal has a great tradition of releasing cutting-edge features as soon as they come out the it's an old story now but it's the it's the one I've got in my head when Google released the at font face property who remembers when the web only had six or seven fonts yeah so when when Google created the at font face which allowed us to make a beautiful internet does anybody know how long it took for the Drupal implementation of that to be live and ready to use take a guess wait who said a week Christina right yeah and you said an hour it was actually 24 hours but it's pretty impressive you know I don't know how long Adobe your site core took but I'm guessing it was longer than 24 hours right there are thousands of us providing service it's open-source we our data is our own so every euro every dollar that we spend on an open-source project we're automatically investing in features we're not in we're not asking for permission we're not paying for that so we can train up our staff we can hire more people we can make it more beautiful we can add something and there's an old saying that I learned from someone at my former employer you know we can build it better not cheaper so we really shouldn't be competing on price with each other but we can deliver a better project by taking the same budget and reallocating it into things that we actually care about in our projects right so very very quick refresher into you know what we're doing here and why our clients should choose open-source solutions so what's blocking developers from contributing now I want to point out that the blue slides are Chris's right this is where I might stumble the the green slides are mine the blue slides are Chris's so pretend I'm about this tall and blonde and have a Dutch accent now and no I can't do it that's how many of you technical people ever wanted to contribute but felt that you couldn't you felt blocked okay and were you blocked because you didn't know how to contribute or what to contribute was that did that ever happen yeah maybe or you maybe who you didn't feel you had time to contribute your your boss doesn't let you do that on billable time that's right okay or how many of you just like thought wow you know Angie Byron and Alex pot and and Daniel Vayner like they wrote this code I couldn't possibly touch it like I'm not good enough to to touch Wow okay that's bad because it was all built by people like us right so Chris at his old job he did a really really interesting project he was working while finishing his bachelor's degree and for his bachelor's thesis he started looking into enabling developers to contribute and that's actually the origin story of this presentation because I was developing how to talk to management about contribution and he was developing how to enable developers to do more contribution we met in the middle and this is the project this resulted of it so I'm having a real trouble seeing these slides from here and I guess the purple thing is not really so readable right people felt I'm gonna grab the other microphone these mind maps get way too big to read in this presentation so just don't it's just that's how it is so people felt they had a lack of knowledge they didn't really know how to contribute right how do I get things out of CVS in the old days they doubted their own skills they didn't have enough time it wasn't clear whether they were allowed to contribute right and then that led to a lack of motivation there were barriers along the way like how do I know if the scope how now how do I know how long it's gonna test and all of these sort of things so here was a set of blockers around contribution that Chris identified across developer teams and he also surveyed a lot of people outside of his company once he established these barriers in in that place so then he also he also spotted negative catalysts so the purplish things are barriers and men the orange things are what he calls negative catalysts you know not knowing what you're doing it really takes energy and time to fit to get to being able to do it and if you have a lack of time already then you're pretty much screwed it's not gonna happen right and if you don't know how to do it maybe you don't want to look stupid in front of your colleagues like oh if I don't know how to you know submit a patch upstream or like you know deal with the issue kids on Drupal.org I just started here maybe I'm supposed to know that right so they could be embarrassed about it and all of this stuff around what is this even allowed did I get scope right so Chris identified these things he calls negative catalysts and then started working on ways to solve these problems providing training and guidance clearly unblocks a lot of this and when you're training people and and providing you know a weekly hackathon or you know a contribution day at work with with mentored contribution like we do in for example a Drupal con all of a sudden people's proficiency is improved and then it'll take less time to do it and then they know how to do it a lot of these things get unblocked right and so there's communication culture there just getting the the definition of done in a project to include contributing patches upstream completely changes the motivational picture for example so so this is a really really interesting mind map I'm happy to send you the slides if you'd like them so so this was the result of Chris's work one of the results of Chris's work now as open source people right as business people we say well you know of course we're going to contribute because you know it's open source this is perfectly obvious to us that we are going to contribute because you know it's the right thing to do because community right because you know that's why we're here okay but and these are not business reasons you can't take this to your board you can't take this to your investors you can't you there's this is just emotional crap right these reasons don't pay the bills and they don't provide any ROI and they're actually not measurable right and that's why we're here and that's my part of the talk and there's some some really good reasons that I'll talk about now going through so here we get to this point of identifying contribution roadblocks and we'll call them we'll call them operational contribution and strategic contribution so strategic contribution that is a lack of vision a lack of corporate policy a lack of support for contribution that's a that's a strategic roadblock to contribution and an operational roadblocks you know feared out lack of time lack of a mandate for the technical teams right so strategic roadblocks I'm a real fan of Simon Sinek and his talk how great leaders inspire action I really really like this and so it's talking about this idea about starting with the why why do we do something so I want to tell the manager why the company should contribute if so the idea of this golden circle right if you start with what what do we do we contribute okay right some patches go well how do you measure that how do you know that anything is any better for that how do you know that your company or your product is now better because you wrote some patches or you had a heck of you don't know so if you start with what you're doing you can't measure what you're doing you can't know if you have any impact so if you define why your organization contributes which I don't want to help you with now you can then create a mandate to contribute and decide how that contribution is going to take place and as soon as you define the how we are going to sponsor we are going to write contribute patches up stream and we're going to train apprentices right what you do becomes perfectly clear how many did we train how much did we improve our project and so on so so this is a really really valuable model and there's no there's no sensible way of doing this from the outside operational roadblocks start if you don't have a why right if there's not a policy in place that lets you do it you just don't even know if you can or maybe you're prohibited from doing non-villable things if you don't know how to do it there is no how and if there aren't procedures definitions measurable things in place there's no what to do it there's no sensible way so doubts about own skills lack of time and so on these are operational roadblocks that that stop developer teams does this feel familiar okay cool so these are the blockers that Chris identified in his old company and I guess we already had this diagram so let's just go on I can't find anything like especially new notes so okay so there's this thing called the boss talk this is this is also about like overall about longer term systematic thinking versus versus quick wins open source contribution brings clear and reasonably met quite measurable economic advantages along the way for your organization so so I mean really simply you know we are here right open source is working and without contribution this project wouldn't exist our companies would exist and you know we wouldn't have the prod product of 15 years of 16 17 years of work to build our own things on top of right so that's a pretty clear benefit to us like we can do Drupal there's an idea that you shouldn't really outsource your core competencies competencies of your company so knowing how your software really really works is essential you can't just leave it to other people to do it and contribution is of technical contribution patches and so on is the absolute the best way to know about how your stuff works and that should improve your ability to acquire and complete projects predictably and profitably and at a high quality Chris says that there is no better training for developers than interacting with a good open source community so you know just using Drupal properly and contributing and involve you know test some patches submit some patches implement some patches write new modules and submit them to community you're gonna get some really tough love in terms of the feedback about your code quality about what the modules do are you addressing the right kind of problems and that gives you back a better developer just letting your developers interact with the community at a technical level makes them better developers right and it's you know given that they're doing this probably while they're trying to solve a problem in a billable project right that's a cheaper way to do that then paying for explicit training for example and and you know frankly I'll talk about the HR effects of this later but it's it's also generally a great motivation to let people hang out with cool smart people like us right continuous contribution to the stuff that you put into production it increases quality over time and increases efficiency over time all of us tend to center in on a specific tool set a set of modules a set of implementation choices and over time and especially if we use testing well we produce a better product every time we produce a product and we make Drupal we make our modules we make the open source project we use better every single time we do our projects and give back everything we fix along the way contributing code upstream allows us not to have to maintain technical debt in-house which is incredibly expensive and incredibly risky maintaining internal liability in-house is stupid when you have an open source community that can help you solve it and take that burden out of your company doing open source right submitting your code to the community in the case of Drupal typo 3 symphony a lot of other projects you get security checks for free you get a thousand or a hundred thousand people using your code you get government agencies checking if your modules okay to use right security comes for free that's a nice benefit and you know if you compare doing proper security checks to the cost of outages and hacks and data breaches and so on you know that's a pretty good calculation to really really relevant to clients is the idea of them paying for a new feature but open sourcing it at the same time and that's a hard conversation to have with some people they're like I have to pay 30 grand for that and everyone else can use it apart from the idea that Drupal's already there for them and and very valuable you can you can tell them well hey you know upgrades are for free like there are smarter people than me out there and when I when I put my code out there your business case won't be unique in the long run somebody else is going to want that they're going to use it they're going to refactor my code they're going to make it more secure we get better code back every time we submit our code and let other people use it so the community adds a lot of value to the work that we do and you know if we build a reputation for delivering great projects as business people that should increase our ability to sell more projects hence our business does better that should have a direct effect on marketing customer acquisition and then if you build a reputation as a company full of smart devs right experts in your field who also contribute maybe you send them to conferences as well you know that becomes a real hiring bonus and it becomes a really great retention tool as well those of you who hire people like how much is the resume worth and how much is their contribution record worth nowadays right like their github account their Drupal dot orgs it's it's for developers it's really important now right and as a company you know you can turn around you say well we offer you know we're specialized in workflows and media and customers know now to say okay who your developers who work on that let me see their patches right so contribution is really a sales tool too and retaining employees is really really important I read some numbers the cost of a new technical hire in the UK in 2014 was 32,000 pounds right and they had an on ramp time on average of 29 weeks before they reach full productivity so there's a 25,000 pound loss in productive output plus recruitment costs plus temp higher costs plus everything else that you go through at the time loss of capacity and so on so there's a ton of value in contributing and putting your name on it right and then there's this other aspect right there's this strategic so so and that's just contribution to the stuff that you have in production the stuff that you're trying to sell if you can get to a place where you let your employees interact with other open source projects just give them a day a month or or or however you want to calculate to say just go do something in open source like go figure out a new framework or or or check out symphony or it doesn't matter it shouldn't be something in production they're gonna come back with new paradigms new ways of interacting like tell them to go submit a patch in another community and they're gonna come back you know potentially with new skills and new new perspectives on how to deliver better projects for you too so so there's this whole world of if you can if you can believe in and trust in the value of contribution simply for your your bread and butter stuff going beyond the bread and butter at some point is a really really interesting experiment contribution snowballs a lot of companies when you tell them hey you should really be contributing like they're like oh my god okay so we have to build something from scratch we have to invest thousands of hours of time and like a full testing suite and a bubba bubba bubba and it becomes like too much oh how could we possibly do that we're not in a vacuum right we are in open source communities and you're not doing this alone and if you contribute now this is a really interesting insight for me if you contribute during a project and part of the building of the project is contribution right not only do you reduce your that shouldn't say reduces project ROI should it hmm that should say that increases your ROI it reduces your cost so increases there we go it's just like Wikipedia here so you build a better project and you put it out your overall project is better and it does better but it reduces project cost if you do it right and I was fascinated I was talking with me know the etiquette from MD systems about this and he's a huge contributor good thank you you're exactly right so so I was like what do you mean it reduces immediate project cost you know because that sounds like aren't you just doing more work and he's like no no no picture the difference you've got you need a feature right build it from scratch take a module that does 50% of what you need and call the maintainer and pay her to finish her module for what you need right you get it done faster and you you know your team does its thing and you're supporting the open source project at the same time right and this is fascinating and he said this completely plays out economically contributing as hard as possible to open source while building current projects reduces their costs as well so have to talk about this with management and get everyone to agree that there is economic value there's bottom line measurable value in this and then you define a contribution policy you say hey we want to contribute and we are going to allocate this much time or this much budget or these kind of activities work on that with the technical department create a mandate for the technical department to then implement and come back and when everyone's in agreement you know you can get on with it and I think that in terms of economic measurability there's a there's one more point that I found really fascinating you can probably say in your organization a contributing a patch costs you know an average of like from start to finish fixing something is four hours of time or six or eight or 20 minutes I don't know what it is and you should be able to calculate that in your organization and then you know what your average cost of a developer is and then that means that if it were four hours and your developer costs you 100 euros an hour a patch costs 400 euros right when you've open sourced a module and the community gives you back 10 patches right that's a lot of value that the community is delivered to you economically and that's a really really nice it's a really really nice way to think about the value of of how we're interacting with each other so we're gonna solve these problems we need to increase the contribution proficiency of our technical teams as well as you know so now we've changed the policy in our organization and we're trying to get people more competent and give them more time to work so Chris suggests that mentored code sprints are incredibly effective like even bring in somebody from the Drupal world who you know is a good mentor and and bring them in for a day or a weekend or a week or what have you and it's a really great way to have knowledge transfer support that person and so on organize internal sprints and stimulate collaboration look at the tradition of the DevOps you know non nonviolent communication style you know blameless reviews and so on encourage a culture of of of collaboration and share success stories and then if people really trust each other you know you should be able to share your failures and learn from those two if you provide opportunities for training and contribution mentorship your developers will reduce the time spent per contribution so they're gonna get faster they're going to make contributions with a higher and higher greater and greater impact over time and they're gonna become better and better acquainted with your production systems of choice so they're going to be delivering better product for your clients which has got to be a good thing I talked about defining and changing organizational policy I don't know if this okay this matches right so in parallel with enabling your developers you need to do the things that I talked about with management discuss contribution get consensus and then define proper policies and mandates with between the IT and the management sections of the business so that you then have measurable contribution over time you know measure by number of patches submitted trainings taken I don't know find things to measure so you can know that you're being successful and start to figure out the value that you're getting from that and developers should ask for clear policies and mandates when they can and then if you can you really need to make explicit time available for contribution so that devs can can practice and become really familiar with open source project workflows and really get to interact with the communities that are relevant to you so a big part of Chris's research focused on integrating development workflows with open source workflows and when we started talking about this he had these incredible flow charts and it was really really interesting it was really long on one axis and then here and had all these things in it and and over the course of a few months we talked through what a development workflow really really is and this is what it is and it's pleasingly simple you build some well you analyze the problem you have right and you build something and then you give it to the person on the next desk and they say well you know do this other thing and do that thing and I would have you know solve this this way analyze the problem again develop a fix review it and when it's ready push it into production right this should feel familiar to you now when you share your work with an open source project the open source project workflow and the internal company workflows are identical right so when we've built something that's great we share it into our open source community and somebody looks at it is this patch rtbc or not yes or no if it's not it can go back into further development you know either over here or then out in the community and we can share these things at any stage put them into the development stage or the peer review stage until they're ready to be and to be contributed and you know we do this all the time you know we take stuff out of open source and if it's good enough for what we need we publish it if it's not we work on it we share it back share the patch review you know until it gets to published and then we also improve on it by the same way so these these arm this ends up being really relatively simple and if we're so if we've built something that works internally submit it to the community you know even if we start using it in its proto form you know we should be able to hopefully you know take back whatever the community then spits out in the end but we've done our part to make to make all of it better so at this point when you're using this kind of a flow right contribution has simply become part of how you work and if you include in your definition of done as I said that if patches have been written as much as possible they should be submitted upstream and then integrated once that all feels okay you can start to make explicit contribution time available and you look at companies like decent and they do this Christian van van Einde I think that's his last name I don't remember the group maintainer he gets a day a week to work on whatever he wants to and mostly he works on group and group is a great module and decent does a lot of projects that use group but that was you know that was Chris's thing anyway and giving people 20% time giving them a day a month giving them a day of the week but whatever you can afford lets them focus and tackle much much harder issues like really focus into difficult things and become really effective contributors and in contributing in ways beyond writing code and that's something to consider if you if you think that your company can afford it so if we think that contribution is a good idea and if we've got good solid contribution workflows with our developers what are the ways that we can contribute Chris's survey work and our experience in the community told us that there are more or less seven or eight ways that are the most effective so and this is pretty simple as well a lot of this you know contributing to code we wouldn't have projects without what we're doing and you know adding new features supports feature reuse adds value to everything that we do code reviews are incredibly valuable and nobody ever does enough of them and tons of pieces of the project are blocked by not having enough reviews so if you can do code reviews to help out your colleagues you know they're essential to code quality they're required to get code committed there are never enough of them and they're just not our favorite thing to do so if you can stand it like do a review a day and you'll really really be helping people it's the old classic but if you actually come across a problem and you know document how to solve it or document some some quirky aspect of Drupal's UI you're doing the rest of the world a great service a lot of documentation is missing for Drupal 8 if you look at some other projects like the symphony project for example it has exceptional documentation just amazing you know and and we can always do better so if you have the stomach for doing documentation please do that and interestingly I found in my old job writing documentation that documentation uncovers UX problems and it can often like documenting something can help you write a bug report or UX suggestion down the road which is which is kind of kind of interesting you know if it's hard to document it probably hasn't been implemented the best way possible sponsorship of events it's a it's a classic you guys have a stand here and you must think that you derive value from sponsoring a lot of other events and you know getting name recognition and so on in the community is important and and without you thank you like we couldn't do Drupal com but it also it enables this knowledge sharing it builds this community spirit thing that we think we have but I wrote investment here as well because this idea that you should just you couldn't just pay somebody to get that module ready or to finish that feature while you're in production for an important project it feels like a really right now it feels to me like a really really relevant important way to contribute so so sponsors have been investment like putting some money in exactly the right place where you need it you can organize meetups and public plan does that as well you can that and it can get you you know just knowing the local people around you knowing local developers well maybe you can hire them maybe you have somebody to help you with a problem maybe they're just cool to have a beer with it's it's all fine right user interface and user experience design are sorely needed in Drupal and many many other open-source projects so if you want to do that if you've got those chops you know please contribute evangelizing telling other people about what we do is also very very important if you grow the pie then we all have more pie right and community contribution doesn't happen without promotion thereof in the community itself so you know if you're able to create policy within your company to contribute you have a huge range of options here you can also take on trainees you can run apprenticeship programs you can organize certification sprints I mean there's just so many ways to help people if you think of it and I think the best way is to decide okay this quarter this year this is what we're capable of we're gonna submit all the patches upstream we're gonna run event and we're gonna buy you know pizza for our favorite module meant to whatever it is make it measurable and make it you know have a measurable impact on your business so I have so much time I don't know what's wrong I'm sorry I've run out of slides here so so so we talked about the old chestnuts of the open-source story why we should contribute some of the organizational and and developer roadblocks there and how to get around them and and some actions that Chris and I think are particularly effective kinds of contribution really thank you for coming to my session thank you for sponsoring triple con and you know thank you for all your contributions it's it's great let some you know we could probably go and have beers now unless questions anybody yes Christina and do you mean like in a company context I think a kind of a fair measurement in the company context is is actually your time right if I'm your boss I know that I've paid two days of your salary to do that if you've done it on work time and I would want to celebrate that and count that just as much as a contribution as anything else some companies have the the page on their website I forget what it's called now the give give back there was a there was a thing in Drupal like eight years ago where we had pushed to have like everybody should have like a you know your site comm slash give back or whatever it was where people would list contributions and I think it's really important to say you know documentation patch module patch mentor to sprint you know sponsored a triple cap I think it's hard to put a specific value on it but it should all be celebrated and you should be acknowledged and thank just as much for like or even more sometimes right documentation is the worst I wrote it for I did it for a living so yeah I think you should be celebrated for that just as much as anybody else for their contribution yes the question was our companies that feel they don't have time to contribute or won't let their developers contribute are those companies or developers doomed I like that question Chris and I have given this talk several times around Europe and we spoke with a development agency in Romania who said their lead developer was offered a job with a significantly higher salary but where he would explicitly not be allowed to contribute to open source and he turned that job down and stayed with the agency replacing great employees is really costly so there's a huge value in figuring out how to do this and honest to God if you are taking open source code and messing with it internally and delivering projects and you're not engaging with your open source communities and you're not engaging with the products you're using you're not as good a company as you could be right so that company might not be as profitable as it could be that might that company might be doomed right because that practice is very short-sighted you're not investing into your own tool set that's that's crazy right and developers who find themselves in that situation if they ask me privately I'd say if you have this skill set you have your choice of jobs so maybe you could go find somebody else right it's it's a very short-sighted decision and it's a matter of perception and it's a matter of shifting your priorities a little bit to get there but I think it's really important Tommy share a success story Tommy I used to live in Ireland and I worked for a company called Anatic and we are given some time not a lot but some time to contribute and I at some point I found the solar and search API really interesting so I invested some time in that and I contributed some patches not a lot but but some I made myself familiar I familiarized myself with the module and then someone said you sound so clever about this rather block post tell everyone else how easy this is so I did that and we thought that was the end of it until a company in Germany called us and said someone from your company wrote a block post about about solar and Drupal and indexing stuff we want that guy sent him to us they say okay and the same thing happens with a company in I guess I think it was in the US where they called all the Atlantic people in the US don't tend to do that as far as I understand but they called us saying we want that guy that knows so much about solar so yeah it paid off in several ways one thank you for proving me right because that's awesome but you weren't looking at me when I was on stage here but this is just like the best feeling right because it's it's everything that I said you profiled yourself as an expert your career was improved an attack did better right more clients and it was just because you were fooling around with something that you were interested in not even for a production right and just writing about it got us all that that's fantastic so awesome thank you that's really cool oh yes so you use Drupal and contributed modules and core yes and your own modules written in the company okay and so you write patches anyway do you do testing oh okay we want to do testing but we don't have time Sebastian backman is gonna be here to talk about testing and he's a good friend of mine and he would we have a lot to say about that that's another session that I do but anyway so business value of software quality right um you write patches already right so when you submit those when you write a patch on your branch right and it gets you test it enough you merge it into like at that point there's no reason why you couldn't spend how long does it take to do it I don't know like a minute longer to put that up in the issue Q under put our great okay well okay um I don't I don't want I'm I'm not scolding and I'm not criticizing like the reality of working for clients is can be terrible right and you know your boss has to pay your salary and you have to deliver working stuff and like everybody's under pressure like I totally get it if you think there's interest at the company about like working on this changing this culture right um completely seriously I can send you Christian to do contribution workshops of how to make that a really efficient part of your day and I know where do you live in Berlin well Sebastian is in Vaughn right but I know that he's very passionate about testing and he can come up and integrate that into your workflow as well and I will introduce you personally if you want because it sounds like you know maybe that would make your work day nicer or we can find you a better place to work well I mean who is it the pre-note the pre-note yeah so buddy Breidert is what I'm on internet she in Frankfurt she's hiring she said that on stage right you guys hiring public plan and just sort of his hiring sorry Larry did you have a question wait wait wait wait hi we have an open Friday once a month where we ask our employees to discuss about problems to do sessions to learn and everything but now as I heard about contribution I think I'm gonna do it as a contribution day where all employees have to contribute something like our project managers they have to write documentations the programmers they have to patch something so I guess we're gonna rename it into a contribution day see and maybe you can send Sebastian to us to teach us how to do this day more efficient for everybody so Christian yeah so yeah but don't tell them they have to like make it something make it there you go if you want to work here you have a chance to contribute and and and he has them right he has them down in the coal mine hidden away from the daylight coding away at the coal face right this is a story that you hear a lot and frankly I guess if his developers did find out that I mean that's a really shitty way to be a boss right I'm sorry I mean he might be right we've seen it very very differently we were at an agency workshop a couple of weeks ago in Holland where it was a different technology but these agencies all use the same technology and we had like a big round table talking about problems talking about solutions making plans they trade developers between the agencies like for projects every now and then it's like I just sent my best guy over there and they sent me somebody and we did our you know because we're doing open source I mean it's nothing mysterious right they said that that improves employee retention right because everybody thinks oh you know public plan they've got the pool table they've got the sauna they've got the free snacks working at public plan must be so amazing right and then everybody at public plan is like oh my god imagine if we worked at brain bits in Cologne you know they've got like the wood paneling and they've got the foosball table and right but if you trade them right you you get new skills and new perspectives and you improve your developers and they see that hey you know Lara's fridge is better and they're whatever but in the end it's all the same right so it doesn't feel sustainable to me and if you know those developers you should invite them to community stuff outside of work hours right I think you'd be doing them a favor or you don't know who they are do you know the developers they might also be really happy it happens right if we're honest the number of people using open source versus the number of people contributing is there's a big difference all right is it beer o'clock I think it's beer o'clock thank you so much but so what's one gerne und ja gerne sehr sehr sehr gerne und ich je nachdem kann ich natürlich irgendwie so das geschäftlich ein bisschen gescheiter und mit ein bisschen grafik und irgendwie mattel und so da präsentieren aber chris unter unter developer ist unser entwickeln der ist so klasse und er ist das hollander das heißt er ist über ehrlich und hart also er sagt einfach was er meint und zu und er ist also in sachen software qualität und in sachen contribution ist der genadenlos gut und es ist es ist echt nicht der ist im prinzip haben wir kriegen wir zeit und im prinzip ist es total gewollt ja und denn ist immer dieser trug da aber kunden aber also die realität da gibt es immer was ist auch war und nicht böse gemeint hey how are you man of course of course of course i'm great is anybody else yeah cool how's things how's it going over there yeah yeah awesome all the walking people i love you so so she and i just found out this company