Hi, I'm Monica. I'm that person with the cat. I'm not Weldorf on Twitter and GitHub and internet places. And I've been on the Polymer team for about two years. You may have seen me meowing about web components a lot. But I started right before Polymer 1 was shipped. This was exciting because back then, I thought web components were really cool, but nobody really knew about them. I would go to conferences and be like, I work on web components. And people would be like, I don't know what that is. Is it an iFrame? No, it isn't. And I really liked doing that because I sort of became this like traveling saleswoman door to door selling web components and be like, let me tell you how web components are right for you. And I'm glad I did that because talking to people, I sort of formed a story about the kind of teams that web components were good for and the kind of people that enjoyed using web components. And that story starts with like the world around us. The world around us is built by people like you and me and sometimes we're crafters and sometimes we're assemblers.  You didn't go into the forest, cut down a tree, sanded it down, cut into slabs, took some screws, made a table out of it, and we're like, I crafted this out of this chair. You didn't do that. Even if you use something like IKEA, you didn't really craft that table. You assembled it.  You took things that other people did and you made them and you glued them together and you made a thing out of it. The same thing happens if you cook. When you make a meal, you take all these ingredients and you mix them together. You don't farm your own tomatoes and corn and churn your own butter and grind your own spices. And this is very good that you don't do this because assembling is faster and it's more efficient and more performant and more accessible. I have no idea how to farm my own tomatoes. I know that because I have a plant. It's in my patio. It makes one tomato every month. I would die of starvation if that was my only tomato. And as a society, assembling is really fast for us. It was the whole point of the industrial resolution, got revolution to move from everybody crafting a lot and doing a lot of manual work and sort of assembling more and making it faster and more oriented. And the thing is the exact same truth for the web. The web is kind of like a society, but on the web, we tend to be more crafting than assembling and that's a little bit weird because that means we're not gonna progress as a society if we don't learn from societies we already have. And the reason why I like this crafters and assemblers metaphor is that web components sit really nicely as a bridge in between these two. If you think about somebody who makes components or elements, they have a lot of institutional knowledge about what makes that element good and all the heavy lifting that you need for that element. Something like paper dialogue requires a lot of really weird knowledge about animations in the CSS spec and what a stacking context is and how you can't just produce one from thin air every time you want that. But on the other hand, while somebody has made you a web component, this enables people to just pick it up and use it and form a really nice experience with it. I can use anybody's custom element, I don't need to know how it works. And that's really great because if you take my metaphor from before, this is great, it's advancing the web society as a whole, it's faster to make things and it's more efficient. The CDO of ING said this at last year's Polymer Summit and I really loved it and it stuck with me and he said that what he wants to see in the world is less crafting and more assembling, less people doing things by hand. You shouldn't have to know how to build a table from scratch to have a really nice living room. You shouldn't have to know what a CSS stacking context is to just have a modal dialogue that tells somebody there's a sale on your website. And this is true of every other industry, but it's not exactly true for the web. Like in the real world, I can be a crafter if I want to, I can be an assembler if I want to, I get to choose, I don't have to be both at once, but a lot on the web we have to both craft and assemble at the same time. And that isn't really great. And all of this comes together in design systems. So before web components, when I say design system, I mean like the elements with the elements library, the things that your brand should look like, like the colors and the padding and the margins and the visual elements that an app can use. And before web components, having a design system was very craft oriented. If you look at something like Bootstrap, which is amazing, but Bootstrap was like somebody crafted you this enormous CSS file that had all these styles and it was great, but even putting the elements in your page was a little bit handheldy. For example, this is a brand nav bar that you could have in your application. I took this from the Bootstrap site. But imagine that at some point your brand changes. Maybe you need to have like that container fluid class needs to go away. What do you do then? You have to literally go in all of this dummy produce and start deleting code or adding code. And that doesn't feel a lot like assembling to me. And of course we know this, web components came and they fixed this because now we have a custom element that abstracts all of this like garbage that we don't actually care about that somebody else built for us because the only thing you care about in this element is just that image. So that's good. But the thing is this story only works if we have tools around this. The story only works if, you know, like Bootstrap we have a catalog of elements. We know as a developer, like all of these things that are available to me and that I don't have to reinvent them from scratch that somebody already made, you know, the perfect kind of blue button that I'm allowed to use. So we made webcomponents.org which, you know, we're very well. It's a public catalog of web components and everybody can upload their components and it's got demos and it's got docs and the world was good and we're happy. Only we weren't super happy because it turns out that didn't work for everyone. There's a lot of companies like EA, like Comcast that are really sold into web components and use web components a lot but their web components aren't public. They can't use webcomponents.org because they can't publish their elements. They develop them internally. So as a result, every one of these companies basically built their own catalog. They could have forked webcomponents.org but webcomponents.org solves a different problem which is how do we let people upload arbitrary components and that isn't the problem that companies with private elements have. They just want to display this fairly limited set of elements they have. And the problem here is that there's no such thing as a one-size-fits-all. Steve told you this this morning when he was talking about elements and it's true for apps and solutions. At best you have something that works in the 80% case. 80% of developers probably want to upload a public web component. But in the 20% case, it's all edgy and weird and you have to do something different and it's usually a more simpler and assemblier solution. So in this case, I build in the elements catalog which it's fairly ugly, it's not amazing but it's also a very specific problem. You have a JSON file and in it you specify what kind of elements you want to load docs and demos for. And these can be Polymer 1 elements or Polymer 2 elements or just vanilla custom elements. They can be anything you want and the code is there for you to do this. And if this doesn't work for you, which is fine, you can fork it, you can clone it, you can fix it to make it work with your workflow and then it's good. And the world was good again. Well, it really wasn't. We again solved another 80% of a bigger problem and left 20% off. It's really great that now your developers know what elements are available for them but they also need to know how they fit together because in an organization with real workflows and real people, you need to be able to validate your prototypes against code that you actually have, not code that you think you might have. And most of my examples when I give talks are from Chrome the browser because I used to work on it and I know the developers and the workflows and this is a page from Chrome Settings. And the way the Chrome Settings page gets designed is first, we give it to a designer, Alan Betz. He's a fantastic human being and he designs all of these workflows in Sketch. He calls these sticker sheets because he basically has stickers of all the material elements that he would like to use or is allowed to use according to material design rules. And then he assembles them together and figures out the screens. And for each particular screen, he does a whole bunch of iterations. Should the bottom be on the left? Should it be on the right? Should the text be centered?  But the thing is, real elements have bugs and have problems, they have implementation limitations. And I know this because I wrote those elements so a lot of the times Alan would be like, this toggle button needs to be 16 pixels and the developer will be, it only works at 18 pixels because Monica didn't make it a resizable. Which is annoying because this means that the prototype that somebody made cannot actually be implemented.  You hope that the prototype that you get from the designer, you actually get to see in real life. There's no guarantee about it and it's nobody's fault that there's no guarantee, it's just not everything works like it has on paper. Because instead of what you need is a common ground or a tool that is a common ground between developers and designers so they can look at the same elements and improve that workflow. Which is what you see is what you get, a wheezy wig. And something like this has been a long time dream of many of the Polymer team members. We had this in 0.5 and it was called Designer, it was really awesome.   And literally from using that app what you would see is what you would get. But he's always dreaming up really big ideas like the Polymer CLI and Lit HTML which you'll see tomorrow so he's never actually finished this. But lucky for you I have incredibly small ideas and very little patience. So I had two free weeks and basically stole his milkshake and built this other thing. Which is more like a getting started tool. It gives you the ability to create something like a prototype but not a full blown app. It doesn't work super well all the time but it helps you get started because what you do is you deserve Justin's tool but we don't have it yet. So instead you get a WYSIWYD which is like a version of that and I'm gonna show it to you. Maybe, okay. So I really, really, really hate live demos and I'm really, really nervous about it. So hold all of your fingers crossed and toes in. Okay, so this is WYSIWYD. You can, oh, I just got a screen saver. It's going well. Okay, it's in polymerlabs.github.io slash WYSIWYD. The code should be open sourced very soon. It's kind of terrible but you'll live. So here's what the app does. It has a couple of panes and one of the things that it lets you is you can select some elements and drag them in. So I can do something like a div which is a native element. I can resize it. I can move it. I can change some of its styles so I can make a background color. And if you see over here, it has properties. I'm gonna zoom in. So it's got like a class list hidden and title. There's also things like custom elements. So for example, I can find God, a good one. Paper input, paper input is my favorite. And when I add it, paper input has different kinds of properties because we actually crawl the prototype chain so that we look at what properties or attributes your custom element has. So in this case, you can see that I have something like value and labeled and disabled and the pattern and all that goodness that comes with paper input. And you can change them. You can change styles. Flex is just the collection of the flex attributes that you might use. And once you're satisfied with the code that you've been producing, there's a code tab where you actually get the code for this element. It's got two imports, the Polymer element and paper input, which makes sense. Let me zoom in. And then as you scroll, it basically gives you an index.html that has both the element definition and the declaration at once. So we have our app and then the DOM module for that app. And you can see that it's got all the styles like I added a div, I added a paper input and here they are in my template. And then it has the element definition at the bottom. You can also see a live preview of it, which is where we actually render the code because I don't trust that designer pain, so I give you this. And because this code isn't editable, because again, that would be a very complicated app and then I would have to like re-render everything. There's also an option to pop this out into a JS Fiddle where it's a conference Wi-Fi, it's amazing. There it is and it's your paper input and it does all the things. And you can from here on start adding logic or JavaScript or whatever you want. Cool, so let's build a thing. Let's delete all the things first and then build a thing. What I'm going to try to build, again, thoughts and prayers, is a YouTube app where basically I'm gonna bang on a paper input and then get a whole bunch of YouTube videos related to that input. And in particular, they're gonna be related to cats because why not? Let me see how I'm doing for time. Okay, so one of the tabs that I didn't show you over here is the samples tab. And these are basically combinations of elements that I've added because I really don't like rebuilding the same thing over and over again. And again, this is the kind of app that you would be able to clone and fork and take home and you could add your own samples for whatever team you have or your particular workflow. So in this case, I'm going to start with a header sample which is basically an app header with a toolbar in it and it has a div. And over here, I'm gonna rename my div to meow tube and put some emoji in there. You can tell that I've practiced this. Let's put a television too. Sweet. So that's it. And now when I save it, it's there. If I preview it, it's there. If I look at the code, I actually have an app header with all of its attributes, a toolbar, and everything else. Cool. So I have my thing and now I wanna render my results. So in here, I'm going to add a DOM repeat because I'm probably going to get a whole bunch of results. Actually, I need an IronAgeX first because we're gonna need to ask YouTube for this. So in my custom elements, IronAgeX, here it is. And IronAgeX has a bunch of things we need to populate. A URL, for example, which I'm going to paste because nobody can remember this unless you're ziling probably.  So here is things like your API key, your query, which in this case, I'm hard coding to cats. Oh, what do you care about, which is the snippet? Handle as JSON. So this basically tells IronAgeX that whatever it gets back from the server, it should be a JSON. We wanna set auto to true so that the moment we refresh the page, it actually fetches this. These are just attributes that you can get from the IronAgeX documentation. They're not made up or anything. And last response, I wanna populate an object with this. So here, I'm gonna put videos. And what this means is that IronAgeX is going to get an JSON object from the server and then put it in this video's object. This is just a regular Polymer data binding. If you're familiar with data bindings, it's just it. It's exactly how you would write it. Cool. So now I have my IronAgeX, it's set up. And then I'm gonna create my DOM repeat. And this is where everything can go south. So, DOM repeat, here we go. I have it. I'm gonna drag it in. It's hanging out. It doesn't look like anything. I also have a paper card sample, which basically has an image and a link in it. And I'm gonna move it around so that it goes into my DOM repeat. So there's these arrows here because sometimes dragging and dropping is infuriating. So if you don't wanna do that, you can just traverse the tree. Speaking of the tree, here on the left-hand side, I haven't shown you this yet. It's basically all of the elements in your app so that you can see the hierarchy and you can click on them and select them because again, dragging and dropping is infuriating. And I know this because I built this and it was just rage. Okay, we have IronAgeX. It's getting data for us. We have a DOM repeat, which repeats, stamps the same thing over and over again. So it's gonna stamp one of these paper cards for every result that we have. And we need to tell the DOM repeat to take the elements from IronAgeX. So, IronAgeX was populating an object called videos and because I've memorized this demo, I know that videos actually has a sub-object called items. That's the one I care about. So here, videos.items is what I wanted my DOM repeat. Now the DOM repeat is gonna take every single thing in this object and create an item object. So to this paper card, I can now give my item. So, I have an image. The image should be this thing that I'm gonna paste called item.snipit.thumbnails.hi.url. Very memorable. And then for my link, I'm going to change the text content to be, let me zoom in again. Item, ooh, hello. Item.snipit.title. And then for my href, every snippet has a video ID. So it's gonna be item.id.videoid. And now if everything goes well, if I go to the preview, I get nothing, amazing. Something that didn't go well. So let's figure it out. We have our image and we, oh, maybe we don't have data. Let's wait for it for a little bit. Nope. Okay. Pardon me? Oh, way louder and thank you. See, drag and dropping. All right, so let's move this one back and move it into the DOM repeat. Nailed it. Thank you. I'm honestly kind of surprised that worked, I'll be honest. So it looks a little bit terrible because links are, you know, display inline and we don't have an input. So let's do that now that we know our thing that works. So first of all, we're going to change our link to be display inline block so that it's sized correctly. And then because I don't want it to grow so that all my things are still aligned correctly, I can also add extra styles. So the thing that I did in here is that as a lazy developer, I didn't ask, I didn't add every single CSS style to this designer because I'd be crazy. So instead, I give you the option to just add whatever you want. If you add garbage, nothing's gonna happen because the CSS parser is smart. So in this case, I want an overflow auto and then that'll be great. So I have my DOM repeat, I need my input. So let's add a paper input again in here. And then I'll drag it into here and then move it before the DOM repeat. And my paper input is going to have a label and it's gonna say, find your meows. And whenever you type it into an input, it has a value property. So I'm going to save that into a query property. Cool. And now all I have to do is give this query to the IronAgeX. So if we move back to IronAgeX, it used to have this parameters object that you know about. And one of the things in here was cats or the query queue. So I'm just gonna add my query here and still keep the cats because it's a meow tube. We only look at cats. Why would you ever want to look at anything else? Now let's just check the code for a second before we run it.  I just like dragged and dropped it and typed into some text fields. And that was awesome. Now if I look at the preview and I look for a burrito, I get burrito cats. Here is a wet cat. And if I open that video, it should work. And it does. Here's your favorite cats just getting wet and miserable. Ah, that's it. That was my demo. Cool. So this is live. It's polymer labs.github.io slash withewid. If Elliot didn't forget about me, he'll probably switch it to open source now so you can actually check the code and judge me and complain about it later at the party. And I think I have like one more slide to tell you about if we can switch back to the suite. Oh my God, it worked. Never doing a live demo again till tomorrow.  But the best thing about it is because it's open source and because of how I try to build it, you can take it, you can fork it, you can clone it, you can change it and make it work for you. Maybe you need a marketing site assembler where you just build things so that your marketing team can put together, I don't know, pamphlets, whatever marketing does, something awesome that sells and gives you money. Fork this tool and build it into that. Maybe you need a designer where your designers can use four of their UI elements to build things. Please fork it, please build it into that and give it to your team. Maybe you want designers instead of designers instead of designers because why not would you want that? In particular, if your name is Dan Friedman and you get a bigger screen so you can do nine of them inside of each other, best use of designer ever. Wendy said this morning that her dream was to bring web components to every browser and every developer and I think the way we're gonna really do this is to start thinking more about visual tools. It's not all about your CLIs and your web packs and your gulps and whatever other tools you use. Sometimes assembling is really visual and we haven't been really good at building visual tools for visual people. So I hope that this at least proves that there's a value to do this, that it's kind of exciting to build this and to use this and it takes it a little bit closer because we're now a little bit closer to just assembling more things and crafting less. Thank you.


