And then we have one minute and it will be... Did you just pick up the instruction on an all-in-all course? You too? We're going to go ahead and get Mr. Kevin C. Fleming. He is in the CTO's office in Bloomberg. And we'll talk to him today about how to engage corporate foundations and other large company organizations in corporate giving for software projects. So thank you very much. Thank you. But actually, before I do that, I'm going to make a segue from Brian's presentation. For those of you here who are just listening to Brian, being a big company who is also a media company, we of course use media to promote everything that we do. We actually promote our open-source projects using media as well. We published a piece of software at KubeCon last year in November in Austin. Four reporters wrote about that. And within, I don't know, a week, we have 1,400 stars on GitHub and tons of forks of the project, which we never would have gotten if somebody hadn't gotten the word out. So it can be really useful. All right, going into what we're going to really talk about here. So let me ask a couple questions. First of all, how many of you work for companies that have at least 100 software developers on your staff? Almost everybody, fantastic. This will be really relevant for you. How many of you work for companies that do volunteer or philanthropic work of some kind as a corporate thing? Excellent. About a third. That's good enough. So first thing I want to do before I get started away, because otherwise I'll forget because I can talk forever. These are all people who helped me make this happen. So they deserve the credit of being on this video. So I wanted to make sure they all got credit for that. Andrew is a developer and a long-term, long-time developer in Bloomberg Engineering, where I work with projects on quite a lot. Henry is a developer in our London office. I'm based in the New York office, and Jeff King, for those of you who don't know, is one of the core developers of Git, and he actually helped us do our very first project, which I'm going to talk about here in a minute. Of course, we have a big philanthropy team. And then Cal Kingsbury, who you have heard of, who built an open source tool called Jepsen that's used for testing distributed systems. He actually helped me solve part of this problem, too. So let me give you just a very quick background about who Bloomberg is to give you some context for those of you who don't know. We are about a 20,000-person global company. The company started 30... Now I'm going to forget the exact number, and this will be bad, 36-ish years ago, in order to provide pricing transparency in a particular part of the financial world where data was previously only made available literally on pieces of paper that had to be copied around and given to people. We're much bigger than that now, as you can imagine, because you didn't need 20,000 people to do that. And so we are a global provider of financial data and analytical tools and all kinds of things. We also run a media organization, have 160 offices around the world and all that kind of stuff. So we're involved in lots of different things. We have about 5,000 software developers around the world. And most importantly, and what drove this happening is the founder of our company, Mike Bloomberg, for those of you who have heard his name, is very much into philanthropy and volunteerism and making the world a better place through the money that he's earned and continues to earn, and we help him earn. So part of the ethos of the company is that we do that. The company's profits go back into its foundation, which is then used for charitable giving and that leads to what we're doing here. So I'm going to show you a series of pictures and I know the contrast in here is kind of terrible, so you can't see these great, but I want people to tell me what you notice about these pictures that I'm showing you. You're all going to notice, first of all, there's laptops everywhere, so don't tell me that because I can see that. So what do these look like to you? Those of you who've done open source events before. That one's a good one, by the way. Lots of people.  Fun is good.  Second, it's people who are working on software. Okay, lots of people like working on software. Software is fun. But as an example here, these are people who came in on a weekend to work on software, even though they work on software all day every day as their job. They wanted to do this because the software that they're working on is something that they wanted to learn about. They wanted to help improve and its owned, operated, use whatever term you like by some organization that is a charitable organization. And we'll talk about who those are. So what we do is, I'm sure all of you have seen open source projects have sprints and hackathons and other things to get people motivated to come help them solve bugs and write documentation and build unit tests and all those kinds of things. We wanted to combine all of that together. So, that's an interesting sound. So, why would we do this? Well, I guess I already covered this part. We don't really need another reason, but we have other reasons. So I covered some of this, but let me give you a few details. So 20,000 employees last year, 12,000 of those people worked for months in a volunteer activity somewhere in the world. Some people do it a lot. I mean, there are people I know in the New York office who volunteer 200 or 300 hours a year of volunteer time. It's really quite amazing. And that, in the past, prior to this program that I'm talking about here, consisted primarily of the things you would expect. So our philanthropy team focuses on certain areas. Obviously, they can't do everything. So they focus on programs in the arts. And sustainability projects. So personally, for example, I have gone out and planted trees. I've gone to Habitat for Humanity projects and helped people's houses get rebuilt. I've gone to food banks and sorted food donations. I mean, there's just a million different things that we do, and we do them all the time. And lots and lots of people like to do that kind of stuff. However, some people prefer to volunteer using the thing, the skills that they have, that they know they're the best at, right? So that's where the best can go sort clothes or wrap presents or hand out food at a food bank or something like that. But if you're given the opportunity to use the thing that you're really the most passionate and the most excel at to volunteer, you're really going to want to do that. So they said, well, could we do skills-based volunteering where people who actually have a particular skill can go help? We have a couple examples of that already in the company. For those that I don't think this exists in Europe, there's a program in the United States called First Robotics, which is basically teams of high school kids that get together and build robots and then go to competitions and have robot wars and win them and get scholarships and all kinds of other things, and it's run by a charitable organization. And so part of the way that's accomplished is they get volunteers from companies who are software developers and smart people to come help the students learn how to put together mechanical devices, how you put together electronic devices, how you write software, how you understand that if I make the motors do this, that's what happens and all that kind of stuff. So we have people that do that and they love it, but they're not actually writing software, right? They're helping students do it and we actually have people do that. Now there's a variation of First Robotics for grade school children, so they use much smaller devices. They don't have robot wars because that's not really appropriate. There's not to be Andrew who I mentioned before. Could there be a way that we could use our philanthropy efforts to help open source projects? So I sat back and went to talk to the philanthropy team and I started talking to them about organizations like these and many more and said these are all, at least in the United States, they're all organized as 501C3 charitable nonprofit organizations whose purpose is to help the world be better via some way. They all use different words to describe what they do, but they're all charities that make the world a better place by producing software that we all use every day. So I went to them and said if I was to organize an event with one of these groups and we had a bunch of employees come in and they spent eight hours on a Saturday helping to improve software for one of these teams or one of these projects, would they get credit for that? Would they get to add that to their volunteer hours? And they said, let's give it a try. So that was, I'm going to back up here, this one. This was the one that we organized with Jeff King of the Git Project. We had about 25 people come in. They spent all day working on Git stuff and that, again, as you would expect was mostly small bug fixes and documentation and unit tests and things like that. Interestingly, when we started the day, went around the room, everybody introduced themselves. Most of the people, this was only open to Bloomberg engineers in New York since this is the first one that we did. And I made everybody introduce themselves. Most of them had never met each other before, even though they work in the same building every day with each other, they never met with other people. So there's actually some networking benefits to it too. And we're going around the room and asking people to introduce who they are and what team they're on and what they do. And this last person introduces himself and says, and I'm not a software developer. And my response was, well, why are you here at a Git hackathon if you're not a software developer? Turns out that he uses Git alongside his team of people who are software developers and he had heard that the documentation was really bad. So he wanted to help improve it. So that's literally what he, Jeff, was ecstatic. He said, I have someone who's going to sit here for eight hours and just fix documentation. Oh, my God, this is amazing. So that was a lot of fun. So that was successful. And so as a result, we've done more.  I think we're up to eight or nine of them now. It has expanded to not just Bloomberg employees, but also, of course, if the, every one of these big open source projects has a local community. So we broadcast it out to the local community. They come along and help if you like. And importantly for us, but also to kind of help the next generation of open source software developers. In every one of the big cities where we have an office, we also, of course, recruit at nearby colleges and universities. And so now we reach out to the student groups of those universities and say, hey, we're going to have this event. And so we do a lot of things. Great, that works out well for us. So that covers motivations. It's fun. It gets more people involved in open source projects that they may have been users of, but never contributed to before. So now this is where it gets really fun. But all of us that are in this room that do community things realize that sometimes the pretty pictures are just that. That's not exactly. I mean, the people who organize this room know it looks easy. We look, I can stand here, and it looks great. And I always spent two months making sure that this came out right. Well, same thing is true here. There's a lot of work that goes into these. Easy things, right? We need to find a place to do it. The place has to be friendly for people to get to on the weekend, by the way, which is not always the case, like in our own offices. We can't do it on a Sunday because Sundays are days that we can't use the building. We've got to give them beverages. We have actually had cases of Red Bull at these events before, so it depends on what people want. And then, of course, we have to get the word out that the event is happening. Well, internally inside the company, that's trivial. We already have mailing lists and blogs and all kinds of other stuff. We can let everybody know. Plus, people who are interested in volunteering, they watch the Voluntary Event announcements. So when we announce an event, great. Okay, that's easy stuff. First of all, you've got to find when. When are you going to do this? Well, you know, people are involved in going to conferences like FOSDEM and they are often holidays and all kinds of things. There's religious holidays and government holidays and all these other kinds of things. Finding a date is challenging.  They need mentors. They need to know how to get started. If they go to the issue tracker and find an issue, they're going to need someone to say, it's probably in this file. There are 180,000 files in the source tree or whatever the number is. It's not that big. But it's probably here. Let me give you a start. So we have to find people who can do that. Sometimes it's our own people who are already contributors to that project. But most often it's people from the project itself. Well, most of those people have jobs, right? They have families. They have schedules. They get them all in one place at the same time as one of the challenges to do this. It's not huge because, of course, we pay for all their travel and we pay for lodging and it's fun and we go to a nice dinner at a nice restaurant and all that. So they're kind of motivated to want to do this if they can. So external advertising, and this kind of ties slightly into Brian's talk, is amazingly difficult sometimes. Many open source projects don't actually have a good place to advertise events that the community of that project needs to know about. So in some cases we literally have to advertise over and over and over again in order for people to actually learn about it. Whereas in other cases, they have a page on their website that's just full of community events. It's a community event calendar and all we have to do is get listed there and then everybody sees it. So if you are involved in open source projects that have community events, please have a central place that's incredibly useful. All right, you saw there was easy stuff. You saw there was moderate stuff. You know what's coming next, right? There's hard stuff. There's always hard stuff. So the first one, how do we pick which projects we're going to do? Well, the first one we did was kind of a fluke. We obviously used Git. We had people already contributing to Git. We already knew the developers of Git and so it was fairly easy to say, just get started. I could just ask Jeff, or one of our people, can just ask Jeff, he'll come, it'll be great. Then it was a success and we had to do more. Great. So how are we going to decide what the next things to do are? Well, we know we have some criteria, right? First, the project has to be run by a charity. Otherwise, it's not going to count as volunteer hours. So that rules out a bunch of projects that are either run by either independent, they're just literally a project on GitHub and there is no legal entity behind them at all, which is a lot of things. In fact, a lot of really big important things are that way. It also rules out projects that are run by non-charity but still non-profit organizations. Even though we all use that software every day, I can't use them as volunteers. Work because they're not charities. But here's the bigger thing. I have to pick projects that my developers are going to want to be motivated to come participate in and that they're going to be successful at participating in. And you wouldn't think that that would be really hard except we do surveys, send out a survey, say, okay, we're thinking about doing two or four or more of these in the next two years. Give us the names of projects that you think you would like us to do these for. So we get them all back and we put them all on a spreadsheet and we do a ranking and everything else. And what are the languages that the things that are on the top of the list are written in? Haskell, Scala, Erlang, all these... Our developers don't write any of these languages. So you can imagine that if I was to say, hey, let's do an event for Apache Spark. Apache Spark is really popular and we use it in it. So Apache Software Foundation, which is great. None of our developers know Scala. How are they possibly going to be productive in one day or two days with something in Scala? So that's the, you know, do what you're good at, not what's shiny, right? That means we have to pick things in our case that are primarily in C, C++, JavaScript, and Python. Some Java, but those four really are big things. The second thing, and any of you who've done this kind of thing before won't be surprised, you can communicate upfront as much as you can to tell people you're going to need the source code checked out on your laptop. You're going to need all the dependencies installed. You're going to need to make sure that it builds and all the tests pass. That won't be true. That absolutely will not be true. More than half the people that arrive, are prepared. At the second time we did one of these, one person literally spent all day, Saturday, just getting the software to build on their laptop. Now that's okay for them, I guess they learned, but it didn't actually help the community really in any way. They did not then go on to become a prolific contributor to the project, right? So we said, alright, we have to find a way to make this better. We've tried a bunch of different things, and I'm going to tell you what we've settled on now. We've tried giving people pre-built virtual machine images, thinking that would be better. Do they get virtual box or VMware or parallels installed on their laptop before the event? No. Okay, that didn't help. So what we have now settled on, and this is what Kyle Kingsbury from the Jepsen Project helped with, is we just give them cloud machines. We sit down with the mentors a month or two in advance and say, point us to the documentation that shows how someone builds your software, and if you don't have any, guess what, we're going to have to work on some because we need to know. We go build a machine image. We happen to use Amazon Web Services, but of course this would work in Azure, GCE, or anywhere else. And we get literally everything working, every dependency installed, every package config file in the right place, everything builds, all the tests run great. Now we have a machine image. What we have beyond that is a set of cloud formation scripts and other things that say, okay, I have 100 people coming to this event. I'm going to launch 100 instances of this virtual machine. They're going to be, of course, in the virtual private cloud, so they're safe and all that kind of stuff. And they're all going to have shell in a box installed on them, and they're all going to have credentials. So what do you need to be able to log into this machine? A web browser. That's it. If you literally want to work from a tablet without a keyboard, you still can get off you go. So at the end I'll have a link to GitHub where that stuff all lives, if you're interested in that kind of stuff. And it's been incredible use. And obviously that costs money, but in the end it's another donation for us, to making the project better. Then the biggest thing that you really have to rely on the mentors for is how do you find a list of things that are issues that newbies can work on? Many projects already have this. They already do labeling or categorization on their issue tracker and you can just they'll call them sprint friendly or hackathon or some other kind of thing. And so they just have to literally go gather that list. When we talk to the Git people, for those of you who've worked in the Git community, issues are reported as posts on a mailing list. So someone literally had to go through the mailing list and find enough issues for us to make this work. For other projects, like when we did Eclipse literally it took Mike like five minutes. He just went to the bug director and said how many do you want? There's at least a thousand. So how many do you want? So that is something you'll have to focus on because you need the people who sit down and log into that virtual machine you give them to be able to have something they can tackle right away and you want the goal to be something that they can finish in at least two days if it's a two day event. It's not in one day if it's a one day event. And then follow up. We have actually had some mentor teams who were really, really good at this who actually tracked all of the patches that got produced during the weekend and what happened to all of them, which is amazingly powerful. All right. So what do we get out of this? Number one, we get lots of patches. We've probably produced something like three or four hundred across all of these events. We have had some where the mentors were actually the committers for a particular section of the project. So someone would say hey I think I got this fixed and they would come over and say hey it looks like that's probably right, let me show you how to create a pull request so they go create a pull request and an hour later it's merged in master in that project. For someone who's never contributed to an open source project before to come in at ten o'clock in the morning on Saturday and at three o'clock your patch just got merged into the master branch that is really powerful. It's really, really powerful. So you've got to get the right people there to make that happen. We've never met each other before. They learn hey you like that stuff too cool now we can meet at lunch and stuff like that. Networking with people outside. We now have people from the git community and the prole community and the python community and all these other communities who know that there are these really smart people at Bloomberg who also work on the same software. And then of course for us engaging with students is important because number one it helps get them involved in open source and number two it helps us hire people and get internships so that's good for us too. To wrap up you should do this. Find a way to do this. Use whatever resources you can get out of your company. If you don't have an organized philanthropy team but at least your company does volunteer work and has some way to organize things that way leverage that. This is not super expensive. I think generally we spend let's say on average around $15,000 to do one of these events. And that includes travel for the mentors hotel rooms and food and all of that kind of stuff. These are not super expensive things to do. So you can reach me any of these ways that link there of course is the one I mentioned. It's full of scripts and documentation and things for how to launch clusters to do this kind of stuff. One thing I will warn you because it is shell in a box enabled virtual machines with usernames and passwords that you can hand down on a slip of paper so someone can log in. It is about the least secure thing you could have route with no password. So there of course is a tool in the repository to destroy the whole thing. So as soon as you're done, as everybody's done you say you got patches on that virtual machine we gave you, get them off by Monday morning because Monday at noon I'm killing them all so it's really useful for that. And with that I don't know how much time we have you left but I'm happy to take a few questions and go from there. Okay great, yes sir. So the question was about basically does this produce long-term results in our engineering team? It does actually. So we've had a number of people who have come to multiple events. We have people who this encouraged them to come to events for software that they weren't sure they could contribute to. So for example the Perl event we had a big room, big round tables and we had, I don't remember, four or five mentors and each of them had a particular focus area so I'm going to take that table and at that table we're going to work on this and one of those tables was Perl 6 we didn't have anybody who'd used Perl 6 for anything there's probably nobody in this room who's used Perl 6 for anything but people said you know what let me go give it a try and so five or six other developers all walked over the table and sat down and within an hour they were writing unit tests which was really great it has also resulted in people doing that project and I think part of that is you get over that scariness hurdle of can I do this and will they like my patches but also you now have a face to put to that person who's reviewing patches on the issue tracker or on the mailing list or whatever else and it becomes friendlier even though they might still you tell you that your patches are terrible your initial reaction is not going to be man that person just hates me so yeah organizing events is business involved in how do they look at focus? so I'm actually part of the business I work in the chief technology officer's office and so this is all supported by that initiative and yes we are very heavily open source friendly we use tons of it we contribute a lot of it so at least in our company this is just one piece of a big strategy just more merge yes we got one more? okay yes


