 10 in five? Yeah. Five is probably five. Okay, more five. I guess this is running in the back, right? Yeah. I don't know if after or right before lunch, which one is the worst, but there will be beer in the talk. I wish I could give it out too, but I think the university frowns upon unregulated distribution of... So, sure. We can start and then people can filter in. Sure. Good afternoon. This is Aaron Baldrige. Aaron is a community builder at Elastic and a founding organizer of the Dan Robson City Meetup and Dan Robson State's Hartford 2017, so he's interconnected. He is passionate for connected units and music technology to enhance our natural connection to each other, and there are references to where you can find the crazy... I'll revisit those, too. His talk today is Coors to Craft, Building Code Community. And that... Hi. So, yeah, that was one title, and I've also called... I was another... Called this talk, Craft as in Beer to kind of play on some of the phraseology you're probably familiar with from free and open source software. So that's where you can actually spell how to find me for email or Twitter. I'd love to connect about this talk on Twitter, because this is an idea I kind of was passing around, and I want to get some feedback on it, so I'd love for people to connect or, like, mention me in the middle of the talk if you're like, oh, I haven't thought about that. Like, that's totally cool, too. So, for some level setting, I want to talk about free software. It's kind of where I borrowed that Craft as in Beer terminology from, and I didn't realize how much Red Hat presence there would be, so I probably don't have to be as detailed in this part of the conversation as I might have to otherwise. But I want to go through it a little bit just so at least we're all on the same point and same understanding of the past here. So in the beginning, software wasn't covered by copyright at all because largely it's hard to copyright, like, the order of holes on a card, and, like, computers looked a lot different than two, so it wasn't really a concern until the mid-70s. Contu, the government agency whose name I forget but remember the abbreviation, argued that basically as far as software represents the original thoughts of the author, it should be covered under copyright laws. And by 1980s it is actually defined and added to the existing copyright in the U.S. And for those who know the history recognize that about 1983, that finally bothers Richard Stallman in a left to leave the MIT Artificial Intelligence Lab and form the Free Software Foundation. Basically at this point copyright exists in the way the licenses are written, so restrictive that even if you wanted to share something like in MIT with another department, you might not be allowed to share the code between each other. You can't really make improvements to it now because it's restricted. And we're still at a very early ages of computers, so there's a lot to change and improve upon on a daily basis. And basically that's the gist of it, right? Like, we are always taught growing up that you should share. Like, if you've got knowledge or a tool that can help someone out, you should share that with them. Growing up you're not told, hey, I'm sorry, you can't let someone else play with your toy because they haven't actually bought the license for that toy, so they're not allowed to use it, right? Like, that's not how society works. So it didn't make sense that this is applying to software too. We have to have a giant picture of Richard Stallman. If we talk about Free Software, I think that's part of the GPL license. So to go over briefly the four freedoms, you might know, but to refresh, it's freedom to run the programs how you want, so you're not restricted to an operating system or a way to actually use the program. You should be free to study and change how the program functions, which is pretty much means access to source code is a prerequisite for that. So source code is going to have to be available so you can see how the program functions and alter it if you want to. Freedom to redistribute copies. If I say, hey, I know you're having the same problem as me, this is the software that worked, how about you try it? Like, that's part of Free Software. And the free to redistribute modified versions. Yeah, I have that bug too. Here's my fix. Try it out. It'll probably work for you. That's all the basic freedoms of free software. So of course, that's a good new. Richard Stallman forms GNU, starts trying to write the first open operating system because there isn't one at this point. All the operating systems have to be licensed. And partially successful. Built a lot of the major tools that make up an operating system. But the more interesting portion that came out of that was copy left and the actual legal frameworks for how to have free software. The problem with just releasing software public domain without copyright is that someone else can then change it and copyright that and then you lose all those fixes and you lose that connection to the community there. So the actual licensing that came along with the GNU GPL is what's really important to come out of the beginning of that project. That's what enables all of the future growth of open source and free software. We do eventually get a kernel that's open source and Linus Torvalds releases in 1990. The Linux kernel and you get the GNU slash Linux operating system using tools from both departments. What was actually the interesting fact I found here was listening to them talk about a GNU is trying to build this micro kernel structure. Very Unix thought each program does a different thing and Linux beat them to the punch mostly because they built a monolith. So interesting conversation as you think about how we talk about like microservices and monoliths today just thought it was interesting. Adoption grows pretty rapidly of Linux. These were numbers from Forbes but you can see pretty much as the internet ubiquity goes up so does adoption of open source and Linux because that's where largely the community lives that wants to use computers. It's a lamp stack. So Linux basically takes over the web. It becomes kind of the de facto way to run websites especially if you're something like GeoCities and you've got a bunch of customers that want to run a bunch of websites and Microsoft and IAS only runs one website per box at this point. It becomes more cost effective to run a bunch of Apache servers than a bunch of Windows servers and IAS. Today that's pretty much what Linux adoption looks like on the web. 97% of the top 1 million domains are run on some form of Linux. 92% of all EC2 instances are some form of Linux. So pretty successful model as far as just adoption of the software. So how many people have read or know of the Cathedral in the Bazaar essay? So most people, cool. So you kind of know the gist. Lost his name, Eric Raymond, right? So Eric Raymond writes the Cathedral in the Bazaar to compare the two existing software development models. The Cathedral is very much the current proprietary. There's not a lot of say from the community but they work on it and then eventually it's released to the public and people can partake on it. Really long feedback cycles and not really taking outside input. Meanwhile the Bazaar, while it can be a little bit chaotic and messy is constantly changing and getting feedback both from the users and the people that are working and maintaining and using that software. Everything iterates very quickly. It's interesting to note that it's not that one is necessarily better than the other but they produce different things and they look different. Everyone remember this logo? So another successful move there is in the 2000s, of course Netscape Communicator has a problem. Anti-competitive practices and philosophy aside they can't make money when 92% of the web is browsed by Internet Explorer given away for free. So taking inspiration from the open models in general and the Cathedral and Bazaar essays they decide to open their source code and invite the community to take part in the actual build process which forms the Mozilla Foundation. So the Mozilla Foundation forms and eventually of course release Firefox as the big first open source wildly successful browser. So that's really cool and shows how you can have success with this open model but what's really interesting about it is where all that success comes from. It's not just because it's free as in you give it away but it invites the community to be part of that software development process. You're actually going out and saying, hey, is this useful for you? Do you want to help me make it better? You start getting things like hackathons to use all this free and open source software and start sharing tools to solve real problems in their communities whether civically or niche interest. You have a lot of mentorship that builds up inside this open source community. You have meetups, they had install parties because we didn't have an official support source so the community turned to itself and said, hey, I want to get started. How do I get started? And you'd have the experienced members come and help people just install free and open source software. So that largely drives the success of this whole format. There had to be people to support the open source movement. And we, of course, can say it's successful because free isn't beer but that's kind of problematic in that it's talking about giving it away but that's not really the exciting part about it. Besides, if I say free beer you're probably not expecting to get like a bunch of Trillium or Treehouse given out to you. You're probably expecting like a bunch of Budweiser. So there's kind of this connotation that if it's free given away it's probably not the best quality. And it's not even that apt of an analogy anyway. It's usually more free as in puppies. Like here you can have it for free but there is some care and feeding and maintenance you're going to have to do. So it's probably going to cost you something if not upfront. So again, not really compelling except for the part that we're talking freedom of the software. Free is in speech. It has certain rights associated with it. That lets you use that software how you want in your own manner without being dictated by a company. So if I were really clever I could come up with some like free isn't speech, free isn't puppies, free isn't beer, free is in some other thing and we could have some cool freedom discussion. But I got distracted by the beer portion so we'll have a beer discussion. So craft beer is really interesting. I want to do a little bit of a history run through here as well. In 1887 there's over 2,000 breweries in the US. Those in US history know there's a problem in about 30 years. Now there are officially zero breweries in the United States because it's now illegal to brew and distribute alcohol. It ends in the 30s and World War II happens. So by the time we're really building up this industry again it's a vastly different world that they're building it up in. A lot of the tradition is gone. Suddenly you can start shipping things nationwide. You can start advertising nationwide very easily. So the popularity comes from beers that are consistent. I can get the same beer in Boston as in LA and it's going to taste the same. I'm advertised to they're largely just generally appealing, not like dangerously niche flavors. So it's pretty much the least offensive things start spreading. But like 70s which is now as far from prohibitions were before there's only about 44 breweries in the US. So a far cry from 2000 even if that's underestimated. And that's mostly because home brewing is still illegal. So 1978 home brewing becomes legal again. In the 1980s there are roughly eight craft breweries. So we wanted to find craft beer a little bit. So we'll go through what actually is craft beer. They're small so they have less than 3% of the total like barrel production in the US. Independent meaning they're not also owned by a company that has more than 3% of the barrel production. And traditional. So they care a lot about where beer came from. The flavors still come from the brewing and fermentation process. It's not some completely off the wall artificial alcoholic beverage. So like Mike's hard lemonade doesn't count as beer. So that's kind of how they're trying to lock that definition with traditional. So you might recognize some of the early brewers from the 80s. These are all the craft beer companies that existed around that time. Anchor has a great history like they're part of craft beer legend because they almost disappeared in the mid 60s. Got purchased, had to kind of modernize their whole infrastructure. Released actually the first American IPA considered come out of anchor. And so by the 80s they're pretty much up and running is one of these local breweries that could still stand. And purchased largely because Fritz Maytag didn't want to see his favorite beer go away. So he bought the company. New Albion was one of the first ones where a home brewer turned business owner only around for six years but largely inspirational for every home brewer who said I bet I could sell this. And of course Sierra Nevada is still around today and largely responsible for the quality of hops that are available to home brewers and microbreweries. Did you say Fritz Maytag? Did you say Fritz Maytag? Yeah, bought Anchor in the 60s. Is the Maytag Maytag? I don't know. I know it's the beer Maytag. I don't know. So yeah, Jack McAuliffe was new Albion who was only around for six years. They've come back a couple times and Ken Grossman is Sierra Nevada. Largely the 90s come along and we have sort of getting a little bit more adventurous. Sam Adams is proving that even a smaller brewer can show up in your sports bar. They don't have to be like some niche thing that you have to know about. We're getting a lot of different flavors. Stone believes we should use all of the hops always. Allagash is bringing over all these Belgian styles. So Blue Moon pretty much wouldn't exist if Allagash didn't brew Allagash white in the 90s. And obviously we've got some of the major staples for today from Treehouse and Trillium, kind of pushing the edge of what you can do with beer. Oscar Blues who made cans cool again and other things going on as well. Pretty much the statistic is you're probably within about 10 kilometers of a brewery. This is not quite the smallest state in the U.S. But where I live and that's all of the craft brewers in Connecticut at this point. Yeah, so it's pretty popular. In fact, you can see there's quite a few compared to eight from 1980. There's now over 6,300 operating in 2018. And what's really interesting is the way it sort of follows this dot-com boom and bust. If you watch it, it grows through the 90s. It kind of plateaus at the end and then jumps up again when 2010 comes around. So again, the economic success is interesting, but isn't what's really compelling about the story, just like free software. So I want to tell a couple stories to sort of get at what's really interesting about craft beer. Does anyone know Smuddy Knows? They're relatively close by. So the great story about this is the owner of Smuddy Knows bought it by accident. He was currently and still is the owner of Portsmouth Brewing Company, the brew pub in Portsmouth, New Hampshire. And I forget the name, but some other brewer owned the location and the materials from Smuddy Knows and went out of business and it was up for auction. So he came by not just to buy it because he needed equipment, but he wanted to be there and welcome whoever bought this into the craft beer community. Like, hey, welcome. What can I do to help you out? Do you need information? How can we help each other? And of course, if you're at an auction, you throw in a lowball bid anyway because why not? And then he won. So he suddenly was faced with, oh, no, I need a company and beers to brew because I already have one, so I need to go reinvent all these recipes. They're able to do all that, as you know they're around, but the kind of the cool thing is they relied on the community to help them build this company that they weren't expecting to have to build. All the labels that come are pictures of people in the local Portsmouth community. They use a local photographer to take them. The original old brown dog is one of the brewery employees dog at the time that posed for the photo and they took a picture of. So it's really cool. They really gave back and made sure the community was part of their actual growth of their company. So Booth Bay Craft Brewery you might not know about. They're a bit further away and I don't think they distribute much outside of their area. But I visited them a number of years ago and they had a really great story about what they were doing. They hadn't finished yet, so now I get to tell this whole thing now that they're done. When they started out, they wanted to do their first beer about Booth Bay, right, kind of establish themselves there. So they gave out hops to the locals in Booth Bay. All the community were part of that. They had them grow them throughout the growing season and harvest season invited everyone back for a big picnic and party and beer and food and harvested all the hops that the community had grown. So they actually used these hops to brew their first pale ale. It happens to be 6.33% ABV which is like the area code for Booth Bay. So they obviously name it 633 and release this community collaboration beer. Like the whole community actually got together to brew this beer. But they didn't just want a brewery. They wanted to build a brew pub. And a true public house that was a part of the community. Like where you go to talk about what are our civic matters? What are matters of our community that we need to fix? So they started building this brew pub and asking the Graph Beer community for support. And companies like Dogfish Head and Allagash actually sent them lumber to help build this big... You can tell it's all the hardwood post and beam construction that they build this out of. So they have lumber that's carved with like the Dogfish Head logo and the Allagash logo. And the community started donating that too and they carved their names and locations from where all this lumber came from to build this brew pub. Now it's completed and it's... You can tell it's not just for people who like Graph Beer, but their families can come in and bring their kids and they can be part of the whole experience that's there. They become that gathering place for the community. And then one more is about a beer store. So they're not a brew pub, but they sell beer. So City Beer is in San Francisco. And when the owners opened it, everyone said you can't sell just beer. There's no way. You're going to end up adding wine. You're going to add spirits. Like you're probably not just going to sell beer out of the store. But they tried anyway. And it's set up kind of like the idea of those wine bars where you can taste wine and then buy and bring it home kind of idea. So not only were they successful because Graph Beer becomes successful and everyone comes and hangs out there, but when people would come, they'd bring friends who might not drink beer. And they could get in that situation and say, hey, do you have any wine? And they'd say, no. And that could be the end of it. But they would start saying, hey, but what do you like to drink? Like, what's your favorite wine? And they'd describe, you know, I like a Merlot, whatever it is. They'd say, awesome. What do you like about the Merlot? Like, what's interesting to you about that that makes you come back and drink it again? And they'd describe, you know, maybe the flavors that they like about it or whatever cool wine words mouth feel. That's probably one of them. And they'd say, awesome. You know, when you describe that, I think of this particular beer. Do you want to try it and just see? I know you don't normally drink beer, but do you want to try it? And more often than not, they'd have someone like it and say, you know, I'm so glad you didn't have wine here. Because if you did, I would have just drunk that and not known about this new thing. But because you didn't have it, I tried something new and discovered this whole community that I can now become a part of. So just by including people that normally would be outside that community and say, hey, do you want to try and see if you like this? They got a lot more people to join and grew their local following. So how does this all tie in? Because I want to maybe coin a phrase called Kraft Software. It's a little bit hard to define as either free and open or measure it as small. Because it's really hard to measure the output of software. Like, do you have less than 3% of the total barrels of code that are output is kind of a weird measurement to figure that out. And I fully understand there's some balance between being able to give away your code and needing to like put food on the table. So it seems unfair to exclude people that want to charge for their work. I understand that. And for some companies like for many beer brewers, their code or their recipe is what makes them apart. That's what makes them different than their competition. So I had some ideas who want to wrap around this and I thought it was more interesting to get at the heart of what really drives both of these two industries of free software and Kraft beer rather than what defines the edges of who qualifies. So I think if you're doing Kraft Software, you're building it with passion. It's not because you need to hit a quota or write a certain number of lines of code to get your paycheck at the end of the day, but you're doing it because you really love to do it. You're doing it because you solve something you care about. You're proud of your work and you care about its impact that it has on other people and the community it's released into. I think there's an innovative tradition there that is sort of picking up ideas of the past, paying respects to where they come from, and seeing what else we can do with those, maybe turning them over in a new light. Like this talk, for instance, is not whole cloth grown but built on the shoulders of all the past of free software and all the past of Kraft beer, putting those together, turning it over a little bit differently and coming up with something interesting. Even our software development movements like DevOps isn't wholly new. It's kind of looking at where open source came from and where Agile is going and saying, how can we apply this to operations and does the supply back now to development? Openness and sharing I think is characteristic. And while I want to say you probably should open source everything you can, it doesn't mean you have to open source the whole company. Companies like Netflix and Twitter open source tools they use that aren't what set them apart necessarily from the competition, but our ways they found, hey, we started doing this practice and we found it really helped us. Maybe this can help you too. And they talk about it on stages and they go to meetups and they open source Chaos Monkey or other things that aren't their secret sauce but help other people get better at what they do. And I think the community is big. I think that's the biggest part is that the community has to be involved in it in some way. They're invited into the production process of your software. Whether it's, again, through you get to be an open source company and you can just fully say come and help us build this or it's that tight connection of how is this working for you? Can we do something to improve it? Or it's even looking at community outside the context of your product and saying, hey, we're in Denver or we're in Boston. What's happening in Boston that we need to care about that we can give back to? Is there other things happening that we can help our community because we're bringing in venture capital? How can we give back? So that's sort of the four hallmarks I think that define what I was thinking of of Kraft software. I'd love to hear some feedback on that. So I don't know, I have a little bit of time I think, right? If anyone has questions or thoughts, I'd love to hear them now and if not, I'll throw up my contact information again. So yeah, we got a microphone going to you. Thank you. First, let me say a wonderful, wonderful presentation and thank you for the analogy that you used between Kraftspear and software. So let me self-identify I am not a developer. I head up a nonprofit. I came here because I want to be more informed and learn about the community so that I can ask common sense questions of my lead master. And so, but thank you for the wonderful presentation. A question that I have and I applaud the community for what you've created. I think that it would be great if other industries followed what you're doing. It would be, especially the financial community, financial and the educational community. So my question goes to your last point about community involvement. Because it's not new to the community that it's lacking a little bit of diversity in terms of women and people of color. So my question, and I will also preface it with a quote by Albert Einstein. So my question is, how do you think the community is addressing it at the root? The root of having more diversity, specifically women and men of color. People of color, I'm sorry, people of color. And I would preface it also with a really powerful quote by Einstein who said, you cannot solve a problem with the same consciousness that created it. You must stand on a higher ground. I have some ideas of solutions, but I would like to hear from this wonderful group of people who are attending here in this particular workshop and I'd like to hear your thoughts. Thank you. So I'm going to end up giving a famous answer for the company I work for too and say it depends. Which means I think it's a really good but really complicated question and there's no easy answer for me to say, oh, it's addressed this way. I think part of it depends on what you consider the root of the issues and part of it depends on which communities you're looking at and how they're addressing it. I can only speak for where I've been involved, part of it for our DevOps days, and actually DevOps days everywhere for the most part, are explicitly required to have codes of conduct and they're usually explicitly inclusive or aggressively inclusive, meaning they make it a point to reach out and invite people in, just hey, we're here if you want to join, but we really want you to be here. Would you please be a part of our community and we're going to make sure that it's a safe place for you to be, that it's not going to be invited in as an afterthought and then ignored once you're here. It's about the inclusion, not just the diversity of attendance. I've seen a lot of tech conferences do a lot better as far as... Some of it's just being conscious about it. In the past, you might set up a conference panel or a speaker list and it's just whoever submitted and you selected what you thought was good. I've seen a lot more conscious effort in making sure people see themselves represented at conferences as well that you can be part of that community. I'd love if anyone else has other things they've experienced maybe or other ideas, then I would love to hear that too. Just to follow on his comment, this conference has a code of conduct and it is rigorously enforced and there is a staff that is dedicated to responding to code of conduct complaints. So there is a conscious effort on the part of companies and developer conferences to at least respond in a responsible way to the various pressures and problems that have occurred over time. Yeah, I just wanted to mention one specific thing. Are you aware of Outreachy? Yeah, because that's a specific thing that was created in response to these kinds of concerns. So that's one thing that is being done that Redhead has been involved with. Just wanted to mention that one. I appreciate crowd sourcing an answer and a talk about community too. It's perfect. So I think it's important to not get caught up in solving the problem immediately, especially for a problem like this. It's not going to be like an overnight solution. If you apply the agile method of software development, it's all about iterative improvement. So you make tiny changes that get you closer to your goal. So every time you get feedback, for example, from your community saying, well, you didn't include enough diversity in this last conference or whatnot or last activity, you take that and analyze it and make an effort the next time you do it to reach out and include those people that may have been underrepresented. So part of it is helping to, you know, some of the concepts for development and innovation of not thinking of failure as something you need to defend, but as a lesson to be learned, I think is a big way to apply that to your community development as well. When you get that feedback of it wasn't whatever was not an adverse enough panel. Instead of jumping on the defensive, you can turn towards that. You know, thanks for that feedback. How can we improve? Do you have ideas that can help us? If not, let's see what we can do and iterate on this for next time. Do you have a question as well? With regards to inclusion, I've been part of a group organizing computer events in Norway. Well, we had traditionally about 5% female attendees and our goal was 25%. And we said, OK, we'll reach this within 7 years. So it was quite a long span and what we did was we had some different things and we said, OK, let's embrace failure. We can try things and say some things will fail. That's OK. So we did some things. We said we have to focus on our volunteers. We have 400 volunteers and 7,000 participants. So we're just, for example, on Facebook, we show faces of different volunteers and their story, why they got involved, et cetera. And we always focused a bit more on the female part than the male part. And also the female, the women that participated once and then disappeared. We rang them up and asked, why did you disappear? What could we do to involve you more, et cetera, et cetera. And we now reached 25% women. And our next goal is, yeah, thank you. And our next goal is like people of color, because that's a small part of Norwegian population, but wants the event to actually mirror the entire population. And yeah. Awesome. We have one minute. OK. So I'll throw up my, this is some info where you can find the slides or I wrote a quick blog to also solicit comments there if you want to comment publicly. Or you can just contact me one way or another. I would love to hear more in-depth feedback or whatever as you, I'm sure, walk away and think about it more. That'd be awesome. I'd love to continue a conversation about this idea. Thanks. If I can, I find my slide.