time is flying, we're getting to the end of the current series, or possibly the current series is on 2D game design and so in two or three more weeks when this series as far as I've done is over I need to continue making more videos so this is a chance for my Patreon supporters to vote and again I'm going to give you three options as normal. Option one, continue with 2D game design and we'll just continue what we're doing I might you know we'll probably build some sort of game at this point I just showed you some basics of designing the games but we'll actually probably design a small game at this point if we continue that so that's option one. Option two would be what was it going to be I just went over this I'm tired oh right open source video editing I will go over how to do some basic video editing and video editing concepts and I'll go over both in Kaden Live which is my video editor of choice and also in Blender so Blender will be a good option if you're not running Linux since Kaden Live last I checked does not support other operating systems although there's no reason that it couldn't be ported at some point because it uses MLT in the background which is cross-platform it uses QT or QT or whatever you want to call it for the GUI I believe which is cross-platform so definitely something it could be used in the future anyway I'm getting off now I'm tired did I say that already and the third option would be application design well we'll look a little bit at GUI's and basic forms because most applications you make are forms filling stuff out searching through data that sort of thing and making stuff like that super simple but there are things you need to think about and I'll just go over some of the things that I look for when I'm designing an application and mainly I try to make my programs my GUI interfaces it's obviously cross-platform which is super simple but but not just cross-platform but easy to use on all devices see some programs are really convenient for touch screens some are really convenient for keyboard but it's important to try to make your application good for both and that's usually my goal when I'm creating GUI interfaces and forms and stuff like that to make sure that there's that little touch that if you're using a desktop computer you can use it with just the keyboard and not have to touch the mouse or at least touch the mouse as little as possible but if you want to use the mouse or touch screen you should be able to do that with typing as little as possible so I try to make a good balance of that so I'll just go over some of those concepts with you guys if that's chosen so again choice one continue 2d game design choice to go or open source video editing choice three application design GUI interface design for basic forms and stuff that you'll use quite often when designing applications so if you're a patreon supporter you should have received a link and if you're watching this video on that link there should be voting below if you're not a patreon supporter think about becoming a patreon supporter over at patreon.com forward slash melex 1000 there should be a link in the description of the video and although it doesn't count as a vote feel free to comment below and let me know which of these topics is your favorite so that I know what people are stood in and if something gets voted up a lot in the comments but doesn't get picked by my patreon supporters I'll be sure to put it on the list for future voting so that's it hope you're all having a great summer it's extremely hot here in Florida how about where you're at have a great day