You thought I lost! DragonFist! I'm not out yet! I'm taking something back home! How's it going everybody? Datoi here and I did not think I would be coming back to Dragon Ball Legends this soon, but the second half of the third year anniversary has revealed one of the best unit to ever come out in the game and visually I'll just go ahead and say this now. This is single-handedly the best unit in the game. That's right, there is an all-new Super Saiyan 2 Gohan from the Bojack movie along with of course a new Bojack and a Trunks from that very same movie. The animations on display here are really hard to put into words so I'll just put a few on screen now, but this LF where Gohan passes out is, this is too good looking there. In fact, all of them look really good. Bojack has this awakening that looks amazing as well. Obviously we want the Gohan a little more but hopefully we can get him as well and then Trunks is just crazy.  But yeah, those are really the main units we'll be trying to get today. Hopefully we can get our hands on at least one of them. Gohan, I'm speaking to you, but really all three would be nice. And of course, if you want to see more Dragon Ball Legends on the channel, definitely let me know down below by either liking the video or leaving a comment just letting me know. But that is enough of that. We are going to hop into step number one here of Bojack Unbound the Banner and you know what? You know, usually I keep the scripts of these videos to myself. These videos are scripted. I don't remember if I started the last video like this either, but I'm just going to go ahead and pull all the units on the first 500 step and we'll start it off by going Super Saiyan. That's how you know. I'm not telling a lie. Let me dodge step back a little. Ooh, I don't like that blue text. Ooh, I don't. I don't. Ooh, I don't. I can't say I'm enjoying what I'm seeing right now. Maybe. Oh, yeah, we're not getting anything. Are we maybe a new extreme unit? Like we mentioned, there are new extreme units that are also sick to pull. Oh, hey, see, you know what? I'll take it. Go cool. That's pretty good. And maybe we get backed up. No, that is a really old one. But hey, not bad. If we're going to get trash, we might as well get the decorative trash. You know that good like go cool. Right. Is he just going to keep showing up? There's other new extreme units, bro. That was it. It was all for Gokua. Man, popped up twice left. Didn't even say anything else showed up. Popped up twice left the room. Absolute Gokua move, honestly, but we did get a ticket and we do get to go into that next step. Man, we do not have a lot of crystals. Watching other people summon on this game is like, bro, you got a lot of crystals. I'm kind of jealous. Meanwhile, I'm working with what I got here. Oh, I didn't even transform. Go cool. Just flexing, I assume. No, this man really just does not have any strength left. Oh, no, don't. Don't do it again. It can't quite possibly be trashed twice. All right, all we have to hope for is a fake out. We literally have to hope the game's pulling a prank on us at this point. Two heroes, hero, a thousand, not even a member of the right clan. Napa, maybe a new extreme. No, that's that's an old one. Isn't it? I don't know. I don't even know if that that one's on the if that one's going on the team. I don't know if there's a new one of that. Oh, no, even when the extreme pops up, I have to get a little bit hyped. Oh, oh, and it hurts. It hurts. That one was pain. That one was a lot of pain. But hey, if that zombie does have to go on the team, you know, six stars. Oh, I'm saying is not too bad.  But another ticket acquired and step three is guaranteed EX or higher. So really, if you're going to get any of those new exes, this is the step to do it on. But, um, yeah, I mainly want all clear skies. Broly. Hey, Broly, if you could hear me, I need some help with Frieza. Hey, Frieza, shot your dad, bro. Loki. Yeah, I'm team. I'm snitching. I'm snitching. Broly. Oh, it would have been hype. It would have been hype. I don't know if it would have guaranteed go on, but the Super Saiyan 2 go on guarantee would have been nice new extreme. Like we said, oh my God, that guy is not the Broly. I was called. Wait, wait, no, no, no, don't do that's not the right go on. Oh, you could actually hear the sound of my heart breaking. You could actually hear the sound of my heart breaking there. Oh God. Oh, oh, oh, no, it's a cooler movie. Dude, I love the cooler movie. Love getting that cooler movie. Goku could not be happier. Can we get one of the new extremes at least any of the new extremes would be cool. It's a it's a whiff. It's a way. It's another whiff step. Oh God, how long is this something going to go on for? Okay. No, it's over. It started with that Broly that we didn't mean to call for. And then that future Gohan. Oh my God. Did we at least get that hybrid Saiyan ability though? Because that would be quite nice. Because if we do pull the go on hybrid Saiyan, there we go. All right, nice. Now we can run that guy with the Gohan if we ever pull him. I don't really have a good team for Gohan. I don't know if I mentioned that in the intro. Truth is this is a flex pull, dude. I am trying to flex by getting this go on. He would not. I would not do very good with it. This is step four run, right? Step four with clear green skies. Namek has never had a better looking day. Me and Frieza just doing it. Just doing this because honestly, it's all we know at this point. I'm getting met. Oh, no way, dude. What is this? Is this? I don't even know what this animation is. We got beat up and then a little bit of text. It pretty much just an extreme hero Roshi. We see hero Gohan. Oh, no, no, no, no. Chow Tzu, Chow Tzu pointing at possibly a new. I'm going to start. I'm going to stop bringing that up that they could be new extremes because on my game, it must be bugged. It's all Jase. It's all Jase. Somebody hacked into the code. They gave me all Jase. Oops. All Jase. Oh, no, not even a better. Oh, my gosh. Oh, gosh. Is this what this banner has been like for other people down below in the comments? Is this what I'm supposed to be feeling? I thought I was born lucky. Where's my luck stat? Oh, come on. The last banner didn't go too good for me, but this one. Come on. Step five, step five. I'm feeling alive. I was born lucky. Dude, hold on. Let me crank the luck stats up to max. There we go. Luck stats maxed out. Why is the why is Namek's doing so well? There's got to be a bit of rain every now and again. Namek could be destroyed once or twice. Oh, blue text. What is happening? Can I get a refund? Where's my free refill? Hero Napa. Oh, is this the all hero? Is this the legendary all heroes up? No. No, it can't. It can't possibly be true. There's no way. Oh, oh my goodness. Oh, we came very close to the all hero summon. That would have been damning for the confidence. Oh my God. Oh, if it wasn't for Broly, my game would have automatically deleted itself. Imagine you get an all hero. Some of the game automatically deletes itself. It might as well. Braids basically telling you to kick rocks. Bro, there's a truck. Hold on. Hold on. Maybe I got to converse with the units because let me I just have to reiterate this whole banner is good. This Gohan would be amazing, but there's also I mean, come on. Look, the Gohan. Yes, give me Gohan, but also I'll take the Bojack, but also I'll take the Bojack Trunks. I mean, when this guy fought TN, that was pretty much the highlight of the movie. Dude, look at this artwork. By the way, my guy is ripped, but yet any of these three would be good or any of the new extreme. Hold on. Let me I need to peep that banner again. Let me go back. Oh, it was this guy. Dude, stop. Where's the extreme units? Oh, here. Here they are. The extreme. I was right. There is a new Zangia and there's go cool. We got him Bito and Boozian. Oh, come on. We haven't even seen it. The banner doesn't exist. All we got was future Gohan. It's rigged against us, but you know what? I think step two is going to bring brighter fields. Dude, I'm getting all three on this one. Where'd this confidence come from? Even I don't know this loading screen. Got me acting different. Oh, Nimbus. That means featured unit. No matter what, I'm going to be happy at least because maybe we'll get a new extreme, but maybe we'll also get a better in a minute. No, no, there's no way. There's no way. It's going to just be one of the new extremes. Oh God, it's going to be one of the new extreme. Oh, I'm dying help. Somebody help.  Vegeta, help me. Thank you. I appreciate it. All right. That means sparking is going to be in here. Does that mean where does that mean we're going to get a go? You want to give me go on? Don't you legends? Okay. I'll play along. I'll play. Beato. We got one of the new gang members. All right. There's Goku. Oh, that is not the right trunks. That is not the correct trunks. Oh, wait. Nope. There is this better. I was wondering when we were going to get extreme murder with all the Jesus lying around. All right. I think that was it for this summit. If we're being honest. Yeah, I got a bad feeling about this one gang. Oh, yikes. And that was it. But at least we got one of the newest extreme units. That's what Nimbus was for, by the way, is for Beato. Let's at least take a look at him. All right. So we have two out of the four necessary extreme units. We have zero of the necessary sparking units and we're on our last step without the tickets. Oh God. I'm scared to click the button. I did it. I clicked the button. I did it. I clicked the button. I did it. I did it. I truthfully did it. Oh, Nimbus and Nimbus destroyed. Super Saiyan. This is good. All of this is good. Nimbus means featured. So we're getting something from the banner. All of the other stuff means it might be something good. Oh, good text. I'm liking the color of the text. Frieza, die. Just die, Frieza. No, cut through the smoke. No, no, no, no, no, no, no, no, no, no, no, no, no. And I'm scared. Now I'm scared. That's not the right Bojack. We're going to have to run a full extreme team. No, what's happening? Oh, no, it was just for the extremes. Wasn't it? Oh, no. Where's the new extreme at least? There it is. That's what Nimbus was for. That means we're not getting anything else. Oh, no. Oh, no, it's going to come down to the tickets. It's going to come down to the tickets. Or am I going to double down and get back in there? I don't know. I think we just have to. Oh, I'm going to let's do the tickets. Even if this isn't the end of the video, we got to do the tickets. Where's the ticket banner? I'm lost. Where is it? Oh, there it is. We only have one ticket. Yeah, they're going to make me do it again, bro. They're going to force me to do it again for the second ticket. I should have expected it. Broly, if you want to show up. Oh, Broly featured unit Broly. Broly loves this place. This is go on. Oh my God. Is it go on? I'm sweating. Go on. Hear my calls. Broly. Oh, where's Broly? Oh, no. That's not good. Wease. Oh, cut through the smoke. You thought I lost Dragon Fist. I'm not out yet. I'm taking something back home with me. And it's Super Saiyan 2. Go on. I'm Super Saiyan 2. But he transforms. Oh my God. In the final hour. Oh, you could hear. Oh my God. I knew it was go on. You could just feel the raw power. I told you I would get him in the crystals I had. Hold on. Go on. Unleash your power for me. Let me see the all. Oh, you could pray. Oh, you can hear the lightning effects. The charging. Listen to them. Oh my goodness. All right. I know a lot of you have asked for PDP in the past. So I decided I'd throw this on here. Like I said in the video though. Hopefully you watched it. I said I don't have a hybrid Saiyan team. This is going to be bad.  This is just purely a flex. Obviously we're really low in PVP. So hopefully it doesn't matter. That's my hope. Oh God. Also, I don't Zenkai units. I should bring that up. I don't Zenkai units. I don't like the Zenkai system. That's why my red Gohan. Also, I don't have enough stars on him. But yeah, he wouldn't be Zenkai anyway. I'm going to try to go for the LF. We're very low in the rankings. That's the only way this team is going to get any wins. Oh, dude, I just okay. We might even be going up against a bot. I know. But that's not the point. We're going to see these animations. All right. It is time. We have go on out of the board, but not the correct one. And I already want to switch out and that is going to say switch out and die. That sounds very grim. But you know what? Let's just switch out. It's time. Let little Gohan take it for a spin. This guy is just not taking any damage. Huh? Hold on. Let me hit him with a little bit of it. All right. There's where we see the damage from. All right. Give me that. Hold on. I'm going to dodge this. Let's see if he steps back. I don't know if this is an actual player. Oh, no, I didn't mean to tap up shallow. Please. It's fine. I actually want to take damage. You know what? I'm going down with the ship, dude. This guy's evolve it. Oh my goodness. This is probably a body is not doing much damage. But even so, we still got to take the hits.  Oh my God. I would have to play so much PvP to actually. I'm just going to rush. He looked mad though. I'd have to play so much PvP to have PvP actually be watchable. Hold on. Piece him up. Yeah. You didn't guess it. Oh, the Gohan team, the Gohan trio getting shallowed out of here. Probably a ways to use rush on shallow. But we'll get another one. Let me dodge that. Actually legit. All right. Do what you got to do, bro. Oh my. All right, relax. Destroy my card. You. Jesus. It's going to take a while for Gohan to die. We're going to have to do some strategic throwing here. Oh wait. We're going to have to do some strategic throwing here chat. Comments. Why do I keep calling you chat? Oh, no. We're going to have to strategically throw. Do we lose this tap battle? Now let me flex on them. Oh, all right. Nice. We're going to have to throw. That's the only way. We have to throw this. Gohan this Goku does revive. It's the it's the hit Goku. Oh, there we go. There we go. Decent damage. All right. Let's get this Goku off his revive. That way we can actually get the LF once we do die. My God overreaction to a key blast. All right. Now we're good to go. All right. Now we're just throwing. Now I'm literally just standing here. Cut to when I die. A few moments later. There we go. There we go. Take me out. Take me out. Here we go. Here we go. Claped in front of me. Father. Oh, look at this animation. Let's go. The powers pulsating. All right. Please don't die to this. I'm going for it, dude. I'm going for it all. LF coming up. Come here. I ain't done with you yet. Strategic throwing against the bot. We had to die. We had to strategically throw. Damn, that is sick. Well, that is going to be the video. Hopefully you enjoyed it. I know obviously the PVP wasn't intense or anything like that. I don't think we could have gotten anything intense with this team, but it definitely was fun to see those animations in action. And I guess I'll try to get up in the PVP ranks with a different team. Definitely not. Definitely not this one. But that said, I have been Dr. Doyle. Hopefully you enjoyed the video. If you did, definitely let me know down below by liking or leaving a comment and check out some of the other videos that should be on your screen right now. Other than that, I've been Dr. Doyle once again. Hope you enjoyed the video and I will see you in the next one.