This is Google season of docs office hours the 28th of September 2020. Thanks for being here I'm going to share my screen and we can look at the proposed agenda Goal, so you should see Right now, I think the agenda is empty other than who we've got attending so draft Google Docs seems like a proper topic Are there other topics we should add to the agenda? Oh like I've asked about incremental Delivery of parts Segments in larger Structure both I do have a topic to add as well right at market and and this is the transfer of Org admin for Google Summer of Docs. I have an update for that. Oh Good, okay Excellent. Thanks. I don't hear any other topics. So Shall we go ahead I Think we should add It's off pick on the issue. I raised last at the last meeting My cue was not around so Yeah, oh the service account issues that is that this one's seen up. Yes Okay, good. So I'm sorry I mistakenly thought we had that resolved my mistake. Let's I would propose we put that one top of the list Because that was one we had agreed. We would we would cover today if it wasn't resolved by by today Yes Okay, good All right, so So then let's take this one as the first topic Z enough could you describe the problem you saw and you may need to share your screen if we get to that point? Yes, I can't show my screen. No, great. Let me stop sharing Okay, it says it started screen sharing not quite visible yet Okay There we go. Now I see it nice ID Visual studio code me Yes, I'm hope it's clear Clean off I can see it Okay, um, so this is where I'm having issues this part So the default value, this is my Jenkins value file. Yeah, I got this from Jenkins Helm charts repository on github so the default value that is there is 1,000 but when I Create this using 1000 and I run. I'm not able to the port keeps crashing. I'm not able to do anything on Jenkins It's I'm having some permissions issue and I'm not really sure how to Resolve that I can't exactly to the port because it's it's not starting So I'm not really sure how to resolve the issue with The permissions if I use if I run as user 1,000 But when I run as zero it works, but using zero means I'm running Jenkins as roots And I wouldn't want to do that So I just did this so I can just get Jenkins so I can continue with the documentation and this doesn't block me from Documenting other parts, but I would like to have this stage resolved So I'm guessing like Christy mentioned in the last miss meeting. I'm guessing I missed a step In the installation, but I'm not sure what that is So that's the problem Give me just a second. I am just taking a note Okay And this is the official Jenkins Helm chart. Yes So just so I'm clear you're saying when you run it as user 1,000 It does not work Yes Is the I didn't think to ask you on Fridays, you know is the FS group Also need to be 1,000. I'm not sure what Okay, so you make them both 1,000. Yes, both came both are 1,000 by default So I changed the both of them to zero Is there do you currently have an example of where the pod is crashing? Did you're able to show us that we could maybe debug live? I'll do screenshots and Unsent to you. Yeah, you can send it to me directly the reason The command that I'm looking for and I'm gonna put it in the chat for zoom here is Give me just a moment while I type it This is in the Jenkins namespace, correct? Yes, that's one. I am gonna need another one as well Can you scroll up on your Jenkins values? Yammer line one. Can you scroll down a little past the Basics the boring code I want to see the lines right after that and scroll down about 10 more lines Stop right there and you put the service account in that we discussed last week, correct? Yes Yes Can you show me that? Can you show me that Yammer? Okay, I don't see it yet. I still just see your open file window Can you scroll down keep going I just want to see the cluster roll binding scroll back up to the cluster Cluster roll.  Wow. Okay, that's really weird. I'm gonna have to look into that because this should By just my initial looks at it. They should actually work So let me let me look into that and I will get you an update Okay, I'll also do the screenshots on send to you to give more content. Yeah, that'll be great. Thank you very much Okay Do you can put that as an action item for me mark on the list if you'd like? Okay, here we go sharing my screen again. Okay, so so give me it was Rkey to attempt to duplicate the problem Is that what mark Markey? Markey to it debug Run as user 1000. I'll start looking into that once we're done with this call. Excellent. Thanks. Okay Anything else on that topic then? No, nothing else Okay, great. Thank you So then the draft Google doc for installing Jenkins on Kubernetes and Just a minute while I grab a copy of that link to that doc. There it is All right. So is enough. I think you've seen Kristen's feedback. Yeah, a couple of minor items I'm going to be reviewing that it's on my list to do this morning Okay And Markey yours is a credible review. Mine is the review of an amateur so much appreciate it I Started I started executing the steps bumped into something that I didn't quite understand what the failure mode was and have to do Some more exploring Yeah, I'll take a look at it. That's it's on my list Great. And did you have any specific topics you wanted to bring to us with regard to it? Do you know anything in detail where you say I'd like to talk about this or this? Sorry, I didn't get that Anything about the installing Jenkins on Kubernetes document that you would like to review with us specifically while we're on the call Not really The only discussion I would have lost to have is there's some comments Christine dropped about the structure of the documentation and I understood what she was saying but I also structured it this way with the location is going to be in Jenkins.io since there's already a heading installing Jenkins in Jenkins.io So this is just going to be like a section of that page Right, okay, so I think her concern is addressed by exactly what you said So that's very good because you're going to integrate it into this page for installing. Is that correct? Yes, exactly. So it's going to be under the installation part from Kubernetes Yeah, so just like we have a Docker section today We will have a we will have a Kubernetes section that is part of this broader document Yes, so under the Kubernetes session we're now going to have different options for installing Jenkins on Kubernetes So that makes sense. I'm going to just embed a copy of that into the link Good, very good. Okay, and I had one on this just capitalization because Linux users like me have a case sensitive set of commands Okay Good any other Questions or topic? No, none for now Oleg had raised a question about incremental delivery of segments into a larger structure. Is he now What are your thoughts on that? Do you see how it could work, etc? I don't really understand what this or this means. I think Oleg's intent was that there's a Framework or an outline form of the final document Okay, like Skeleton or something. Yes. Yes skeleton. That's a good. Yeah, that's a very good word for it then and and then Pieces are added in faster smaller steps Or more frequent smaller steps to the skeleton Yeah, okay So my question here will be that this skeleton are we going to Create it on Jenkins.io and push it there first and Start adding the content later on or it's just for us to use it as a guideline as the documentation goes forward I Then also the skeleton is it going to be in relation to what we have on Jenkins.io Or just the content we are adding to it. Yeah, good question So my my my thought was add the skeleton to Jenkins.io If you're uncomfortable with it being visible make it as content as comments commented sections as commented adoc So the famous four slashes creates it starts a block comment and Four slashes ends the block comment Oh Okay, so you could you could do it that way would be one alternative that would let you have a place to put things without Displaying empty headings to readers during the period while it's developing You could also we have plenty of places where we have empty headers as well Okay, I don't know if it's possible to get like an example so I can understand Yeah, good question. Let's see marky are there any places you can think of where we might already have an example that we could use to highlight this I Don't know of know of any off offhand myself, but we might be able to find some Yeah, I can't think of any We certainly got plenty we've got many places where the the content says This is a work in progress so Maybe that's what we should get as examples and say look here's here's how we've we've got this this section of material That is identified as a work in progress. Here's how it was done Okay Maybe let's while we're here. Maybe we can avoid that leaving the action of open You're okay if I just look really quickly for for a sample So if I recall correctly system administration was a pretty common place to have Yeah, so okay, so here's here's one example backing up and restoring Jenkins says right now that it's a work in progress but and monitoring Jenkins also says it's under development and and Secure yeah, good. So these these pages give us some indicator of Hey, there's they're part of a bigger section, but they say look this is under this is under development Okay, okay, okay So does that does that help you Zina? Yes sufficient? Okay? Okay, so as you guys this I think what I'll do is just Go through all the contents. We've agreed to work on for the documentation and see the sections in Jenkins I aware we can add them. I'll open a pull request so Everyone can review That sounds good to me That sounds very good So for Installing Jenkins on Kubernetes since I already have some content on that I'll just include that in the full question section is not empty Right, right. That sounds really good Anything else on the incremental delivery idea that any other clarification you'd like to request, you know No Okay Transfer of organization admin from Oleg to Markey Markey Yes, I talked with Oleg Yesterday or today, I can't remember which day it was and he it is on his list to do So hopefully he'll be doing that within the next day or so and Has to That's something he has to initiate certain.  Yeah He just has to list me as one and then we'll remove him as the third and then they'll just be Off got it. All right Any other topics? Okay, so I assume are one of our goals for the next session Thursday is We'll see a pull request ready for be based on the the install material that you've done. That's cool. Yeah Excellent, thanks very much Zina. Thank you Markey. Thank you. Thank you all have


So here are the topics that I'll cover in this webinar. We'll talk about the types of studies and data that are available, and the types of research questions that they can be used to answer. I'll also highlight some useful resources that will help you find out more about the data that are available and how you can access these data sets. And we'll also briefly look at how you can maximize the comparability of mental health data in order to conduct cross-study research. The UK has a long history of world-leading longitudinal research. Some of the world's longest-running longitudinal studies are hosted here in the UK. The studies shown here are just some of the fantastic resources that we have access to. And these studies have been driving research and influencing policy across many fields for generations. These longitudinal studies allow us to track changes over time, both within individuals and across different generations. And this can help us identify normal developmental trajectories and how development is shaped by risk factors that can be either fixed or time-varying. Given that longitudinal studies typically measure a wide range of variables from different domains, we can control for many extraneous variables. And in some circumstances, depending on the data that are available, make causal inferences about relationships between variables. So what types of studies are available to researchers who are interested in mental health? In this webinar, we'll deal with mainly longitudinal studies. First, household panel surveys. A household panel study is a type of longitudinal research in which a group of households are selected and followed over a period of time, typically several years or more. The purpose of a household panel study is to observe changes in the behaviours, attitudes and characteristics of the households and their members. In a household panel study, data are collected through repeated surveys of the same group of households, usually on an annual or bi-annual basis. The surveys typically cover a range of topics related to the households such as their economic status, demographic characteristics, health and wellbeing, and social and community engagement. The advantages of a household panel study include the ability to track changes in households and their members over time, the ability to examine relationships between variables at different levels such as individual, family, geographic region, and the potential for more in-depth analysis of specific subgroups of interest. Perhaps the best example of a household panel study in the UK is understanding society, which will be covered in depth by Mark in the next talk. So for the rest of this webinar, I will be focusing on several British birth cohort studies. A birth cohort study is a type of longitudinal research that follows a group of individuals born during a particular time period, usually within a single year or a few years. The individuals in the cohort are usually followed throughout their lives with data collected at various time points to investigate how different factors such as genetic, environmental, social and behavioural factors affect their health and wellbeing. Birth cohort studies can provide valuable information on the development of physical and mental health and on the impact of various exposures on health outcomes. They can also provide insights into the effectiveness of interventions such as public health programmes and policies. Many of the UK birth cohorts are nationally representative, therefore they have the further advantage of being generalisable to the UK population. Some of the most well-known and utilised birth cohorts in the UK include the National Survey of Health and Development, which began in 1946 and is the UK's longest running birth cohort study. The study follows a randomly selected sample of 5,362 people born in England, Wales and Scotland during a single week in March 1946. This was approximately one third of all babies born that week. These individuals have been followed up 25 times through a combination of paper questionnaires and visits by health visitors or nurses either in the home or in the clinic. The most recent assessment of this cohort occurred during the COVID-19 pandemic when participants were aged approximately 74 years. The 1958 National Child Development Study, or the NCDS, is following the lives of an initial 17,415 people born in England, Scotland and Wales in a single week of 1958. With 11 follow-ups, the study has collected information on their physical and educational development, economic circumstances, employment, family life, health behaviour, wellbeing, social participation and attitudes. Similarly, the 1970 British cohort study is following the lives of around 17,000 people born in England, Scotland and Wales in a single week of 1970. Next steps, previously known as the Longitudinal Study of Young People in England, follows the lives of around 16,000 people born in England between 1989 and 1990. Unlike the other studies, next steps did not commence at birth, rather it began in 2004 when the cohort members were aged 14. Next steps has particularly rich data on education, for example it can be linked to the National Pupil Database Records. And the Millennium Cohort Study, known as the Child of the New Century to cohort members and their families, is following the lives of around 19,000 young people born across England, Scotland, Wales and Northern Ireland between 2000 and 2002. Like all of the above studies, the most recent sweep of data occurred during the COVID pandemic to study how individuals coped during that unprecedented situation. What type of information are routinely collected and available in these studies? So obviously, most people here are interested in mental health data. This is something that is routinely collected throughout the life course in these studies for both the cohort members themselves, but also frequently for parents and other family members. Mental health problems are typically assessed using well-established screeners, usually self-report questionnaires in adults and parent and teacher proxy reports in children. In terms of other variables that may be related to mental health, these cohorts are designed to be used in many disciplines, therefore they capture a range of relevant information across many domains, such as demographic characteristics, socio-economic status, physical health, cognitive ability in education, and also social and community factors. Most of this information is freely available, however more sensitive data such as linked administrative records and genetic data can be obtained via secure access routes. In terms of how this data can be used and what research questions we can answer, the answer is, well, we can answer an endless amount of research questions really. If we narrow our focus on mental health, many studies look at time trends. For instance, how does mental health develop across the life course? Are there universal periods of high risk and is this consistent across different cohorts? Other studies may be interested in looking at how certain risk factors are associated with the development of mental health, either at different stages of the life course or across different cohorts. Really, the limits of the research questions we can answer are determined by what you are interested in and what data are available. However, when we want to explore the data that are out there, we are faced with two issues. First, we need to find out what studies are out there and have the necessary data to answer our research question. Second, once we've identified the studies that can do this, we need to find out what specific variables are available in these studies when they were measured and how they were operationalised. How do you go about sourcing this information? Each individual study has a website, often with detailed cohort profiles and technical manuals. However, rooting through these can be a time-consuming and imprecise process. Thankfully, a number of organisations and initiatives exist to help with data discoverability. In other words, making it easy for researchers to find out what studies are out there and what information is gathered in each study. One example is CLOSER, the UK's home for longitudinal research. This consortium provides a searchable engine discovery that allows you to browse the content of a large number of UK-based longitudinal studies. It includes a simple search function where you can enter the construct you are interested in and it will provide you with a list of variables. You can then filter these by things like study or a particular life stage. To find out more about the value of longitudinal studies, have a look at the CLOSER website. For those who are specifically interested in mental health data, I recommend using the catalogue of mental health measures, a tool that's been developed by Professor Louise Arsenault and her team at Kings College London. This tool covers over 50 longitudinal studies and it's easy to use interface, allows researchers to quickly get to grips with the mental health data that are available in each cohort. Once you have identified your relevant studies and variables, you will no doubt be keen to access this data. And while there's no one-stop shop for UK longitudinal data, at least not yet, many of the studies discussed today can be downloaded via the UK Data Service. This provides researchers, government analysts and charities access to high-quality resources free of charge. On the UK Data Service website, researchers can browse a range of metadata and download the data they need quickly and easily. Along with full sweeps from individual studies, a range of linked and harmonized datasets for cross-cohort comparisons are also available. It is worth noting, however, that not all data can be downloaded directly. Sensitive information such as linked administrative records, for instance, from health or education databases, these often require secure access and further information about this can be found on the UKDS website. For other studies, bespoke applications must be made to the host institutions. This usually involves submitting a research proposal with the main aim of avoiding overlap between separate projects and research groups. Also, depending on the cohort in question, a fee may be required to access the data. Increasingly, researchers look to combine data from multiple birth cohorts to study how certain phenomena are changing across different generations. When conducting cross-cohort studies of mental health, researchers are often confronted with measurement problems, mainly the fact that different questionnaires were used to assess mental health depending on when the assessments occurred. For instance, child mental health in the 1946 cohort was measured with a precursor to the router behavior scales, whereas in more recent cohorts, the strengths and difficulties questionnaire is the most common instrument used. Mental health screeners such as these often differ in a range of features from the content of specific questions to the number of response options. In order to help researchers make the most of existing data and currently leading a project which is funded by the Wellcome Trust, in which we're developing an online tool that uses machine learning, specifically natural language processing, to match and quantify the similarity of questions from different questionnaires based on their semantic content. This tool, Harmony, will allow researchers to identify subsets of questions from different instruments that can be used to make direct comparisons across studies. For more information on Harmony, visit our project, website or open science framework page.