What's going on guys, it's your boy DPJ here today with another Destiny video and today I bring you my challenge of the Elders Luting Results across all three of my characters for the past week. Now before we go any further let me know down below in that comment section if you guys received anything you wanted or needed. Also just let me know what you got but let's just get straight into the video and starting on my Hunter and from the 30k package I received the Lethal Norbucy. Now I think that's a pronounced that first word I ain't got a clue. This is the Queen's Scout rifle and from the 90k package I received the Warden sight which is epic. Now the Lethal Norbucy dropping at a 335 this is the Queen's Scout obviously.  The Warden sight is the helmet. This dropping is absolutely epic as my current helmet is only a 332 defense on my Hunter which is crazy I know. This one dropping at a 335 so I'm super happy with it I really am. Moving on to my Titan and from the 30k package I received the Final Duty Porsche Rifle dropping at a 335 ATK. Mud's wear, life support and spray and play so roll could have been a lot better. So I think this one will just end up being infused. From the 90k package I received the Witness Gauntlet. These dropping at a 335 defense offering discipline and strength. Mud's wear increased grenade throw distance and increased reload speed with scout rifles. Now moving on to my Warlock and from the 30k package I received the Final Duty Porsche Rifle again and from the 90k package I received the Keeper's Gloves. The Porsche Rifle dropping at a 334 ATK and offering partial refund and feeding frenzy. This again is not the worst roll but could have been a lot better. The Gauntlet struck at a 335 defense offering intellect and discipline. Mud's wear increased grenade throw distance and increased reload speed with shotguns and that is it people that is a loot I received across all three of my characters from this week's challenge of the Elders. Not a bad week at all finally got a 335 helmet on my Hunter who is now only one item of that 335 light level and that's the artifact which I can get from numerous places. So my Hunter should now be my first 335 character saying that though both my Warlock and Titan are one item off a 335 so this next week now I should be a 335 and all three characters and what I do from then on I have no idea we just have to wait and see but guys hope you enjoyed the video do drop a like would I appreciate that support I really do. Thanks for stopping by as always and I'll catch you guys on that next one. Peace out until next time. POST! Always and the wrong Knowing where we stand Never get around