That's a lot. Thank you for inviting me today. I'm going to talk about clouds in high energy physics. I thought I would first maybe make a definition or explain what high energy physics is. I'll leave the cloud definition to this group. I'd rather not put that one up. What we do as particle physicists or high energy physicists is study the fundamental particles of nature and their interactions. We use a variety of facilities. We use accelerators. The picture on the far left is the linear accelerator at Stanford University. I've been part of an experiment there for a number of years. The middle one is an underground laboratory in northern Ontario in Suburban. Suburban, it's 8,000 feet underground where we put detectors to look at particles from the sun. It's the Suburban neutrino observatory. I visited there. And then we have detectors in the space station, the alpha magnetic spectrometer. Some of this was in the news in the last week. I'm hoping to go there, but I'm not optimistic. With these facilities, we try to address a number of questions that are important for our understanding of the universe. The one that you may have heard most about, and I'll explain a little bit more as I go along, is the Higgs boson. We've discovered this particle among one of the atlas experiment at CERN. And we see evidence for the Higgs boson, which is supposed to give the source of mass to all the particles that we know about. It's been coined the God particle. That's not our name, but it's sort of stuck in the media that way. And I'll go over a bit of the detail of this. We're also asking other questions. I mean, maybe you saw angels and demons about how we can make anti-matter. We can make anti-matter, but one of the questions we're wondering is why the universe today is only made of matter and not matter and anti-matter. We expect that the Big Bang, and we're both created equally, but why don't we see a galaxy of anti-matter and a galaxy of matter, but we don't? We only see matter. So something has happened during the evolution of the universe so that we only see matter in the world. Any other, the last question I'll just highlight is our understanding of the universe is actually pretty limited. This pie chart shows that atoms or matter is 5% of the universe. Dark matter is 24% and dark energy is 71%. And dark just means we don't know what it is. We find this out from projects such as this WMAP satellite that measures the temperature of the universe. We can also measure it in astronomical data and other, but the bottom line is we don't understand what 95% of the universe is made of, which is kind of embarrassing. So we work, or at least I work in these projects. And so we have astronomers use telescopes in a sense of particle physics and these accelerators are basically big microscopes. So we've evolved from these simple instruments to more complex instruments. The astronomers have their telescopes in space. We have large detectors. This is the atlas detected that I'm involved in during its construction at CERN. Our collaborations are now massive. The atlas is 3,000 scientists. So these projects are decades long, large scale projects. I work at the Large Hadron Collider at CERN. This is in Geneva. I think it's the largest instrument in the planet. It's 27 kilometers in diameter, or circumference rather, and it's 100 meters underground. And so protons circulate in this ring one in one direction, one in the other, and we collide them in certain areas. It's basically a microscope and we're probing distances of the order of 10 to the minus 20 meters. By going back in small distances, we're going back in time and studying the Big Bang. So it's sort of analogous to what the astronomers do. They look deep into space and they go back in time. We look at small distances and go back in time. So since we're studying the same things in complementary ways. The Large Hadron Collider, as I say, is a tunnel. It's 27 kilometers. You need a transportation to get around. The blue beam pipe, the blue pipes contain the magnets and two beam pipes for the protons to circulate opposite each other. It's also at 1.8 degrees Kelvin, so I think it's the biggest refrigerator in the world. At certain points along the ring, we have these detectors. So this is the Atlas detector. There is another large detector called CMS, and then there are two other specialized detectors as well. You can see the scale with the people at the bottom. It's 44 meters across, 25 meters high. It's basically a camera. I forget how many megapixels. So this is the picture looking down the proton beam line in 2005 as the Atlas detector was being constructed. So in a sense, the center is hollow right now and they're sliding the pieces in. So it gives you the scale of the facility. So it's a fairly large facility and it took probably between five to 10 years to construct. Today we're recording data. We've just finished a period of data taking and we're now in an upgrade period of two years where there's no more beam for that time. So this is a picture of a proton-proton event. The protons are coming in and out of the page. The yellow lines are the charged particles. They bend one way or the other depending on their charge because there's a magnetic field and the color boxes around represent the energy of it. So we collect roughly 200 of these per second. I'll explain a little bit more as we go along. Actually, I'll do it now. So the protons are colliding every 25 nanoseconds. So we get 40 million per second. The Atlas detector then selects 100,000 per second and then we pass them to event filter computers to select 200 per second at two megabytes per event. So we're collecting 400 megabytes per second for roughly half the year. So this means we need a large computing system. What we've constructed over the last decade is called the WLCG computing grid, worldwide large Hadron Collider grid and it's based on a hierarchical model where there's a large center at CERN, a tier zero we call it. There are 10 tier ones distributed around the world. The data from the detector comes to the tier one and then gets distributed to the 10 tier ones in near real time, a few hours. And then there are 60 other what we call tier two sites that are also distributed around the world for creation of simulated data and analysis. At the moment we're of the order of 140 petabytes of data, we have a private routed network for most of these facilities all at 10 or 100 gig now. Now last year we found evidence for the Higgs, both Atlas and the CMS experiments, see evidence for Higgs like particle. The little circular picture is the same one where I'm sort of cutting the view along the direction of the proton and the other picture on the left is more of a three dimensional one. It's where the candidate particle goes to four electron like particles. It's either an electron or a muon. The muon is just a heavier version of an electron. If we, here's the only science plot you'll get. This is a frequency plot. So I'm plotting the mass of those four leptons as a function of its mass. So the number of candidates is in the vertical axis, the mass is on the bottom. And we see an excess of events at about 125 proton masses. The colored, the points are data and the other histograms or the colored plots are the predictions of our simulation. And we would get the red and the purple is based on no Higgs and the blue box is what we expect for the Higgs particle. So we see it in this channel, we see it in other channels and we see it in two experiments. So I think we're pretty confident that it is. And as a result, this made the mainstream media I think last summer. So it was all across the world in this way. Okay, so I'm gonna change directions just for the last part of my talk. How are we using clouds in high energy physics? One of our first uses was to help us preserve and archive high energy physics data so that we can continue to use it in the future. We're trying to use clouds to take advantage of special computing resources that I sort of also described that are attached to our detectors. A more common use is to help us simplify just the management of in-house resources. We've used commercial clouds to some extent for exceptional needs. And one of the projects that I'm interested in and some of my group and colleagues are working on is how can we use it if you want a grid of clouds where we can utilize both high energy physics, non-high energy physics resources to meet some of our computing needs. So I mentioned the Slack accelerator before. There was a detector experiment there called Babar. It studied B quarks, B and the B bar. So that's why it's Babar. And we got to use Babar as long as we don't change the color or change the shape of the elephant. You see an event picture. It's a lower energy accelerator. So you see simpler pictures of events. It's again along the direction of the beam line. And this experiment stopped taking data in 2008. The problem we face is once the experiment ends, the funding stops, but we still wanna analyze data. We still have graduate students looking at some of this data. We may wanna look at it in five years. But we have nobody maintaining the system. The software will not be maintained beyond a scientific Linux five, Red Hat five operating system. And so we need to maintain the software. The software will only run on an old operating system. And so we have to build a what we call a long-term data access system. So it's the first experiment that's done this. It did it a few years ago. It's basically a static cloud. They just build the, you know, SL5 VMs. It just has access to the software and the data. And it's transparent to the users. And it's been in operation for a while. As I mentioned with the Atlas trigger, we have these racks of processors that are used in real time to filter the data. But now we're down for two years. So we're converting these, what we call HLT farms, high-level trigger to clouds. So we don't need these 50,000 cores. They'd sit idle if we didn't use them. So they're being converted to OpenStack clouds. I think some of them are in operation today. And there's actually a talk today by Tony Perez at 11. So I encourage you to go see it. I won't say anymore. We're also using or converting our internal resources to clouds, either that they're transparent to the users or they appear as cloud resources. The Ibex cloud, Jan Mandeldijk and Tim Bell are in the audience. And you can find out more about them. But that's one example of how we're starting to convert our facilities into commercial, not commercial, but cloud-based platforms. We've also used commercial resources in, let's say, a limited way. We've Amazon, Google, Rackspace, others. There have been a number of reports by the Star Experiment at Brookhaven. There's the Bell Experiment in Japan and Atlas and others have used it. Typically, it's been used for exceptional demands where we don't have enough capacity to get enough data or process for a particular conference. We tend to use it for low IO demands, say, generating simulated data. We face challenges using it. Particle physicists use X509 certificates for identity management, so we have to figure out different ways to do it. Network connectivity, for example, if I wanna get to Amazon from Canada, I have to go over to commodity network, which is a pain. And the costs are a little bit higher than our private resources, so we're using it, but as I say, for exceptional resources, or exceptional needs. The area where I have a bit of interest in is trying to take advantage of our distributed computing infrastructure because particle physics is a global collaboration. Everyone has their resources and we would like to use them in some kind of seamless way. We have built a grid, it's working, but I think one of the ideas, maybe is to try and use it as a grid of clouds. It's also been coined as sky computing by Kate Keehe of Chicago. So what we're trying to do is use both dedicated and non-dedicated high energy physics resources. We wanna use them independent of the cloud type. We wanna remove any application dependence from the actual site, but also support multiple projects that I'll show you in a minute. I just wanna show you a very simple workflow for what we're doing, and then you can see how some of my requests, maybe for open stack development would be useful. So we have a system where a user submits a batch job to HT Condor. We have these clouds out there, but we have a customized service where we call cloud scheduler. So this cloud scheduler, the user submits a job, the cloud scheduler discovers the job, the cloud scheduler then boots a virtual machine on one of the clouds. That VM registers itself with Condor, and then the job gets dispatched to that VM. So that's how we're running a cloud of I think 10 or 12 distributed clouds right now. We use a combination of Nimbus clouds, open stack clouds, and some commercial cloud. The VM for some of them are pulled in from a remote repository. The data is also remote as well. For open stack clouds, we upload it. So we're using it for Atlas in production. We're also using it in the Canadian astronomical community. They use it for user analysis. We have a variety of clouds. We've had ties with the Nimbus group for a number of years, but that's proved to be a fruitful collaboration. So we have clouds that we have used in Victoria, Ottawa, excuse me, and Future Grid in Chicago, Future Grid in San Diego, we also in Florida. In terms of open stack, we've used Melbourne Nectar clouds, a certain Ibex cloud. There's two Canary clouds that we brought online, last week, and we're starting to talk with the Oxford people. So we've been in operation for about a year and a half. Astronomy has run maybe 500,000. We're over 300,000 jobs now using 10 clouds. Yesterday, we're running 1,000 simultaneous jobs. I mean, it's not large, but it's, we're just starting to get going now. And their jobs are roughly 12 hours, and they run, and they're all submitted, at least the Atlas jobs are submitted from CERN. We can, in principle, use Amazon and Google as well. So this just shows this week, these are just the number of each, that's the number of virtual machines that we boot up as a function of the day of the week. Each color is a different cloud. Some clouds go up and down, depending on their internal needs, but generally we're running about 100 to 150 whole node VMs, so as the order of 1,000 jobs. And then, as I say, we've run at least nine clouds there and over three continents. So it seems to work reasonably well, and we're hoping to scale it up further. So as a, I guess I'm a particle physicist that's interested in computing. At least I see myself and my team as integrators rather than developers of cloud technology. And what we would like to see that would help our life is the following, at least these key things, is common authentication. Maybe a centralized VM image store that we could download from, rather than having to upload to every cloud. Maybe consistent metadata and don't use Nova as your cloud name. So there's some things you could help simplify us, simplify our lives for us. Okay, so I'm reaching the end, so I just want to summarize the goal of high energy physics is to understand the universe. We believe we've discovered the Higgs. The next step in the LHC is to search for the particle that's the source of dark matter. Maybe we'll understand the difference between matter and antimatter with our studies. We do have an impact on society. It's always useful to remind you that the World Wide Web was developed by particle physicists at CERN. The first two sites were CERN and Slack. They're now more accelerators in hospitals for imaging and cancer treatment. Building these large instruments generates technology development. I mean, just look at the cryogenics involved with the LHC and we're training highly qualified people. In terms of computing, we've had large distributed systems. Initially grid, now we're looking more towards cloud. We have a very big global network that consumes a lot of the bandwidth. We're trying to use the novel computing technologies that this community is developing for. So that's all I have to say. Clouds are a collaborative endeavor and many people have helped us in our work and I need to acknowledge them. If you want to contact me, this is my email. I'm around for today and that's our website. Thank you. Thank you.