Hi, my name is Todd Bacastau. Welcome to lesson three, lecture two of geospatial intelligence and geospatial revolution. This lecture, we're going to talk about joint data sources. Joint data are collected both openly and covertly. Covertly is secretly, and we'll talk a little bit more about that. Data collected covertly can be considered closed source, and that's the term we'll use throughout this. Some intelligence collection must remain covert or secret, as their disclosure could jeopardize the individuals involved with the collection. Maybe the technical means of collection or the subject that's being collected about. Open source data or information that is widely available may be incomplete or inaccurate and may require another source like closed source data to complete the picture. So they really do work together, the great synergism between them. Open source information and open source software are not the same thing. These are terms that are often confused in particular within the intelligence community. Open source software is computer code available with a license in which the copyright holder provides the rights to study, change, or redistribute the software. Open source information is any type of information that is lawfully and ethically gathered about something. It typically comes from publicly available sources. Let's examine the term publicly available in a little more detail. Publicly available sources are data facts, instructions, other material published or broadcast for public consumption. They are available on request to members of the general public. They can be lawfully seen or heard by any casual observer. It can also be made available at a public meeting. Social media is a great source for open source information. Social media of those websites and applications enable users to create and share information. Examples are Facebook, YouTube, and Twitter. A world of information, a wealth of information can be found at those sites, but there's many others. Social media is helpful to intelligence agencies to moderate world crisis and even track terrorist groups. It can be used to look at trends. It can be used to signify warning signs potential national crises are happening. Social media postings can also define geographic areas of an event. One of the attractions of open source information is the perception that it's easily collected with no accountability. This is incorrect. In some areas of the world, information must be collected for a legitimate purpose and need. Some European countries have incorporated the European Convention of Human Rights into their legislation. Under the convention, a search that engages private life issues must meet a threshold. The intent is to protect private life of the individuals against arbitrary interference by public authorities and private organizations such as the media. Competitive intelligence or CI refers to the legal and ethical collection, analysis, and dissemination of information about business products, markets, pricing, and plans. Competitive intelligence or CI is information that has been legally found and analyzed. It does not involve industrial research or commercial spying. Closed source data can be available from both government and private sources. In simple terms, it is closed source data if the data is not meant to be opened publicly. Closed source data because of its origin are often considered more accurately reliable. It may or may not be true, though. Closed source typically includes materials such as government classified information, proprietary business information, law enforcement data, educational records, banking records, and medical records. In general, closed source data are obtained and distributed from sources that are marked do not make this information available to the public. Government classified information is guarded with such markings. It is marked with a security, something like classified, secret, etc. Typically put on by the source of the information. Proprietary is a term used by business. It is closed source information that is often used interchangeably with the term trade secret. Examples of proprietary information include manufacturing information, marketing information, financial data, and research and development information. Generally, data is termed proprietary by the owner so they can limit who can view it and see the contents. There are some interesting circumstances that happen, though, between the open and closed source worlds. Take, for example, an open source system, potentially a satellite that is flying over a car factory and using that imagery to count the cars coming off a production line. So this is covered by the open skies doctrine that the U.S. tends to follow. There is no standard used by business for determining what is proprietary. The nature of what is held proprietary varies from industry and individual business practice. If the information is not seen to be readily available, it should be considered proprietary and not for public use. Thank you for viewing this lesson. This lesson we discussed in need for intelligence requirements process, the high level data collection strategies and sources, and the advantages and disadvantages of the sources. Thank you very much. I look forward to seeing you in lesson 4.