It's time, baby. Are we doing prox chat? Yes. Oh.   Never mind. I gotta go. I gotta leave. Hello. Wait, why did you say you have to leave? Is it because I'm here? I need them.  People are gonna think that, like, we have beef now, Mika. You can't do that. People are gonna think that behind the scenes, we got into, like, some big fight, and now we can't talk anymore. Why is this every along us map with us? It's been, it's never me.  Mika's being all weird and like, I get in and she's like, oh, I have to leave. And then I'm, I'm all like, hey, we can't make, we can't make these jokes. Big internet is watching Mika. Okay, wait, what are we doing? I'm so excited.  You can choose where you start. This is crazy. I don't know this, but don't kill me. So big.  Please don't kill me. RIP to a legend. Me, the legend. Oh, no. Wait, who got you? Yeah, I mean, we can just skip this one. That's right. Yeah, that's fine. It's eating stuff. Yo, what's up with Mika?    I'm so nice to you all the time.  I deleted it.   Oh, Hank stay.    I did too. Yeah. I saw it. I saw it. I've missed among us. All right. Time to figure out and do me tasks. Let's do some tasks in it. All right. Let's do a little bit of talk. See you all wrong. Hello. Hello. Hello. Hi. And how do you? I wish I could kill you really badly. How do you? I don't know where I'm at. Can you go up the thing? Oh, yeah, I got Q chance. We got.  All right. All right. Two in the shed.  Well, did you start coming? Beautiful, beautiful. What are you doing? I was getting phone signal so I could check my messages. So you can check them out. Did you respond to my? Did you see my message that I sent to you? Well, that's me. Well, maybe you should be on red. Do you start? Wait. Hi. How are you? We haven't gained much. Before we get started really quick, I want to say that I was unsecured.  All right. Well, let's all just give it to Ashley now while we can. Okay. Wow. Excuse me. I saw you murder Hankster in cold blood. Wait, is this a Christmas special? What? This self-sacrifice. Oh, Brian, it's just been, it's just been such a long time since I've played among us and I haven't thought about the Christmas special in a while. Rent free. What do you want to do? We have five dead. I saw Ashley kill Sammy in the bathroom. No, what are you fucking? Also, every time I asked Ashley if she was the killer, she literally didn't answer me. I did. What are you talking about? Okay. That is kind of true. I got so close to killing that. I got so close to killing that. And then I went out on the phone deck. I just like missed click barely. Can you explain what happened to Sammy? Because she's dead. Sammy is Hankster, by the way. I don't know. I left her in the bathroom. No, you didn't. You left her outside the stall in half. Oh my God. No, we were plunging the toilet together and I left. You were plunging your body. She's dead. She's dead. Down the toilet. She's gone. Y'all go plunge together. Stay together, baby. Brian, what did you do? I'm only hearing one person pointing the finger with eyewitness testimony. I trust Chris here. Thank you, Brian. Okay.  I didn't.  You didn't trust Chris. This is so sad. I love the music. That was so funny. That was so funny.  What are the chances you think that it's a Chris Mal special? I don't like this. It's pretty high because he's good at the game and I'm not, so I'm easily swayed. Okay. Oh my God. Baby. You just got to scream, you know? Yeah, sometimes you just, oh. Yeah, sometimes you just got to scream. What if I get imposter like 12 rounds in a row again? Remember when that happened? That sucked. I say hi. Hi. I'm sorry. Hi.   Oh Jesus, I thought Miko killed me. Jesus. My dad's trust fund is in here. Do you start coming in? I don't stop coming. Ooh. This is security, isn't it? Oh, and it only goes into the corner? That's so not. I wish I didn't do that. Y'all cooking up some grub? Excellent. Excellent. Excellent. I love it. Dad, is that you? Excellent. Does he? Does he like his burgers like medium well or something? No. This is the fixed lights, though. Wait, who? Wait, where was this? Who are you? Ethan, where did you find this body? In nap? Question mark? Okay, there was also a report button in kitchen. So whoever, someone died in the kitchen. I have some information because I saw Ethan with Miko. Wait, wait, wait, wait, wait. When did two of them? I was in there and then I left Ethan with Miko. Ethan, I'm so sorry. I don't want to point fingers, but I have information from once in my life and I just want to share it. Fine, point your fingers. Ethan is going to do that right now. I'm assuming it's Ethan. Ethan, do you have anything to say for yourself? Ethan was right with Miko. Yeah, I was in the kitchen with Miko and then I left the kitchen. And that's the information that I have. Okay, so Miko's body's in the kitchen. Solid, solid. Listen, Daytune and I were in the kitchen and then I passed Kat when I left. So the body was in kitchen? No, Ethan found a body. I found a body in Nav. I was just with Ethan and Miko and Miko was alive when I saw them. So I left kitchen. My volume just went. I was in the kitchen with Miko and then I left the kitchen and went up to Nav. And that's the information that I have. Miko went off bottom right. No, Daytune, I left. And I passed Kat as I left. I went through the armor. Oh, there. Definitely Sammy. Vote Sammy. Vote Sammy. Crispy, it's literally you. Sammy, what killed Chris? 100%. Oh, I know it. I know it near the bottom. And Crispy goes. Oh, 100%. Definitely Sammy. You will not. I get it. I get it. Seriously, vote Crispy out on that. I want to go out the ladder. I like the ladder. This is calling. Fuck. Oh, no. What happened? Okay, so we were right. I was going past Ethan and I found a dead body. I found Crispy and it's Ethan. It's Ethan. Oh, Ethan. Oh, where did you find Crispy? I found Crispy because there is because there is a vent in that room. Was his body on top of the vent? Honestly, I just saw the cheeks and I saw you running and I said, No, no, no. Shoot my shot. I didn't see anything, but I do know. I would have lost. Well, hold on a second. No, no, no. Go ahead. Try to change our votes. We haven't voted. Because there is a vent bottom of that room where you say his body was. So was his body on top of the vent? I changed my vote to cat. I panicked. No, it wasn't me. I have no idea if there's a vent there.  Damn it. I'm using my cell phone out here. This is crazy. Ow! Want to get some Wi-Fi over here? Yeah. I was just really afraid of you. Crispy, Crispy, stop chasing me. Stop chasing me. Why are you so fast? Get away.  Chris has spent such a long time since we've played Among Us. I have to go make a burger in the kitchen. Do you have that one or no? No, I don't. I have electrical. Ethan's ignoring me. No. Can you not hear me? Hello? No. Chris, I'm going to have a beer real quick. I'll be knocking. Have fun peeing. Have a great pee. Yeah. I'm also going to go pee. Be very safe. I'll be right back. I will be very safe. I'm back. Well, maybe I'm going to go pee now, too. No, no, no. You know what? No, I'm going to go pee. Okay. Oh, we're playing. Fuck. I am, buddy. I thought we were all going pee. Is that not what was happening? Were we not going pee? I thought we were going pee. I didn't even take that long to pee. I feel bad for the people that took a long time to pee for a second. You know, I got to make a burger. Okay. Wait, I already forgot. Wait, is that tomato? No. Onion. Wait. Jesus Christ. There we go. How's it going? Did we all, did we all go? I thought we were all going pee and then I came back and we were playing. Yeah. Brian and I spawned together and we came back and we were like, wait, we were peeing, though. Yeah. Why are we in a game? Oh my God. You're also going to keep this. So who started it? Who started it? I don't know. I don't know. I don't know. I don't know. Who started the game without letting us pee? Yeah, I was pee. Yeah, who's running the house? Chris, Chris. Hey, Chris. Chris, is this my turn to pee?  Yeah, they were pissing our pants. Maybe that's the other one.   I want to go in the thing. It does make a fart noise. Big pencil. I can't trust big pencil, guys.   I'm downloading Big Titty Goth girl porn. What's going over there? I was just downloading some. That was quick though. Oh my God, you got the same file as me. Yes, cat. Oh, wait. Don't Ethan. What? I have a cell phone. Chris, don't kill me, please. I have a phone. I have a phone to catch. Chris. I have a phone to catch. I'm not doing it. I'm not going to do anything. I have a phone. I trust you. Never a second. Ahhhh. Help! help! All right, butter dog dog with the butter. This is where we go to the tip tip tip tip tip tip tip top of the map. Tip tip tip tip tip tip tip tip. Top of the map. Tip top of the map tip top of the map. Let's go. Baby.  I just have mustard. Okay I don't know you can hear me. No, I can hear you. Sorry. I was looking at numbers. I'm not done with my task What about you guys? I've just got cockpit communications and viewing deck now. Okay, Krispy. How about you? Oh Listen guys, we gotta finish up this round cuz I gotta go to the bathroom Listen guys, I gotta go I gotta go Krispy.   All right. He knew you're gonna go to the bathroom He knew well, what is this taking a shower? I'm dirty.   Oh, I wanted to be squeaky No, I saw Chris vent I saw Chris vent chasing me Ethan was chasing me. He wasn't No, Chris vented Chris vented Ethan was chasing me Chris vented. Please believe me. Please believe my screams of terror No, it's Chris Listen to my screams of terror Chris was chasing me up to the button because I saw him vent.  I was tying my shoe. I swear on Spencer's life that I saw Chris vent. Oh My god That's Bro, what if your game was glitching that's fucked up My father took me into the city He said I Sometimes I get the feeling and she's watching over me Good, I just think it about my chemical romance I found this body at the top of the ladder that leads down to electrical The only two people I saw coming from that direction were actually in Chris But I can't confirm how recent the kill was I left Will in showers where percussive maintenance is a thing and then I took off and I'm currently making a burger And it is onion lettuce. No lettuce onion onion and I put onion lettuce lettuce because I got a bad words onion Brian I saw will in I think electrical and then I went up I went up there and I passed you and there was no one around me when I went when I passed you and then I Was once with my task. Yeah, the last time I saw Greg He was in the showers with Ashley and then I peaced out. This could be like a fresh kill I don't know man. Well, I just came from cockpit. Oh Yeah, is that the one where's the one where the big circle?  Hey, your boy's kind of growing up here. I remember we he couldn't even walk I know right. It's nice to see.   Yeah.  Mm-hmm I don't know I believe it right before right before Sammy died Mika goes don't tell anyone Okay, but hold on let everybody give their let everybody give their sides Okay, Mika. Did you kill and say don't tell anybody because that is something that you would absolutely do I don't like the silence All right, I'm voting just Voted I promise it's Chris. Okay, but the hesitation there was rough Hesitation is because I my captions were off and I hit my mute button And whoa 100 gifted dope, thank you so much And then the lights went out I fixed lights all of the levers were off I flipped them all on I was with Sammy at that time. She walked over to the panel I finished lights and then she went out to the kitchen I followed behind her and Chris kills and I see Chris right next to the body. He doubles back.  I cannot do the door Brian. I cannot do my god. I'm too powerful dude I am too powerful. Thank you. I got the vaccine. So like my arm got the vaccine baby. That's why A little bit of I got a little bit of this Guys that was that was a hundred percent Chris on that one


Hello everyone, this is Amit Dan of amitdan.com. Today I'll have another episode of travel luggage review video and I'll be reviewing the original penguin crimson 21 inch hardshell carry-on spinner. If this is your first time or a repeat visit on this hybrid channel, I'm always trying new and different ideas to take you beyond boundaries. If you're into thinking outside the box, this is a channel for you. If you're looking for more travel review videos, there'll be links in the description box below. So let's go over quickly some of the features this carry-on spinner has. So this is honeycomb pap hardshell and it is expandable. There are eight wheels and 360 degree maneuverability and then we have interior mesh pocket and then the size is 21 by 18 sorry by 14 by 9.5 inch and weight is five pound. So this is a carry-on friendly but you can use also as a you know luggage. So let's take a look at outside first. So we have here the hardshell and then you can see that you know this is flexible or expandable which is right here. So you can if you have too much you know stuff you can just open one layer of zipper and then this is going to be expandable and then you have here eight wheel so two each. So this gives you like you know a very flexibility when you want to maneuver or when you are like you know going through the airport. It is very easy to move. Then we have a handle right here right here which is very nicely patterned and this is a very good handle and then we have another handle right here and also this is a very nice padding right here and then looks like they gave a address tag which is right here and then this is the luggage tag so hard case spinner collection and this is made by Penguin. I never had their luggage before and so we have some more information here so this is a carry-on friendly and then you know 25 percent more expandable than the regular size and you have eight wheel spinner and then this is honeycomb designing and then we have the branded logo right here but it's not that much like you know Shui so I kind of like that it's kind of like you know hidden or not that much you know sticking out. So I'm just going to start opening the box in terms of outside it looks fairly you know good looking and looks like it's going to hold up so let's start opening and see how it looks inside so I'm going to start from here okay so once you open the luggage you can see the difference so what is that it has organizational compartment inside which I don't find it in many luggage so there's like you know mesh pocket here and then you can put in like a small items and there's a compression you know strap to keep things together and then here I see that there is a zipper but it doesn't have a zipper handle so when I try to open it it just looks like they're covering the you know hardware just by putting it so I don't think this has any other uses that's why they didn't bother to put in even a zipper handle and then here we have more organizational compartment so you can put the stuff in here and you can just like you know close the zipper this way and then here you can see that more organizational compartment and then here there's another layer of the zipper compartment and you can put some more stuff in here so that's very you know good designing it has lots of you know organizational compartments and you don't have to like you know look for where to keep what because of the way it's divided and this mesh this strap compression strap would be very handy to keep things things tied together so the weight is actually this is very lightweight only five pound given the fact that you know this has lots of features and also there's another feature which is let me just you know close the zipper first then it looks like the zippers have very good you know they're easy to pull and the other thing I found out that looks like they're not yk a zipper there's no even branding on zipper so it looks like these are penguins on zipper but by the way it looks looks like they're going to be holding up and another good thing is that you know it has locking feature so you just like you know pull them together and you can use a cable lock to lock it so I like that feature and then here there's another easy pull this is you know you can use to expand so you can see that you know if you're opening that layer of zipper this is going to expand and let me just close this here so another feature it has here that there's the handle and handle actually it can stretch quite a bit as you can see and there's a kind of like you know button so when I press the button you can see that this is going inside and then it's easier to place it and then you can even like you know adjust the length based on what you're looking for the button I don't kind of I don't like it it looks like not too strong you can see that this is kind of like you know not firm it's moving a little bit so I'm not sure how long the button is going to hold but it might you know hold longer but that's something they need to improve so the system or the handle with button doesn't feel like that durable that's something to look for and except that everything else I'm happy with the product and you know except the button or the handle thing except the handle I have nothing else to complain about everything else looks nice and sturdy and I'm going to be using actually as a luggage not a carry-on on my next Asia trip which is coming up within a month and I'll find out more at that point when you know I actually travel with this but by the looks and everything I'm not I'm happy with the product except I'm not happy with the way the handle designed as just doesn't feel too sturdy and firm so this is not a paid or affiliated review all my reviews are non-affiliated unbiased and honest so that way you get that totally honest opinion so that was the review of the penguin crimson 21 inch harshal carry-on luggage for the next review there's going to be a link on the screen so I'll see you in the next video thank you