It's LinkedIn learning author Monica Wahee with today's data science makeover. Watch while Monica Wahee demonstrates how to create a matrix in R and then coerce it into a data frame. Hi everyone today I'm going to show you how to make a matrix from scratch. Remember what a matrix is? It's an object in R. One of the tabular objects R has. Honestly, I don't like matrices much. Personally when I have a matrix I always convert it to a data frame. So here's the code we are going to run to make the matrix. We see a word and then an arrow. This means we are making something. Obviously we are making a matrix. In this case the matrix is going to be called zero underscore matrix. And you will see why in a moment. So here we are with the matrix command. And we are going to get into an argument. Actually three arguments. So the first argument, well I'm kind of cheating with the first argument. This says what to put in the middle of the matrix. I'm just demonstrating what to do. So I put a zero. That means in each cell meaning each intersection of a column and a row in the matrix, R is going to put a zero. I say I'm cheating because usually this part is more complicated. But I just want a zero for demonstration purposes. Our second argument is n row equals three. That means we want three rows. I just pick that number. And our last argument is n call equals five. I think we want five columns. So if we get what we want we will run this and get a matrix that's three rows long, five columns wide and filled with zeros. Let's see what happens. Okay now let's run our new matrix. See that in the console? Great. Perfect. Looking good so far. But remember how I don't like anything but data frames? This is a matrix, not a data frame. I'll prove it to you by running this class command on this zero underscore matrix. If you want more information on the class command, look in the description. I linked to a video. See over here? It says matrix. We thought it would do that. But I wanted to be a data frame since as you know, I prefer data frames. I can coerce it to be a data frame by using this code. See this code? I'm using the as dot data dot frame command as data frame. I'm converting the matrix into a data frame named zero underscore df. See how the as data frame is spelled as dot data dot frame? And it has one argument and that's the matrix, our zero underscore matrix. So let's run this and see if we are successful in forcing this zero underscore matrix into a data frame format. Well it ran. To make sure it did what we think it did, let's run this class command below it here. This is to see if the class of zero underscore df is really a data frame. So I'm going to run it. There, see it in the console? Zero underscore df is indeed a data frame. So you know I'm partial to data frames. But often I'm building a data frame. Like an analytic data set that I'm going to analyze. On the way I often need to add different things. Like for example a bunch of columns that have zeros in them which I will update later with code. Two state flags. What I showed you here is one of my tricks. Making a matrix then converting it to a data frame. Then I can patch it onto some other data frame I'm building. And then when I'm done that clumsy awkward matrix is a gorgeous data frame. And now that you've had your data science makeover, you have a gorgeous day. Thank you for watching this data science makeover with LinkedIn Learning author Monica Wahee. Remember to check out Monica's data science courses on LinkedIn Learning. Click on the link in the description.