The hankerful art and beauty was inborn with Rabindranaths, the house of Tagore's, at Jorashako, Ashadindra Renaissance, the cultural rebirth of India. A lively imagination, a natural dexterity, a fine-flowing hand for calligraphy and a sudden discovery of a hidden talent for self-expression through lines and colours. The reasons which explained the emergence of Rabindranath Tagore as a creative experiment of the modern Indian art.


Good afternoon pastor David. Hey John welcome everybody to unfiltered a random moment with pastor pastor on Sunday You mentioned that you'll be teaching in Ephesians chapter 5 this week and You mentioned something interesting that I want to tease out today, and then on Thursday spend a little bit more time on it The scripture that you're using it says and do not be drunk with wine, which is dissipation, but be filled with the spirit So my question would be Can Christians drink, you know Christians can do a lot of things, you know Drinking is one that some Christians have a liberty to do. They believe that they can and And so they participate in in drinking alcoholic beverages and You know as I've told my fellowship before where I to walk into a restaurant and Where they to be there eating their lunch drinking a beer or sipping on a glass of wine. I've said to them Don't ever feel that I'm going to condemn you because I won't scripture forbids the the drunkenness the drinking to excess and the the dissipation or lack of self-control that is often the result of Overdrinking so there are those who will argue that because scripture does not forbid drinking That it's permissible. There are others who will say that you're not taking into consideration A variety of things that pertain to others and how you affect them Let alone what you may be doing in an unself-conscious way to yourself and So that's where the the crux of the argument seems to be But scripture doesn't say that I cannot do that scripture doesn't say that I can't have an occasional beer or whatever and so I excuse me, I have I Have never wanted to make a case for a total abstinence in the sense that That you should never have a beverage I do know scripture says that you should not drink in excess and lose self-control But I I I follow a greater a greater I don't know what the word would be maybe My philosophy Related to drinking it has a different kind of Approach and that is that I understand that in Christ. I have liberty and I also know that There are Christians who are legalistic So what I'm wanting to find is the balance between legalism and Access usage of my liberties, you know, there's on the one hand the straining of Nats the other would be the swallowing of camels and so instead of the liberty and instead of the the Legalism I like to say love so Out of love for other people I will voluntarily restrict what I might sense a freedom that I actually have I will restrict that Because I don't want to be a stumbling block To to a believer if somebody walked in from my fellowship walked into a restaurant that Marie and I were We're eating lunch at and they walked in and saw me with a beer or glass of wine I guarantee you it would stumble my people guarantee Because they expect their their leader the pastoral leader of the church to set an example and to take into consideration the the weaknesses of some of the saints and Not that not that having a Hatred for drunkenness is a weakness. It's actually a strength But sometimes the younger believers and all They can be stumbled at what somebody perceives as their their liberty their freedom And I don't use my my liberty to cause people to stumble now personally. I don't drink I haven't had a sip of alcohol in 40 some years So I don't I don't I don't even remember the taste of it. It's been that long John And on my case I was not a sipping saint ever But I certainly was a drunk prior to come to Christ I I drank and drank to excess and so I have a built-in rejection of that because I know That that is not the place I'm supposed to be that's not what I'm supposed to do And so in in our study tomorrow I'm gonna be sharing some things related to to drinking and perceived freedom And repercussions and what is it that should really rule my heart as it pertains to those things and What ought to rule my heart is the desire not to stumble a brother or a sister Love will always triumph over my perceived liberties. Do I believe that Christians should drink? I personally do not think that they should I personally feel that it's a trap I personally feel that it will Limit any ministry that you're ever going to be able to accomplish. I know it does I have no doubt in my mind that it does especially here in the United States and So I I will share scripture. I will share the variety of things that pertain to such a subject tomorrow and The answer to all of that is rather than drinking which causes a lack of self-control Paul says be filled with the spirit and the fruit of the spirit is self-control. So rather than yielding to my flesh and Coming under the influence of Alcohol I'm supposed to die to my flesh and come under the influence of the Holy Spirit So when people want to argue with me about their freedoms is usually a freedom to indulge their flesh That's what it usually is. It's not a philosophic. It very often is not a theologic It is a it's a personal belief that I like alcohol more than I like to walk in the spirit of God and That may be reducing it to absurdity But in the end that's pretty much what it is if I am willing to argue and fight for my alcohol But I'm real kind of what's the word? On the fence when it comes to things of walking in the spirit Then I'm exposing my own carnality to the world because I'm an alcohol evangelist Rather than an evangelist of the gospel, but anyway tomorrow night We'll be talking about it and want to invite you guys to come out and join us at Wednesday tomorrow evening at 7 p.m And I'm looking forward to this because so many people as you have heard Well Jesus drank and so they use all kinds of things but come tomorrow night and pastor They will be teaching on this and so I look forward to it pastor And I want to thank you guys for joining us and tuning in and so we look forward to seeing you on Wednesday just a reminder men in a couple days after Wednesday is our men's conference So I want to make sure there's conference tickets still available the day of conference tickets that will be sold up until the conference You can come join us for that. So pastor. Thank you so much for your time God bless you guys and we'll see you tomorrow


Look, nobody wants to be in this situation. You got behind the wheel of your car, maybe you had a few drinks earlier in the night. I'm not saying you're intoxicated. I'm not even saying you broke the law, because there is a legal limit of .08, and if you're underneath that legal limit, you might be entitled to drive your car safely. But the cop stops you. The cop has suspicions. Maybe there is alcohol in your breath. So what does the cop do? They want to have you perform maneuvers. They want to check you out.  I'm here to tell you you do not have to do those tests. Those are called field sobriety tests or field sobriety exercises. And when the cops ask you to do those, they're asking you to agree to a voluntary test. I'm here to tell you that once they've done that, they already have a basis to believe you're intoxicated, regardless of whether you are or not. And when they're asking you to do those tests, they're just looking for additional evidence. My suggestion? Don't do those tests, because you don't have to do those tests. Allow your lawyers to deal with the case after the fact. Don't give the cops additional evidence. Most people can't walk a straight line without stumbling a little bit. The cops are going to assume it's because you're intoxicated. Don't give them that opportunity to get that on video. Let's use your lawyers instead. Carlson Meisner, Hardin Hazlet, protecting your rights since 1971.


What's up everybody? Jason here for jazzy's case brace.com This is our last filler guys This is give away the last five spots in the mystery crate with this 2016 optic football hangar one box break random teams number 40 And again guys first we do the break randomize cuz we're names teams distribute the hits out Then at the end we're gonna randomize the cuz we're names that bought in and Top five get spots in the mystery crate, which will be coming up next So here we go guys good luck roll it. Let's do the break first Uh 500 three eight times one two three four five six seven and Eight the final time Daria down to Steve one two three four five six seven eight Jaguars down to the chiefs All right guys, so stick to what you got of course All right, let's get this hangar going really quick Slorox wipes you not here no more no You can use lysol spray under the cash register and just use a DeMarcus Robinson Cody Kessler And a little Dak Prescott. I'll show some refractor rookie All right, it's a little Dak there at least for the cowboys.


The Kremlin has confirmed the withdrawal of the Russian peacekeeping contingent from the Garabag region of Azerbaijan, note that since yesterday, the process of withdrawal of the temporary station Russian peacekeeping contingent in Garabag has begun, the first team and military equipment belonging to the peacekeeping contingent have left the territory of the Albanian temple in the Kalbajar region. The peacekeeping contingent completely vacated the temple area several days ago, currently, the Azerbaijani police are guarding the Albanian temple, thus, the process of the withdrawal of the Russian peacekeeping contingent from Azerbaijani territory has begun the Russian president's spokesperson, Dmitry Peskov, confirmed that the withdrawal of the Russian peacekeeping contingent from the Karabag region of Azerbaijan has begun. While answering the questions of the Russian media, yes, it is like that, Peskov stressed. Earlier, dozens of peacekeepers' observation posts in the Karabag region were closed after Azerbaijani military reclaimed control over the entire region following the counter-terrorist measures in September. It should be noted that the Russian peacekeeping contingent was temporarily stationed in Garabag on November 10, 2020, following a trilateral statement signed by the leaders of Azerbaijan, Russia and Armenia.